378.55 UPnP Port Forwarding

[MarkyPancake]

I'm not having a lot of luck with the latest Merlin builds and UPnP. My Xbox One keeps getting a Moderate or Strict NAT on build 378.55 and 380.57 and when I check the UPnP port table it's empty. The Xbox One isn't in it and nor are the two PS4s.

I'm not a fan of the DMZ and can't use port forwarding, because of the multiple devices requiring the ports. I haven't experienced this issue on older firmware versions to this extent where I can't get it working. I'm guessing something has changed with the UPnP service in more recent builds.

I like some of the functionality that the new builds bring, but the consoles are used so much that this issue renders this firmware unusable for me, which is a shame.

I shall have to go back to j9527's fork on my AC68U for now, which I also like, as I need UPnP to actually work, unless anybody has any other ideas.

 

[L&LD]

Does hggomes firmware exhibit the same issues?

 

[MarkyPancake]

Does hggomes firmware exhibit the same issues?

I haven't tried that firmware yet.

For now I've used port forwarding on the X1, so I can play with friends for a bit tonight. I'll have another go at it over the weekend when I've got more time.

 

[MarkyPancake]

I've just had a look through the system log and this entry appears at various dates and times:

Jan 21 23:04:00 miniupnpd[2429]: could not open lease file: /var/lib/misc/upnp.leases

Could this have something to do with UPnP not working properly?

Edit: It's not that. Found this reply from Merlin:

You can safely ignore it. miniupnpd tries to load the file if it exists - it won't if there was no previous upnp leases to reload after a service restart.

 

[john9527]

Can you post up your minupnpd config file?

cat /etc/upnp/config

 

[MarkyPancake]

Can you post up your minupnpd config file?

cat /etc/upnp/config

Here you go (I've masked the serial MAC):

ext_ifname=eth0
listening_ip=br0
port=0
enable_upnp=yes
enable_natpmp=yes
secure_mode=yes
upnp_forward_chain=FUPNP
upnp_nat_chain=VUPNP
notify_interval=60
system_uptime=yes
friendly_name=RT-AC68U
model_number=3.0.0.4.378.55
serial=xx:xx:xx:xx:xx:xx

clean_ruleset_interval=600
clean_ruleset_threshold=20
presentation_url=http://192.168.1.1
uuid=3b1812ed-5747-4279-b376-affd350ca50e

allow 1024-65535 192.168.1.1/255.255.255.0 1-65535
min_lifetime=120
max_lifetime=86400

deny 0-65535 0.0.0.0/0 0-65535
lease_file=/var/lib/misc/upnp.leases

 

[MarkyPancake]

For a long time after the Xbox One launched it suffered an issue where it wouldn't trigger any ports when powering up from instant-on mode and works only do this when powering up from a full shutdown.

With the many console updates it has had since launch, I assumed Microsoft has resolved this issue, particularly as I hadn't noticed it with later firmware on my N66U.

I also haven't noticed this issue on the AC68U until trying the more recent Merlin builds, which is why I wonder if something has changed with UPnP in the firmware, especially as the UPnP port table is empty, despite multiple devices relying on it and usually appearing in it, due to how often the Xbox One and PS4s are used.

 

[MarkyPancake]

I've just powered the Xbox One up for the first time today from instant-on and it has triggered a port via UPnP:

UDP | 3074 | 192.168.x.x | 3074 | N/A | Teredo

I've just fired up the PS4, which was fully shutdown last time I used it, and that is also appearing in the UPnP port table:

UDP | 9308 | 192.168.x.x | 9308 | N/A | 192.168.x.x:9308 to 9308 (UDP)

Neither of these devices were appearing in the UPnP port table yesterday and the router hasn't been rebooted during this time either.

Seems like some strange and inconsistent UPnP behaviour.

 

[MarkyPancake]

I've just observed some further unusual behaviour. My PS4 (wired) has a static DHCP address and appeared in the UPnP port table today, but the other PS4 (wireless), which gets its IP address via DHCP and is in use right now, does not appear in the UPnP table. The Xbox One is also wired.

The plot thickens.

 

[MarkyPancake]

I installed Merlin 378.56_2 a few days ago and the router is running great, but the UPnP issue persists.

I've just run cat /etc/upnp/config and this is what I get.

ext_ifname=vlan2
listening_ip=br0
port=0
enable_upnp=yes
enable_natpmp=yes
secure_mode=yes
upnp_forward_chain=FUPNP
upnp_nat_chain=VUPNP
notify_interval=60
system_uptime=yes
friendly_name=RT-AC68U
model_number=3.0.0.4.378.56
serial=xx:xx:xx:xx:xx:xx

clean_ruleset_interval=600
clean_ruleset_threshold=20
presentation_url=http://192.168.1.1
uuid=695aebb3-2eff-4a1b-a0ef-e8b1c170f0a2

allow 1024-65535 192.168.1.1/255.255.255.0 1-65535
min_lifetime=120
max_lifetime=86400

deny 0-65535 0.0.0.0/0 0-65535
lease_file=/var/lib/misc/upnp.leases

Why is the ext_ifname value vlan2 this time, whereas it was eth0 on the other firmware?

 

[john9527]

@MarkyPancake

The major difference between my fork and the later levels is that the later levels incorporated support for IPv6 in miniupnpd. I have a vague memory that when I tried to port it over it caused problems, so I just put it aside. As a test, you might want to try making a jffs/scripts/upnp.postconf file with the following contents. This should get the IPv6 support out of the picture.

#!/bin/sh
CONFIG=$1
source /usr/sbin/helper.sh
 
pc_replace "listening_ip=br0" "listening_ip=192.168.1.0/24" $CONFIG
 
exit

 

[TheReverendSlim]

So was this issue ever resolved? Having similar problems with two Xbox Ones on the same network. I'm using 378.56_2 right now because everything after that makes NAT on the Xbox Ones work inconsistently. Even 378.56_2 isn't perfect, but it's livable. I really wish there was one that worked 100% of the time.