Head Exploded with Port Forwarding

Django x2 · 20 Aug 2013 at 15:29

Ok, this is the situation.

I have two servers behind a router / firewall that I need to access on port 443.

Now, with the crappy standard BT HomeHub, I was able to do this by accessing on a different port, and then the router / firewall would translate that to 443 and forward on to the relevant server.

ie:
external 80.80.80.80:443 would go to internal 192.168.2.110:443
external 80.80.80.80:444 would go to internal 192.168.2.100:443

Now, we have "upgraded" (in quotes, because it doesn't feel like an upgrade) to a Netgear DGN2200v3 with the latest firmware and the option of "translates to" doesn't seem to exist.

With changing the listening port of the application on the 192.168.2.100 server, is there not a way around this?

Thanks

bremen1874 · 20 Aug 2013 at 16:14

Amazingly the necessary options do appear to be missing. A quick search finds other people with the same problem rather than any solutions.

Django x2 · 20 Aug 2013 at 17:44

Have I got the terminology right? I was sure it was called port translation, or, translates to, in the homehub

I don't really want to stick one of the boxes in the DMZ.

bremen1874 · 20 Aug 2013 at 18:06

The names vary, but it would be called something like that.

My Vigor2920 calls it 'Port Redirection'. A BT Business Hub I have access to refers to it as port translation.

Sin_Chase · 20 Aug 2013 at 18:37

The Netgear supports NAT as you would expect, but will not translate the source port to a different destination port.

Netgear equipment sucks. Period.

I have a DGN2200 in use....with EVERYTHING disabled in the capacity of a Wireless AP only....and it even sucks at that.

Return the Netgear, it is a substandard product.