Question Helpl opening ports for call of duty warzone hub3.0

[Ollyh2015]

having a network issue with warzone and activation advised me the only thing left to try is port forwarding but it’s proper confusing for me. They’ve sent me the port numbers but I have no clue which box to enter them on my router can anybody help im not very good with routers I’ve attached photos of port numbers and the forwarding page on my router can someone explain which numbers go
Into which box it would be much appreciatEd

 

[Fallen Kell]

Basically looking at that second pick, you need to put in the IP of your xbox at the top (and will need to change it every time you get a different IP address with your xbox if you are just using DHCP and have not setup a static DHCP rule for your xbox to always obtain the same IP address on your internal network), and for each of the ports listed at the bottom, you need to add them for both the external and local value and select the appropriate protocol (i.e. TCP, UDP, or both). So for example, you need:
Local Start Port: 3074
Local End Port: 3074
External Start Port: 3074
External End Port: 3074
Protocol: TCP
------------------------------------------
Local Start Port: 88
Local End Port: 88
External Start Port: 88
External End Port: 88
Protocol: UDP
------------------------------------------
Local Start Port: 500
Local End Port: 500
External Start Port: 500
External End Port: 500
Protocol: UDP
------------------------------------------
Local Start Port: 3074
Local End Port: 3075
External Start Port: 3074
External End Port: 3075
Protocol: UDP
.
.
.
etc...
But keep in mind, doing this basically opens up your xbox to the external network on these ports (i.e. someone performing a network scan would then have access to communicate to your xbox when using those ports when scanning your router's IP address (as the router will forward that to the xbox). Unlike normally where your xbox would have to first connect to an external device and only that device (or a spoof) would be able to communicate back to your xbox (i.e. the initial connection has to start from your internal network, an external entity would not otherwise be able to start a connection to your equipment on it's own). It might not be an issue if there is no remote exploit that can use those ports/protocols to do anything with the xbox, but you are opening an avenue for possible remote access.

 

[Ollyh2015]

Basically looking at that second pick, you need to put in the IP of your xbox at the top (and will need to change it every time you get a different IP address with your xbox if you are just using DHCP and have not setup a static DHCP rule for your xbox to always obtain the same IP address on your internal network), and for each of the ports listed at the bottom, you need to add them for both the external and local value and select the appropriate protocol (i.e. TCP, UDP, or both). So for example, you need:
Local Start Port: 3074
Local End Port: 3074
External Start Port: 3074
External End Port: 3074
Protocol: TCP
------------------------------------------
Local Start Port: 88
Local End Port: 88
External Start Port: 88
External End Port: 88
Protocol: UDP
------------------------------------------
Local Start Port: 500
Local End Port: 500
External Start Port: 500
External End Port: 500
Protocol: UDP
------------------------------------------
Local Start Port: 3074
Local End Port: 3075
External Start Port: 3074
External End Port: 3075
Protocol: UDP
.
.
.
etc...
But keep in mind, doing this basically opens up your xbox to the external network on these ports (i.e. someone performing a network scan would then have access to communicate to your xbox when using those ports when scanning your router's IP address (as the router will forward that to the xbox). Unlike normally where your xbox would have to first connect to an external device and only that device (or a spoof) would be able to communicate back to your xbox (i.e. the initial connection has to start from your internal network, an external entity would not otherwise be able to start a connection to your equipment on it's own). It might not be an issue if there is no remote exploit that can use those ports/protocols to do anything with the xbox, but you are opening an avenue for possible remote access.

Thanks for response you’re probablygoing to think I’m really thick here lol. Should I enter them all exactly how you shown above ? Or is that just an example

 

[Fanatical Meat]

Thanks for response you’re probablygoing to think I’m really thick here lol. Should I enter them all exactly how you shown above ? Or is that just an example

I am far from a networking expert but I do know from running a few different home game servers port 3075 & 3074 are pretty common game server ports that need to be forwarded.

 

[Ollyh2015]

I am far from a networking expert but I do know from running a few different home game servers port 3075 & 3074 are pretty common game server ports that need to be forwarded.

Do you think I should just do them ones then? It’s really confusing for me and activision on are no help at all just told me I need to forward the ports to fix the issue

 

[Fanatical Meat]

Do you think I should just do them ones then? It’s really confusing for me and activision on are no help at all just told me I need to forward the ports to fix the issue

again no expert but yes, I would try forwarding them first then see what happens.
I had tons of problems figuring out how to port forward. Make sure you are doing it right.

 

[ch33zw1z]

Really just a few basic steps, you'll probably learn in the process, as port forwarding will work the same for whatever you need to forward.

*If you don't wanna forward ports, you can put the device in the DMZ (demilitarized zone) in the router config. This will put it outside the routers built in NAT/firewall config. But, be warned, ALL ports are allowed and it's considered a vulnerability that most people won't accept

Ok, onto the steps...

Step 1 - figure out what the INTERNAL IP is for the device in the network. Either look at the devices settings or find it in the router client lease.

This is also a point where you will want to set a STATIC DHCP IP for that specific device (and outside the DHCP pool addresses). You'll do this is the router, somewhere in the config pages. This is a good step to ensure 1) the router always gives this device the same IP 2) no static config required on the device

Once you do this, reboot the device a few times and check it's IP config to ensure its getting the IP you configed the router to give it.

Once you're confident this is working ok, move on...

Step 2 - Configuring the rule. As you can see in the second pic, there's a few options. In this case, the LOCAL IP is the IP you configured in step 1. The rest is as simple as configuring the internal and external ports, either individually, or as ranges. In this case, the Internal/external ports should match.

*Much of this is searchable on the web.
** If you don't do Step 1, and the device gets a different IP, then you will need to edit your rules and change the local IP to the new IP lease.

 

[Fanatical Meat]

^^^^Listen to the guy above, he is a real computer networking guy.