Secure Shell (SSH) filtering

[jacqieklein]

Hello, all!

I'm writing because it appears that Mediacom blocks SSH access (tcp port 22) both inbound and outbound. I have various shell accounts - none of which can be accessed from my home internet connection. Below, you'll find the output from the tcptraceroute(1) utility installed on the computer wired directly to the cable-modem (CM).

[3] (root@softfw1) ~$ tcptraceroute -m 5 sdf.org 22
Selected device eno1, address 192.168.0.2, port 40513 for outgoing packets
Tracing the path to sdf.org (205.166.94.16) on TCP port 22 (ssh), 5 hops max
1 192.168.0.1 1.285 ms 1.202 ms 1.202 ms
2 * * *
3 * * *
4 * * *
5 * * *
Destination not reached
[3] (root@softfw1) ~$ tcptraceroute -m 5 sdf.org 80
Selected device eno1, address 192.168.0.2, port 49479 for outgoing packets
Tracing the path to sdf.org (205.166.94.16) on TCP port 80 (http), 5 hops max
1 192.168.0.1 1.281 ms 1.202 ms 1.196 ms
2 10.152.65.1 10.589 ms 9.693 ms 9.997 ms
3 172.30.5.53 10.918 ms 10.639 ms 10.386 ms
4 10.16.80.235 17.264 ms 15.255 ms 15.023 ms
5 10.16.80.93 15.493 ms 14.959 ms 15.259 ms
Destination not reached

Can someone from Mediacom please weigh in on this? We're paying for the 1Gbps Internet package - what more must we do to get /unfiltered/ Internet access?

[MediacomTom]

Hello jacqieklein. Thanks for reaching out. The Mediacom network does not intentionally or knowingly block any ports outside of port 25 for security/spam reasons. Although we do not block SSH or VPN's from being used, we do not actively support them and apologize for any inconvenience this may cause.

[jacqieklein]

Moderator,

Please review the configuration on device 10.152.65.1. This is the second hop upstream from me; it's the hop at which my SSH connection attempts are being dropped while HTTP connections are passed.