[120029] in North American Network Operators' Group
Re: Breaking the internet (hotels, guestnet style)
daemon@ATHENA.MIT.EDU (Owen DeLong)
Tue Dec 8 10:18:35 2009
From: Owen DeLong <owen@delong.com>
In-Reply-To: <4B1E19EE.40409@accessplus.com.au>
Date: Tue, 8 Dec 2009 07:14:47 -0800
To: Andrew Cox <andrew@accessplus.com.au>
Cc: nanog@nanog.org, jgreco@ns.sol.net
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Dec 8, 2009, at 1:18 AM, Andrew Cox wrote:
> Sounds like a great idea in theory but would require OS support or a =
dual-hotspot setup that provided for both options until support was =
expected.
> Until such time it's simply unworkable.
>=20
> That and as mentioned in my previous post, the setup we have *just =
works* for users who don't have the permissions to change off of a =
static IP and use DHCP on their laptops.
>=20
And it just breaks for those of us who actually expect "internet access" =
to mean
access to the internet, not just the web.
I make a habbit of calling support and pushing the issue hard through =
multiple
layers until I finally get a management denial, then, demand refunds of =
my
connectivity charges every time I encounter this at a hotel.
I figure that the reason you guys deploy what "just works" as you put it =
is because
it lowers your support costs, so, I do what I can to increase the =
support costs of
delivering a broken internet.
I encourage others to do the same.
Owen
> Andrew
>>=20
>> This really should be a DHCP option which points to the =
authentification
>> server using ip addresses. This should be return to clients even
>> if they don't request it. Web browers could have a hot-spot button =
that
>> retrieves this option then connects using the value returned.
>>=20
>> No need to compromise the DNS or intercept http.
>>=20
>> Mark
>> =20
