Netgear MR814 - Port Forwarding with linux??
 

I have a network behind a Netgear Wireless AP/Router (MR814) consisting of one Redhat 8.0, one Windows 98se, and one Windows XP machines, The linux machine is the only one acting odd with the router. When I first kicked it up, I had assigned ip 192.168.0.4 to the linux machine, I had through to the internet )though SOME pages wouldn't load, google.com for example, but this one would, and the router's config page said only the two windows machines were attached to it, though I steadily watched the traffic indicators for the linux machine flash, and the router was handling traffic from it. Found that a bit odd, I shutdown and restarted the RH box, and now it shows it as it should on the router config page. however when I tried to forward ports 80 and 22, niether respond from the outside, internally they function well. If anyone has any idea why port forwarding isn't forwarding the ports correctly, or has had similar problems I'd appreciate any help with this. thank you -- Edit: Also I just noticed, when connected to an SSH service outside my internal network, if I send no data for 30seconds - 1 minute it closes the connection, usually I can leave this up for hours with no problem, anyone?



-robf

have you set the dns servers in /etc/resolv.conf? Thats the only thing I can think of... I have a similar network. If you set it up as dhcp for one boot, it´ll throw the correct addresses in there.

yeh DNS is fine...it was just an oddity...cos it resolved most url's but some didn't then it started working, I think it needed just to restart ut, however it still kills the SSH connection (me = client) after 1 minute of being idle, that's not the server, it's the firewall obviouslly as it never occured before and we've not changed anything. The Linux machine is 192.1687.0.4 internally it's getting that IP like it's supposed to just fine, my only remaining issue now is the Port Forwarding, it's simply not doing it.... From the outside a port scan shows
"
Scan of 24.214.127.xxx shows 1 host responding to Pings
Services:
<none>
Host may be behind firewall.
"
however port 80 / 22 should be listening and responding...but nothing, attempts to connect via http and SSH are just the same, nothing....however the services function from behind the router, just deaf to the outside

This may or may not help from the router are you using dhcp for the internal network and if so ar you using dhcp for connecting to your isp. If so I would first recomend setting hard ips for the internal network. It may also be a good idea to find out what ip your isp assigned you and plug it in to the router as hard then try to foward from the outside.

With that said if you already have done that or cant then go to netgear website and ensure your router has the latest firmware. I have a linksys and believe me well its a great router but you must stay current with firmware

I too am having similar problems with the NG MR814. Both incoming and outgoing SSH connections die after a couple of minutes or inactivity. I wonder if it has something to do with the MTU settings for the NG POS.

I had forgotten this thread I'm glad you responded to it. The first test and easiest is to see if you can foward any ports through any other machine other then linux. If so then it is a linux problem. If not it is a router problem.

steps for linux

make sure firewall restrictions are removed. If not for all ports then at least for thoughts you wish to use.

if this is done then try to foward port 23 (telnet) and see if you can get an incoming connection from outside or from an internal machine using your wan ip.


steps for router

check to insure you are using the latest firmware on the router. If so then to test remove dhcp from the picture. both internal and external


finnaly it is possible that the ssh client you are using may just have a timeout value for security. It may also be possible that that there is a timeout value associated with either the router or the linux firewall settings. As far as MTU set for 1500 I doubt this is causing you a problem

When Dmz'd the SSH connections don't die, I just realised that now.... though that's annoying to have to DMZ something just to keep a connection alive, since I spend a lot of time using outside machines, I hate to have to reconnect everytime I need to do something....