www.eftps.gov contact

[Jared Mauch]

On Dec 18, 2012, at 10:38 AM, Darren Pilgrim wrote:

> On 2012-12-18 07:24, Jared Mauch wrote:
>> Seems to work for me.. perhaps a local ipv6 issue for you?
> 
> The issue occurs at multiple sites connected to different ISPs.  Some sites get IPv6 via 6in4, some are native dual-stack.  I have one host where I can reach port 80 over IPv6, but not port 443.  I'm fairly sure this is a path MTU issue on EFTPS' end.

Like I said, I'm having no trouble connecting via IPv6 from puck.nether.net (you can try to traceroute6/ping6 it).

puck:~$ traceroute6 www.eftps.gov.
traceroute to www.eftps.gov. (2620:10f:400e:a::12), 30 hops max, 80 byte packets
 1  ge-0-7-0-22.r05.chcgil09.us.bb.gin.ntt.net (2001:418:3f4:1::1)  0.809 ms  0.846 ms  0.961 ms
 2  ae-6.r21.chcgil09.us.bb.gin.ntt.net (2001:418:0:2000::e1)  0.195 ms  0.136 ms  0.183 ms
 3  ae-4.r21.dllstx09.us.bb.gin.ntt.net (2001:418:0:2000::81)  137.733 ms  137.783 ms  43.145 ms
 4  ae-5.r07.dllstx09.us.bb.gin.ntt.net (2001:418:0:2000::1f2)  31.186 ms  27.814 ms  31.444 ms
 5  2600:807:2::1 (2600:807:2::1)  35.207 ms  59.030 ms  35.244 ms
 6  2600:805:51f::12 (2600:805:51f::12)  82.765 ms  87.069 ms  87.411 ms
 7  2600:805:51f::12 (2600:805:51f::12)  77.901 ms  76.984 ms  73.573 ms
 8  2620:10f:400e:1::6 (2620:10f:400e:1::6)  77.204 ms  77.435 ms  77.221 ms
...

appears to be where it times out for me from the udp-port unreachable standpoint, but the tcp session starts up just fine over HTTPS, and since the main page is 11.7kb, I suspect it's not a p-mtu issue.  I suspect you are having other networking issues, but without further data on your source(s), it's hard to say.

Can you reach https://puck.nether.net/ over IPv6?

- Jared