Netcomm NF5 port forwarding weird issue

Forums › LAN (ethernet/Wifi/routers/Bluetooth) › Netcomm NF5 port forwarding weird issue

manuleka

76 posts

Master Geek

#148771 30-Jun-2014 18:27

Platforms:
Netcomm N300 NF5
Ubuntu 12.04 [LAMP]

So i have recently been supplied an NF5 Netcomm N300 router with my new Vodafone Cable broadband...

When ever i enable port forwarding (80) the router is in accessible from outside/internet (through ip)... but when port forwarding is disabled i can view the Router web interface (weird)...

I have tried using a NP803N Router (which was my wireless repeater) and port 80 forwarding works fine on it...

I'm no networking savvy so was wondering if anyone know of any settings needed altering for port 80 forwarding to work on NF5?

The router is 3 months old (came new with vodafone broadband)...

sheldonlendrum

Sheldon
120 posts

Master Geek

Lifetime subscriber

#1077276 30-Jun-2014 19:28

That is connect functionality.

The router uses port 80 for web management.
You can alter the port is listens to from the outside world ( Not that you should have that enabled anyhow ).

Then forward port 80 to your internal web server with out issues.

Edit: On mine, this is set in the 'Security Settings' tab, under 'Miscellaneous'.
I would disable that anyhow, how often would you need to manage it when your outside of the network ?

manuleka

76 posts

Master Geek

#1077279 30-Jun-2014 19:36

sheldonlendrum: That is connect functionality.

The router uses port 80 for web management.
You can alter the port is listens to from the outside world ( Not that you should have that enabled anyhow ).

Then forward port 80 to your internal web server with out issues.

yea i my problem is when i enable port forwarding to my server on the NF5 it doesn't work... for some reason the router doesn't forward port 80 requests to specified address, the forwarding process doesn't seem to work, i'm just curious if there's some setting that i'm missing

and as i've mentioned, when i swap it with the NP803n router (Netcomm as well) and enable port forwarding (80) to point to my Linux Server things work perfectly fine

weird - may be a faulty router...