Flushing Dead Links
hi, I am trying to maintain a connection to the internet through my modem and a connection through network. I route most my traffic through the modem and only select traffice through the fast connection.. handy for controlling users that want full access to the net :)
i run from my ppp startup a script that adds in this as my gateway
default proto static
nexthop via 260.74.283.1 dev eth0 weight 1
nexthop via 5.4.48.10 dev ppp0 weight 11it 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 ?
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 deadWhen 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
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
Hello,
Quoted 7 lines · 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 11it 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.
Quoted 11 lines
When ppp0 drops
default proto staticnexthop via 250.74.283.1 dev eth0 weight 1 nexthop via 5.4.48.10 dev if40 weight 11 deadWhen it redials again
default proto staticnexthop 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 <[email protected]>
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
Quoted 1 line · Julian Anastasov
You can try to recreate the route. The routes remember the
How do i recreate the route ? i re-run this script everytime the connection goes up but it only works the first time, when it redials it doesnt work anymore
ip rule add prio 201 from $eth0_network/24 table 201
ip route add default via $eth0gw dev eth0 src $ethoSRC proto static table 201 ip route append prohibit default table 201 metric 1 proto static
ip rule add prio 202 from $pppgw/32 table 202
ip route add default via $pppgw dev ppp0 src $pppSRC proto static table 202 ip route append prohibit default table 202 metric 1 proto static
ip rule add prio 222 table 222
ip route add default table 222 proto static nexthop via $eth0gw dev eth0 weight 1 nexthop via $pppgw dev ppp0 weight 11
Quoted 31 lines · Julian Anastasov
Hello,
Quoted 7 lines · 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 11it 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.Quoted 11 lines
When ppp0 drops
default proto staticnexthop via 250.74.283.1 dev eth0 weight 1 nexthop via 5.4.48.10 dev if40 weight 11 deadWhen it redials again
default proto staticnexthop via 260.74.283.1 dev eth0 weight 1 nexthop via 5.4.48.10 dev if40 weight 11 dead-regards mok2
Quoted 9 lines
Regards
--
Julian Anastasov <[email protected]>_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/