Bug 190602

Summary: forums not reachable over IPv6 (but provide IPv6 AAAA record)
Product: Services Reporter: Michael Gmelin <grembo>
Component: ForumsAssignee: Forum Adminstrators <forum-admins>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: ---    
Version: unspecified   
Hardware: Any   
OS: Any   

Description Michael Gmelin freebsd_committer freebsd_triage 2014-06-04 08:46:53 UTC
# host -t a forums.freebsd.org
forums.freebsd.org has address 149.20.54.209

# host -t aaaa forums.freebsd.org
forums.freebsd.org has IPv6 address 2001:4f8:3:36::209


IPv4

# ping forums.freebsd.org
PING forums.freebsd.org (149.20.54.209): 56 data bytes
64 bytes from 149.20.54.209: icmp_seq=0 ttl=55 time=187.456 ms
64 bytes from 149.20.54.209: icmp_seq=1 ttl=55 time=186.347 ms

IPv6

# ping6 forums.freebsd.oorg
PING6(56=40+8+8 bytes) ..... --> 2001:4f8:3:36::209
^C
--- forums.freebsd.org ping6 statistics ---
4 packets transmitted, 0 packets received, 100.0% packet loss

vs.

# ping6 www.google.com    
PING6(56=40+8+8 bytes) ..... --> 2a00:1450:4016:801::1014
16 bytes from 2a00:1450:4016:801::1014, icmp_seq=0 hlim=56 time=20.246 ms
16 bytes from 2a00:1450:4016:801::1014, icmp_seq=1 hlim=56 time=20.148 ms
^C
--- www.google.com ping6 statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 20.148/20.197/20.246/0.049 ms

Fetch over IPv4

# time fetch -4 -o - https://forums.freebsd.org >/dev/null
-                                                       46 kB  123 kBps

real    0m1.515s
user    0m0.560s
sys     0m0.145s

Fetch over IPv6

# time fetch -6 -o - https://forums.freebsd.org >/dev/null
fetch: https://forums.freebsd.org: Host is down

real    0m18.554s
user    0m0.021s
sys     0m0.016s

vs

# time fetch -6 -o - https://www.google.com >/dev/null    
-                                                       11 kB 7414 kBps

real    0m0.754s
user    0m0.523s
sys     0m0.066s
Comment 1 Michael Gmelin freebsd_committer freebsd_triage 2014-06-16 18:36:53 UTC
As of today this seems to work again.
Comment 2 Michael Gmelin freebsd_committer freebsd_triage 2015-06-27 09:09:20 UTC
Never got a response on this one, but apparently it got fixed -> Closed