What's new
  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Port Forwarding Issue

s_Fanous

Occasional Visitor
Hi

My setup at home is as follows

Internet <--> Bell Fibe Home Hub 2000 (External interface = Real IP / Internal interface = 192.168.0.1) <--> RT-AC68U (External interface = 192.168.0.2 / Internal interface = 192.168.1.1)

Bell doesn't allow putting the HH 2000 in bridged mode but one could consider it to be in semi bridged mode as I've disabled Wifi and DHCP is only giving out 1 IP (192.168.0.2 to the Asus Router). All my hosts reside on the 192.168.1.0/255 subnet.

Port forwarding from the HH2000 to the Asus router works without issue. I'm able to connect to the OpenVPN server running on the Asus router as well as the HTTPS web UI from WAN.

The problem I have is that port forwarding from the Asus external interface (192.168.0.2) to any of the hosts residing on the 192.168.1.0 is not working even though I've setup port forwarding rules on the Asus router.

e.g. I've forwarded port 443 to 192.168.0.2:44300 on the HH2000. I've then also forwarded port 44300 to 192.168.1.100:443 on the Asus router. Packets never reach 192.168.1.100. As a matter of fact using tcpdump I can see SYN packets reaching port 44300 on the 192.168.0.2 external interface but are never forwarded to the 192.168.1.0/255 interface and thus never make it to the intended host.

What could the problem be and how can I solve it?

P.S. I've also tried seeing if using netcat to manually open a port and forward all it's traffic would work. Command used is as follows

netcat -L 192.168.1.100:443-p 44300

If I connect to 192.168.1.1:443 from the LAN then the packets are forwarded to 192.168.1.100 as expected, but from the WAN packets again only reach the 192.168.0.2 interface and die.

TIA
 
Last edited:
Looks like I solved it by creating nat-start and adding the following to it

Code:
#!/bin/sh

iptables -t nat -A POSTROUTING -j MASQUERADE

Traffic is now being passed from the Asus router to the hosts.
 
Well I might have posted too soon. This doesn't seem to be a reliable solution. It seems to be a hit and miss whether the port is reported as open or not!!!

If any of the experts can chime in and help I'd really appreciate it.
 

Similar threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Back
Top