I had a perfectly running IPv6 config on my Zoom 5341J, routed through my Linux server, which looks like this:
p3p1 (WAN) is accepting RAs and has a link-local IPv6 address only.
bond0 (LAN) is allowing forwarding and is assigned a static IP from the /64 PD obtained on p3p1.
DNSmasq is serving DHCPv6 and SLAAC, doing RAs on bond0.
With the Zoom, the local Linux server, Windows machines, and mobile devices all passed http://test-ipv6.com perfectly, and quickly.
With the only change being the SB6183, here is what I see:
-Windows machines work fine and pass the test quickly every time.
-The local Linux server and mobile devices sometimes pass and mostly fail, with no consistency. Furthermore, the tests are very slow to run, even if it does pass. When it fails, the errors are all over the place (no IPv6 address, large packet (PDMTU) failure, browser blocking test URLs, no direct IPv6 access, etc.) - I've seen combinations of them all! Anything IPv6 related done directly on the server works, but is very slow or stalls entirely (example - wget on http://download.thinkbroadband.com/1GB.zip, which is IPv6). DNS lookups via Comcast's IPv6 DNS are instant. Almost seems like an MTU issue somewhere along the line that Windows isn't having a problem with, which may also explain these in dmesg (lots of them):
[22257.883035] Peer 0000:0000:0000:0000:0000:ffff:0c2f:ae63:49925/80 unexpectedly shrunk window 1023049849:1023051199 (repaired)
[22259.075034] Peer 0000:0000:0000:0000:0000:ffff:0c2f:ae63:49925/80 unexpectedly shrunk window 1023049849:1023051199 (repaired)
[22275.339033] Peer 0000:0000:0000:0000:0000:ffff:0c2f:ae63:49925/80 unexpectedly shrunk window 1023238849:1023240199 (repaired)
I've tried just about everything I can think of and it's leading me to some problem with the 6183 - I've even completely disabled the firewall and all associated rules on the Linux server, and direct access from the server still fails testing.
Any thoughts on this?
↧