pay.gov and IPv6

Mon Mar 17 22:41:26 UTC 2014

It was reachable by hand-typed URL, but the machines trying to follow a redirect from the FCC site during payment flow failed. Had to be brought back online, so once it was determined that turning v6 off was sufficient, that was the end if the debugging.

Matthew Kaufman

(Sent from my iPhone)

> On Mar 17, 2014, at 1:02 PM, Jared Mauch <jared at puck.nether.net> wrote:
> 
> One more (498?) set(s) of data points:
> 
> I used RIPE ATLAS probes to check the SSL certificate over IPv6 (a nice way to check reachability)..
> 
> Measurement# 1584700
> 
> You can look through the data to determine where it's not reachable from, but it seems to be "generally reachable" without issue from nearly all the probes.
> 
> JSON link as well:
> 
>    https://atlas.ripe.net/api/v1/measurement/1584700/result/
> 
> - Jared
> 
>> On Mar 17, 2014, at 3:35 PM, Jared Mauch <jared at puck.nether.net> wrote:
>> 
>> No issues for me over IPv6 on Comcast.
>> 
>> Perhaps some local network issue?  Any reported issues if you try to visit http://www.test-ipv6.com/ ?
>> 
>> - Jared
>> 
>>> On Mar 17, 2014, at 2:55 PM, Matthew Kaufman <matthew at matthew.at> wrote:
>>> 
>>> Windows 8 running Google Chrome as the browser.
>>> 
>>> Matthew Kaufman
>>> 
>>>> On 3/17/2014 11:46 AM, Arturo Servin wrote:
>>>> 
>>>> No Happy Eyeballs?
>>>> 
>>>> Perhaps also time to ditch XP and IE for something new as well.
>>>> 
>>>> -as
>>>> 
>>>> 
>>>> 
>>>> 
>>>> On Mon, Mar 17, 2014 at 11:43 AM, Matthew Kaufman <matthew at matthew.at <mailto:matthew at matthew.at>> wrote:
>>>> 
>>>>  Random IPv6 complaint of the day: redirects from FCC.gov to
>>>>  pay.gov <http://pay.gov> fail when clients have IPv6 enabled. Work
>>>>  fine if IPv6 is off. One more set of client computers that should
>>>>  be dual-stacked are now relegated to IPv4-only until someone
>>>>  remembers to turn it back on for each of them... sigh.
>>>> 
>>>>  Matthew Kaufman
> 