From: Ben Greear <greearb@candelatech.com>
To: NetDev <netdev@vger.kernel.org>
Subject: Routing tables associated with VLANs dissappear when parent ethX down/up
Date: Tue, 20 Nov 2007 17:20:36 -0800 [thread overview]
Message-ID: <474387E4.7020802@candelatech.com> (raw)
Hello!
Found something strange today.
Suppose I have eth2 with VLAN 2 (eth2.2) associated with it. I
add a routing table that is associated with eth2.2 (table 76 in my case).
Now, I run:
ifconfig eth2 down
ifconfig eth2 up
All of the routes in routing table 76 are now gone! I can
understand how it might be useful to remove the routes from
the eth2 table (as is also done), but it seems pretty extreme
to muck with the VLAN device's tables as well.
[root@lanforge-33-46 local]# ip route show table 76
27.1.1.0/24 via 27.1.1.2 dev eth2.2
default via 27.1.1.1 dev eth2.2
[root@lanforge-33-46 local]# ifconfig eth2.2
eth2.2 Link encap:Ethernet HWaddr 00:03:2D:08:33:47
inet addr:27.1.1.2 Bcast:27.1.1.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
[root@lanforge-33-46 local]# ifconfig eth2 down;ifconfig eth2 up
[root@lanforge-33-46 local]# ip route show table 76
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2007-11-21 1:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 1:20 Ben Greear [this message]
2007-11-21 19:51 ` Routing tables associated with VLANs dissappear when parent ethX down/up Ben Greear
2007-11-21 20:00 ` Stephen Hemminger
2007-11-21 20:25 ` Patrick McHardy
2007-11-21 20:54 ` Ben Greear
2007-11-21 21:12 ` Patrick McHardy
2007-11-21 21:52 ` Ben Greear
2007-11-21 22:24 ` Patrick McHardy
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=474387E4.7020802@candelatech.com \
--to=greearb@candelatech.com \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).