[LARTC] Flushing Dead Links

Linux Advanced Routing and Traffic Control

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



	Hello,

On Tue, 29 Jan 2002, mok2 wrote:

> default  proto static
>         nexthop via 260.74.283.1  dev eth0 weight 1
>         nexthop via 5.4.48.10  dev ppp0 weight 11
>
> it works fine but when the connection drops it puts the ppp0 gw as a deadlink and when it redials it
> still sees it as a dead link the only way i can make it work again is to reboot..
> how can i flush this dead link ?

	You can try to recreate the route. The routes remember the
device by index, not by name and can not detect that the new
device is a replacement for the previous one. The ifXXX name means
the device is unregistered which is bad. Routes containing
unregistered devices should be recreated.

> When ppp0 drops
> default  proto static
>         nexthop via 250.74.283.1  dev eth0 weight 1
>         nexthop via 5.4.48.10  dev if40 weight 11 dead
>
> When it redials again
> default  proto static
>         nexthop via 260.74.283.1  dev eth0 weight 1
>         nexthop via 5.4.48.10  dev if40 weight 11 dead
>
> -regards mok2

Regards

--
Julian Anastasov <ja@ssi.bg>



[Index of Archives]     [LARTC Home Page]     [Netfilter]     [Netfilter Development]     [Network Development]     [Bugtraq]     [GCC Help]     [Yosemite News]     [Linux Kernel]     [Fedora Users]
  Powered by Linux