Port Redirection

Nefarious · 9 Sep 2009 at 07:21

I have two internet connections to an office, managed by separate routers. One has a dynamic IP address and one a static. The service provided on the static line is unreliable to say the least so the majority of the trafic goes through the dynamic line with the router set to be 192.168.0.1 and the static line to 192.168.0.2

A number of incomming connections are required including FTP, VPN and SSH. The VPN works fine, but the port redirection does not. I would not have thought that the IP address being other than .1 would have caused such a problem - am I missing something? Can you suggest a way around this?

Skidilliplop · 9 Sep 2009 at 09:43

First thing that pops to my mind is why not use dynamic DNS and just have the inbound services on the stable line.

IF you're VPN'd in then your remote site should be virtually attached to the LAN so all hosts and ports should be local private.
Not sure i full understand what you're trying to achieve.

feriso · 9 Sep 2009 at 10:03

Do you mean port redirection on incoming traffic - if so then this should be set at the router, if it's not working properly then either you've not set it right or the router is buggered

Nefarious · 9 Sep 2009 at 10:15

I shall attempt to clarify. There are several inbound connections on the static address. The Billion router allows upto 5 VPN accounts to dial in which it assigns an IP address on the local network. The VPN functionality seems to be fine with the router set to 192.168.0.2.

The router also provides virtual server functions and intercepts inbound services on various ports and redirects them to different addresses on the local network. For example port 22 (SSH) is directed to 192.168.0.100. It is the virtual server functionality that seems to be unable to function at the moment.

I have no idea what Skidilliplop is suggesting. I don't have a remote site and am unsure how I could use dynamic DNS to allow remote users to access the server via SSH. Please could you explain further.

Skidilliplop · 9 Sep 2009 at 10:40

Using a dynamic DNS domain name to connect to the router rather than it's IP address which changes means you only need the one active line and simplifies the setup a bit.
As for the virtual server functions if set up for the right services and the right relevant IPs it should just work. However if the router for the inbound connections is .2 and the default gateways of the hosting servers on the local network is .1 the SSH FTP etc connections are coming in on one line and going out the other. The result being the remote client sees the responses coming from a different source IP and hence won't make the association with the outgoing connection and the service won't appear to connect.