Jump to content

Bert

Members
  • Content Count

    370
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by Bert

  1. Yeah that's exactly what I was doing but for some reason the packets over the bridge weren't showing up.
  2. You are using bridged instead ICS? When I tried bridging I could not get wireshark to read anything. Maybe I need to try bridge mode again. That probably makes getting open NAT easier and explains why I could not get the game to run on port 3074.
  3. That is weird. It changed for me when I went from my PC ICS connection to test with wireshark back to directly plugged into my XR500.
  4. The difference between having the source port changing is between open and moderate NAT. Basicly is you have open NAT source is always 3074 (on PS4) If you have moderate NAT the source will be in the range 62000-65535. You can go into the network tab in MW and display the external IP, it will show the port its using. 3074 or 6xxxx.
  5. No but what I meant is that there is more communication going on with the server, outside gaming traffic. I was trying to separate that but I don't think it's possible with open NAT. When I use moderate NAT I am sure I can. Because in my previous setup the QoS light only lit up when you were in the lobby and playing. With 3074 - 30000-45000 it lights up as soon as you boot the game, so it's hard to know if you actually prioritize game traffic instead of other traffic from and to the server.
  6. Yeah I see where you are coming from. When I was set to moderate NAT, I had communication from 3074 to 30120 on the server. And this was just idling in the lobby, not searching for games etc. And actual game traffic was 62000-65535 to 31000-45000. Looking at the time stamps it's game traffic in your log though. Maybe on open NAT both traffic go to that same port. By the way the IP you are crossing out is a internal one, nobody can use that for anything. Saves you the hassle
  7. They are not hosted by Sony or MS, servers are 3rd party hosted. So it doesn't make a different anyhow.
  8. When I used R1 I could never get above 55 mbit either in PPPoE setting. For people that connect straight to a modem or ONT with their R1 I would actually get something like a Edgerouter X and simply run them in tandem, add your credentials in the ER-X and it should work better. ER-X is only 60 bucks I believe so a cheap work around. Or simply use the ISP router for that. The other route is going XR500 but a little warning here, with a lot of fiber companies if you want to connect straight into the ONT you need to set up VLAN tagging, and that is bugged in the XR500. So really you would need a switch or another router in front of your XR500 anyway. Some ONT's allow a setting for VLAN tagging though but often it needs setting up from the provider's side. So really I doubt you will get help with this.
  9. For in game optimal is obviously 60 packets per sec on both sides. If you have UDP 3074 in your prioritization, there is also some other talk with the server going on on 3074. But with open NAT they all come from the same port. For moderate NAT you need to set source to UDP 62000-65535 instead of UDP 3074 as the game uses different ports for game traffic in that case.
  10. I have found the port ranges also change with your setup. Basicly OPEN NAT = SRC 3074 Moderate NAT = SRC 62000-65535 anywhere in there Also it might be coincidence but I was playing on my alt account with crossplay on, and it seems like the PC players were unkillable. So I turned that off as well.
  11. If you have windows 10, try using the speedtest.net desktop app. For me, their website always reads low but for some odd reason the desktop app is bang on. DSL reports usually doesn't give me accurate results due to the distance to their server.
  12. Could be but then you should see it in the last result as well. Note that the CoD servers don't respond to ICMP requests. So what you see on DumaOS and Pingplotter is usually the hop before that. Usually doesn't matter though as it is very close.
  13. Your router is just filtering ICMP requests. Ie it prevents flooding. As long as you get 100% to the final target it's fine. Not all servers / routers are happy with you pinging them all the time.
  14. It depends on your ISP and a number of things. You should get a lower ping from a geographical point of view. But depending on your equipment and the routing to the server you might not get it better. From The Netherlands I get 8ms to AMS, 12-15ms to London and 15-18ms to Frankfurt. Paris is a bit odd as it gives 25ms. Spain gives me 25ms also and Italy gives me 28ms. 50ms in game is not bad by the way that is about 34ms for ICMP ping. It's nothing to worry about.
  15. These ports mentioned in the starting post don't work. I have UDP SRC 62000-64000 and DST 31000-45000 and the reverse rule into QoS at the moment. For some odd reason I found some communication with the datacenter (in my case Amazon Singapore) at 30110 and 30120 while just sitting in the lobby. With the above ranges it turns on QoS only from the moment it finds a lobby until you return to the lobby. There it stays on for a minute until it doesn't detect any traffic and then switches off. I can't say that it makes a difference though.
  16. Here in Asia you litterally can't play CoD without a Netduma. Well you can but you get connected up to Japan and then it's game over. There is a second of delay between shot and hitmarker LOL.
  17. I use internet sharing and run my console through my PC. But I think you can make it work by renaming the executable file. From what I see you're better off prioritizing something like source 60.000-65.000 destination 30.000-40.000. Better is the actual ports but you have to change your QoS every time you enter a new lobby. I checked on my setup with the default QoS option and the hitreg is really fine. If you experience delays it's in the game not in your router.
  18. These ports quoted technically can't even work. Whenever I watch MW traffic on wireshark I get a source port in the 60.000 range and a destination in the 30.000 range. They are changing every time however source stays the same every time you start the game. So for gameplay traffic implementing 3074 in your ports doesn't seem to make a difference. I think it's only used by Demonware for matchmaking. That's why I just stick with the Games Console classification if it's for PS4 / Xbox.
  19. Bert

    Openwrt

    What type of router is it and sort of CPU does it have? CAKE is pretty hardware intensive.
  20. Well depending on your home network you might not need it. Ground war is a bit wonky since the servers run 20Hz. That means that update rates from the server are lower. So you will always have a longer delay between shot and hitmarker.
  21. Issue with MW is that the ports for game traffic keep changing. I have just set it to DumaOS Games console under QoS but for PC there seem to be some issues. Port forwarding doesn't affect latency or hitdetection.
  22. I think you both had the same thought LOL.
  23. They have always done that. So many times when I quit a match they just toss you back in the same lobby. You can run and gun just fine in this game but the more slow playstyle currently has a lot of advantages. However. There is probably 10+ ways a player can improve himself. Most people just stand opposite of eachother, shoot, or strafe a bit and shoot, or at best use cover. If you're in a 1:1 situation you need to figure out other tactics than shoot and aim for the best.
×
×
  • Create New...