Port Forwarding bug disables Control Panel access from Wan

[AsNCo]

Hi guys.
Since in the past, my Netduma has been my secondary router specifically for gaming behind my Asus router which is the primary router in the house in order to achieve the full speed of my internet.

The problem lies in that thanks to Infinite Warfare's inconsistent games, I followed SimJC's idea to do manual port forwarding of the PS4 ports in the Netduma. However, I then started realizing that my ability to access Netduma's control panel with its second IP address which I configured as 192.168.1.3 no longer works when accessing from an Asus router client PC along with the direct client PC in Netduma.
The moment I disabled my port forwarding ports in my Netduma and click apply, I can access it from both Asus client and Netduma client directly with 192.168.1.3

It seems that the Port Forwarding page has created a bug that will disable 'Access control panel from WAN' functionality in the Netduma. I tried experimenting enabling just 1 of the ports and again, the bug returns.

2nd bug I noticed: As a result of any ports enabled in Port Forwarding, I'll be unable to Save Current Settings in Profile unless I untick 'Save Hyper-Lane' under Personal Settings without an error popping up.

Just a head's up so you guys can fix this bug before our long awaited DUMA OS.   

Note: DMZ enabled from Asus side to Netduma. No issues for years with my Netduma in this configuration until I used the R1's Port Forwarding.

[PharmDawgg]

Port forwarding > Upnp.  Always preferred port forwarding vs upnp. Just got better results. And I don't believe it is a security risk as many may proclaim because it is only opening ports to my console which I am ok with.  

I have never used the 'Access control panel from WAN' option but if there is a bug great catch AsNCo. 

[Chive972]

Stop bitching when they say something wrong.

They help the gamer community as fast as they can.

If you think they're wrong for something, just explain why and it will change the way they/we think.

We're not here to say who is right and who is wrong.

[Chive972]

As you said, the port forwarding is better for the best gaming experience but for some people who have any clue of networking, it's a pain in the ass.

After the duma os 2.0, we need to create a dedicated topic for all beginners.

[Chive972]

I understand your point of view but the problem is that a lots of people will think that you're here to "spit your science".

A lots of users here won't be able to explain a basic thing of networking like a DMZ.

 

Netduma is a great idea and you can't say nothing about it.

If you think that something is wrong say it but there is a way to do it, not like this.

 

We're here to talk about things around the netduma, not for bitching or create a debate about networking.

 

If your good on the subject then you can propose ideas or try to help the community.

 

I'm not here to scream against you because you have a point of certain misunderstandings.

 

We've seen a lots of trolls here and i don't want that you to be associated to that dumb people so keep calm and stay focused about things we can change on the new OS.

[Netduma Jack]

This thread was hijacked by a malcontent customer, so I've cleaned it up to focus on the issue at hand.

 

Thank you for bringing up these bugs - a few people on here have been experiencing an interface slow-down when port forwarding. It'd be fantastic if you could tell us your set-up, which firmware version you are on, and which ports you're forwarding. We're going to try to replicate this issue in-house so we can remedy it.

[AsNCo]

This thread was hijacked by a malcontent customer, so I've cleaned it up to focus on the issue at hand.

 

Thank you for bringing up these bugs - a few people on here have been experiencing an interface slow-down when port forwarding. It'd be fantastic if you could tell us your set-up, which firmware version you are on, and which ports you're forwarding. We're going to try to replicate this issue in-house so we can remedy it.

Thank you for getting back to me. Here are the necessary information.

 

Primary Router connected to modem: Asus RT-AC68U running Merlin 380.57 firmware.

Netduma Firmware: 1.03.6g

Netduma is connected to the Asus router and not to modem.

 

In the Port Forwarding page, try enabling any of the ports and voila, the 2 bugs mentioned in the previous post will happen.

I used to write some of the ports for Hyper-Traffic on the Congestion Control page but due to the bug, I first assumed it was because of it and had to Factory Reset the Netduma. From there, Even after applying the profile, I still had to configure some of the settings which did not apply well. So my Hyper-Traffic is currently empty until I find the time to reapply them. But it should not cause any issue except for Port Forward ports.

 

 

[Netduma Fraser]

Just curious why do you also have 1.2 etc set to the R1? Could these perhaps be causing conflicts? Do you also have UPnP enabled on the Asus as this could potentially cause conflicts. Do you have UPnP forwarding enabled on the duma misc settings? As this could also cause conflicts.

 

With Hyper traffic you should just use the services as they will include the ports you specify anyway. 

[AsNCo]

Just curious why do you also have 1.2 etc set to the R1? Could these perhaps be causing conflicts? Do you also have UPnP enabled on the Asus as this could potentially cause conflicts. Do you have UPnP forwarding enabled on the duma misc settings? As this could also cause conflicts.

 

With Hyper traffic you should just use the services as they will include the ports you specify anyway. 

I have a Desktop PC with dual Ethernet ports.

1st port is set for Asus router at 192.168.1.2 (by enabling route from 192.168.1.2 to 192.168.1.3, hopefully it ensures that I can access the Netduma without having to decrease subnet mask and it works)

