-
Posts
3796 -
Joined
-
Days Won
159
Posts posted by Netduma Alex
-
-
@shrooma @Grimm @verydispleased
My apologies for the delay! I will remind Joseph to get this done today.
Ooh that rhymed...
-
9 hours ago, verydispleased said:
2600:6c5d:5000:173e:bcfb:f6f2:417a:c390
71.9.203.143
7777 is open and im on 1.03.3
I have forwarded this to Joseph so he can send you the fix.
-
On 1/3/2019 at 1:07 PM, YOBIGDUSOFLY said:
Awesome thank you! You are the best!
11 hours ago, Zeddarius said:Got the original email but haven't been receiving the updates.
Check your forum messages.
-
The R1 is quite dated now in terms of hardware so it's possible that the 80mb is a hardware limit. Your speeds might improve with DumaOS although in my experience DumaOS is actually more taxing on the hardware than the original firmware. Nevertheless, it may be worth a try. You can always downgrade again.
I'll forward this to Joseph so that he can fix your firmware for upgrades.
-
I like these ideas a lot!
We're aware of how useful these features would be...
And i'll make sure the devs know that people really want this.
- Zippy, Dave Masefield and Nalsano_
-
2
-
1
-
On 7/19/2019 at 10:51 PM, julien5032 said:
please upgrade my netduma thank
PortStatus7777open (98ms)Okay, i'll forward this to @Netduma Joseph - We'll let you know when it's done!
-
Yes that might be related, i've never seen that before.
I'm going to forward this thread to the devs so that they can figure out what's going on here.
-
No I think it happens with every service but i'm not sure.
-
Maybe the correct list will be reinstated if you downgrade your firmware and upgrade it again?
Download this firmware and send it to your router: https://kb.netgear.com/000053241/XR500-Firmware-Version-2-0-0-28
Then download this firmware and upgrade to it again: https://kb.netgear.com/000060464/XR500-Firmware-Version-2-3-2-40
-
The DNS leak is a known problem, we're working on that.
No unfortunately there's no way to make the VPN cover a whole physical port. Good idea though, i'll add it to the suggestions list.
As for the fact that you don't have any Australian cities in your list, that's really weird, i'll ask the devs.
-
Could you take a screenshot of the menu with the cities missing?
-
You said there's no cities listed for Australia? On mine I have Brisbane, Melbourne, Perth and Sydney
-
It's possible that the preset you were using is out of date. Which location were you attempting to use that didn't work? I can test it to see if we have to update it.
-
Well i've never tried anything like this, but I think it could work.
- Have the ASUS router connected to your modem, apply your QoS settings
- Connect the LAN port of the ASUS to the WAN port on your R1
- Go to System Information on R1, write down WAN IP, put this WAN IP into the DMZ on the ASUS
- Go to QoS on R1, Anti-Bufferbloat menu, tick Disable QoS
- Connect gaming device to R1, add to Geo-Filter
- Use Geo-Filter as you normally would
Hopefully, by putting the WAN IP into the DMZ of the ASUS, you'll avoid any double-NAT issues.
-
Of course there's presets for PureVPN and hidemyass so I guess i'd suggest those, although I'm obviously a bit biased!
Anything with OpenVPN 2.4.3 config files available will work though.
-
Is that the same as the speeds from the WAN port?
-
Oh well if the spiking is occurring because of other devices in the house, the anti-bufferbloat options in DumaOS might be able to sort that out.
-
I asked some of my colleagues and they suggested enabling the Guest Network on your XR500 and connecting the Hue Bridge to that. I don't know why that would work but hey it's worth a go right?
-
What about the Port Forwarding page?
-
On 5/31/2019 at 9:55 PM, Donald said:
Ok now you need to follow the rest of this guide to get your router up to date:
-
17 hours ago, Donald said:
Ok thanks so much
Sorry about the delay, we're going to do it tomorrow now, for sure.
In the meantime please make sure that you've done everything in this guide so that we don't have any problems connecting:
-
Didn't have time to do it on Friday, will try and get it done today.
-
2 hours ago, Donald said:
That link takes me no where, I don't know how to make the router accessible
Okay well i'll copy the relevant section of the guide:
- Access your Netduma R1 interface
- Go to >Settings >Miscellaneous
- Tick ‘Allow remote access to Netduma tech support’
- Go to Settings >UPnP and enable the feature if it's not already enabled
- Go to Settings > Port Forwarding and remove any rules
- Now verify that everything is working by going to https://www.whatismyip.com/port-scanner/
- In the port entry field, type in 7777 and click Scan
- If the result is 'Open' then you have successfully allowed us to access your router to run the fix.
-
I'll add that to our list of suggestions!
Upgrading your Netduma R1 to DumaOS from a version lower than 1.03.6
in Netduma R1 Support
Posted
Welcome to the forums!
Yes i'll get it done.
And yes, once the bug is patched you should upgrade to the most recent "original firmware" and after that, you could upgrade to DumaOS if you wanted.