All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo <terminus@iespana.es>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: dead onlink
Date: Wed, 05 Nov 2003 10:52:11 +0000	[thread overview]
Message-ID: <marc-lartc-106804438831891@msgid-missing> (raw)


 Hello people:
 	I've implemented the script for load balancing of
 "Linux Advanced Routing & Traffic Control HowTo" on this structure:


                  ------------------linux gateway (subnet 1)
		!
linux router ------------------intranet (subnet 2)
		!
                 ------------------linux gateway2 (subnet 3)
		!
		 ------------------intranet (subnet 4)


and I've a question:
  When I run the next command : "ip route" I get the folowing information:

 --------------
 192.168.0.32/27 dev eth0 proto kernel scope link src 192.168.0.33
 192.168.0.96/27 dev eth2 proto kernel scope link src 192.168.0.97
 192.168.0.64/27 dev eth1 proto kernel scope link src 192.168.0.65
 192.168.0.128/27 dev eth3 proto kernel scope link src 192.168.0.129
 127.0.0.0/8 dev lo scope link
 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" ?
 This message is always there but the 192.168.0.126 gateway is online.
 Do I need the Julian's dead gateway detection patch?.

 Thanks in advance.

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

             reply	other threads:[~2003-11-05 10:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-05 10:52 Marcelo [this message]
2003-11-06  5:53 ` [LARTC] Re: dead onlink Julian Anastasov
2003-11-06  7:56 ` gypsy

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-106804438831891@msgid-missing \
    --to=terminus@iespana.es \
    --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.