All of lore.kernel.org
 help / color / mirror / Atom feed
From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: dead onlink
Date: Thu, 06 Nov 2003 07:56:54 +0000	[thread overview]
Message-ID: <marc-lartc-106810648532302@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106804438831891@msgid-missing>

Marcelo wrote:
>  default
>         nexthop via 192.168.0.126 dev eth2 weight 1 dead onlink
>         nexthop via 192.168.0.61 dev eth0 weight 1
>
>  Is normal the part of "dead onlink" ?
No, it is not normal.  I don't know what "onlink" means, but "dead"
means just what you fear it means; eth2 has been set dead by the
kernel.  It could be a routing issue or it could be your firewall, or
possibly the NIC is telling the kernel something bad?

You really need to run 
# ip route list table eth2
# ip route list table eth0
# ip route list table main
to see what is going on.  And assure that when only eth2 is up that you
can surf (perhaps unplug the WAN wire on eth0?).

>  This message is always there but the 192.168.0.126 gateway is online.
Are you 100% sure it is online?  I have NEVER seen "dead" unless it was
true.  I _have_ been able to send/receive on a different (wrong)
interface while one interface was dead.  (I have 3 ISPs)

>  Do I need the Julian's dead gateway detection patch?.
Well, whether you "need" it or not, I strongly recommend you apply it.  

You might also want to use
# ip route add default   equalize   scope global nexthop via BLAH
BLAH...
rather than
# ip route add default scope global nexthop via BLAH BLAH...

If you run a kernel version 2.4.22 you will need to tweak Julian's patch
(I could only find a patch for 2.4.20); if you want my tweaked version
(2.4.22) you can FTP it from andthatsjazz.net/pub/linux/.

And I use KeepState (see nano.txt), though I have NO CLUE why it is A
Good Thing <grin>.  I do not ping from inside though.  I run a dgd ping
from outside; when the ping fails I scp a flag file to the multilink
setup that triggers a flush there.

>  Thanks in advance.
> 
> Marcelo.
gypsy
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2003-11-06  7:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-05 10:52 [LARTC] Re: dead onlink Marcelo
2003-11-06  5:53 ` Julian Anastasov
2003-11-06  7:56 ` gypsy [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-106810648532302@msgid-missing \
    --to=gypsy@iswest.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.