[195318] in North American Network Operators' Group
Re: Reporting/fixing broken airport/hotel/etc wifi?
daemon@ATHENA.MIT.EDU (Guillaume Tournat)
Fri Jul 14 18:11:02 2017
X-Original-To: nanog@nanog.org
From: Guillaume Tournat <guillaume@ironie.org>
In-Reply-To: <20170714210453.GN3506@sizone.org>
Date: Sat, 15 Jul 2017 00:10:56 +0200
To: Ken Chase <math@sizone.org>
Cc: "nanog@nanog.org list" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Using sshd on port 443, I can ssh my box with a tunnel to a local squid. My b=
rowser then use this tunneled proxy to go to internet.=20
Private and secure.=20
> Le 14 juil. 2017 =C3=A0 23:04, Ken Chase <math@sizone.org> a =C3=A9crit :
>=20
>=20
> This is exactly why i have SSHd on port 443 and 53 on one of my boxes/IPs.=
Once
> I got SSH sky's the limit on what I can fix/setup/tunnel.
>=20
> /kc
>=20
> On Fri, Jul 14, 2017 at 01:43:21PM -0700, Eric Kuhnke said:
>> I've found many times it's the other way around, with highly restrictive
>> captive portals that only allow traffic to 80 and 443. This is exactly th=
e
>> reason why I have an OpenVPN server running in tcp mode (not udp) on 443.=
>>=20
>>=20
>> On Fri, Jul 14, 2017 at 1:33 PM, Christopher Morrow <morrowc.lists@gmail.=
com
>>> wrote:
>>=20
>>> Was there a list of folks collecting to provide fix actions for
>>> hotel/airport/etc?
>>>=20
>>> Seems that IAD / Washington Dulles don't like "random" tcp/443 sites on t=
he
>>> internet? 173.194.205.129
>>>=20
>>> for instance, ping, traceroute, http but no https :(
>>> https works just fine from lots of other places on the tubes... just not=
>>> the dulles wifi.
>>>=20
>>> -chris
>>>=20
>=20
> --
> Ken Chase - math@sizone.org Guelph Canada
