Port forwarding

Sp00n · 3 Dec 2006 at 16:00

Seeing as i have somewhat of a strange setup, im finding port forward extremely difficult at the moment.

My setup is zyxel 660r > WRT54g > *network*

Now the zyxel is a dhcp server and gives out 192.168.0.3 to the wrt54g, the wrt54g is a dhcp server for the network and the network see's it as 192.168.1.1 and the zyxel from the network is 192.168.0.1.

Now i have supposably forwarded all ports ont he zyxel to 192.168.0.3 which should basically give the wrt54g complete control over port forwarding, or so i would have thought. However when i try to ftp to my ip address with the server up, it refuses the connection and i cant see why!

I've unblocked port 21 from the WAN on the zyxel and port 21 is forwarded to my pc 192.168.0.2 but it just refuses te connection =/

I've tested with various other ports too like emule and torrent but these don't seem to work either.

Anybody have any ideas?

Phemo · 3 Dec 2006 at 16:08

It depends whether the Zyxel supports loopback. It's common for port forwards not to work from the internal network on home routers. Can you get anyone else to test this from an external connection?

In short, it's very possible that it is working absolutely fine - you just won't be able to connect to your WAN IP from your LAN. Of course that wouldn't explain the p2p oddities but FTP is a lot easier to test with initially.

Lastly, why are you using two routers? This means you're NAT'ting twice which is a pain sometimes.

Sp00n · 3 Dec 2006 at 16:12

Phemo said:
It depends whether the Zyxel supports loopback. It's common for port forwards not to work from the internal network on home routers. Can you get anyone else to test this from an external connection?

In short, it's very possible that it is working absolutely fine - you just won't be able to connect to your WAN IP from your LAN. Of course that wouldn't explain the p2p oddities but FTP is a lot easier to test with initially.

Lastly, why are you using two routers? This means you're NAT'ting twice which is a pain sometimes.

The zyxel came with the ADSL connection and only has a single port ethernet connection but it is also the modem so i have to use that.

Then the WRT54g is the router to distribute to the network as well as other stuf like QoS.

In regards to the NAT, i have forwarded all ports to the linksys in "SUA only" mode on the 192.168.0.x network which i thought would have put the linksys in control of all ports?

Sp00n · 3 Dec 2006 at 16:24

LOL, i just had a look at the NAT routing on the zyxel and noticed that the ip of the linksys had changed, reset the ip setting and it seems to work perfectly now!

Clarkey · 3 Dec 2006 at 17:12

can you not put the linksys in the DMZ of the zyxel?

Sp00n · 3 Dec 2006 at 17:14

The zyxel doesnt have a DMZ option as far as i can see =/

Clarkey · 3 Dec 2006 at 17:16

fair enough, might as well turn the DHCP server on the zyxel off and give the linksys a manually assigned IP, avoid any further confusion and probably reduce cpu load on the zyxel a little.

Pint · 3 Dec 2006 at 19:40

Turn off DHCP on the Zyxel.
Turn off the firewall on the Zyxel.
Give the Netgear a Static IP.
In the NAT section of the Zyxel set the default server to be whatever address you've given the Netgear.
You're trying to double NAT and that's always asking for problems.