From: Sven Anders <anders@anduras.de>
To: lartc@vger.kernel.org
Subject: [LARTC] Problem with duplicate route entry (2. TRY) / Route on
Date: Mon, 13 Mar 2006 19:00:51 +0000 [thread overview]
Message-ID: <4415C163.8050602@anduras.de> (raw)
In-Reply-To: <44074BCB.1000809@anduras.de>
[-- Attachment #1: Type: text/plain, Size: 3609 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
(Sorry, if you got this mail twice, but the LARTC maillist server had problems).
Hello!
** I modified this a little bit and added some command to make it clearer. **
I have a problem with a duplicate route entry, when using a pre-installed route
and automatic take-over by the "heartbeat" daemon, which adds an address and
the kernel adds an route automatically.
Maybe anyone has an explanation...
> ip addr
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1514 qdisc pfifo_fast qlen 1000
inet 10.10.20.100/32 scope global eth0
> ip route
127.0.0.0 dev lo scope link
10.10.20.0/24 dev eth0 scope link
default via 10.10.20.1 dev eth0
- -- Now I add a route for my ha net:
> ip route add 10.100.0.0/24 dev eth0 proto kernel scope link
> ip route
127.0.0.0 dev lo scope link
10.10.20.0/24 dev eth0 scope link
10.100.0.0/24 dev eth0 proto kernel scope link
default via 10.10.20.1 dev eth0
- -- The 'heartbeat' will add an address on switch-over:
> ip addr add 10.100.0.1/24 brd 10.100.0.255 dev eth0
ip addr
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1514 qdisc pfifo_fast qlen 1000
inet 10.10.20.100/32 scope global eth0
inet 10.100.0.1/24 brd 10.100.0.255 scope global eth0
> ip route
127.0.0.0 dev lo scope link
10.10.20.0/24 dev eth0 scope link
10.100.0.0/24 dev eth0 proto kernel scope link
10.100.0.0/24 dev eth0 proto kernel scope link src 10.100.0.1
default via 10.10.20.1 dev eth0
My question is:
Why did the kernel add a duplicate routing entry, shouldn't it notice the
existance and avoid this??
Is this a bug of the kernel?
| "Radoslaw Horodniczy" answered:
|
| This is not a bug, as you see there are 2 different routes
Ok, then try this:
> ip route del 10.100.0.0/24 dev eth0 proto kernel scope link
> ip route
127.0.0.0 dev lo scope link
10.10.20.0/24 dev eth0 scope link
10.100.0.0/24 dev eth0 proto kernel scope link src 10.100.0.1
default via 10.10.20.1 dev eth0
Now I removed my manually set route. It succeeds.
If I then try to readd it, it fails. But why?
> ip route add 10.100.0.0/24 dev eth0 proto kernel scope link
RTNETLINK answers: File exists
I thought they are different!?!
Is here any difference I did not see?
If they are not different, why does the kernel not recognize it
(see above) and avoid the duplicate entry?
- --------
Another question:
Why can't I set a route on an interface that is down?
I can set an address, so why not a route?
I there a reason for that?
Example:
> ip link set down dev eth0
> ip addr add 10.100.0.1/24 dev eth0
> ip route add 10.100.0.0/24 dev eth0 proto kernel scope link
RTNETLINK answers: Network is down
- --------
PS: I'm running Linux 2.6.15.1
Regards
Sven Anders
- --
Sven Anders <anders@anduras.de> () Ascii Ribbon Campaign
/\ Support plain text e-mail
ANDURAS service solutions AG
Innstraße 71 - 94036 Passau - Germany
Web: www.anduras.de - Tel: +49 (0)851-4 90 50-0 - Fax: +49 (0)851-4 90 50-55
Mit freundlichen Grüßen
Sven Anders
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEFcFi5lKZ7Feg4EcRAsbNAKCTTnDmHACtK0jRknO+/DJZ3QotcQCfa6wa
+XKjJP1EFDMSLCsN4PyNHr0=
=ox5B
-----END PGP SIGNATURE-----
[-- Attachment #2: anders.vcf --]
[-- Type: text/x-vcard, Size: 339 bytes --]
begin:vcard
fn:Sven Anders
n:Anders;Sven
org:ANDURAS AG;Research and Development
adr;quoted-printable:;;Innstra=C3=9Fe 71;Passau;Bavaria;94036;Germany
email;internet:anders@anduras.de
title:Dipl. Inf.
tel;work:++49 (0)851 / 490 50 - 0
tel;fax:+49 (0)851 / 4 90 50 - 55
x-mozilla-html:FALSE
url:http://www.anduras.de
version:2.1
end:vcard
[-- Attachment #3: Type: text/plain, Size: 143 bytes --]
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-03-13 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 19:47 [LARTC] Problem with duplicate route entry Sven Anders
2006-03-10 18:40 ` [LARTC] Problem with duplicate route entry (2. TRY) / Route on Sven Anders
2006-03-13 8:10 ` Sven Anders
2006-03-13 19:00 ` Sven Anders [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=4415C163.8050602@anduras.de \
--to=anders@anduras.de \
--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.