On Thu, 3 Jun 1999, Jose M. Sanchez wrote:
> This sounds like your Novell server is exchanging RIP packets with your
> Linux box...
>
> Your Linux box "learns" the new routes after a few minutes, which are not
> valid...
> hence your connection is lost.
I'm not sure if this is happening... if I look at my routing table
everything is fine. I think the linux box is receiving RIP packets, but
is rejecting them properly.
My question, is it possible that the client machine is receiving the RIP
packets and learning from them? My intuition seems to make me think
maybe the client is learning the wrong route and doesn't go through the
linux box any more. I may be totally off base though :)
> Solution: remove RIP in Novell, you don't
> need it enabled if you
> are not using the Novell machine as a gateway... (and/or) disable the
> corresponding linux
> daemons...
Hmm... I'm not sure if I can remove RIP in novell.. as of now that
machine is something that I can change. Is there a way to make sure the
deamons are disabled in linux?
> BTW: While I know you are using reserved IP's for both your subnets, it
> seems that you
> have different IP addresses for a single segment...
>
> Isn't this a -BIG- no-no?
Do you mean the fact we are using 10.x.x.x IPs and 192.168.x.x IPs?
I thought that was kind of a no-no as well, but that's how the network
environment that I'm part of has been set up... is that something that I
should get changed? If it is a big enough no-no I'm sure something could
be done.
Anyway, thanks for your help.
I'll keep you all posted.
Sincerely,
Josh Estelle
One last question...
why does pining the DHCP server, and then the client restore the clients
connection to the linux box?
Thanks.
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
http://tiffany.indyramp.com/mailman/listinfo/masq
Admin requests can be handled by web (above) or [EMAIL PROTECTED]
