Hi all, I've been searching for a solution Mediacom's practice of blocking specific outbound ports from residential service, specially port 22 (ssh). I'm a new customer after having moved to Delaware from Pennsylvania, and my prior providers (Comcast and Verizon) did no such blocking. I IM'd MediacomChad to inquire if baselining would solve the issue (I do have my own router), but he indicated that baselining would only turn off wireless, and that he'd be unable to offer support to any ssh/vpn issues (which is a fair statement). My testing has verified the behavior; I run a server at an ISP, and if I move the ssh service to an open port, like 443, the connection works for a while but is also ultimately terminated.
What is find frustrating beyond the behavior is that publicly Mediacom states that they follow the tenets of net neutrality and don't limit/block traffic but clearly they do. I've searched and found other customers experiencing the same issue. Calls to support haven't helped, as they mistakenly believe I'm talking about ssh inbound to my residence, and incorrectly state that port forwarding is the solution.
Has anyone had experience with this scenario, and, if so, has baselining and using your own router resolved the issue?
Aside from ssh (and I believe outbound port 25 to block email spammers), does anyone know what other ports/services are being blocked?
Thanks in advance for your time and comments!
-John
↧