forums.freebsd.org doesn't respond on IPv6

Very slow for me these last few days. I've hardwired the IPv4 address in /etc/hosts and the forum is absolutely flying now. IPv4 only for this forum for now.
 
If you use Firefox you can set network.dns.ipv4OnlyDomains in about:config.
 
And now it's broken again...

Code:
> traceroute6 -n forums.freebsd.org
traceroute6 to forums.freebsd.org (2001:4f8:3:36::209) from 2a02:2770::21a:4aff:fe5f:62a9, 64 hops max, 12 byte packets
 1  2a02:2770::1  7.305 ms  1.801 ms  3.691 ms
 2  2a02:2770:2::16  0.943 ms  1.221 ms  0.885 ms
 3  2001:7f8:1::a500:6939:1  4.916 ms  1.548 ms  1.472 ms
 4  2001:470:0:3f::1  8.203 ms  14.467 ms  18.197 ms
 5  2001:470:0:128::1  69.138 ms  66.030 ms  66.862 ms
 6  2001:470:0:1c6::2  84.187 ms  84.131 ms  85.772 ms
 7  2001:470:1:34::2  127.144 ms  129.486 ms  127.396 ms
 8  2001:500:71:6::1  137.994 ms  126.911 ms  126.830 ms
 9  2001:4f8:0:1::4a:1  135.682 ms  136.098 ms  136.662 ms
10  2001:4f8:1b:1::8:2  137.746 ms  131.126 ms  129.909 ms
11  * * *
12  * * *
13  * * *
14  *
    2001:4f8:1b:1::8:2  2866.846 ms !A *

Broken at ISC, again.
 
Yeah, it seems to be the common denominator each time IPv6 connectivity to here goes down.
 
Hurray! A response, still not working but at least somebody is looking into it.

Hello,
I am looking into this problem now, and unfortunately I don't see an overall network
issue within ISC. I do see that forums is not responding to IPv6 at all right now.
Is that intentional?

Last time this happened it was intermittent, and when Leo performed a trace back to
your IPv6 source, he encountered problems when transiting AS5580.

We'll keep looking into it and see if there any other customers with similar issues
that may give us a clue as to the the root cause.

Thanks,
Jeremiah

Could a few other people post their traceroutes? Working and not working, if possible.
 
This trace is also originating in Slovakia, though different region as I pasted before:

Code:
traceroute to forums.freebsd.org (2001:4f8:3:36::209), 30 hops max, 80 byte packets
 1 2001:4118:804::1 0.451 ms 0.470 ms 0.452 ms
 2 2001:4118:0:2:c 4.070 ms 4.107 ms 4.165 ms
 3 2001:628:0:3::1 5.349 ms 5.582 ms 5.690 ms
 4 2001:7f8:30:0:2:1:0:6939 10.307 ms 10.335 ms 10.357 ms
 5 2001:470:0:284::2 12.972 ms 12.979 ms 12.994 ms
 6 2001:470:0:213::1 18.173 ms 18.136 ms 18.150 ms
 7 2001:470:0:21b::2 27.529 ms 27.568 ms 27.508 ms
 8 2001:470:0:1b1::1 105.978 ms 106.018 ms 105.975 ms
 9 2001:470:0:1b5::2 118.302 ms 118.356 ms 118.266 ms
10 2001:470:0:ce::2 185.652 ms 185.501 ms 185.498 ms
11 2001:500:61:6::1 185.468 ms 185.612 ms 185.702 ms
12 2001:4f8:0:1::49:1 185.546 ms 185.249 ms 185.173 ms
13 2001:4f8:1b:1::8:2 188.291 ms 187.424 ms 186.887 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 2001:4f8:1b:1::8:2 4194.273 ms !H 4194.252 ms !H 4194.233 ms !
 
Code:
traceroute6 to forums.freebsd.org (2001:4f8:3:36::209) from 2a01:348:294::1, 64 hops max, 12 byte packets
 1  2a01:348:6:45c::1  20.825 ms  19.611 ms  20.151 ms
 2  2a01:348:0:4:0:3:1:1  19.666 ms  20.177 ms  21.154 ms
 3  2a01:348:0:4:0:3:0:1  21.175 ms  20.611 ms  20.207 ms
 4  2a01:348::36:1:1  21.363 ms  21.428 ms  21.139 ms
 5  2a01:348::24:1:1  21.136 ms  21.862 ms  21.913 ms
 6  2a01:348::40:1:1  23.365 ms  22.345 ms  23.138 ms
 7  2a01:348::41:1:1  21.899 ms  24.621 ms  24.354 ms
 8  2a01:348::17:0:1  20.879 ms  21.163 ms  21.398 ms
 9  2001:7f8:17::1b1b:1  21.428 ms  23.805 ms  23.621 ms
