OVH Community, your new community space.

IPv6 router problem


dail8448138225
27-12-2014, 12:10
Hi
I have a netgear wndr300 wireless router. Recently it has been losing connection and then regaining connection on it's own. we have several computers and a tv along with an ipad running though it.
any suggestions

Dani
03-09-2014, 16:28
Hi

I have raised a ticket for this issue. You will be informed via the ticket.

Danny

nkukard
02-09-2014, 11:17
Bump, ticket is now 3 days old and yet no answer

nkukard
01-09-2014, 12:05
Hi guys,

I logged a support ticket for ns330491.ip-94-23-1.eu, when the IPv6 is properly setup in rescue mode the router does not respond to solicitations.

I have multiple servers, so the config is done exactly as another one except replacing the relevant portions.

Setup:
# ip -f inet6 route add 2001:41D0:2:02ff:ff:ff:ff:ff dev eth0
# ip -f inet6 route add default via 2001:41D0:2:02ff:ff:ff:ff:ff
# ip -f inet6 addr add 2001:41D0:2:02d3::1/64 dev eth0

Testing:
# ping6 2001:41D0:2:02ff:ff:ff:ff:ff
PING 2001:41D0:2:02ff:ff:ff:ff:ff(2001:41d0:2:2ff:ff:ff :ff:ff) 56 data bytes
From 2001:41d0:2:2d3:: icmp_seq=1 Destination unreachable: Address unreachable
From 2001:41d0:2:2d3:: icmp_seq=2 Destination unreachable: Address unreachable
From 2001:41d0:2:2d3:: icmp_seq=3 Destination unreachable: Address unreachable

# ip -6 neigh list
fe80::222:91ff:fe08:400 dev eth0 lladdr 00:22:91:08:04:00 router STALE
2001:41d0:2:2ff:ff:ff:ff:ff dev eth0 FAILED
fe80::222:91ff:fe08:1c00 dev eth0 lladdr 00:22:91:08:1c:00 router STALE

Traffic dump from a server in UK to OVH:
# tcpdump -i eth0 -n -nn ip6 -e
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
11:53:07.998452 00:22:91:08:1c:00 > 33:33:00:00:00:66, ethertype IPv6 (0x86dd), length 68: fe80::222:91ff:fe08:1c00.2029 > ff02::66.2029: UDP, length 6
11:53:10.254499 00:22:91:08:1c:00 > 33:33:ff:00:00:00, ethertype IPv6 (0x86dd), length 86: fe80::222:91ff:fe08:1c00 > ff02::1:ff00:0: ICMP6, neighbor solicitation, who has 2001:41d0:2:2d3::, length 32
11:53:10.254538 4c:72:b9:43:ea:89 > 00:22:91:08:1c:00, ethertype IPv6 (0x86dd), length 86: 2001:41d0:2:2d3:: > fe80::222:91ff:fe08:1c00: ICMP6, neighbor advertisement, tgt is 2001:41d0:2:2d3::, length 32
11:53:10.256833 00:22:91:08:1c:00 > 4c:72:b9:43:ea:89, ethertype IPv6 (0x86dd), length 118: 2001:1b40:5600:XXXX::200 > 2001:41d0:2:2d3::: ICMP6, echo request, seq 1, length 64
11:53:10.256882 4c:72:b9:43:ea:89 > 33:33:ff:ff:00:ff, ethertype IPv6 (0x86dd), length 86: 2001:41d0:2:2d3:: > ff02::1:ffff:ff: ICMP6, neighbor solicitation, who has 2001:41d0:2:2ff:ff:ff:ff:ff, length 32
11:53:11.250117 00:22:91:08:1c:00 > 4c:72:b9:43:ea:89, ethertype IPv6 (0x86dd), length 118: 2001:1b40:5600:XXXX::200 > 2001:41d0:2:2d3::: ICMP6, echo request, seq 2, length 64
11:53:11.254909 4c:72:b9:43:ea:89 > 33:33:ff:ff:00:ff, ethertype IPv6 (0x86dd), length 86: 2001:41d0:2:2d3:: > ff02::1:ffff:ff: ICMP6, neighbor solicitation, who has 2001:41d0:2:2ff:ff:ff:ff:ff, length 32
11:53:12.254932 4c:72:b9:43:ea:89 > 33:33:ff:ff:00:ff, ethertype IPv6 (0x86dd), length 86: 2001:41d0:2:2d3:: > ff02::1:ffff:ff: ICMP6, neighbor solicitation, who has 2001:41d0:2:2ff:ff:ff:ff:ff, length 32
11:53:13.189810 00:05:73:a0:00:00 > 33:33:00:00:00:66, ethertype IPv6 (0x86dd), length 134: fe80::222:91ff:fe08:400.2029 > ff02::66.2029: UDP, length 72

I notice traffic coming in from 00:22:91:08:1c:00, which appears to be the router. (first line in bold)
I notice that nothing on the network is replying to the soliciation to find where the router is. (second line in bold)

So I got thinking ....
# ip -6 neigh list
fe80::222:91ff:fe08:400 dev eth0 lladdr 00:22:91:08:04:00 router STALE
2001:41d0:2:2ff:ff:ff:ff:ff dev eth0 FAILED
fe80::222:91ff:fe08:1c00 dev eth0 lladdr 00:22:91:08:1c:00 router STALE

Interesting ... what happens if we add it manually?

Firstly I tried 00:22:91:08:1c:00 which looks like a Cisco Nexus? 002291 is Cisco...
# ip -6 neigh add 2001:41d0:2:2ff:ff:ff:ff:ff dev eth0 lladdr 00:22:91:08:1c:00

Traffic now worked inbound and outbound, but I could not ping the router IPv6 IP. I looked at the above dump again and saw another device which is also a Cisco 00:05:73:a0:00:00, 000573 is also Cisco. Third bold line above.
# ip -6 neigh replace 2001:41d0:2:2ff:ff:ff:ff:ff dev eth0 lladdr 00:05:73:a0:00:00

BINGO!

# ping6 2001:41D0:2:02ff:ff:ff:ff:ff
PING 2001:41D0:2:02ff:ff:ff:ff:ff(2001:41d0:2:2ff:ff:ff :ff:ff) 56 data bytes
64 bytes from 2001:41d0:2:2ff:ff:ff:ff:ff: icmp_seq=1 ttl=64 time=6.17 ms
64 bytes from 2001:41d0:2:2ff:ff:ff:ff:ff: icmp_seq=2 ttl=64 time=0.437 ms
64 bytes from 2001:41d0:2:2ff:ff:ff:ff:ff: icmp_seq=3 ttl=64 time=0.672 ms
64 bytes from 2001:41d0:2:2ff:ff:ff:ff:ff: icmp_seq=4 ttl=64 time=0.466 ms

On another OVH server, everything works as expected when booting in rescue mode. Its just the above server not working and it appears to be an issue on OVH's router.