seems to be trying to document the method to signal to clients how to authenticate. I was having horrible luck with Boingo yesterday at RDU airport with their captive portal and deauthenticating me so just went to cellular data, so wondering if IPv4 doesn’t work well what works for IPv6.
I working on a large airport WiFi deployment right now. IPv6 is "allowed for in the future" but not configured in the short term. With less than 10,000 ephemeral users, we don't expect users to demand IPv6 until most mobile devices and apps come ready to use IPv6 by default.
We use the HotSpot feature on a Mikrotik box as a captive portal. It does not re-direct IPv6 web traffic but it does redirect all IPv4 DNS traffic to a DNS resolver that only answers with A records. Once a device has been authenticated IPv4 DNS traffic goes to a DNS server that will answer with AAAA records also.
We manage 65+ hotels in Canada and the topic of IPv6 for guest internet
connectivity has never been brought up, except by me. It's not a discussion
our vendors or the hotel brands have opened either.
I working on a large airport WiFi deployment right now. IPv6 is "allowed
for in the future" but not configured in the short term. With less than
10,000 ephemeral users, we don't expect users to demand IPv6 until most
mobile devices and apps come ready to use IPv6 by default.
1. Users will never demand ipv6. They demand google and facebook. So that
road goes nowhere
2. What data do you have that most devices and apps are not default-on /
ready for ipv6. My guess is most devices carried by airport users
will accept and use ipv6 address, and most used destinations (google, fb,
netflix, wikipedia, ....) use ipv6
I wonder if the front desk ever understood and forwarded my complaints
about filtered ports (like 22) and other issues with NAT and firewalls.
How do we know what customers "demand" if they don't bother reporting
or are unable to produce a sophisticated report going beyond
"it does not work for me"?
What if Microsoft releases a portable IPv6-only game console one day?
We manage 65+ hotels in Canada and the topic of IPv6 for guest internet
connectivity has never been brought up, except by me. It's not a discussion our
vendors or the hotel brands have opened either.
I would argue customers never asked an IPv4 connection either, they asked for an Internet connection. The Internet is IPv4 and IPv6.
> I working on a large airport WiFi deployment right now. IPv6 is
> "allowed for in the future" but not configured in the short term. With
> less than
> 10,000 ephemeral users, we don't expect users to demand IPv6 until
> most mobile devices and apps come ready to use IPv6 by default.
Absolutely agree. It's not their job to even know to ask for a specific
protocol version in the first place. Their experience should be as seamless
and consistent as possible at all times.
What we should be be concerned about is that the hospitality industry is so
far behind the game on technology. Hotels and restaurants will be some of
the last to drop IPv4 unless they don't realize they're doing it in the
first place.
Unfortunately, the hotel staff wouldn't be able to answer that question.
But they might give them free internet in exchange and hope the guest
doesn't ask any more questions!
Unfortunately, there are still some that would report 2mbit via dsl and
think that was ahead of their competition (and it might be in some
cases...)...
Don't they actually 'demand' "access to content on the internet" ?
Since you seem to have a greenfield deployment, why NOT just put v6 in
place on day0? retrofitting it is surely going to cost time/materials
and probably upgrades to gear that could be avoided by doing it in the
initial installation, right?
+1 and you will most probably see about 50% of the traffic being IPv6 if
you do so. There is lots of IPv6 capable equipment out there just waiting
to see a RA.
What I noticed when I ran a transparent HTTP proxy at my gateway
where it had IPv6 on the outside but the hosts inside did not, a lot
of traffic was converted from IPv4 to IPv6 on the exterior.
As the internet has been moving to HTTPS/HSTS having
DHCP and client-side support of something like
draft-wkumari-dhc-capport is going to become more critical as the days
go by.
While attempting to trigger the captive portal at RDU this
week, Boingo redirected a query for google to their HTTPS to the
portal and since HSTS was enabled I had no way to proceed from there
to the right location to authenticate.
There was also some other broken stuff at RDU so I ended up
just using cellular data.
In message <A24F7CF2-0CD8-4EBA-A211-07BC36988A87@beckman.org>, Mel Beckman writ
es:
Limited municipal budgets is all I can say. IPv6 has a cost, and if they
can put it off till later then that's often good politics.
-mel via cell
IPv4 has a cost as well. May as well just go IPv6-only from day one and
not pay the IPv4 tax at all.
The cost difference between providing IPv6 + IPv4 or just IPv4 from
day 1 should be zero. There should be no re-tooling. You just
select products that support both initially. It's not like products
that support both are more expensive all other things being equal.
