[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: morrowc.lists at gmail.com (Christopher Morrow)
- Date: Fri, 14 Jul 2017 16:52:05 -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>
Yea, I was able to get around the broken-ness with openvpn, but.. that's
sad :( and not everyone has that capability.
On Fri, Jul 14, 2017 at 4:43 PM, Eric Kuhnke <eric.kuhnke at gmail.com> wrote:
> 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
>>
>
>