From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julian Anastasov Date: Tue, 29 Jan 2002 18:20:34 +0000 Subject: Re: [LARTC] Flushing Dead Links Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lartc@vger.kernel.org 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 _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/