07-15-2012 04:11 PM
So I'm on vacation and I'm trying to get into my home network.
I have a dynamic dns deal setup, and when I run nmap on that domain, it seems to resolve to the right address, listing ports 80, 23 (telnet), and 443 (https) as closed ports. I have forwarding setup so connecting to my router with ssh will forward it to the proper ssh server on my network.
What gives? Why can't I connect to my router even though I can see it (or rather, why are the ports closed?) I suspect comcast is blocking things somehow, but is there a way to turn this off?
07-16-2012 08:36 AM
07-16-2012 05:33 PM
I don't have those ports forwarded, so that makes sense. I did test it before I left, but internally, IE ssh to my router, which then redirected fine to my target server. It's a wrt54g with updated firmware (I forget the name, it's the one that everyone uses when they hack their wrt54g). So not comcast supplied. But yes, very strange as I can see the router and it's the correct one, but it just doesn't seem to be accepting the connection--perhaps I have outside IPs disabled and I forgot to set that before I left?
07-16-2012 07:43 PM
07-16-2012 10:12 PM
Yes, DD-WRT is the one.
And you may be right actually--I may not have setup my server to accept remote connections... I assume it's probably not configured that way by default with debian?
And yeah, not the *most* secure setup... I'd say it's a reasonably tolerable level of security, maybe I will setup private key authentication instead of password for remote connections when I get back... But yeah, sounds like I may be out of luck on this trip since I'm gone already :-/
©2011 Comcast | Investor Relations | Press Room | Corporate Blog | Privacy Statement | Visitor Agreement | Comcast.com Feedback | Site Map