From: Szymon Miotk <spam@crocom.com.pl>
To: lartc@vger.kernel.org
Subject: [LARTC] Problem with third link in multiple uplink configuration
Date: Wed, 07 May 2003 07:44:52 +0000 [thread overview]
Message-ID: <marc-lartc-105229354610550@msgid-missing> (raw)
Hello!
I have access server with 4 uplinks (nice, huh?). I ran RedHat 7.3.
Yesterday I did an upgrade to RedHat 9.
After upgrade Linux says the third link is bad:
# ip route show
2.2.2.0/30 dev eth2 scope link src 2.2.2.2
4.4.4.0/30 dev eth4 scope link src 4.4.4.4
3.3.3.0/29 dev eth3 scope link src 3.3.3.3
1.1.1.0/28 dev eth1 scope link src 1.1.1.1
10.1.1.0/24 dev eth0 scope link
10.1.2.0/24 dev eth0 proto kernel scope link src 10.1.2.1
10.1.3.0/24 dev eth0 proto kernel scope link src 10.1.3.1
127.0.0.0/8 dev lo scope link
default
nexthop via 1.1.1.254 dev eth1 weight 11
nexthop via 3.3.3.254 dev eth3 weight 20
nexthop via 2.2.2.254 dev eth2 weight 10 dead pervasive
nexthop via 4.4.4.254 dev eth4 weight 11
When I change the order of links in this command:
ip route add default scope global \
nexthop via 1.1.1.254 dev eth1 weight 11 \
nexthop via 3.3.3.254 dev eth3 weight 20 \
nexthop via 2.2.2.254 dev eth2 weight 10 \
nexthop via 4.4.4.254 dev eth4 weight 11
it's always the third link that is dead!
Anybody have a clue?
Szymon Miotk
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-05-07 7:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-07 7:44 Szymon Miotk [this message]
2003-05-08 7:52 ` [LARTC] Problem with third link in multiple uplink configuration Szymon Miotk
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-105229354610550@msgid-missing \
--to=spam@crocom.com.pl \
--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.