2nd PC Ethernet port is set for Netduma R1 at 192.168.88.5 (Disabled by default unless I want to use the Geo Filter feature when gaming on PC, then I'll disable 1st port and enable 2nd port)

 

The last picture shows UPnP Forwarding enabled in Netduma's misc settings.

 

Everything works fine and dandy. I'm sure if you are able to use your own router and allow a direct connection to the Netduma and then enabling Port Forwarding, the Netduma will refuse direct LAN access from the Asus router.

 

The main issue is that even when just using port 2 that is directly connected as a 'Netduma client', Netduma will still block access to the Router page via 192.168.1.3 But will only respond to 192.168.88.1 until I disable all Port Forwarding in the Netduma.

 

I'm sure you understand that an 'Asus client' can't access 192.168.88.1 directly without decreasing the router's subnet mask to 255.255.0.0. But by doing so, I will risk increasing latency due to there being more IP Address range available.

Thus this solution of routing 192.168.1.3 to 192.168.88.1 is a better overall solution along with giving that IP Address DMZ mode to ensure it is not affected by Asus's UPnP services but I digress.

 

You are free to replicate this setup and hopefully get this bug fixed before the next big update.

 

Anyway, thanks for clarifying Hyper Traffic

[ColonicBoom]

Do you also have UPnP enabled on the Asus as this could potentially cause conflicts. Do you have UPnP forwarding enabled on the duma misc settings? As this could also cause conflicts.

 

With Hyper traffic you should just use the services as they will include the ports you specify anyway. 

 

Can post my own thread if needs be but you can probably clear this up as you're on the subject...

I can't set my new ISP's router to 'modem mode' to pass through it so I have UPnP enabled on both the Duma and the ISP hub at the moment AND I have UPnP Forwarding enabled in Duma misc settings.

What's optimal? To disable the ISP hub's UPnP, Duma's UPnP, Duma's UPnP forwarding?

[Chive972]

Can post my own thread if needs be but you can probably clear this up as you're on the subject...

I can't set my new ISP's router to 'modem mode' to pass through it so I have UPnP enabled on both the Duma and the ISP hub at the moment AND I have UPnP Forwarding enabled in Duma misc settings.

What's optimal? To disable the ISP hub's UPnP, Duma's UPnP, Duma's UPnP forwarding?

1) Disable UPNP on ISP router

2) Set a static IP with the MAC address of the duma

3) Set the DMZ with that static IP

4) Port forward all the the ports needed for your game

[Netduma Fraser]

Looking at it again I believe the issue is coming from the fact your are port forwarding on the duma for an IP address outside the DHCP range it has. If you port forward with an IP inside the DHCP range do you have the same issue?

 

Can post my own thread if needs be but you can probably clear this up as you're on the subject...

I can't set my new ISP's router to 'modem mode' to pass through it so I have UPnP enabled on both the Duma and the ISP hub at the moment AND I have UPnP Forwarding enabled in Duma misc settings.

What's optimal? To disable the ISP hub's UPnP, Duma's UPnP, Duma's UPnP forwarding?

 

Recommend disabling UPnP & port forwarding on the ISP hub but ensuring you have the R1 in it's DMZ. I would disable UPnP forwarding in the duma miscellaneous settings. 

[ColonicBoom]

1) Disable UPNP on ISP router

2) Set a static IP with the MAC address of the duma

3) Set the DMZ with that static IP

4) Port forward all the the ports needed for your game

 

If I'm in the DMZ then wouldn't that negate the need to port-forward?

 

 

Recommend disabling UPnP & port forwarding on the ISP hub but ensuring you have the R1 in it's DMZ. I would disable UPnP forwarding in the duma miscellaneous settings. 

 

I'd rather not cut my firewall out completely for all devices though, so what's the alternative?

[AsNCo]

Looking at it again I believe the issue is coming from the fact your are port forwarding on the duma for an IP address outside the DHCP range it has. If you port forward with an IP inside the DHCP range do you have the same issue?

Could that be it? Will try it later though you know, by setting a static IP within the DHCP range, it could bring about a conflict of IP addresses if another device is turned on before the PS4 that was given a static IP. That is why it is better to have a static IP out of the DHCP range. Kind of weird to recommend otherwise.

 

EDIT: Just tried it, still the same issue. The moment I enable even just 1 port in Port Forwarding and click apply, the 192.168.1.3 IP address stops working.

[AsNCo]

1) Disable UPNP on ISP router

2) Set a static IP with the MAC address of the duma

3) Set the DMZ with that static IP

4) Port forward all the the ports needed for your game

Hi. So I also just tried the disable UPnP on the Asus router and the conclusion is that once again, when I enable just 1 Port Forward ports in the Netduma, it again makes me unable to access the Netduma router page via 192.168.1.3

 

So now both the suggestions given failed.

[Chive972]

Hi. So I also just tried the disable UPnP on the Asus router and the conclusion is that once again, when I enable just 1 Port Forward ports in the Netduma, it again makes me unable to access the Netduma router page via 192.168.1.3

 

So now both the suggestions given failed.

Make sure that your host filtering is configured with the port 3074 TCP/UDP both and it won't be a problem.

I got the same issue when my host filtering is configured with playstation network.

[Netduma Fraser]

I would suggest doing a 1 on 1 but as you are quite far away it would be incredibly laggy. I will try and replicate your settings as much as I can next week though it won't be exact and see if I can come up with a solution.

[AsNCo]

I would suggest doing a 1 on 1 but as you are quite far away it would be incredibly laggy. I will try and replicate your settings as much as I can next week though it won't be exact and see if I can come up with a solution.

Sure. That will be great. Thanks