Comcast

[abreauj-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org (John Abreau)]

I gave up on inbound ssh ports on my home firewall a couple years ago.
These days, I use OpenVPN, where the vpn server is outside my house,
and all my machines at home are vpn clients. I can then ssh into them
over the vpn, and I don't have to open the ssh port on my firewall.



On Thu, Nov 12, 2009 at 2:03 PM, Jerry Feldman <gaf-mNDKBlG2WHs at public.gmane.org> wrote:
> Certainly that type of written agreement is better than a general TOS. I
> think in general, speakeasy has a more sophisticated client?le. My
> concern is not port 25 but some of the ssh inbound ports I use. In any
> case I would just as soon Comcast block both 80 and 25 so that I don't
> get all that junk traffic.
>
> On 11/12/2009 11:47 AM, David Hummel wrote:
>> Which is meaningless since Comcast has and will randomly disable
>> inbound access to TCP ports typically used to run servers (or any
>> others they choose apparently). ?They're not prohibiting servers,
>> they're just not guaranteeing that they won't block access to them.
>> With Speakeasy, I have written and verbal guarantees that they will
>> not engage in this kind of activity. ?I'm paying for internet access,
>> not inbound/outbound access on ports X, Y, and Z...
>>
>
>
> --
> Jerry Feldman <gaf-mNDKBlG2WHs at public.gmane.org>
> Boston Linux and Unix
> PGP key id: 537C5846
> PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB ?CA3B 4607 4319 537C 5846
>
>
>
> _______________________________________________
> Discuss mailing list
> Discuss-mNDKBlG2WHs at public.gmane.org
> http://lists.blu.org/mailman/listinfo/discuss
>
>



-- 
John Abreau / Executive Director, Boston Linux & Unix
GnuPG KeyID: 0xD5C7B5D9 / Email: abreauj-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org
GnuPG FP: 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99