Help needed setting up Netcomm NFV18ACV port forwarding

Forums › LAN (ethernet/Wifi/routers/Bluetooth) › Help needed setting up Netcomm NFV18ACV port forwarding

ageorge

626 posts

Ultimate Geek

#275765 8-Sep-2020 12:50

Greetings.

I set up port forwarding as explained in various places, but checking the port shows its still closed.

I suspect the IP address, but Ive used as shown and 192.168.20.100 with Ubuntu IFconfig to find WAN port and also used WAN port under info in the NFV18ACV dialogs.

I dont understand the process, just following guides, but need help if anyone can suggest what could be stopping port forwarding from working?

I can open the ports with access control, but thats not the correct method:

1 | 2

BDFL - Memuneh
76417 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#2560261 8-Sep-2020 13:01

What you have done on the second screenshot is open up your router to the world. I suggest you revert those changes now.

Please support Geekzone by subscribing, or using one of our referral links: Dosh referral: 00001283 | Sharesies | Goodsync | Mighty Ape | Backblaze

freitasm on Keybase | My technology disclosure

Sharesies kids

Free kids accounts - trade shares and funds (NZ, US) with Sharesies (affiliate link).

ageorge

626 posts

Ultimate Geek

#2560264 8-Sep-2020 13:04

freitasm: What you have done on the second screenshot is open up your router to the world. I suggest you revert those changes now.

I can open the ports with access control, but thats not the correct method!

taneb1

472 posts

Ultimate Geek

ID Verified

Trusted

Mercury

#2560265 8-Sep-2020 13:05

What type of internet connection do you have ADSL/VDSL or UFB?

Any comments made are my personal views and does not represent those of my employer

ageorge

626 posts

Ultimate Geek

#2560267 8-Sep-2020 13:10

taneb1:

What type of internet connection do you have ADSL/VDSL or UFB?

UFB

I just went to my network PC settings and got my IPV4 address as 192.168.20.9 but thats not doing it either.

taneb1

472 posts

Ultimate Geek

ID Verified

Trusted

Mercury

#2560282 8-Sep-2020 13:17

Okay, so if you access it internally it is on https://192.168.20.9 ? I would possibly try use a different external port start/end instead of 443 and see if that works instead.

Any comments made are my personal views and does not represent those of my employer

ageorge

626 posts

Ultimate Geek

#2560284 8-Sep-2020 13:19

taneb1:

Okay, so if you access it internally it is on https://192.168.20.9 ? I would possibly try use a different external port start/end instead of 443 and see if that works instead.

Been there, done that, not work

taneb1

472 posts

Ultimate Geek

ID Verified

Trusted

Mercury

#2560285 8-Sep-2020 13:21

So just confirming it is https://192.168.20.9 you use if you access it internally? Might be worth contacting Netcomm Support directly.

Any comments made are my personal views and does not represent those of my employer

ageorge

626 posts

Ultimate Geek

#2560287 8-Sep-2020 13:22

As I understand it:

alistair@alsmain:~$ ip r
default via 192.168.20.1 dev enp1s0 proto dhcp metric 100
169.254.0.0/16 dev br-fcb5695d0a8b scope link metric 1000 linkdown
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
172.18.0.0/16 dev br-fcb5695d0a8b proto kernel scope link src 172.18.0.1 linkdown
192.168.20.0/24 dev enp1s0 proto kernel scope link src 192.168.20.9 metric 100

My default gateway is 192.168.20.1 so any IP in forwarding should work thusly: 192.168.20.100 and so on correct?

If correct, what could possibly be the problem?

Thanks.

Al.

ageorge

626 posts

Ultimate Geek

#2560294 8-Sep-2020 13:24

taneb1:

So just confirming it is https://192.168.20.9 you use if you access it internally? Might be worth contacting Netcomm Support directly.

Netcomm are overseas based and unlikely to spend phone time with an unknown user.

I did phone up my ISP Slingshot first, and they have no idea about port forwarding (or so their operator said)

Maybe I need to change to a cheaper ISP ;-)

noroad

751 posts

Ultimate Geek

Trusted

#2560300 8-Sep-2020 13:36

So you are trying to allow public access to an internal server on 192.168.20.9 port 443 ? Firstly as people have suggested you need to confirm you can internally access that. People have asked if you can get to https://192.168.20.9 internally, if you can not do that then its nothing to do with your port forward, go back to the server and work out why before continuing. I would suggest you need to open up the firewall on the server. Do NOT do this unless you are properly patching it. Secondly you can not have a port forward to a port that you are using on your management/access control. You show samba (just no!) on port 443 so that will not work. change the samba port to something random and disable it. It is only safe to enable ICMP (do this) on the wan, never enable anything else unless you really understand what you are doing. Your port forward itself looks fine, just fix those other two things.

ageorge

626 posts

Ultimate Geek

#2560305 8-Sep-2020 13:44

noroad:

So you are trying to allow public access to an internal server on 192.168.20.9 port 443 ? Firstly as people have suggested you need to confirm you can internally access that. People have asked if you can get to https://192.168.20.9 internally, if you can not do that then its nothing to do with your port forward, go back to the server and work out why before continuing. I would suggest you need to open up the firewall on the server. Do NOT do this unless you are properly patching it. Secondly you can not have a port forward to a port that you are using on your management/access control. You show samba (just no!) on port 443 so that will not work. change the samba port to something random and disable it. It is only safe to enable ICMP (do this) on the wan, never enable anything else unless you really understand what you are doing. Your port forward itself looks fine, just fix those other two things.

Re the samba - I repeat that was only used as a test and its port is actually 442 and its disabled by default. The reason for using it modified to 443, was to ascertain if the port was able to be accessed by my default gateway.

Port forward to 192.168.20.100 should be fine. I will check as you suggest what might be blocking it thanks.

Al.

djtOtago

982 posts

Ultimate Geek

#2560308 8-Sep-2020 13:52

So what computer on your internal network has the IP address 192.168.20.100 and what service does it have that is listening on port 443

ageorge

626 posts

Ultimate Geek

#2560309 8-Sep-2020 13:53

OK if I turn off the firewall in Netcomm NFV18ACV then the port forward works. So thats the culprit. Wonder how I can have my firewall enabled, but still port forward.

The above is wrong, all ports are forwarded if the firewall is turned off.

ageorge

626 posts

Ultimate Geek

#2560316 8-Sep-2020 14:05

djtOtago:

So what computer on your internal network has the IP address 192.168.20.100 and what service does it have that is listening on port 443

ip r:

default via 192.168.20.1 dev enp1s0 proto dhcp metric 100

Am I wrong assuming that any range in 192.168.20.?? should reach as per original post?

djtOtago

982 posts

Ultimate Geek

#2560322 8-Sep-2020 14:15

192.168.20.100 will work, But there has to be something on your internal network with that IP address. Otherwise you are just forwarding to nothing.

1 | 2