IPv6 routing down?

[Rachel]

... seems to be, since yesterday. Just times out trying to connect to anything (including ipv6.google.com). Have already tried bouncing my router.

[Bill]

Seems patchy... ipv6.google.com works for me, as do some others. Some test sites work, others don't, those that don't often report a v4 DNS error as well


edit- for "patchy", read "patchy and intermittent"... tbb reported I was connecting over v4, a reload came up as v6, another reload came up as v4

I get the feeling it may be routing outside IDNet, but it's no more than that.

[Rachel]

Seems patchy... ipv6.google.com works for me, as do some others. Some test sites work, others don't, those that don't often report a v4 DNS error as well

DNS is fine for me; everything's resolving OK; it's just not routing. I'm slightly suspecting this Billion 7800N router everyone here said to get of being rubbish and suffering from multiple failures. Wifi failed on it yesterday, which google tells me is a common failure mode, so is turned off at the moment. But if my router is failing to route properly, I don't know if that's because it has suddenly developed an ipv6-specific firmware error or if it's not getting autoconfigured from upstream properly.

(in below: merrow.strangenoises.org is a ipv6-enabled hosted server I have outside of idnet (in germany); celestia.strangenoises.org is a computer in my home subnet...)

celestia:~ rachel$ host ipv6.google.com
ipv6.google.com is an alias for ipv6.l.google.com.
ipv6.l.google.com has IPv6 address 2a00:1450:4007:800::1010
celestia:~ rachel$ ping6 ipv6.google.com
PING6(56=40+8+8 bytes) 2a02:390:feed:6d2e:4d44:a78f:8605:cbc8 --> 2a00:1450:4007:800::1013
^C
--- ipv6.l.google.com ping6 statistics ---
702 packets transmitted, 0 packets received, 100.0% packet loss

celestia:~ rachel$ traceroute6 ipv6.google.com
traceroute6 to ipv6.l.google.com (2a00:1450:4007:800::1010) from 2a02:390:feed:6d2e:4d44:a78f:8605:cbc8, 64 hops max, 12 byte packets
1  2a02:390:feed:6d2e::1 (router LAN IP)  1.256 ms  0.574 ms  0.450 ms
2  2a02:390:ffff:ffff:ffff:ffff:ffff:fffc (what??)  17.313 ms  17.531 ms  17.237 ms
3  2a02:390::ff01:204:4eff:feb3:7419  16.687 ms  17.338 ms  16.730 ms
4  2a02:390::ff00:21b:21ff:fe70:869c  17.207 ms  18.078 ms  17.465 ms
5  2001:7f8:17::3b41:1  18.484 ms  18.535 ms  18.010 ms
6  2001:4860::1:0:3067  18.819 ms  18.581 ms
    2001:4860::1:0:15f  18.933 ms
7  2001:4860::8:0:2ddf  19.135 ms  18.837 ms  18.975 ms
8  2001:4860::1:0:9f2  37.010 ms  26.767 ms  26.673 ms
9  2001:4860:0:1::182  26.757 ms  26.709 ms  26.893 ms
10  2a00:1450:8000:5::b  26.299 ms
    2a00:1450:8000:5::e  26.352 ms
    2a00:1450:8000:5::c  26.218 ms
celestia:~ rachel$ host merrow.strangenoises.org
merrow.strangenoises.org has address 88.198.45.142
merrow.strangenoises.org has IPv6 address 2a01:4f8:131:2482::2
celestia:~ rachel$ traceroute6 merrow.strangenoises.org
traceroute6 to merrow.strangenoises.org (2a01:4f8:131:2482::2) from 2a02:390:feed:6d2e:4d44:a78f:8605:cbc8, 64 hops max, 12 byte packets
1  * * *
2  * * *
3  * * *
4  * * *
5  * * *
6  * * *
7  * * *
8  * * *
9  *^C


And on my outside-idnet box, everything's fine unless I try to connect to my idnet network:

