Innbox V50U - NAT virtual server ports not open

Forums › LAN (ethernet/Wifi/routers/Bluetooth) › Innbox V50U - NAT virtual server ports not open

andynz

360 posts

Ultimate Geek
Inactive user

#129545 19-Sep-2013 09:33

Anyone using an Innbox V50U with NAT/Virtual servers setup and working ok?

I have 4 port forwards setup but they all appear to be blocked. I have an old ADSL modem router on the LAN with ADSL service with Xnet. I have a totally separate Innbox router using ADSL with Full Flavour. The 2 routers use their own respective DSL connections and are on different lan IP's.

The Xnet/SMC modem has 4 port forwards which all work fine. Port forward on the Innbox does not. Any ideas anyone?

Please note neither modem is behind the other so no conflict there. 2 independent DSL/modems.

This is a temporary situation as I need to get the new Innbox up and running before dropping the Xnet connect.

Cheers
Andy

qyiet

454 posts

Ultimate Geek

Trusted

#898518 19-Sep-2013 14:54

This is what I think you described. (the IP address/ports are arbitrary)

And your issue is when you use the public IP on the innobox you don't get any response from server1 on port 80. If I got this right the first question I'd ask is which gateway is server1 using. If it's still xnet try swapping it to the innobox router and see if that fixes your forwarding issue.

Warning: reality may differ from above post

andynz

360 posts

Ultimate Geek
Inactive user

#898551 19-Sep-2013 15:34

Hey thanks for your time with the diagram and questions, thats great :)

Your exactly right in the diagram and description. Server 1's gateway is xnet .0.1. Does the gateway make a difference to incoming connections form either router?

qyiet

454 posts

Ultimate Geek

Trusted

#898562 19-Sep-2013 15:54

Does the gateway make a difference to incoming connections form either router?

I've not tried that exact setup, but I expect it will.

I think that the request comes in via the innoxbox, and server1 tries to respond via the xnet (as that's where the gateway is) but this loop means either the xnet router doesn't know what to do with the outgoing stuff, or the client at the other end is confused about getting data it didn't ask for from xnet wan IP address.

A very quick test would be to manually move the gateway IP for server1 to 192.168.0.2 and see if that lets you run the fwds over the innobox connection. I would expect that to break the ones from the xnet link though.

Warning: reality may differ from above post

andynz

360 posts

Ultimate Geek
Inactive user

#898573 19-Sep-2013 16:02

Ok tried the test and changed the mail server gateway to the Innbox and same result. As a mater of interest with the mail server gateway set to Innbox I tried an SMTP test via the xnet WAN IP and it still worked so it looks like it is not gateway related.

Having just spend an hour with the tech from Innbox we are coming to the conclusion it could be an ISP block on all ports. I will check with FFM.

Inphinity

2780 posts

Uber Geek

#898578 19-Sep-2013 16:08

You should ideally add both gateways to any server or device that could potentially require both connections, and use metric weighting to define priority. Some protocols won't work if you are traversing a different gateway (and thus different public IP) for the return path.

richms

28193 posts

Uber Geek

Trusted

Lifetime subscriber

#900822 22-Sep-2013 20:08

If the machines gateway is .0.1 then only portfowards on that router will work, if you want to have 2 incoming ranges then you need to have 2 seperate internal lan IP ranges so that there is a route out from the server to the second dsl connection, seperate nic or a second IP on the single lan adapter both worked for me when I needed it.

Richard rich.ms

andynz

360 posts

Ultimate Geek
Inactive user

#900977 23-Sep-2013 08:41

Thanks Rich for your comments. The simplest solution was removing Xnet 0.1 and then the innbox works fine. I was trying to have redundancy whilst we complete the torturous change over from Xnet to FFM.

Still seems odd that with both routers active, the port forwards on the xnet 0.1 work fine but the port forwards on the innbox only work with one router, itself, active.

Quic Broadband

Move to New Zealand's best fibre broadband service (affiliate link). Free setup code: R587125ERQ6VE. Note that to use Quic Broadband you must be comfortable with configuring your own router.

richms

28193 posts

Uber Geek

Trusted

Lifetime subscriber

#900991 23-Sep-2013 09:36

Not really odd, as the computer will be sending responses to the wrong router, it will have no entry in its nat or spi firewall table, so drop the packets.

Richard rich.ms

qyiet

454 posts

Ultimate Geek

Trusted

#900993 23-Sep-2013 09:39

richms: Not really odd, as the computer will be sending responses to the wrong router, it will have no entry in its nat or spi firewall table, so drop the packets.

That's why I'm surprised that switching the gateway didn't work for andynz. That said NAT is such a nasty set of lies, I'm never surprised when it doesn't work as expected.

Warning: reality may differ from above post