Default route keeps disappearing...

Question

Level 1

0 points

Default route keeps disappearing...

My default route keeps disappearing on me randomly when I'm connected to my network via ethernet. The airport is not turned on. I'm happily working away and then all of a sudden my network connection is dead. When I do a "netstat -r" I get the following:

Internet:
Destination Gateway Flags Refs Use Netif Expire
default link#4 UCSc 5 0 en0
127 localhost UCS 0 0 lo0
localhost localhost UH 2 421015 lo0
169.254 link#4 UCS 1 0 en0
Carlsberg.local localhost UHS 0 0 lo0
169.254.255.255 ff:ff:ff:ff:ff:ff UHLWb 0 1 en0
172.16.99/24 link#8 UC 1 0 vmnet1
172.16.99.255 ff:ff:ff:ff:ff:ff UHLWb 0 5 vmnet1
172.16.248/24 link#7 UC 2 0 vmnet8
172.16.248.255 ff:ff:ff:ff:ff:ff UHLWb 1 7 vmnet8

My local network is 192.168.139.0/24 and my gateway is 192.168.139.1. It has totally disappeared! So far, all I can do to get it working again is rebooting. Any ideas?

Macbook Pro 15", Mac OS X (10.5.2)

Posted on Feb 29, 2008 9:24 AM

Reply

Answer 1

teamchachi Author

Level 1

0 points

Feb 29, 2008 9:53 AM in response to teamchachi

Here's what it looks like after a reboot:

Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.139.1 UGSc 9 2 en0
127 127.0.0.1 UCS 0 0 lo0
127.0.0.1 127.0.0.1 UH 0 0 lo0
169.254 link#4 UCS 0 0 en0
172.16.99/24 link#8 UC 1 0 vmnet1
172.16.99.255 ff:ff:ff:ff:ff:ff UHLWb 0 12 vmnet1
172.16.248/24 link#7 UC 1 0 vmnet8
172.16.248.255 ff:ff:ff:ff:ff:ff UHLWb 1 12 vmnet8
192.168.139 link#4 UCS 4 0 en0
192.168.139.1 0:48:54:80:f7:2c UHLW 9 33 en0 1181
192.168.139.11 0:50:da:6a:99:13 UHLW 2 104 en0 1114
192.168.139.129 0:1a:e9:96:2d:33 UHLW 0 0 en0 1156
192.168.139.200 127.0.0.1 UHS 0 0 lo0
192.168.139.255 ff:ff:ff:ff:ff:ff UHLWb 0 17 en0

Reply

Answer 2

Camelot

Level 9

58,575 points

Feb 29, 2008 9:57 AM in response to teamchachi

My local network is 192.168.139.0/24 and my gateway is 192.168.139.1

Not according to that netstat output.

Nowhere does 192.168.139 appear anywhere in the list. In fact, that's telling me that 169.254.x.x is the subnet attached to your ethernet port.

That typically happens because your machine didn't get a response from the DHCP server. This could be due to a flaky DHCP server (e.g. its unreliable, slow, or otherwise not responding), or because your DHCP server has run out of addresses to issue to clients.
It could also be caused by poor cabling between you and the DHCP server.

Either way it sounds like your DHCP lease isn't getting renewed, and that's where I'd focus.

Reply