From: mok2 <mok2@armageddonnet.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Flushing Dead Links
Date: Tue, 29 Jan 2002 18:24:06 +0000 [thread overview]
Message-ID: <marc-lartc-101232864627571@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101232655920477@msgid-missing>
On Tue, 29 Jan 2002, Julian Anastasov wrote:
> 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
On Tue, 29 Jan 2002, Julian Anastasov wrote:
>
> 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>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
prev parent reply other threads:[~2002-01-29 18:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-29 17:49 [LARTC] Flushing Dead Links mok2
2002-01-29 18:20 ` Julian Anastasov
2002-01-29 18:24 ` mok2 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-101232864627571@msgid-missing \
--to=mok2@armageddonnet.com \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.