Reporting/fixing broken airport/hotel/etc wifi?

Alain Hebert ahebert at pubnix.net
Fri Jul 14 21:18:48 CST 2017


     Could also do: OpenVPN, with a proxy in front, that listen to all 
the ports in case they're using a gateway that transparent proxy some 
protocol.

     2017 version of wack-a-mole.

-----
Alain Hebert                                ahebert at pubnix.net
PubNIX Inc.
50 boul. St-Charles
P.O. Box 26770     Beaconsfield, Quebec     H9W 6G7
Tel: 514-990-5911  http://www.pubnix.net    Fax: 514-990-9443

On 07/14/17 17:04, Ken Chase wrote:
> 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