raiden
All American
10504 Posts
user info
edit post |
After many hours of googling, I'm coming to the forums with a question.
On a server that just recently had CentOS installed on it, bonded interfaces with vlans created, and IPv6 configured on the upstream switch I get the following info:
[root@server1A ~]# ip -6 route show
unreachable ::/96 dev lo metric 1024 expires 21244779sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable ::ffff:0.0.0.0/96 dev lo metric 1024 expires 21244779sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:a00::/24 dev lo metric 1024 expires 21244779sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:7f00::/24 dev lo metric 1024 expires 21244779sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:a9fe::/32 dev lo metric 1024 expires 21244779sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:ac10::/28 dev lo metric 1024 expires 21244779sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:c0a8::/32 dev lo metric 1024 expires 21244779sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:e000::/19 dev lo metric 1024 expires 21244779sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 3ffe:ffff::/32 dev lo metric 1024 expires 21244779sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295
fd0d:deba:d97c:ff2::/64 dev bond1.4 proto kernel metric 256 expires 2147145sec mtu 1500 advmss 1440 hoplimit 4294967295
fd0d:deba:d97c:ff5::/64 dev bond1.2 proto kernel metric 256 expires 2146980sec mtu 1500 advmss 1440 hoplimit 4294967295
fd0d:deba:d97c:ff8::/64 dev bond1.3 proto kernel metric 256 expires 2147039sec mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev bond1 metric 256 expires 21245614sec mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev bond1.2 metric 256 expires 21245616sec mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev bond1.4 metric 256 expires 21245630sec mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev bond1.3 metric 256 expires 21319977sec mtu 1500 advmss 1440 hoplimit 4294967295
default via fe80::21a:6dff:fe2e:5ff dev bond1.2 proto kernel metric 1024 expires 1623sec mtu 1500 advmss 1440 hoplimit 64
default via fe80::21a:6dff:fe2e:5ff dev bond1.3 proto kernel metric 1024 expires 1682sec mtu 1500 advmss 1440 hoplimit 64
[root@server1A ~]#
There's a lot that I'm ok with, but a lot that I'm not. For one, what's with all of the unreachable routes? They were there even before the server was connected to the switch. Another thing is why are there 2 default routes? The ipv6 address is the same for each default route, so why are they there?
Interface setup scenario.
I have eth01 and eth02 bonded together.
[root@server1A ~]# cat /proc/net/bonding/bond1
Ethernet Channel Bonding Driver: v3.4.0 (October 7, 2008)
Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth01
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
Slave Interface: eth01
MII Status: up
Link Failure Count: 2
Permanent HW addr: 00:1e:67:00:72:20
Slave Interface: eth02
MII Status: up
Link Failure Count: 2
Permanent HW addr: 00:1e:67:00:72:21
[root@server1A ~]#
and on top of bond1, I have vlan interfaces.
[root@server1A ~]# ifconfig -a
bond0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
UP BROADCAST MASTER 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)
bond1 Link encap:Ethernet HWaddr 00:1E:67:00:72:20
inet6 addr: fe80::21e:67ff:fe00:7220/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:20528 errors:0 dropped:0 overruns:0 frame:0
TX packets:17762 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1993308 (1.9 MiB) TX bytes:1931480 (1.8 MiB)
bond1.2 Link encap:Ethernet HWaddr 00:1E:67:00:72:20
inet addr:10.250.62.85 Bcast:10.250.62.95 Mask:255.255.255.240
inet6 addr: fd0d:deba:d97c:ff5:21e:67ff:fe00:7220/64 Scope:Global
inet6 addr: fe80::21e:67ff:fe00:7220/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:11708 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:1253352 (1.1 MiB)
bond1.3 Link encap:Ethernet HWaddr 00:1E:67:00:72:20
inet addr:10.250.62.133 Bcast:10.250.62.143 Mask:255.255.255.240
inet6 addr: fd0d:deba:d97c:ff8:21e:67ff:fe00:7220/64 Scope:Global
inet6 addr: fe80::21e:67ff:fe00:7220/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:386 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:41364 (40.3 KiB)
bond1.4 Link encap:Ethernet HWaddr 00:1E:67:00:72:20
inet addr:10.250.62.37 Bcast:10.250.62.47 Mask:255.255.255.240
inet6 addr: fd0d:deba:d97c:ff2:21e:67ff:fe00:7220/64 Scope:Global
inet6 addr: fe80::21e:67ff:fe00:7220/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:2172 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:237880 (232.3 KiB)
bond2 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MASTER 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)
bond3 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MASTER 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)
eth01 Link encap:Ethernet HWaddr 00:1E:67:00:72:20
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:18684 errors:0 dropped:0 overruns:0 frame:0
TX packets:15795 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1799162 (1.7 MiB) TX bytes:1695772 (1.6 MiB)
Interrupt:98 Memory:b8820000-b8840000
eth02 Link encap:Ethernet HWaddr 00:1E:67:00:72:20
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:1865 errors:0 dropped:0 overruns:0 frame:0
TX packets:1991 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:195532 (190.9 KiB) TX bytes:241020 (235.3 KiB)
Interrupt:114 Memory:b8800000-b8820000
[root@server1A ~]#
As you can see, each bonded vlan interface resides on its own network. The issue is that in the routing table on centos there are several default routes (link-local). Will having these defaults routes (which were added by router advertisements from the upstream router) have a detrimental effect on failover/appropriate routing of traffic through the segmented networks? 11/12/2010 3:54:17 PM
|
Tarun
almost
11687 Posts
user info
edit post |
Happy IPv6 Day! 6/8/2011 10:05:36 AM |
qntmfred
retired
40435 Posts
user info
edit post |
ha. Nice bump tarun 6/8/2011 10:20:11 AM |
Tarun
almost
11687 Posts
user info
edit post |
the other ipv6 thread was from 2007. i have been learning about ipv6 from so long and now is the time! 
ibt[OLD] 6/8/2011 10:37:27 AM |
wdprice3
BinaryBuffonary
45908 Posts
user info
edit post |
haha, thread left behind. 6/8/2011 11:24:52 AM |
lewisje
All American
9196 Posts
user info
edit post |
I got a perfect score on the IPv6 Eye Chart: http://ipv6eyechart.ripe.net/ 6/8/2011 3:25:47 PM |
synapse
play so hard
60917 Posts
user info
edit post |
english holmes we are not all computer wizzes 6/8/2011 10:24:11 PM |
lewisje
All American
9196 Posts
user info
edit post |
It meant that my IPv6 connection was working just fine, so on that day when most of the Web will need to go dual-stack to accommodate the IPv6-only clients (and that later day when much of the Web will go IPv6-only), I'll be doing just fine. 6/8/2011 10:41:00 PM |
raiden
All American
10504 Posts
user info
edit post |
yeah, I figured out the answer so I never answered my own thread.
built some test boxes & networks, and did some exploring. There is no detrimental effect.
and thanks for the bump. 6/9/2011 1:27:34 PM |
