Xbox One - Black Ops 3 - BOUNTY
-
Hey everybody,
Does anybody have an up-to-date, working solution for allowing multiple Xbox Ones behind a single IP to play games together? To preface, I am running 2.3.4 and I have all 3 Xboxes with open NAT via DHCP reservations, static NAT outbound, and UPnP.
I am specifically having an issue with Black Ops 3. All Xboxes grab the Teredo port when they come online. However, when the first Xbox gets on COD, it grabs 3075 and sometimes 3076, then successive Xboxes fail to make it online in COD, usually getting 3075 internally mapped to a slew of seemingly random ports.
Has anybody else experienced this and has anybody found a good solution?
I followed this post: https://forum.pfsense.org/index.php?topic=105767.0 , but had no success. I still had open NAT on the two Xboxes I configured this way, but had the same issues with COD.
Thanks in advance!
** UPDATE**
I've yet to garner any responses from this forum, probably because I've asked noob questions, so I've decided to add a bounty of $50 to start as this is really a burning question for me. I've spent too much time, money, and effort building a machine to use as my pfSense router to have to resort to going back to my r8000, just so my housemates can game together.Also as an update to what has been attempted, I've now changed my ACL entries to have one Xbox be allowed 3074, the next 3075, the final 3076, then 2 rules for all of them to be allowed to grab 53-3073 and 3077-65535, as it seems from another forum that this was Activision's suggestion. Still no dice.
-
This is great. I like them very much
Thank you very much. I will also introduce to my friends, hope you have a lot of good new and meaningful topics. -
Also as an update to what has been attempted, I've now changed my ACL entries to have one Xbox be allowed 3074, the next 3075, the final 3076, then 2 rules for all of them to be allowed to grab 53-3073 and 3077-65535, as it seems from another forum that this was Activision's suggestion. Still no dice.
You cant do that.. Xboxs try 3074, then a Random Port (40k+) for Teredo, you MUST allow Xboxes to grab ANY port they want, the ONLY one you can deny is 3074, nothing else.
You can not force an Xbox you use certain ports by restricting what UPNP will allow, the Xbox will just give up since UPNP doesn't tell it "you can only use these", the Xbox ask UPNP, "can i use this", UPNP say nope, Xbox ask then "can I use this", UPNP says nope, Xbox gives up.
The ONLY UPNP rule you should have is.
deny 3074 192.168.1.0/24 3074 <<---- Replace 192.168.1.0/24 with you LAN Subnet
This forces the Xboxes to pick a different port for "Teredo", this also allows all games on all Xboxes to UPNP themselves another port if they need it.
As far as UPNP goes, every Xbox MUST be allowed to use every port except 3074.
In my setup, I have no Xbox Dedicated Inbound or Outbound NAT Rules, the only thing Xbox Related is a deny ACL for 3074.
For Outbound NAT my whole LAN has Static Port, making a separate rule is not very helpful, and forcing random ports for LAN devices hurts worse then it helps anyways, not that it hurts much, point is it offers practically 0 benifit.
I have UPNP only Blocking the use of 3074 "deny 3074 10.0.1.0/24 3074".
Then for "NAT Loopback" or "NAT Reflection" I have
Goto System -> Advanced -> Firewall & NAT
NAT Reflection mode for port forwards: Pure NAT
Enable automatic outbound NAT for Reflection: Check/EnabledThat is it, Xboxes have full open NAT, any Games can UPNP more ports if they need, and they can talk to each other via the WAN IP.