Re: routing table

2003-06-09 Thread antonio
Robert wrote: Well, I can say for sure the 169.x.x.x address is from an unaddressed interface.. when you fired up the box at one point, it could not get an address... or you ahve a second NIC that is set DHCP and it could not get an address.. the 169.254 entry is for DHCP Unassigned

Re: routing table

2003-06-09 Thread antonio
antonio wrote: An additional clue: in my office network that is very similar to my home network of my previous message output of netstat .nr is: Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.100.1 0.0.0.0

RE: routing table

2003-06-09 Thread Nick White
/network-scripts/ifcfg-* files: NOZEROCONF='yes' For more info on zeroconf, see http://www.zeroconf.org/ Hope this helps, Nick -Original Message- From: antonio [mailto:[EMAIL PROTECTED] Sent: Monday, June 09, 2003 10:01 AM To: [EMAIL PROTECTED] Subject: Re: routing table antonio wrote

Re: routing table

2003-06-09 Thread antonio
to /etc/sysconfig/network-scripts/ifcfg-* files: NOZEROCONF='yes' For more info on zeroconf, see http://www.zeroconf.org/ Hope this helps, Nick -Original Message- From: antonio [mailto:[EMAIL PROTECTED] Sent: Monday, June 09, 2003 10:01 AM To: [EMAIL PROTECTED] Subject: Re: routing table

Re: routing table

2003-06-09 Thread Roger
Around Mon,Jun 09 2003, at 10:06, Nick White, wrote: In RedHat 9 the 169.254.0.0/16 gets added to the routing table on boot. Probably to play nicely with windows boxen. In Windows 2000+, if there is no DHCP server available, an APIPA address (169.254.x.x) is assigned. Not just windows uses

Re: routing table

2003-06-09 Thread MKlinke
On Monday 09 June 2003 18:28, Roger wrote: Around Mon,Jun 09 2003, at 10:06, Nick White, wrote: In RedHat 9 the 169.254.0.0/16 gets added to the routing table on boot. Probably to play nicely with windows boxen. In Windows 2000+, if there is no DHCP server available, an APIPA address

RE: routing table

2003-06-09 Thread Nick White
10:24 AM To: [EMAIL PROTECTED] Subject: Re: routing table Nick White wrote: In RedHat 9 the 169.254.0.0/16 gets added to the routing table on boot. Probably to play nicely with windows boxen. In Windows 2000+, if there is no DHCP server available, an APIPA address (169.254.x.x) is assigned

Re: routing table

2003-06-09 Thread Roger
Around Mon,Jun 09 2003, at 07:59, MKlinke, wrote: On Monday 09 June 2003 18:28, Roger wrote: Around Mon,Jun 09 2003, at 10:06, Nick White, wrote: In RedHat 9 the 169.254.0.0/16 gets added to the routing table on boot. Probably to play nicely with windows boxen. In Windows 2000+, if

re: routing table

2003-06-09 Thread Felipe Leon
In RedHat 9 the 169.254.0.0/16 gets added to the routing table on boot. Probably to play nicely with windows boxen. In Windows 2000+, if there is no DHCP server available, an APIPA address (169.254.x.x) is assigned. Yep. RedHat 9 introduces zeroconf, which you need to disable if you don't

Re: routing table

2003-06-08 Thread Robert
Well, I can say for sure the 169.x.x.x address is from an unaddressed interface.. when you fired up the box at one point, it could not get an address... or you ahve a second NIC that is set DHCP and it could not get an address.. the 169.254 entry is for DHCP Unassigned addresses.

Re: routing table messed up by ppp

2000-10-07 Thread Glen Lee Edwards
Here's my routing table before ppp is initiated: $ netstat -rn Kernel IP routing table Destination GatewayGenmask Flags MSS Window irtt Iface 192.168.1.100 0.0.0.0255.255.255.255 UH0 00 eth0 192.168.1.0 0.0.0.0255.255.255.0 U 0 00