Re: Treasurydirect.gov unreachable over IPv6?

[Chris Adams]

Once upon a time, Jay Hennigan  said:
> On 5/17/23 12:19, Jesse Rehmer wrote:
> > From Spectrum, I'm able to hit port 80, but the redirect to 443 fails.
> 
> Smells like broken PMTUD to me.

Yeah.  From Google Fiber, IPv4 works.  IPv6 connects on port 80, gets
redirected to HTTPS, which connects on port 443 but fails in SSL
negotiation.

I wonder if some over-zealous network admin blocked all ICMPv6.
-- 
Chris Adams 

Re: Treasurydirect.gov unreachable over IPv6?

[Jay Hennigan]

On 5/17/23 12:19, Jesse Rehmer wrote:

 From Spectrum, I'm able to hit port 80, but the redirect to 443 fails.


Smells like broken PMTUD to me.

--
Jay Hennigan - j...@west.net
Network Engineering - CCIE #7880
503 897-8550 - WB6RDV

Re: Treasurydirect.gov unreachable over IPv6?

[Jesse Rehmer]

From Spectrum, I'm able to hit port 80, but the redirect to 443 fails.


% curl -6IL treasurydirect.gov
HTTP/1.0 302 Moved Temporarily
Location: https://treasurydirect.gov/
Server: BigIP
Connection: Keep-Alive
Content-Length: 0

curl: (35) Recv failure: Connection reset by peer

Cheers,

Jesse

On 5/17/23 1:30 PM, holow29 wrote:
Is anyone able to reach treasurydirect.gov  
over IPv6? Unable to do so over Verizon Fios, and I'm not sure if it is 
a routing issue or an issue on Treasury's end.

Re: Treasurydirect.gov unreachable over IPv6?

[holow29]

Thanks all.
Given that traceroute can reach Zayo and Zayo appears to have route to
Treasury's AS13506, is it reasonable to assume this is on Treasury's end,
potentially blocking traffic from VZ's AS701?

@John Lightfoot: Yes, they rolled out largely throughout last year.

On Wed, May 17, 2023 at 3:24 PM John Lightfoot  wrote:

> Verizon has IPv6?
>
>
>
> *From: *NANOG  on behalf of
> Jay Hennigan 
> *Date: *Wednesday, May 17, 2023 at 3:21 PM
> *To: *nanog@nanog.org 
> *Subject: *Re: Treasurydirect.gov unreachable over IPv6?
>
> On 5/17/23 11:30, holow29 wrote:
> > Is anyone able to reach treasurydirect.gov <http://treasurydirect.gov>
> > over IPv6? Unable to do so over Verizon Fios, and I'm not sure if it is
> > a routing issue or an issue on Treasury's end.
>
> Reachable from AS4927 in California.
>
> --
> Jay Hennigan - j...@west.net
> Network Engineering - CCIE #7880
> 503 897-8550 - WB6RDV
>

Re: Treasurydirect.gov unreachable over IPv6?

[John Lightfoot]

Verizon has IPv6?

From: NANOG  on behalf of Jay 
Hennigan 
Date: Wednesday, May 17, 2023 at 3:21 PM
To: nanog@nanog.org 
Subject: Re: Treasurydirect.gov unreachable over IPv6?
On 5/17/23 11:30, holow29 wrote:
> Is anyone able to reach treasurydirect.gov <http://treasurydirect.gov>
> over IPv6? Unable to do so over Verizon Fios, and I'm not sure if it is
> a routing issue or an issue on Treasury's end.

Reachable from AS4927 in California.

--
Jay Hennigan - j...@west.net
Network Engineering - CCIE #7880
503 897-8550 - WB6RDV

Re: Treasurydirect.gov unreachable over IPv6?

[Jay Hennigan]

On 5/17/23 11:30, holow29 wrote:
Is anyone able to reach treasurydirect.gov  
over IPv6? Unable to do so over Verizon Fios, and I'm not sure if it is 
a routing issue or an issue on Treasury's end.


Reachable from AS4927 in California.

--
Jay Hennigan - j...@west.net
Network Engineering - CCIE #7880
503 897-8550 - WB6RDV

Re: Treasurydirect.gov unreachable over IPv6?

[John Levine]

It appears that holow29  said:
>-=-=-=-=-=-
>
>Is anyone able to reach treasurydirect.gov over IPv6? Unable to do so over
>Verizon Fios, and I'm not sure if it is a routing issue or an issue on
>Treasury's end.

Works fine via a HE tunnel.

R's,
John

Re: Treasurydirect.gov unreachable over IPv6?

[Daniel Marks via NANOG]

You can utilize online (i.e. https://dnstools.ws/) or ISP looking glass 
tools to check for routing issues.


It's up for us via AS12129

On 5/17/2023 2:30 PM, holow29 wrote:
Is anyone able to reach treasurydirect.gov  
over IPv6? Unable to do so over Verizon Fios, and I'm not sure if it 
is a routing issue or an issue on Treasury's end.