All of lore.kernel.org
 help / color / mirror / Atom feed
From: mok2 <mok2@armageddonnet.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Flushing Dead Links
Date: Tue, 29 Jan 2002 17:49:19 +0000	[thread overview]
Message-ID: <marc-lartc-101232655920477@msgid-missing> (raw)

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 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 ?

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



_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/

             reply	other threads:[~2002-01-29 17:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-29 17:49 mok2 [this message]
2002-01-29 18:20 ` [LARTC] Flushing Dead Links Julian Anastasov
2002-01-29 18:24 ` mok2

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-101232655920477@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.