Jump to content
NeeWii

DumaOS causing GlobalProtect VPN (required for my work) to disconnect

Recommended Posts

Hello,

DumaOS is causing the VPN installed on my work laptop (that I require to be able to access work systems) to disconnect. It will connect for a brief period of time, up to around 30 seconds, however it will then interrupt the connection and cause the VPN to disconnect and spend a while trying to reconnect again, and the cycle will repeat.

Under the previous version of NetDuma, I had more or less the same problem - but the workaround I had in place was changing the QoS congestion control settings to "Pre-emptive" rather than "Reactive". "Reactive" mode caused similar problems for me, but "Pre-emptive" allowed the VPN to stay connected just fine (albeit with much lower maximum bandwidth speeds). However I can't see any way to configure things in a similar way on the new DumaOS.

I have tried disabling QoS altogether on DumaOS, however this doesn't appear to fix the problem. Is there a way to replicate "Pre-emptive" QoS settings (or something similar) on DumaOS? Or any other solution to the problem (e.g. put my laptop on a DMZ, but I can't see the option to do that).

For reference, setup is VM Superhub 3.0 in Modem mode --> R1 DumaOS --> Netgear Nighthawk (wifi AP) --> work laptop.

Any help would be greatly appreciated. As it stands, DumaOS is not viable for me at all as I work at home.

Thanks,

NeeWii

 

Share this post


Link to post
Share on other sites

Very odd. If you disable QoS altogether and the issue still continues then the issue must be somewhere else (i.e. QoS is not the blocker).

Do you have IPv6 enabled? Please disable it in Network Settings for both LAN and WAN. I'm thinking that could be the cause.

Also please enable UPNP if you haven't done so already

 

Share this post


Link to post
Share on other sites

Hi - thanks for the response. I can confirm that the settings already have IPv6 disabled on both LAN and WAN, and UPnP is enabled also. I think a similar recommendation was made a couple of years back when I made a post about reactive mode causing the same problem (post appears to have disappeared though) - IPv6 didn't fix the problem in the old firmware either though. Is there anything else I can try? It's definitely something in the Duma, as I get no issues connecting directly via the VM Superhub.

And if not is there a usable workaround? I was thinking worst case scenario I could have the VM Superhub in router mode but the Duma in a DMZ? Then connect my work PC via the Superhub wifi and everything else through the Duma/Nighthawk. Far from ideal given the added wifi congestion but I can't picture any other option.

Thanks in advance.

Edit - I've attached the logfile after disabling QoS again, then re-enabling for a while - just in case it's of any use.

 

 

 

log-1541025451494.txt

Edited by NeeWii
logfile added

Share this post


Link to post
Share on other sites

Thanks Fraser, that would be greatly appreciated. Happy to help troubleshoot if needed.

In the meantime I've gone with my suggested workaround, with the R1 within the Superhub DMZ. For some reason in this configuration the speed I get is only around 130Mbps; using modem mode instead on the superhub gives me around 260Mbps (a 350Mbps connection but I figure the R1 is strained above 200Mbps). It's not wifi interference as disabling wifi on the superhub doesn't improve anything, only changing back to modem mode increases the bandwidth back to normal. Have you come across this before? Are there settings in the superhub that should be disabled when R1 is in its DMZ or something? I can't see anything about QoS or similar to disable in the superhub menu, I had thought something like that might be the cause.

Share this post


Link to post
Share on other sites

Great thanks!

The only things I can think of to do to give you the best chance of your higher speeds when in DMZ mode are:

  • Disable UPnP on hub
  • Disable any manual port forward rules added on hub
  • Disable WiFi on hub 

If you're still not getting expected speeds it may be a limitation with DMZ mode on the hub

Share this post


Link to post
Share on other sites
On 11/1/2018 at 1:16 PM, Netduma Fraser said:

Great thanks!

The only things I can think of to do to give you the best chance of your higher speeds when in DMZ mode are:

  • Disable UPnP on hub
  • Disable any manual port forward rules added on hub
  • Disable WiFi on hub 

If you're still not getting expected speeds it may be a limitation with DMZ mode on the hub

Hi Fraser,

