Reporting/fixing broken airport/hotel/etc wifi?

Guillaume Tournat guillaume at ironie.org
Fri Jul 14 22:10:56 CST 2017


Using sshd on port 443, I can ssh my box with a tunnel to a local squid. My browser then use this tunneled proxy to go to internet. 

Private and secure. 


> Le 14 juil. 2017 à 23:04, Ken Chase <math at sizone.org> a écrit :
> 
> 
> 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.
> 
> /kc
> 
> 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 the
>> reason why I have an OpenVPN server running in tcp mode (not udp) on 443.
>> 
>> 
>> On Fri, Jul 14, 2017 at 1:33 PM, Christopher Morrow <morrowc.lists at gmail.com
>>> wrote:
>> 
>>> Was there a list of folks collecting to provide fix actions for
>>> hotel/airport/etc?
>>> 
>>> Seems that IAD / Washington Dulles don't like "random" tcp/443 sites on the
>>> internet?  173.194.205.129
>>> 
>>> 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.
>>> 
>>> -chris
>>> 
> 
> --
> Ken Chase - math at sizone.org Guelph Canada



More information about the NANOG mailing list