rachel@merrow:~$ traceroute6 ipv6.google.com
traceroute to ipv6.google.com (2a00:1450:4016:801::1013), 30 hops max, 80 byte packets
1  2a01:4f8:131:2480::1 (2a01:4f8:131:2480::1)  2.195 ms  2.228 ms  2.233 ms
2  2a01:4f8:0:13:1:0:13:1 (2a01:4f8:0:13:1:0:13:1)  0.411 ms  0.426 ms  0.442 ms
3  hos-bb1.juniper4.ffm.hetzner.de (2a01:4f8:0:1::1:4)  4.800 ms  4.781 ms  4.788 ms
4  de-cix10.net.google.com (2001:7f8::3b41:0:1)  5.591 ms  5.701 ms  5.822 ms
5  2001:4860::1:0:11 (2001:4860::1:0:11)  6.335 ms 2001:4860::1:0:10 (2001:4860::1:0:10)  6.397 ms 2001:4860::1:0:11 (2001:4860::1:0:11)  6.071 ms
6  2001:4860::8:0:3016 (2001:4860::8:0:3016)  5.884 ms  6.709 ms  6.282 ms
7  2001:4860::1:0:336d (2001:4860::1:0:336d)  11.705 ms  12.066 ms  12.039 ms
8  2001:4860:0:1::537 (2001:4860:0:1::537)  12.220 ms  12.590 ms  12.995 ms
9  2a00:1450:8000:1f::a (2a00:1450:8000:1f::a)  12.186 ms  12.128 ms  12.055 ms
rachel@merrow:~$ ping6 ipv6.google.com
PING ipv6.google.com(muc03s02-in-x13.1e100.net) 56 data bytes
64 bytes from muc03s02-in-x13.1e100.net: icmp_seq=1 ttl=56 time=69.5 ms
64 bytes from muc03s02-in-x13.1e100.net: icmp_seq=2 ttl=56 time=80.5 ms
^C
--- ipv6.google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 69.513/75.009/80.505/5.496 ms
rachel@merrow:~$ traceroute6 celestia.strangenoises.org
traceroute to celestia.strangenoises.org (2a02:390:feed:6d2e:3e07:54ff:fe52:4b5a), 30 hops max, 80 byte packets
1  2a01:4f8:131:2480::1 (2a01:4f8:131:2480::1)  0.981 ms  0.998 ms  1.003 ms
2  2a01:4f8:0:13:1:0:13:1 (2a01:4f8:0:13:1:0:13:1)  0.317 ms 2a01:4f8:0:13:3:0:13:2 (2a01:4f8:0:13:3:0:13:2)  0.351 ms 2a01:4f8:0:13:1:0:13:1 (2a01:4f8:0:13:1:0:13:1)  0.310 ms
3  hos-bb1.juniper4.ffm.hetzner.de (2a01:4f8:0:1::1:4)  4.827 ms  4.812 ms  4.810 ms
4  20gigabitethernet4-3.core1.fra1.he.net (2001:7f8::1b1b:0:1)  5.612 ms  5.850 ms  5.956 ms
5  10gigabitethernet5-3.core1.lon1.he.net (2001:470:0:1d2::1)  24.261 ms  24.131 ms  28.553 ms
6  idnet.gigabitethernet25.switch2.lon1.he.net (2001:470:1:222::2)  20.589 ms  20.494 ms  17.774 ms
7  2a02:390:0:ff00:212:7fff:feae:411b (2a02:390:0:ff00:212:7fff:feae:411b)  21.163 ms  20.932 ms  21.298 ms
8  2a02:390:feed:6d2e:c06d:a183:e83:92ef (home router WAN IP) (2a02:390:feed:6d2e:c06d:a183:e83:92ef)  35.362 ms  34.789 ms  38.256 ms
9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
rachel@merrow:~$ ping6 celestia.strangenoises.org
PING celestia.strangenoises.org(2a02:390:feed:6d2e:3e07:54ff:fe52:4b5a) 56 data bytes
^C
--- celestia.strangenoises.org ping statistics ---
496 packets transmitted, 0 received, 100% packet loss, time 495000ms

[Bill]

I think it's safe to say you know a lot more about IPv6 than I do- I just use it

I'm using the same router, we really need a comment from someone using a different one. Anyone with a Fritzbox having/not having problems?

One thing I have noticed is that IPv6 seems to be working better on the iMac (fixed IPv6 address) than on the MacBook (DHCP). Not sure what, if anything, that proves.

[Rachel]

i'm probably going to have another go at setting up a linux box to be router, with the draytek vigor used as a simple PPPoE-PPPoA bridge. The closest I came to having it all work before was with an Ubuntu system. I've now installed ubuntu on the old G4 mac mini I used to use as my router before, so I may give this a go. Can't do so until tomorrow night at earliest though.

Rapidly gaining a poor opinion of billion routers.

[Rachel]

Actually I may give the Airport Extreme another go, with manually-configured IPv6 router settings. (Already established it doesn't do automatic configuration over PPPoE.) With further understanding gained since the last time I tried there's now just one field in its manual configuration that I don't know what value to give: IPv6 Default Route. Presumably this is the address of the upstream router at IDNet, which ought to be determined automatically. As I can't trust my outgoing ipv6 traceroutes now, I don't know what that is. :-)

(But of course i still don't know that the problem isn't at that upstream router rather than mine.)

[Rachel]

hm. ipv6 is actually working again; i didn't do anything. :-) Oh actually. I can ping6 and I can visit with http, but I can't ssh; those connections are timing out, like they're firewalled; then ssh client reverts to ipv4. They're certainly not firewalled as outgoing at my end, so I still reckon IDnet are messing with something...

Also still with that entry in my traceroutes:


2  2a02:390:ffff:ffff:ffff:ffff:ffff:fffc  18.286 ms  17.641 ms  17.248 ms


Think that might be the default route or something. :-}

--
Rachel

[Bill]

hm. ipv6 is actually working again; i didn't do anything. :-)

Don'tcha just love comms 

[Rik]

Always has been a black art, Bill. 

[Rachel]

yeah and it's not working again, so I don't know.

[Bill]

Mine's been flaky since about 3pm, so likely not all of the problems are at your (or my) end