On Mon, 13 Dec 2004 09:13:01 -0800, o.blomqvist wrote:
> Hello !
>
> This seemingly simple problem is giving me a hard time. I have a
> regular Optimum Online Cable connection. It is routed using a 4 port
> Linksys router. I have turned off DCHP, the firewall, all router
> filters and turned on DMZ for the server IP, NAT is turned on. All the
> computers running on the local network (192.168.2.x, same as Server)
> can connect just fine to the internet and the server (SSH). In
> hosts.allow I have SSH: ALL.
>
> Still, when I try to connect using SSH from the internet I get a
> connection timeout response. I can ping the WAN IP, but I dont know if
> that response if from the router or the server.
You modem/router is NATing - hence the ping reply is from the modem. It
would only be the server if you were operating in bridging mode.
>
> I suspect this has to do with some Network security setting on the
> Linux box, but I'm far from sure where. Any ideas ? I'm Running RH 8
>
If you can SSH in internally, then it *really* should work. Try looking at
your firewall on the server and see what the rules are on port 22.
# iptables -L
Here a working line for my SSH that works through my NAT router:
hackbox:/home/tmccoy# iptables -L
Chain INPUT (policy DROP)
target prot opt source destination
ACCEPT tcp -- anywhere anywhere tcp dpt:ssh
Where as, if you have no firewall, you'll get:
freeton:~# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
> Thanks a lot !
>
>
> By the way, Optimum Online is blocking incoming traffic on ports 80,
> 1080, 8080, 25, 3128, 135-139, and 445. That should not be a problem,
> right?
These ports won't cause any issues. But why-oh-why would they block WWW on
port 80? That's just mean :P
The only other thing I can think of is the DMZ is playing a little havoc.
It's supposed to be used for this purpose (I think?) but I run all my NAT
SSH machines purely on my internal network. Maybe try moving it off the
DMZ and see what happens?
Cheers
Tim
--
"Linux... because rebooting is for adding new hardware!"
http://home.swiftdsl.com.au/~tmccoy
MSN:
(E-Mail Removed)
ICQ: 160341067