Just upgraded to milestone 1.3, have noticed a significant decrease in download speeds (given the exercise I went through per above posts, I know that the speed through the Duma was satisfactory previously - believe I was seeing around 250Mbps on a direct wired connection (of a 300Mbs connection). My maximum download speed now is only around 160Mbs.I noted user "infernomachine" commented that they'd also seen an impact on their speeds upon upgrade - see Duma Admin response at:

Connecting directly to the Virgin Media Superhub immediately after the 160Mbs Duma result, actually gave me a download speed of 370Mbps on speedtest.net (it's easy for me to jump between them and compare given the Duma is just in the DMZ of the Superhub). Nothing has been changed recently on the Superhub either.

So I'm seeing a very severe difference in speeds compared to my potential maximum, and a severe drop in speeds from 250Mbps down to 160Mbps upon upgrade to milestone 1.3.

Has this been identified as a recognised issue? It would appear not from the Netduma Admin response above, but it definitely seems like something's up.

 

NeeWii

 

Share this post


Link to post
Share on other sites

Have double checked, no change to IP address, superhub also still configured correctly. Is there a way I can downgrade to previous version/milestone to make absolutely sure it’s this update that caused the problem?

Share this post


Link to post
Share on other sites
10 hours ago, NeeWii said:

Have double checked, no change to IP address, superhub also still configured correctly. Is there a way I can downgrade to previous version/milestone to make absolutely sure it’s this update that caused the problem?

There is a way to downgrade - check out the instructions here: http://support.netduma.com/en/support/solutions/articles/16000085792-downgrading-back-to-the-original-r1-firmware-from-dumaos.

Have you tried removing the R1 from your Modem DMZ and adding it again using the WAN IP shown on the System Information page?

Share this post


Link to post
Share on other sites

Hi Jack, just checking - is the above method suitable for downgrading from one version of DumaOS to another, rather than from DumaOS to original R1 firmware?

Have tried removing R1 and re-adding, but no change. Settings were the same as before, WAN IP hadn't changed for the R1 and so it was still configured correctly in the Superhub.

Share this post


Link to post
Share on other sites

Hi both. Had a play around, both versions are showing me the slow speeds so it can't have been a result of updating. I have no idea what has changed since I first set this all up, but for whatever reason the speeds must have dropped down on the Duma at some point and I only noticed after updating the firmware. Seems I'm back to square one in getting a setup with decent speeds!

I've tried re-applying the original options suggested (turning off uPnP, WifI, etc, on the Superhub) to no avail - seems the Duma just doesn't do well in the Superhub DMZ, and modem mode is still not an option for me given the Duma blocks my work VPN.

I'll try as you suggest Fraser, and do a complete factory reset - will let you know how I get on.

Thanks again.

Share this post


Link to post
Share on other sites
1 hour ago, Netduma Fraser said:

Okay well at least we can rule out the update causing the issue specifically. Keep us updated!

So I tried the factory reset, no change to the speed results on factory settings, and no change also when putting back to my previous settings.

Just finished doing some more testing, all direct ethernet cable into the Duma or Superhub respectively:

 - Speeds, whether in the Superhub's DMZ, or with the Superhub in Modem mode, are largely equivalent it seems. I'm averaging around 150Mbps in each (varying between around 130Mbps and 180Mbps in tests; no other network traffic at the same time). A little surprising to me, as I'm sure the modem mode had previously yielded better results a while back (>200Mbps).

- Again, plugging a cable directly into the Superhub yielded a far greater speed - a solid 380Mbps.

Unless there's a deficiency in both the Superhub's modem mode, and in it's DMZ feature, the above would suggest it's the R1 itself that's bottlenecking things. The key features of the R1 I use are the QoS (and good uPnP implementation for open NATs) to allow for Plex streaming from my home server, at the same time as playing games online on multiple consoles. - I'm honestly at a bit of a loss as to what to do here - while it's functional, it's a real shame to be losing out on more than half my bandwidth in getting effective QoS. Just now I'm pretty much just throwing money at Virgin Media without getting the benefit of what I'm paying for!

I really appreciate the help you've both provided, but I think at this stage it's looking like I'll have to investigate what other routers are out there with effective (if not necessarily quite as user friendly as the Duma!) QoS / uPnP abilities. If you have any further suggestions though they'd still be appreciated!

Thanks.

Share this post


Link to post
Share on other sites

This is quite a strange case. I'm in agreement with the others above - if you disable QoS and loads of other features yet are unable to reach those speeds, this has to be some kind of limitation caused by something else. It's very possible that your speeds are lower due to the hardware being old, as routers can degrade over time. When did you get your Netduma?

If this speed issue happens no matter whether your R1 is in the DMZ or not, or despite any different modem settings, it's most likely a hardware fault.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×