billion_fan wrote:
With the two Xbox's they both show open NAT within the network settings, but within the game one xbox shows a Moderate, I have forwarded both threads to our engineers, hoping to get a reply soon
Thank you. Much appreciated.
Also other routers seems to have issues also, so hoping our engineers can come up with something (other then a range of static WAN IP's)
I've read that uPnP is a bit hit and miss in its implementation and that for some router manufacturers two consoles can have open NAT with uPnP and other manufacturers not. Unfortunately upnp doesn't seem to be implemented reliably as far as I can gather across the board - perhaps Billion can be leaders in reliable upnp . One thing for sure though is (at least I think it is) that once a device is powered down it should release the previously used open port(s) from the virtual server (upnp) list for use by other devices and the Billion should not hold on to these ports ad infinitum until the router is power cycled. That one should hopefully be fixable . Hopefully - pretty please .
I've read that uPnP is a bit hit and miss in its implementation and that for some router manufacturers two consoles can have open NAT with uPnP and other manufacturers not. Unfortunately upnp doesn't seem to be implemented reliably as far as I can gather across the board - perhaps Billion can be leaders in reliable upnp . One thing for sure though is (at least I think it is) that once a device is powered down it should release the previously used open port(s) from the virtual server (upnp) list for use by other devices and the Billion should not hold on to these ports ad infinitum until the router is power cycled. That one should hopefully be fixable . Hopefully - pretty please .
That is what I am trying to get our engineers to concentrate on (UPNP rules not clearing)
it might be of interest to you that some of the newer games are coded for uPnP IDG2.0 (blops3 and destiny for instance) as such the router might be suffering from an IDG version mismatch and thus the problem with one getting a restricted or moderate nat, i just enabled upnp on my router (8800axl) and despite having multiple 360's and pc's only have the one xbone and no ps4 and haven't had any problems, but so far we don't have destiny or blops3 so haven't run into this issue, perhaps the virtual server is only connecting one device as an authenticated unit and the remainder are not thus the moderate/restricted status on the nat within the game itself, not a code geek but perhaps its all linked to one bad line in there /
the virtual server not releasing is an issue I've run into though and i found setting static ip's up for all the devices removed the problem of not freeing up the ports (it just re-connects the device to them each time you fire up that bit of kit)
nanotm wrote:it might be of interest to you that some of the newer games are coded for uPnP IDG2.0 (blops3 and destiny for instance) as such the router might be suffering from an IDG version mismatch and thus the problem with one getting a restricted or moderate nat, i just enabled upnp on my router (8800axl) and despite having multiple 360's and pc's only have the one xbone and no ps4 and haven't had any problems, but so far we don't have destiny or blops3 so haven't run into this issue, perhaps the virtual server is only connecting one device as an authenticated unit and the remainder are not thus the moderate/restricted status on the nat within the game itself, not a code geek but perhaps its all linked to one bad line in there /
the virtual server not releasing is an issue I've run into though and i found setting static ip's up for all the devices removed the problem of not freeing up the ports (it just re-connects the device to them each time you fire up that bit of kit)
There is no issue with Destiny (as I used to play it on my xbox one, UPNP was enabled and NAT type was open)
yeah same as me, but several people on other forums were complaining about it and some code geek setup a Linux box to run as his home router to see what the problem was,
here's a slightly edited quote, you might even understand what the guy is talking about i'm not entirely sure that I do
I managed to fix this. It seems my issue was that the game expects UPnP IDGv2 behavior.
I think if a router does not do this then COD Black Ops III isn't going to get open nat. IGDv2 has been around for a while and earlier this year IGDv1 was officially deprecated - so in future at least certified upnp routers should work.
I guess unless someone knows different that the routers are v1.
The specific feature needed is setting up snat/masq port mapping to match the incoming port opening/mapping.
The reason it works as is (old routers) for the xbox its self is that on boot the xbox will ask for UDP 3074 if it can't have it it will choose some other high port. It then proceeds to use the port it got for outgoing connections so this will work with v1.
BO3 isn't so compatible, it will ask for UDP 3075 and if it can't have it some other port 3xxx but it still wants to and does use 3075 internally, so even though dnat is set up to redirect (new) incoming 3xxx to internal 3075 it doesn't work out as far as the servers are concerned as they expect the IGD to change it for outbound also.
http://upnp.org/specs/gw/...Connection-v2-Service.pdf Section 2.5.16 figure 2.2 (of course looking at figure 2.2 the dnat rule alone could be seen as being enough, but BO3 won't work without explicit snat/masq on outgoing new connections which of course never hit dnat (well not in the world of iptables/netfilter).
I don't use a router, I use Linux on a little DC PC to route/nas/pvr/qos etc. I was using something called igd2-for-linux for my upnp but despite its name it didn't have the feature needed so I had to hack it in.
Is there going to be a fix for this issue of the 8800 not releasing ports? Is it possible to tell us this because if not I'll probably try a different router as it's pretty frustrating.
I've been trying to get around it by using port triggering but it doesn't seem to work, upnp overrides it I think. Disabling upnp permanently isn't an option as i don't want to reconfigure the router for every application and every port I'm using which is ever changing.
MrChips wrote:Is there going to be a fix for this issue of the 8800 not releasing ports? Is it possible to tell us this because if not I'll probably try a different router as it's pretty frustrating.
I've been trying to get around it by using port triggering but it doesn't seem to work, upnp overrides it I think. Disabling upnp permanently isn't an option as i don't want to reconfigure the router for every application and every port I'm using which is ever changing.
Thanks.
Just chased our engineers again, hoping for a some positive feedback soon
I've just read back through the thread and someone suggested fixing the IP address of all devices that don't have their ports released in the virtual server list - I'll try that later as I know of the two devices that conflict on my network (competing for the same ports) one has a fixed IP and the other doesn't.
One other question - does Port Triggering only work when uPnP is turned off? As it seems any application that has a port in the Port Triggering list is still opened by uPnP.
. One thing for sure though is (at least I think it is) that once a device is powered down it should release the previously used open port(s) from the virtual server (upnp) list for use by other devices and the Billion should not hold on to these ports ad infinitum until the router is power cycled. That one should hopefully be fixable 
.