Xbox Live primarily uses port 3074 udp. If the xbox determines that port 3074 is not available, then it will attempt to connect through a randomly generated port. In a best case scenario, one xbox will have an open NAT, the other will have a moderate NAT.
Having two xboxes, the first xbox that is turned on claims port 3074, while the second attempts to use a random port. I have one xbox that I use more than the other, so I went ahead and defined NAT rules for that xbox; that way it will always have an open NAT.
Code: Select all
0 ;;; Xbox Live
chain=dstnat action=dst-nat to-addresses=10.254.6.43 to-ports=3074
protocol=tcp src-address=!10.254.6.0/24 in-interface=ether1-gateway
dst-port=3074
1 chain=dstnat action=dst-nat to-addresses=10.254.6.43 to-ports=3074
protocol=udp src-address=!10.254.6.0/24 in-interface=ether1-gateway
dst-port=3074
2 chain=dstnat action=dst-nat to-addresses=10.254.6.43 to-ports=88
protocol=udp src-address=!10.254.6.0/24 in-interface=ether1-gateway
dst-port=88 Due to the 2nd xbox trying to use a random port, I enabled UPnP to facilitate this. The problem I am running into is that the second xbox is generating a dynamic NAT rule for port 3074. Which I have already defined a static rule for.
It was my understanding that the tik should not allow a duplicate NAT rule to be created, and that it should report back to the xbox that this port is unavailiable, correct?
This issue has been plaguing me for a while now, and I cannot seem to come up with a viable solution. If I disable the static NAT rule, then both xbox's have a moderate NAT, or a strict/moderate NAT. Both of which can affect gameplay.
Xbox1 has IP 10.254.6.43
Xbox2 has IP 10.254.6.38
both are static.
