Actually, after diald is started in rc.local (after the eth0 initialization), the
routing table is simply left empty. But I will try as you suggest and see if that
fixes the problem.
--Brian
Ed Doolittle wrote:
> Could it be that the route to your ethernet is a default route, and when
> you start diald it overrides the old default route? Run the route command
> with and without diald running and post the output to this list.
>
> If that is the problem, the proper way to handle it is to only route
> traffic to the ethernet card that can actually reach its destination
> through the ethernet card ... typically just one network.
>
> Ed
>
> On Tue, 29 Sep 1998, Brian wrote:
>
> > I've noticed that starting diald seems to wipe out the routing table (such as
> > is set up when you initialize your NIC). No one on this ML seems to know a
> > way around this.
> >
> > Bill Luo wrote:
> >
> > > Everytime I start diald, my ethernet stop responding. And if I kill
> > > diald, ethernet will go back to work again. If anyone can tell me why? I
> > > run diald on Red Hat 4.2, my ethernet adapter is 3C509. The kernel
> > > version is 2.0.30( I also tried 2.0.35 and nothing changed).
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-diald" in
> the body of a message to [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
