sigh. well that was some fun hours debugging; not. thanks randy

If you really need them, you'll need to use some sort of tunneling mechanism, ie PPTP. Regards, Filip On 11.9.2016 21:21, Ryan, Spencer wrote:

Having those ports exposed to the Internet is scary. Comcast is right in blocking them.

Sent from my Verizon, Samsung Galaxy smartphone

-------- Original message -------- From: Randy Bush <randy@psg.com> Date: 9/11/16 2:48 PM (GMT-05:00) To: Ca By <cb.list6@gmail.com> Cc: North American Network Operators' Group <nanog@nanog.org> Subject: Re: comcast and msoft ports

sigh. well that was some fun hours debugging; not.

thanks

randy

On Sep 11, 2016, at 4:02 PM, Ca By <cb.list6@gmail.com> wrote:

On Sunday, September 11, 2016, Filip Hruska <fhr@fhrnet.eu> wrote:

...

If you really need them, you'll need to use some sort of tunneling mechanism, ie PPTP.

Friendly reminder, next week ios 10 drops

Prepare servers for iOS 10 & macOS Sierra. Crypto Deprecations: - SSLv3 - RC4 - PPTP VPN support.apple.com/en-us/HT206871 support.apple.com/en-us/HT206844

And expect your SSH DSA keys to require a workaround, or just generate new ecdsa and RSA keys. - Jared

On Sun, 11 Sep 2016, Randy Bush wrote:

sigh. well that was some fun hours debugging; not.

135/137/139/445 has seen widespread filtering since... errr.. 2000? I know it was widely done back in those days when people were connecting their computers directly to the bridged modem/ETTH jack and things ended up in the newspapers that peoples files were available on the Internet because they didn't set a password on their windows share.... or when versions of Windows were pwned during installation of Windows because... Windows. -- Mikael Abrahamsson email: swmike@swm.pp.se