On Tue, 13 Apr 1999, Stephen R. van den Berg wrote:
> Basically, I have 10.0.0.1 bound to eth0, and 192.168.0.1 bound to eth0:0.
> In Linux 2.0 this means that whenever I say that gated has to accept/send
> OSPF packets on eth0, it will only bind to 10.0.0.1 and use that to communicate
> with its peers.
> In Linux 2.2 the kernel most of the time suppresses the fact that 192.168.0.1
> is actually bound to eth0:0, instead it will simply report a mere eth0 in
> many views. Gated therefore occasionally tries to start OSPF negotiations
> using 192.168.0.1 instead of 10.0.0.1. This then messes up the state
> machine at the other routers' ends and causes them to reinitiate the
> negotiations.
I've seen gated 3.5.10 have other problems (probably for similar reasons)
on linux 2.0.x when using IP Aliasing. I've since moved to almost always
specifying the interface IP address in gated.conf rather than the
interface name.
----don't waste your cpu, crack rc5...www.distributed.net team enzo---
Jon Lewis *[EMAIL PROTECTED]*| Spammers will be winnuked or
System Administrator | nestea'd...whatever it takes
Atlantic Net | to get the job done.
_________http://www.lewis.org/~jlewis/pgp for PGP public key__________
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
