Sorry, seems I used the wrong sender address...
---------- Forwarded message ---------- Date: Sat, 6 Apr 2013 23:59:12 From: Marlen Caemmerer nosy@c-base.org To: Wikimedia Toolserver toolserver-l@lists.wikimedia.org Subject: Re: [Toolserver-l] Ipv6 issues
Hey,
On Sat, 6 Apr 2013, Merlissimo wrote:
I think nosy needs some sleep because she hasn't slept last night.
"getent ipnodes willow" does not return the ipv6 address configured at /etc/hostname6.bnx0
Well... rnosy@hemlock:~$ host willow willow.toolserver.org has address 185.15.59.202 willow.toolserver.org has IPv6 address 2a02:ec80:101::2:4 rnosy@hemlock:~$ host 2a02:ec80:101::2:4 4.0.0.0.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.0.1.0.0.8.c.e.2.0.a.2.ip6.arpa domain name pointer willow.toolserver.org.
root@willow:~# ifconfig -a lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 bnx0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 185.15.59.202 netmask ffffffc0 broadcast 185.15.59.255 ether 0:1d:9:71:74:cb lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1 inet6 ::1/128 bnx0: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 2 inet6 fe80::21d:9ff:fe71:74cb/10 ether 0:1d:9:71:74:cb bnx0:1: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 2 inet6 2a02:ec80:101::2:4/64
root@willow:~# host willow willow.toolserver.org has address 185.15.59.202 willow.toolserver.org has IPv6 address 2a02:ec80:101::2:4 root@willow:~# host 2a02:ec80:101::2:4 4.0.0.0.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.0.1.0.0.8.c.e.2.0.a.2.ip6.arpa domain name pointer willow.toolserver.org.
I dont see any problem there.
Do you?
So record is missing at dns. If dns cannot be changed ipv6 address must be added to /etc/inet/ipnodes (which is always a good idea if dns is not 100% reliable). /usr/lib/inet/in.ndpd is running.
ifconfig -a6 shows that the ip address is configured three times as local interface for the same physical interface. Is this expected? And physical interface bnx0 is associated with a link local address only. This shows that the router is not propagating the site prefix. So you must change the router config or add the site prefix locally. Maybe interfaces were not plumbed.
I'd really like to reboot tomorrow. Everytime I do what is the equivalent to /etc/init.d/networking restart it adds an interface with the v6 address.
The next try from my side would be to switch back to the old v6 range to see if the problems all go away. I currently cant reach even from the same network.
root@willow:~# ping 2a02:ec80:101:301::2:2
^C
Solaris is not my home base system but I only changed the prefixes in the config files so it should work as it did before.
Lets see how this goes tomorrow after some sleep.
Cheers Marlen/nosy
On 07/04/13 09:28, Marlen Caemmerer wrote:
Sorry, seems I used the wrong sender address...
---------- Forwarded message ---------- Date: Sat, 6 Apr 2013 23:59:12 From: Marlen Caemmerer nosy@c-base.org To: Wikimedia Toolserver toolserver-l@lists.wikimedia.org Subject: Re: [Toolserver-l] Ipv6 issues
Hey,
On Sat, 6 Apr 2013, Merlissimo wrote:
I think nosy needs some sleep because she hasn't slept last night.
"getent ipnodes willow" does not return the ipv6 address configured at /etc/hostname6.bnx0
Well... rnosy@hemlock:~$ host willow willow.toolserver.org has address 185.15.59.202 willow.toolserver.org has IPv6 address 2a02:ec80:101::2:4 rnosy@hemlock:~$ host 2a02:ec80:101::2:4 4.0.0.0.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.0.1.0.0.8.c.e.2.0.a.2.ip6.arpa domain name pointer willow.toolserver.org.
root@willow:~# ifconfig -a lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 bnx0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 185.15.59.202 netmask ffffffc0 broadcast 185.15.59.255 ether 0:1d:9:71:74:cb lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1 inet6 ::1/128 bnx0: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 2 inet6 fe80::21d:9ff:fe71:74cb/10 ether 0:1d:9:71:74:cb bnx0:1: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 2 inet6 2a02:ec80:101::2:4/64
It gives a different output for root? :S
platonides@willow ~ $ ifconfig -a lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 bnx0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 185.15.59.202 netmask ffffffc0 broadcast 185.15.59.255 lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1 inet6 ::1/128 bnx0: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 2 inet6 fe80::21d:9ff:fe71:74cb/10 bnx0:1: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 2 inet6 2a02:ec80:101::2:4/64 bnx0:2: flags=20a0841<UP,RUNNING,MULTICAST,NOLOCAL,ADDRCONF,IPv6> mtu 1500 index 2 inet6 subnet 2620:0:862:101::/64 bnx0:3: flags=20a0841<UP,RUNNING,MULTICAST,NOLOCAL,ADDRCONF,IPv6> mtu 1500 index 2 inet6 subnet 2a02:ec80:101::/64 bnx0:4: flags=2000840<RUNNING,MULTICAST,IPv6> mtu 1500 index 2 inet6 2a02:ec80:101::2:4/64 bnx0:5: flags=2000840<RUNNING,MULTICAST,IPv6> mtu 1500 index 2 inet6 2a02:ec80:101::2:4/64 bnx0:6: flags=2000840<RUNNING,MULTICAST,IPv6> mtu 1500 index 2 inet6 2a02:ec80:101::2:4/64 bnx0:7: flags=2000840<RUNNING,MULTICAST,IPv6> mtu 1500 index 2 inet6 2a02:ec80:101::2:4/64 bnx0:8: flags=2000840<RUNNING,MULTICAST,IPv6> mtu 1500 index 2 inet6 2a02:ec80:101::2:4/64
(bnx0:1,3,4,5,6,7,8 have 2a02:ec80:101::2:4, bnx0:2 2620:0:862:101::)
It looks a problem with the routes: platonides@willow ~ $ route get -inet wikimedia.org route to: wikimedia-lb.pmtpa.wikimedia.org destination: default mask: default gateway: vl102-ve6.csw1-esams.wikimedia.org interface: bnx0 flags: <UP,GATEWAY,DONE,STATIC> recvpipe sendpipe ssthresh rtt,ms rttvar,ms hopcount mtu expire 0 0 0 0 0 0 1500 0
(correct, it's the same gateway as the linux servers)
platonides@willow ~ $ route get -inet6 wikimedia.org route to: wikimedia-lb.pmtpa.wikimedia.org destination: default mask: default gateway: fe80::20c:dbff:fefc:b00 interface: bnx0 flags: <UP,GATEWAY,DONE> recvpipe sendpipe ssthresh rtt,ms rttvar,ms hopcount mtu expire 0 0 0 0 0 0 1500 0
fe80::/10 are link local addresses. I expect that the geteway would be 2a02:ec80:101::1 per teh output of the route to be applied on reboot: platonides@willow ~ $ route -p show persistent: route add -inet6 default 2a02:ec80:101::1
2a02:ec80:101::1 and fe80::20c:dbff:fefc:b00 appear to be different hosts. Although the later does seem to belong to a router, as it runs RomSShell_4.61 [1]
As a workaround, a bit of googling suggests that writing DEFAULT_IP=IP_VERSION4 into /etc/default/inet_type should disable ipv6. Unplumbing the inet6 interfaces should also leave with a working ipv4 system until it is fixed.
Cheers
toolserver-l@lists.wikimedia.org