The only way around this is to let the firewall dynamically remap the source port of the outbound traffic to ensure a unique UDP connection in the stateful database for the appropriate XBOX.
#XBOX ALTERNATE MAC ADDRESS NOT WORKING HOW TO#
This is a HUGE problem if all packets are being statically translated, because the firewall won't know how to properly create a stateful connection for both XBOX's. I also discovered that when a Halo 5 match starts, both of the XBOX's in my house were creating a UDP connection to the exact same host using the exact same source port and destination port combination at the exact same time. By looking at the traffic, I discovered that certain UDP/TCP packets will use the XBOX configured port as the source port of the packets. XBOX traffic uses a lot of multicast and UDP packets. All traffic from the XBOX will preserve the original source port no matter what which doesn't work well with Halo 5 and multiple XBOX's. This will help you achieve Xbox Live Open NAT, but it's like using a bazooka to kill a mosquito.
I noticed that most posts that include a "fix" for the XBOX Live Open NAT issue will tell you to configure an outbound NAT rule for the XBOX and choose the option "Static Port". I use OPNsense as my firewall, but the same steps will work on PFSense or any other firewall that allows you to configure inbound port forwarding and outbound PAT (port address translation). I'm specifically talking about Halo 5, but it could pertain to other games as well.įor anyone else that is still having a problem, I have a potential solution that allows multiple XBOX's connected behind a single Internet IP address achieve an open NAT on XBOX Live, and work with Halo 5. This might help others with multiple xbox's behind the same public IP.
0 kommentar(er)
