[175619] in North American Network Operators' Group
Re: pay.gov and IPv6
daemon@ATHENA.MIT.EDU (Hugo Slabbert)
Sat Oct 25 15:52:32 2014
X-Original-To: nanog@nanog.org
From: Hugo Slabbert <hslabbert@stargate.ca>
To: Matthew Kaufman <matthew@matthew.at>
Date: Sat, 25 Oct 2014 19:50:58 +0000
In-Reply-To: <544BDD4A.10103@matthew.at>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Why not just use a browser plugin that allow you to disable v6 selectively =
on a per site/domain basis? Most of them just display v4/v6 information, bu=
t 4or6 allows you to quickly set a domain/site as v4 only. Ref https://addo=
ns.mozilla.org/en-US/firefox/addon/4or6/?src=3Dsearch
--
Hugo
On Oct 25, 2014, at 10:26, "Matthew Kaufman" <matthew@matthew.at<mailto:mat=
thew@matthew.at>> wrote:
On 3/17/2014 11:43 AM, Matthew Kaufman wrote:
Random IPv6 complaint of the day: redirects from FCC.gov<http://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 a=
re now relegated to IPv4-only until someone remembers to turn it back on fo=
r each of them... sigh.
Matthew Kaufman
Still broken, 7 months later. And again, I was too busy trying to pay to tr=
y to pull a full set of logs. But if you do something on the FCC site that =
requires payment, the redirection flow dies halfway through if you're comin=
g from IPv6 and works fine if you turn it off... so yet another computer in=
the house has IPv6 disabled until manually turned back on.
Matthew Kaufman
