| Author |
Re: Wierd routing table entry in Redhat 9.0
|
|
| Gary Smith 2004-01-23, 7:14 pm |
| James,
I have a bunch of new RH9.0 boxes and I am seeing the same thing but
not on all of them. I reboot and it just comes up on some and not
others.
What is weird is that I have some VPN routing occuring on the GW and
on all machines that have the 169.254.0.0 route I cannot ping the
destination servers on the other end of the VPN.
I'm not sure what is causing this. I do run a DHCP server (win2K) on
the same network but these RH9 machines all have static 10.0.0.x IP's.
If you find the root cause or a solution at this point can you let us
know.
Gary
| |
| Alexander Dalloz 2004-01-23, 7:14 pm |
| Gary Smith <gary.smith@primeexalia.com> wrote:
quote:
> James,
>
> I have a bunch of new RH9.0 boxes and I am seeing the same thing but
> not on all of them. I reboot and it just comes up on some and not
> others.
>
> What is weird is that I have some VPN routing occuring on the GW and
> on all machines that have the 169.254.0.0 route I cannot ping the
> destination servers on the other end of the VPN.
>
> I'm not sure what is causing this. I do run a DHCP server (win2K) on
> the same network but these RH9 machines all have static 10.0.0.x IP's.
>
> If you find the root cause or a solution at this point can you let us
> know.
>
> Gary
The reason for this route is not clear to me at all. But you can
deactivate it by setting NOZEROCONF=yes in /etc/sysconfig/network.
Alexander
--
Alexander Dalloz | Enger, Germany
PGP key valid: made 13.07.1999
PGP fingerprint: 2307 88FD 2D41 038E 7416 14CD E197 6E88 ED69 5653
| |
|
|
|
|
| CL [dnoyeB] Gilbert 2004-01-23, 7:15 pm |
| On Thu, 04 Sep 2003 20:33:03 +0200, Alexander Dalloz wrote:
quote:
> Gary Smith <gary.smith@primeexalia.com> wrote:
>
>
> The reason for this route is not clear to me at all. But you can
> deactivate it by setting NOZEROCONF=yes in /etc/sysconfig/network.
>
> Alexander
This seems to be a RH9 thing exclusively and not RH8. getting about 1
post every 2 days on the topic here lately.
in windows you get that if it cant contact a DHCP server. but seems like
RH9 is getting it regardless..
CL
| |
|
|
| Gary Smith 2004-01-23, 7:15 pm |
| Thanks... This should help some. I have two routers on the network
10.0.0.1 and 10.0.0.254 and some some odd reason the machines in
question were set to use 10.0.0.254 as the primary GW but they were
trying to go out the wrong one. I think it's because RIP broadcast
was enabled on the 10.0.0.1 router.
I've seen this happen on a Windows box before but never linux. We
have disbled the RIP.
As for the NOZEROCONF=yes I will set it on the boxes and test. It's
always nice to disable anything you don't need (especial routes!!!)...
Gary Smith
quote:
> The reason for this route is not clear to me at all. But you can
> deactivate it by setting NOZEROCONF=yes in /etc/sysconfig/network.
>
> Alexander
| |
| Gary Smith 2004-01-23, 7:15 pm |
| Thanks... This should help some. I have two routers on the network
10.0.0.1 and 10.0.0.254 and some some odd reason the machines in
question were set to use 10.0.0.254 as the primary GW but they were
trying to go out the wrong one. I think it's because RIP broadcast
was enabled on the 10.0.0.1 router.
I've seen this happen on a Windows box before but never linux. We
have disbled the RIP.
As for the NOZEROCONF=yes I will set it on the boxes and test. It's
always nice to disable anything you don't need (especial routes!!!)...
Gary Smith
quote:
> The reason for this route is not clear to me at all. But you can
> deactivate it by setting NOZEROCONF=yes in /etc/sysconfig/network.
>
> Alexander
| |
| Gary Smith 2004-01-23, 7:15 pm |
| Thanks... This should help some. I have two routers on the network
10.0.0.1 and 10.0.0.254 and some some odd reason the machines in
question were set to use 10.0.0.254 as the primary GW but they were
trying to go out the wrong one. I think it's because RIP broadcast
was enabled on the 10.0.0.1 router.
I've seen this happen on a Windows box before but never linux. We
have disbled the RIP.
As for the NOZEROCONF=yes I will set it on the boxes and test. It's
always nice to disable anything you don't need (especial routes!!!)...
Gary Smith
quote:
> The reason for this route is not clear to me at all. But you can
> deactivate it by setting NOZEROCONF=yes in /etc/sysconfig/network.
>
> Alexander
| |
| CL [dnoyeB] Gilbert 2004-01-23, 7:18 pm |
| On Thu, 04 Sep 2003 20:33:03 +0200, Alexander Dalloz wrote:
quote:
> Gary Smith <gary.smith@primeexalia.com> wrote:
>
>
> The reason for this route is not clear to me at all. But you can
> deactivate it by setting NOZEROCONF=yes in /etc/sysconfig/network.
>
> Alexander
This seems to be a RH9 thing exclusively and not RH8. getting about 1
post every 2 days on the topic here lately.
in windows you get that if it cant contact a DHCP server. but seems like
RH9 is getting it regardless..
CL
| |
| CL [dnoyeB] Gilbert 2004-01-23, 7:18 pm |
| On Thu, 04 Sep 2003 20:33:03 +0200, Alexander Dalloz wrote:
quote:
> Gary Smith <gary.smith@primeexalia.com> wrote:
>
>
> The reason for this route is not clear to me at all. But you can
> deactivate it by setting NOZEROCONF=yes in /etc/sysconfig/network.
>
> Alexander
This seems to be a RH9 thing exclusively and not RH8. getting about 1
post every 2 days on the topic here lately.
in windows you get that if it cant contact a DHCP server. but seems like
RH9 is getting it regardless..
CL
| |
|
|
|
|
| Gary Smith 2004-01-23, 7:18 pm |
| Thanks... This should help some. I have two routers on the network
10.0.0.1 and 10.0.0.254 and some some odd reason the machines in
question were set to use 10.0.0.254 as the primary GW but they were
trying to go out the wrong one. I think it's because RIP broadcast
was enabled on the 10.0.0.1 router.
I've seen this happen on a Windows box before but never linux. We
have disbled the RIP.
As for the NOZEROCONF=yes I will set it on the boxes and test. It's
always nice to disable anything you don't need (especial routes!!!)...
Gary Smith
quote:
> The reason for this route is not clear to me at all. But you can
> deactivate it by setting NOZEROCONF=yes in /etc/sysconfig/network.
>
> Alexander
| |
| Gary Smith 2004-01-23, 7:18 pm |
| Thanks... This should help some. I have two routers on the network
10.0.0.1 and 10.0.0.254 and some some odd reason the machines in
question were set to use 10.0.0.254 as the primary GW but they were
trying to go out the wrong one. I think it's because RIP broadcast
was enabled on the 10.0.0.1 router.
I've seen this happen on a Windows box before but never linux. We
have disbled the RIP.
As for the NOZEROCONF=yes I will set it on the boxes and test. It's
always nice to disable anything you don't need (especial routes!!!)...
Gary Smith
quote:
> The reason for this route is not clear to me at all. But you can
> deactivate it by setting NOZEROCONF=yes in /etc/sysconfig/network.
>
> Alexander
| |
| Gary Smith 2004-01-23, 7:21 pm |
| James,
I have a bunch of new RH9.0 boxes and I am seeing the same thing but
not on all of them. I reboot and it just comes up on some and not
others.
What is weird is that I have some VPN routing occuring on the GW and
on all machines that have the 169.254.0.0 route I cannot ping the
destination servers on the other end of the VPN.
I'm not sure what is causing this. I do run a DHCP server (win2K) on
the same network but these RH9 machines all have static 10.0.0.x IP's.
If you find the root cause or a solution at this point can you let us
know.
Gary
| |
| Alexander Dalloz 2004-01-23, 7:22 pm |
| Gary Smith <gary.smith@primeexalia.com> wrote:
quote:
> James,
>
> I have a bunch of new RH9.0 boxes and I am seeing the same thing but
> not on all of them. I reboot and it just comes up on some and not
> others.
>
> What is weird is that I have some VPN routing occuring on the GW and
> on all machines that have the 169.254.0.0 route I cannot ping the
> destination servers on the other end of the VPN.
>
> I'm not sure what is causing this. I do run a DHCP server (win2K) on
> the same network but these RH9 machines all have static 10.0.0.x IP's.
>
> If you find the root cause or a solution at this point can you let us
> know.
>
> Gary
The reason for this route is not clear to me at all. But you can
deactivate it by setting NOZEROCONF=yes in /etc/sysconfig/network.
Alexander
--
Alexander Dalloz | Enger, Germany
PGP key valid: made 13.07.1999
PGP fingerprint: 2307 88FD 2D41 038E 7416 14CD E197 6E88 ED69 5653
| |
| CL [dnoyeB] Gilbert 2004-01-23, 7:22 pm |
| On Thu, 04 Sep 2003 20:33:03 +0200, Alexander Dalloz wrote:
quote:
> Gary Smith <gary.smith@primeexalia.com> wrote:
>
>
> The reason for this route is not clear to me at all. But you can
> deactivate it by setting NOZEROCONF=yes in /etc/sysconfig/network.
>
> Alexander
This seems to be a RH9 thing exclusively and not RH8. getting about 1
post every 2 days on the topic here lately.
in windows you get that if it cant contact a DHCP server. but seems like
RH9 is getting it regardless..
CL
| |
|
|
| Gary Smith 2004-01-23, 7:22 pm |
| Thanks... This should help some. I have two routers on the network
10.0.0.1 and 10.0.0.254 and some some odd reason the machines in
question were set to use 10.0.0.254 as the primary GW but they were
trying to go out the wrong one. I think it's because RIP broadcast
was enabled on the 10.0.0.1 router.
I've seen this happen on a Windows box before but never linux. We
have disbled the RIP.
As for the NOZEROCONF=yes I will set it on the boxes and test. It's
always nice to disable anything you don't need (especial routes!!!)...
Gary Smith
quote:
> The reason for this route is not clear to me at all. But you can
> deactivate it by setting NOZEROCONF=yes in /etc/sysconfig/network.
>
> Alexander
|
|
|
|