| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 104664 | 2009-11-04 07:15:00 | How to port forward on RTA1025W router | andreas.hagen (15380) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 827104 | 2009-11-04 07:15:00 | Hi I am trying to use openssh with a debian 5 "lenny" server. Can someone please give info on port forwarding port 22 for a Dynalink RTA 1025W router. Either a guide or some instructions. Thanks in advance!:banana | andreas.hagen (15380) | ||
| 827105 | 2009-11-04 07:22:00 | Embarrassed that I voted :yuck:. Doesn't seem relevant to the question though the answer to which I don't know |
gary67 (56) | ||
| 827106 | 2009-11-04 07:42:00 | Theres the user guide here: www.dynalink.co.nz Step by step guide: www.portforward.com |
Dannz (1668) | ||
| 827107 | 2009-11-04 08:17:00 | Cheers for the links but still no success ... I have a static IP for the server of 192.168.1.4 and setup port forwarding to this address as per the port forward.com on the RTA1025W I look up the external IP by going to the site whatismyip.com from the server. Then from the vista computer running putty ssh I get access denied after specifying the external IP address. I am new to this, does any one have some thoughts? |
andreas.hagen (15380) | ||
| 827108 | 2009-11-04 08:56:00 | This is tricky to test unless you've got a 2nd internet connection to go out on via PuTTY. If not, just post your static IP & SSH username & password & one of us will check it out for you... ...NOT! ;);) OK - that's not the best idea. Maybe a dialup connection? Hmmm, that probably won't work these days either (who has dialup AND broadband?). Maybe a friendly neighbour, or can you do it via a 3G connection? The only other option that might be a goer is to use a proxy server, but I'm not sure whether that will be viable either. I have a working SSH setup on my NAS here, might have a look at that option & get back later. |
MushHead (10626) | ||
| 827109 | 2009-11-04 09:13:00 | Use the Port Checker tool to test www.portforward.com | whellington (15030) | ||
| 827110 | 2009-11-04 10:24:00 | If you can't use a separate connection to check, what you need is "NAT Loopback", but unfortunately this isn't supported on your router as far as I can see. What that does, is that if you try to access (in this case) SSH to your external IP (WAN) address from another PC within the LAN, the router spots that the port forwarding for SSH is in effect, so rather than the router ignoring the request (assuming that it wasn't also looking for SSH traffic on the same port), it forwards the data to the internal server address as specified in the port forward table & rewrites the source to be the same as the WAN IP of the router. When the SSH (or whatever) server replies, the router reverses the process so that the traffic returns to sender, but again with the WAN IP as the source. By default, routers don't do this & trying to talk to a LAN server via another machine on the LAN using the WAN IP address will simply not work - you need an external (on the WAN side) machine to talk to the WAN IP to make the port forwarding work. |
MushHead (10626) | ||
| 827111 | 2009-11-04 17:37:00 | Nicely explained MushHead :) | Chilling_Silence (9) | ||
| 1 | |||||