10  2001:470:0:128::1  89.403 ms  94.831 ms  100.491 ms
11  2001:470:0:1c6::2  106.648 ms  114.330 ms  107.058 ms
12  2001:470:1:34::2  168.521 ms  169.213 ms  168.710 ms
13  2001:500:71:6::1  168.287 ms  168.447 ms  168.476 ms
14  2001:4f8:0:1::4a:1  170.197 ms  169.210 ms  169.469 ms
15  2001:4f8:1b:1::8:2  171.518 ms  170.409 ms  172.404 ms
16  * *
    2001:4f8:1b:1::8:2  2122.118 ms !A
 
It should be good now. It seems to be a transient issue that I will need to track down.

I have setup monitoring on HTTP via IPv6 so I will be notified when it crops up again.
 
Broken, again :(

Code:
dice@vps-2417-1:~> traceroute6 -n forums.freebsd.org
traceroute6 to forums.freebsd.org (2001:4f8:3:36::209) from 2a02:2770:3:0:21a:4aff:fe5f:62a9, 64 hops max, 12 byte packets
 1  2a02:2770:3::1  6.624 ms  1.561 ms  1.201 ms
 2  2a02:2770:2::20  0.497 ms  0.345 ms  0.348 ms
 3  2001:7f8:13::a500:6939:1  0.869 ms  1.049 ms  12.208 ms
 4  2001:470:0:3f::1  7.878 ms  16.620 ms  7.930 ms
 5  2001:470:0:128::1  70.097 ms  69.802 ms  69.206 ms
 6  2001:470:0:298::1  91.423 ms  90.772 ms  90.443 ms
 7  2001:470:1:34::2  134.153 ms  134.078 ms  134.356 ms
 8  2001:500:71:6::1  131.765 ms  132.581 ms  131.400 ms
 9  2001:4f8:0:1::4a:1  135.484 ms  135.834 ms  135.479 ms
10  2001:4f8:1b:1::8:2  137.910 ms  137.767 ms  137.434 ms
11  2001:4f8:1b:1::8:2  8294.958 ms !A * *
 
I am not sure if I have configured something wrong on my router or if the forums are down on IPv6 again. What is your monitoring telling you, @brd? :D
 
There seems to be a current issue again, I can reproduce the situation which @SirDice had last year:

Code:
smtp2:/home/peter $ traceroute6 -n forums.freebsd.org
traceroute6 to forums.freebsd.org (2001:4f8:3:36::209) from 2a01:7c8:aaaf:36f::1, 64 hops max, 12 byte packets
 1  2a01:7c8:aaaf::2  0.379 ms  3.593 ms  0.357 ms
 2  2001:7f8:1::a500:6939:1  0.812 ms  0.751 ms  0.770 ms
 3  2001:470:0:2d0::1  7.965 ms  8.020 ms  8.018 ms
 4  2001:470:0:2cf::2  80.351 ms  74.650 ms  74.687 ms
 5  2001:470:0:298::1  91.054 ms  92.110 ms  99.735 ms
 6  2001:470:1:34::2  91.560 ms  91.686 ms  91.145 ms
 7  2001:500:71:6::1  91.586 ms  91.406 ms  91.622 ms
 8  2001:4f8:0:1::4a:1  143.458 ms  143.133 ms  143.367 ms
 9  2001:4f8:1b:1::8:2  146.428 ms  146.014 ms  145.654 ms
10  * *
    2001:4f8:1b:1::8:2  4143.397 ms !A
11  *
    2001:4f8:1b:1::8:2  4167.449 ms !A  9158.427 ms !A
 
Last edited by a moderator:
Oddly enough it seems to be working fine from my side at the moment.

In Firefox (about:config) search for network.dns.ipv4OnlyDomains and set it to "forums.freebsd.org". That should stop the delay and use IPv4 for forums.freebsd.org.
 
Appears to be stuck again.

Code:
dice@armitage:~ % fetch -6 https://forums.freebsd.org
fetch: https://forums.freebsd.org: Host is down
dice@armitage:~ % fetch -4 https://forums.freebsd.org
forums.freebsd.org                            100% of   61 kB  323 kBps 00m00s
 
site loads for me but I am loading over ipv4, I have not disabled ipv6 locally, so chrome specifically chose to load over ipv4 for whatever reason, which I guess its because it detected an issue on ipv6.
 
Works for me now:

Code:
$ fetch -6 https://forums.freebsd.org
forums.freebsd.org                            100% of   61 kB  284 kBps 00m01s
$ file forums.freebsd.org
forums.freebsd.org: HTML document, UTF-8 Unicode text, with very long lines
$
 
Confirmed.
Code:
dice@armitage:~ % fetch -6 https://forums.freebsd.org
forums.freebsd.org                            100% of   61 kB  355 kBps 00m00s
 
This was reported to the admins via BugZilla and passed on by me to Brad, who handles the network side of the forums. So I guess it has been tackled. There was indeed not a single IPv6 connection on the forum server, so there was an external cause somewhere upstream.
 
Since I configured my Firefox to always use IPv4 for the forums I didn't notice it myself. But somebody was having issues and posted about it to the Facebook group. I do believe he's also the one that opened the PR for it.
 
Back
Top