another tilt at the Verizon FIOS IPv6 windmill

I think it's been about a year and a half since I last looked (and
cried) at the status of FIOS IPv6. As far as I can tell, there's been no
new official news since 2013. We're deploying IPv6 at the university I
work at, so IPv6 at home is moving from "wish I had it to play with"
towards "need to have it to work from home". So it seems I either cancel
my fios and go with business class cable (I live in Time Warner
territory and it looks like they're good to go with IPv6) or set up a
tunnel with HE. Or pray Google fiber comes to my neck of the woods.

Any new rumors floating around? Any Verizon employees interested in
posting anonymously and explaining what on earth is going on inside the
company? Any secret phone numbers to call to get in on an alpha/beta
test in the So Cal area ;)?

If nothing else, it always feels better to hear other people say how
ridiculous this is too <sigh> :).

Thanks...

Yes, move your business to TWC. TWC has a proven v6 deployment and is
actively engaged in the community, as where vz Fios is not.

Business only understand $

CB

The only reason I have FIOS is because they gave me a 2 year deal of
15/15 internet for $30/month. Their advertising is basically just lies
and I wouldn't hold my breath over IPv6; I have to run stunnel so I can
send email from home because they don't even use TLS..... Having said
that, I have an HE tunnel which works flawlessly with my Asus RT-N66U
router....

Just set up the tunnel. It works beautifully.

And thank you, HE.net, for being such a stellar tech leader!

-mel

Yah, cheap bastards :). I've got 50/50 fios right now; TWC can match the
downstream but it looks like the upstream maxes out at 20 :(. At least
for standard business internet, looks like their "Dedicated Internet
Access" can be had at up to 10G. Arg, no prices for anything online
though. I'd really hate to lose my upstream and I don't think I want to
know how much DIA costs ;). I'm paying $125 for 50/50 with 5 static IPs
right now. And I'm actually pretty happy with it other than the dead
silence regarding IPv6.

I suppose the average "business" user doesn't even know what IPv6 is
<sigh>, and Verizon probably doesn't care if they lose a handful of
techies :(. What has Frontier done about IPv6 in the fios territories
they've already purchased? Assuming the deal goes though I'll be a
Frontier customer by this time next year...

Hmm, I just recently set up my mail client to use Verizon's smtp
servers, and TLS seemed to work fine for me. smtp.verizon.net port 465,
smtps. Took me a while to sort out smtp.verizon.net vs relay.verizon.net
vs outgoing.verizon.net, but once I found the right one it's been
working fine.

Just set up the tunnel. It works beautifully.

Yeah, I probably will. Shouldn't expose my bluff, but I probably won't
switch to business cable, I actually use my upstream 8-/. But I needed
to get in one last rant before I went that way :).

And thank you, HE.net, for being such a stellar tech leader!

And thanks in advance from a soon-to-be tunnel requestor ;).

