http://www.dslreports.com/forum/r20314985 en Wed, 20 Aug 2008 19:59:39 EDT Wed, 20 Aug 2008 19:59:39 EDT http://www.dslreports.com/forum/remark,20383277 gzphreak : hehe, Im not to worried about using the FTP port at all. I use Linux as my NAT firewall. OpenSSH does not have _that_ many "security holes" for them to be worried about it. I would be more worried about blocking ftp or tftp(if that's how they flash their hardware) which does not use secure communication to authenticate.]]> http://www.dslreports.com/forum/remark,20383277 Thu, 24 Apr 2008 23:44:34 EDT http://www.dslreports.com/forum/remark,20321442 magmaikh4 : Don't use port 21, that's ftp and ftp is a bastard protocol that takes special handling in firewalls.

Use something high, 8022 is a common 'next best' for sshd if 22 isn't available.

Another thing to keep in mind... sshd has had several exploits and unless you've dumped OpenWRT onto your router the sshd version on it is going to be old.

It's possible they blocked port 22 until they fixed their sshd's.]]> http://www.dslreports.com/forum/remark,20321442 Sat, 12 Apr 2008 01:36:21 EDT http://www.dslreports.com/forum/remark,20317769 gzphreak : Maybe I can use the fact that other WOW customers are not being blocked as ammo to figure out exactly why I am having this problem, or get it fixed! ]]> http://www.dslreports.com/forum/remark,20317769 Fri, 11 Apr 2008 12:00:27 EDT http://www.dslreports.com/forum/remark,20317236 bewale : Same here. If WOW truly is port blocking 22/tcp (SSH) inbound, then it's only a very selective group of users impacted.
--
"In a world of compromise, some don't."]]> http://www.dslreports.com/forum/remark,20317236 Fri, 11 Apr 2008 10:05:27 EDT http://www.dslreports.com/forum/remark,20317003 aes128 : Well, I am also in Michigan and port 22 is NOT blocked for me. I can SSH into my router with no problem at all. So if WOW is blocking this port, it's on a selective basis. I am at work now and just did an SSH connect to my home router to check and this worked fine.]]> http://www.dslreports.com/forum/remark,20317003 Fri, 11 Apr 2008 09:03:17 EDT http://www.dslreports.com/forum/remark,20316010 gzphreak : I am running my SSH server on port 21 now... :(

I did confirm with WOW customer service that they are blocking it(as mentioned above.) I am pretty confident it's not a problem on my end. I tried a few different computer both behind a NAT device with port forwarding and another hook right into the cable modem. I had been using SSH before with no problems.

I was able to nmap myself from a friends computer and found where ssh was getting blocked, a WOW router one hop from my cable modem.

Outbound ssh is fine. They would be extra retarded to block that as well.]]> http://www.dslreports.com/forum/remark,20316010 Thu, 10 Apr 2008 22:59:16 EDT http://www.dslreports.com/forum/remark,20314985 parkut : I can confirm that try.wideopenwest.com is not blocking inbound port 22 (ssh) traffic.]]> http://www.dslreports.com/forum/remark,20314985 Thu, 10 Apr 2008 19:36:23 EDT http://www.dslreports.com/forum/remark,20314659 bewale : So am I. :)]]> http://www.dslreports.com/forum/remark,20314659 Thu, 10 Apr 2008 18:36:21 EDT http://www.dslreports.com/forum/remark,20313756 FileShackOrg : OP is referring to inbound as in running ssh on a home computer and connecting to it remotely I believe.]]> http://www.dslreports.com/forum/remark,20313756 Thu, 10 Apr 2008 15:57:24 EDT http://www.dslreports.com/forum/remark,20312619 aes128 : Works fine here as well...]]> http://www.dslreports.com/forum/remark,20312619 Thu, 10 Apr 2008 07:06:50 EDT http://www.dslreports.com/forum/remark,20310941 bewale : SSH is still working for me too. Suggest you look for other problems.
--
"In a world of compromise, some don't."]]> http://www.dslreports.com/forum/remark,20310941 Wed, 09 Apr 2008 21:02:13 EDT http://www.dslreports.com/forum/remark,20309205 hamburglar_ : Still working here.]]> http://www.dslreports.com/forum/remark,20309205 Wed, 09 Apr 2008 16:05:54 EDT http://www.dslreports.com/forum/remark,20307058 parkut : If true, there's an easy work around. Change the listening port to something else - either in your router, or in the ssh server

»www.google.com/search?hl=en&q=ss···ing+port
--
Hello, my name is Bill and I'm a crunchaholic...


Proud to be the current host of Crunchenstein #1, #3, #5, and Foldy #3]]> http://www.dslreports.com/forum/remark,20307058 Wed, 09 Apr 2008 09:31:32 EDT http://www.dslreports.com/forum/remark,20307017 gzphreak : Just got off the phone with tech support(which has been rather nice) after finding out WOW was blocking SSH. Their final answer after going through many lame excuses was they blocked inbound traffic on the SSH port to protect their equipment. This is a cop out! There are numerous methods to prevent unauthorized access to their crap. Tech support was unwilling to file a complaint any further. Does anyone know how/who I could write a polite nasty-gram to in order for my voice to be heard?

Thanks.]]> http://www.dslreports.com/forum/remark,20307017 Wed, 09 Apr 2008 09:21:20 EDT