Re: Do ISP's collect and analyze traffic of users?

On 5/17/23 12:06 AM, Mark Tinka wrote: On 5/16/23 16:55, Saku Ytti wrote: I can't tell what large is. But I've worked for enterprise ISP and consumer ISPs, and none of the shops I worked for had capability to monetise information they had. And the information they had was increasingly low

Re: Treasurydirect.gov unreachable over IPv6?

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

NANOG 88 Agenda is Now Available! + More

*NANOG 88 Agenda is Now Available! * *Join Us for our 88th Community-Wide Gathering 12-14, June* Sync your calendars today and plan out your NANOG 88 experience! *VIEW AGENDA * *What's Trending on the Mailing List? * *Find or Give a Solution on

Re: Treasurydirect.gov unreachable over IPv6?

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

Re: Treasurydirect.gov unreachable over IPv6?

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

Treasurydirect.gov unreachable over IPv6?

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?

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?

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 > over IPv6?

Re: Treasurydirect.gov unreachable over IPv6?

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

Re: Treasurydirect.gov unreachable over IPv6?

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

Re: Treasurydirect.gov unreachable over IPv6?

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

Re: Do ISP's collect and analyze traffic of users?

> Why would there be a difference between wireless and wired? Service provisioning in a mobile network is at the device level and tied to an individual vs. at a home shared across many devices & people. So just starting off there is more visibility to say X traffic is related to Y person. Then

[NANOG-announce] NANOG 88 Agenda is Now Available! + More

*NANOG 88 Agenda is Now Available! * *Join Us for our 88th Community-Wide Gathering 12-14, June* Sync your calendars today and plan out your NANOG 88 experience! *VIEW AGENDA * *What's Trending on the Mailing List? * *Find or Give a Solution on