I think it's been about a year and a half since I last looked (and
cried) at the status of FIOS IPv6. As far as I can tell, there's been no
new official news since 2013. We're deploying IPv6 at the university I
work at, so IPv6 at home is moving from "wish I had it to play with"
towards "need to have it to work from home". So it seems I either cancel
my fios and go with business class cable (I live in Time Warner
territory and it looks like they're good to go with IPv6) or set up a
tunnel with HE. Or pray Google fiber comes to my neck of the woods.

I've shaken this tree many times in the 3 years I've had FIOS (Pittsburgh, PA), and the results from Verizon have not been promising. I call their
customer service center to ask about IPv6 availability every few months,
and get the electronic equivalent of a blank stare. Promises to "make a notation in my account" don't mean much if no one who is in a position to act on that notation will ever read it.

I've also asked our Verizon rep through $dayjob about the v6 deployment status, and Verizon is so segmented and siloed internally, that it's been nearly impossible for them to find the right people.

As others have suggested, set up a tunnel with Hurricane Electric, and move on with life. I've had one for probably two years, and it's been rock-solid. While it would be great to have native v6 from Verizon, it doesn't look like it'll happen any time soon.

From what I understand, many of the ONTs and possibly set-top boxes if

you have FIOS TV service don't play nicely with v6. I don't know how true that is, or if those are still issues. I do recall hearing that upgrading
to their Quantum service might get you a different ONT, but if that's true, I don't know if the those ONTs are any more v6-friendly. I don't
know if there are any v6 compatibility issues further up the chain from the ONT.

jms

smtps was deprecated years ago and is not implemented in postfix, hence
the need for stunnel. I should have said they don't implement STARTTLS
on either 25 or 587.

From: John Peach
Sent: Monday, July 13, 2015 5:02 AM

smtps was deprecated years ago and is not implemented in postfix, hence
the need for stunnel. I should have said they don't implement STARTTLS
on either 25 or 587.

Oh, ok; I assumed you were talking about a client, not an MTA. Why are you
relaying through Verizon rather than just sending directly? My home MTA on
FIOS hasn't had any problems sending mail to the Internet at large, although
I do have a static IP with appropriate matching/reverse DNS.

Seems to be a lot less noise on this iteration of the shake fist at
Verizon's lack of IPv6 thread, I guess everybody is pretty much burned out
and given up 8-/. Verizon should just update their IPv6 status page with a
link to hurricane electric's tunnel broker page <sigh>.

> From: John Peach
> Sent: Monday, July 13, 2015 5:02 AM
>
> smtps was deprecated years ago and is not implemented in postfix,
> hence the need for stunnel. I should have said they don't implement
> STARTTLS on either 25 or 587.

Oh, ok; I assumed you were talking about a client, not an MTA. Why
are you relaying through Verizon rather than just sending directly?
My home MTA on FIOS hasn't had any problems sending mail to the
Internet at large, although I do have a static IP with appropriate
matching/reverse DNS.

I'm cheap :slight_smile:
For $30 a month they don't allow port 25 outbound.

Seems to be a lot less noise on this iteration of the shake fist at
Verizon's lack of IPv6 thread, I guess everybody is pretty much
burned out and given up 8-/. Verizon should just update their IPv6
status page with a link to hurricane electric's tunnel broker page
<sigh>.

The fact that my router supports the HE tunnel natively makes this
completely painless.

Yes, because TWC-BC's IPv6 support is stellar. Sorry, I misspelled "non-existent".

Their "DIA" (metro-e) stuff, *might*, but I doubt it.

For a long time, Verizon's general "What is IPv6?" page stated the standard assignment for customers was a /56... or 56 LANs. *headdesk*.

jms

I think that's exactly what's occurred. There was a point where I spent
several years wasting time sending notes to the sales rep, opening
support tickets, trolling them on twitter and their own forum, etc., all
with either no useful answer or no answer at all; ultimately I gave up
and replaced the inexpensive Fios connection with a more $$ TWTC
circuit. I'd flip it back to Fios if they rolled out v6 since it was a
lot less expensive and had been perfectly reliable at the location that
used it.

David

David,
Did you consider running an IPv6 tunnel through HE.net?

-mel via cell

Tunnels work, but they really are getting old. I have run 3ffe:: 6bone, HE tunnels, and (currently) aiccu. They all work very reliably, and I have immense gratitude towards the people who commit the time, the hardware, and the software, to making that go. But the bottom line is that 200+ms RTTs to my servers over v6 tunnels simply can't compete with 20ms RTTs on native v4. I know my code works over v6, but how can I ever know it works well when I'm behind a v6 dialup link?

This past weekend I bit the projectile and decided to flip my service over to Teksavvy. The latter have native v6, claim to offer /48s, and have the audacity to charge me $10/month less than Telus. I'm game. More importantly, after eight years of Telus promising an IPv6 beta, I can tell them to
see https://orthanc.ca/figure-1 :stuck_out_tongue:

--lyndon

David,
Did you consider running an IPv6 tunnel through HE.net?

We couldn't get the desired throughput via HE tunnel. We tried it, then
switched to v6 through VPN using a slice of our own allocation, but
ultimately didn't want that overhead either.

David

For a bit of fun, the results after 30 minutes of https://orthanc.ca/figure-1 being out on the nanog list:

  IPv4: 315
  IPv6: 22

This is strictly GETs on the target page, not tainted by CSS or favicon nonsense.

I don't know what this says about the proclivity of Nanog readers to blindly click on email URLs. (But the delineation between web and MUA email client user behaviours is ... interesting ...)

On 7/13/15, 3:43 PM, "NANOG on behalf of Ricky Beam"

Yes, move your business to TWC. TWC has a proven v6 deployment and is
actively engaged in the community, as where vz Fios is not.

Yes, because TWC-BC's IPv6 support is stellar. Sorry, I misspelled
"non-existent".

Business Class DOCSIS customers get a prefix automatically (unless you
provide your own gateway and DHCPv6 isn¹t enabled). Since it¹s dynamic, it
might change; working on providing stable prefixes.

Their "DIA" (metro-e) stuff, *might*, but I doubt it.

Does, but since it requires BGP or static route configuration, you have to
ask.

Lee

I looked last night at the office in Cary, NC. NO RAs are seen on the link coming from the Ubee (bridged) providing our dynamic/DOCSIS connection. Without an RA, nothing will attempt IPv6.

(I've not checked the one in Raleigh that's also a hotspot)

Residential? sure, there's lot of v6 there -- has been for over a year. But as I'm an Earthlink customer, and those morons cannot be bothered to give TWC one of their *5* UNUSED /32's, all I get is:
  (IA_PD IAID:327681 T1:0 T2:0 (status code no prefixes))

--Ricky