Jump to content

RL317

Members
  • Content Count

    1,137
  • Joined

  • Last visited

  • Days Won

    13

Reputation Activity

  1. Like
    RL317 reacted to Netduma Admin in Which takes priority: Allow/Deny or Strict Mode?   
    @lllRL is correct - it will not activate in spectating mode. 
    Great question though - first to ask that!
  2. Like
    RL317 got a reaction from Kudarat in DumaOS on the Netduma R1 is now in Open Beta!   
    Yeah. I often do updates with my phone! 
  3. Like
    RL317 got a reaction from dpk_ydv in Which takes priority: Allow/Deny or Strict Mode?   
    I believe spectating mode acts like unticking enable on the pre-DumaOS R1. It's recommended for games that already have a server browser so it would make sense; I don't think allow/deny would be in effect in that case. 
  4. Like
    RL317 reacted to PUBzZz in DumaOS on the Netduma R1 is now in Open Beta!   
    I'm not trying to tell anyone how they should feel. However I signed up within the first 30 minutes of the sign up going live and it took me 3 days to get my link.  Sure during those 3 days I was wondering what the hell is taking so long. Listen, trust me when I say this. Once you get the DumaOS on the R1 you will be happy you waited. 
    Also my personal advice. Once you update to DumaOS and it's up and running do a Factory Reset. Then put in all your settings.  Some settings don't carry over well when you upgrade to the DumaOS and you will get errors when you try to edit or delete stuff.
  5. Like
    RL317 got a reaction from DAKOTADOCKALL in DumaOS on the Netduma R1 is now in Open Beta!   
    It's being rolled out in stages bud. There was a ton of interest as you can imagine, so everyone will get their chance eventually
  6. Like
    RL317 got a reaction from titofuenla in DumaOS on the Netduma R1 is now in Open Beta!   
    It's being rolled out in stages bud. There was a ton of interest as you can imagine, so everyone will get their chance eventually
  7. Like
    RL317 got a reaction from Netduma Fraser in DumaOS on the Netduma R1 is now in Open Beta!   
    It's being rolled out in stages bud. There was a ton of interest as you can imagine, so everyone will get their chance eventually
  8. Thanks
    RL317 reacted to Netduma Admin in Advanced traffic prio not working on downstream   
    I'll DM you something now.
  9. Like
    RL317 got a reaction from Buster in Reverting to Original Firmware   
    Nice one. That was pretty useful when I needed to swap a modem or cable out to make sure my line hadn't gone to *beep* lmao
     
    Plus now I'm using the Huawei HG612 modem for its bridge mode, I can't access the GUI through the R1 as you can with a regular ISP hub because you need to plug into its second LAN port and change your laptop IP to access it - a bit of a kerfuffle if you just want to check something quickly. The Netduma Diagnostic test lets you easily check if you've been switched from fast path to interleaving on the go with your phone. 
  10. Like
    RL317 reacted to erwan55 in DumaOS on the Netduma R1 is now in Open Beta!   
    Guys ... be patient .. I've signed in the first day and got my upgrade this afternoon 
     
    thank you Netduma Team!!! 
  11. Like
    RL317 reacted to Netduma Fraser in Reverting to Original Firmware   
    What pollution said above. Are you reffering to the connection diagnostic that would give you ping/jitter/spikes etc? If so then yes I expect that will come at a later date as it was a good feature.
  12. Like
    RL317 reacted to Racer15crx in DumaOS on the Netduma R1 is now in Open Beta!   
    i have been everyday for 5 days XD almost every hour as well. i have a problem XD.
  13. Like
    RL317 got a reaction from Racer15crx in DumaOS on the Netduma R1 is now in Open Beta!   
    Check your spam. I signed up the minute it was announced and it took me a while to realise the email was hiding in my spam box because I never look in there LOL
  14. Like
    RL317 got a reaction from Alex49H in How are you finding DumaOS on the R1?   
    I didn't even notice that, wow! 
     
    Naming the OS after A7Legit was a classy move. GG Netduma team. I'd like to buy you all a beer. 

  15. Like
    RL317 got a reaction from Netduma Jack in Help with BThub   
    Yeah that's my best advice mate. A cable can be easily damaged over time, so performance with it could even be worse than over WiFi. 
     
    You plug the cable into the first port on the left hand side of the Hub (not the small DSL socket but the first ethernet socket) and connect that to the port farthest on the left on the R1 (marked PoE I think). 
     
    Edit: sorry I misread that... coffee hasn't kicked in yet it seems LOL. How have you been connecting all of your devices with just the one cable? What device are you testing the speed on? 
  16. Like
    RL317 got a reaction from JOE1305 in DumaOS on the Netduma R1 is now in Open Beta!   
    My pleasure. Personally I was looking around for a "miscellaneous" tab for a while until I started clicking random stuff and noticed it was hidden up there haha
  17. Like
    RL317 reacted to JOE1305 in DumaOS on the Netduma R1 is now in Open Beta!   
    Thanks bro. 
  18. Like
    RL317 got a reaction from JOE1305 in DumaOS on the Netduma R1 is now in Open Beta!   
    Click the information button:

     
    And you'll be able to access the reset and reboot buttons here:

  19. Like
    RL317 got a reaction from Netduma Jack in How are you finding DumaOS on the R1?   
    I didn't even notice that, wow! 
     
    Naming the OS after A7Legit was a classy move. GG Netduma team. I'd like to buy you all a beer. 

  20. Like
    RL317 reacted to Dan in Reverting to Original Firmware   
    Teething issues I guess.....but reckon a large part of the CoD community owes Sledgehammer an apologetic nod at the least. They aren't the only developer to have issues at launch.
    The weird thing about P2P was that the hosts were all over the place in countries I'd need an atlas for. No UK, France, Italy or German connections in an hour's session so gave up.
     
  21. Like
    RL317 got a reaction from FLEX_Jastrzebie in Advanced traffic prio not working on downstream   
    It seems that regardless of what ports we set under source or destination, advanced traffic prioritisation will only cover upload traffic even if it's impossible for me to be uploading over those ports. I'll explain... 
     
    Using Wireshark we can see which ports are in use during different activities on a console (such as matchmaking, playing in a multiplayer game, using a voice party etc), and we could in fact see this on the pre-DumaOS R1 while clicking on bandwidth bars in the network monitor - you would see an overview of all ports in use on every bandwidth "bar". The mainstay in Call of Duty is 3074 and this is a commonly known port. However, what is less commonly known is that 3074 only exists on the console end, as it needs multiple ports available to communicate to the server. In Infinite Warfare for example, these are between 30000 and 50000.
     
    Obviously under QoS we have the classified games section for plug and play gaming, but if you know what you're doing this is preferable so you don't accidentally prioritise an irrelevant port as far as in-game performance goes. Actually I've noticed that either the classified games preset doesn't seem to make a bit of difference at all, or it can actually downgrade connection quality on the same server at the same latency. I played three games today:
     
    1. On 40ms with no traffic prio after discovering advanced prio wasn't activating;
    2. On 40ms with the classified games prio preset, in the same lobby as before;
    3. On 15ms with the classified games prio preset...
     
    The first gave me the most in-sync gameplay with faster hitmarkers than I've seen for months (I haven't touched this server since last year), the second was noticeably worse than the first despite now using traffic prio for ALL relevant ports, and the third game on the "best" latency while also using prio for arguably the most optimal setup gave me the most objectively laggy gameplay with delayed hitmarkers, assuming they were to pop up at all. I recorded hitmarker delays of up to 328ms(!) in that game, with many landed shots not registering. But I digress... 
     
    Anyway, the first thing I wanted to try was setting destination to 3074 UDP and source to 30k-50k to see if I could prioritise downstream, because of how behind the action I've often been and how much UDP lag I see on the downstream on Wireshark (as high as 200ms UDP latency on 7ms ping, as proven by the Wireshark capture below (check the bottom two timestamps), which seems to be the cause of me getting kicked from countless games because CoD has a limit of 800ms:

    You'll also notice that downstream is all 40040 (server) > 3074 (my console), and that a search of that 45.63.x.x IP will indeed show up as a Choopa server in London, which is 40 miles away from me. 
     
    I set this advanced prio up with src 30000-50000 and dest 3073 but noticed the "light" wasn't coming on to indicate prio was taking place, so I changed the destination to 1-65535 instead. It then lit up and showed it had kicked in, but only upload traffic was being prioritised for some reason in game, which is impossible because there's no port 3074 to upload to - it doesn't exist on the server end. At the same time there's no downstream traffic being prioritised or acknowledged:

    I thought maybe source and destination had been mixed up somehow during coding or as part of a strange bug, so I swapped them around:

    And as you can see, still only the upload traffic was being prioritised. The bottom setup actually makes sense, since you can upload from 3074 to the other port that's listening (somewhere between 30000-50000) on the server. However it's acting exactly the same either way: there's no download prioritisation taking place 😕
  22. Like
    RL317 got a reaction from DAKOTADOCKALL in DumaOS on the Netduma R1 is now in Open Beta!   
  23. Haha
    RL317 reacted to Gazz in DumaOS on the Netduma R1 is now in Open Beta!   
    It surprises me that I haven't read any threats of legal action given DumaOS on the  R1 has now moved from 'closed beta' to 'private Beta' not 'open beta'.  those threats won't come from me though cause i can't even pronounce 'beta' correctly......  or plug my R1 in.....
  24. Haha
    RL317 got a reaction from nyder in DumaOS on the Netduma R1 is now in Open Beta!   
  25. Like
    RL317 got a reaction from kinel in How are you finding DumaOS on the R1?   
    Installation went without a hitch, except for me not realising you need to use "admin" and "password" to sign in to the GUI lol
     
    I just loaded up Infinite Warfare for the first time in a few weeks and got a nuke in my first game with DumaOS LMAO. Something was next level broken with my connection for over a year on BT (and the same when I moved to TalkTalk) - I could get tiny latency, negligible jitter (I'm talking 50-100 MICROSECONDS at worst), zero packet loss etc, yet CoD matches would play like I was on a one bar. One day I bridged my PS4 connection through my laptop to run Wireshark and found I was getting UDP latency between packets as high as 2650ms between me and my local CoD server in the UK, which I can ping in a constant flat 7ms. I could fire my gun at a guy and not get a hitmarker for 200ms on a good day, over 500ms on a bad day, and it was genuinely like playing on a one bar... or half a bar ¯\_(ツ)_/¯ anyway I set up my DumaOS settings and after having some issues with UPnP, it was 2am by the time I found a game. I set a 750 mile radius around my home location dot in the south of England, had to wait a while because of the time, and all I could find was a late join but it'd taken long enough to find that match so I just said eff it and spawned in. A tryhard on the other team was 17-2, decimating my team; I even had a 3KD teammate who was getting rocked. I died a couple of times, once when weak, once when running unaware out of my spawn, and then I got a nuke LOL. This guy gets creamed not long after the tide turned and dashboards
     
    I turned off after that just because I'm tired and lobbies were pretty empty anyway. Of course it's only one game but it seems better to me ¯\_(ツ)_/¯ all I can do is get on tomorrow in the day time and hope it's consistently better, but it's a good start. I always wondered if the R1 was causing problems before, perhaps with how I installed the last original OS update? Idk, all I can do is speculate... 
     
    Couple of things I should report after flicking through the GUI:
     
    • There are issues with certain drop down menus. For example on the geofilter map zoom setting, it fades into the background and it's hard to see the magnification settings. With the advanced traffic prio drop down box (the one where you pick TCP/UDP) it just doesn't pop up at all. The background glows to acknowledge you're clicking on it, but that's it. Same goes for trying to change device type on device manager (a phone of mine is stuck as a "computer").
     
    • The LAN/WAN settings menu is buggy. Unless you move your cursor around or click random stuff beforehand, you cannot select PPPoE or static, or the options in those menus (such as MTU). Only after randomly clicking other settings can you interact with them. Also if you look at the LAN side and then click another submenu (such as UPnP or port forwarding), the screens seem to layer on top of each other making everything an indecipherable mess. Only by moving your cursor outside of the confines of that menu can you remove the additional text to see what you're trying to look at. 
     
    • UPnP does not work at all. When I first set everything up, I simply turned it on and then rebooted the R1 when I had everything set up. I turned on my PS4, loaded up IW and had a moderate NAT. I went back to the UPnP screen and nothing was showing up (it should have shown UDP 9308 and 3074). I disabled UPnP, re-enabled it, rebooted my console, loaded up the game and still it was moderate. I then came here to look for a fix and someone mentioned that it normally forces ports to open if you run a PS4 connection test (which takes care of 9308) and then simply join a lobby in CoD (and 3074 will open), but that did nothing so I just played with moderate NAT. I wouldn't mind using port forwarding (assuming it doesn't cause GUI freezing and WiFi dropouts when the geofilter is enabled at the same time, as happened with the original R1 firmware), but I use Remote Play and the ports used by my phone change all the time so I can't simply look them up and manually forward them. Obviously this is more serious than a few graphical issues as above, so it should be addressed first. 
     
    • Doesn't run well on a mobile browser. Unfortunately you can only see half of the screen of the GUI on a mobile browser, while the old firmware ran flawlessly on Android Chrome. You can get away with forcing the desktop version of the site, but that makes it more difficult to use and navigate due to shrinking everything. 
     
    Sorry for the essay but, yeah... I'm pretty happy overall. Only a few minor niggles to iron out, with a broken UPnP arguably being the most problematic. 
     
    While I'm here I'd just like to thank the team for the invitation and opportunity to try this out. Cheers and happy gaming my fellow nerds 🤓 
×
×
  • Create New...