[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Reporting/fixing broken airport/hotel/etc wifi?
- Subject: Reporting/fixing broken airport/hotel/etc wifi?
- From: math at sizone.org (Ken Chase)
- Date: Fri, 14 Jul 2017 17:04:53 -0400
- In-reply-to: <CAB69EHjwXpqTTK7WDLnHTD3ZtROgCKJg_qEgngK8b9hxc_p=9g@mail.gmail.com>
- References: <CAL9jLaYzRW1iZGxm1p1bK4G4OvV4SQ+5z5tusS4-K=UHvO9+Jw@mail.gmail.com> <CAB69EHjwXpqTTK7WDLnHTD3ZtROgCKJg_qEgngK8b9hxc_p=9g@mail.gmail.com>
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