I'm connecting to: [karl@NewFS ~]$ ping6 svn.freebsd.org PING6(56=40+8+8 bytes) 2600:8807:8600:7941:230:48ff:fe9f:1d6 --> 2610:1c1:1:606c::e6a:0 16 bytes from 2610:1c1:1:606c::e6a:0, icmp_seq=0 hlim=54 time=58.461 ms 16 bytes from 2610:1c1:1:606c::e6a:0, icmp_seq=1 hlim=54 time=58.114 ms
Which appears to be the same place you are pulling from. On 12/9/2018 20:04, Jamie Landeg-Jones wrote: > Karl Denninger <k...@denninger.net> wrote: > >> Since I can't find evidence of a FreeBSD problem internally this is more >> of a "is anyone else seeing this on Cox?" sort of request; what I find >> especially interesting, however, is that it /always /happens when >> talking to Project machines for updates whether for packages or SVN, >> which is why I'm bringing it here. > I'm not on cox, but i do daily svn's from host svnmir.nyi.freebsd.org. > (2610:1c1:1:606c::e6a:0) to my colo in NJ. I've seen no problems (indeed, > a just did a manual checkout and confirmed it was on ip6) > > The thing is, you don't say which of the geo-servers you are connecting to.. > > I'd humbly suggest creating a temporary ip6-4 tunnel from > https://tunnelbroker.net/ - they have POPs in Miami and New York, amongst > other places. > > That would at least help you test the non-cox ip6 side of things, especially > if you can get a 6-4 server close to you. > > cheers, jamie -- Karl Denninger k...@denninger.net <mailto:k...@denninger.net> /The Market Ticker/ /[S/MIME encrypted email preferred]/
smime.p7s
Description: S/MIME Cryptographic Signature
