loveleeyoungae
Regular Contributor
@RMerlin: I think I should say sorry for wasting our time as I hadn't really performed the tests carefully. So yesterday I decided to perform the tests more thoroughly, this time wrote out every step. (The tests made me exhausted which in turn made me realize how much effort and time you put into the firmware, really appreciate that!). I found things that are 100% reproducible, I think they may be useful and worth mentioning, so please bear with me and suggest more troubleshooting steps if possible.Might be a security measure taken by the miniupnpd author to reject UPNP forwards where the WAN side of thing is a LAN IP. I don't know.
I tested using:
- an AC68U
- firmwares: 384.5, 384.6, 384.7
- an IP Camera (limited test as it was being used in the house)
- a laptop running Plex and Emby (installed them for testing, so no configuring or setups, just defaults)
To be clear, these are steps I did to ensure a successful factory-reset (flash) of any firmware:
1. Ssh'ed into the router to erase nvram (and write firmware):
admin@RT-AC68U-11C8:/tmp/home/root# mtd-erase2 nvram
admin@RT-AC68U-11C8:/tmp/home/root# nvram erase
(admin@RT-AC68U-11C8:/tmp/home/root# ls
RT-AC68U_384.5_0.trx
admin@RT-AC68U-11C8:/tmp/home/root# mtd-write2 RT-AC68U_384.5_0.trx linux
linux: CRC OK)
admin@RT-AC68U-11C8:/tmp/home/root# mtd-erase2 nvram
admin@RT-AC68U-11C8:/tmp/home/root# nvram erase
2. Turned off the router at this step for 5 seconds.
3. Hold the WPS button and turned on the router. Released it when the power led started blinking.
4. Waited for the router boot up to access welcome page: set Router mode, automatic IP, change SSIDs names & passwords, changed admin password.
A. When the router was offline (i.e. no cable plugged into WAN port, no WAN IP)
On all tested firmwares:
- Right after setting things on welcome page and logging in the webgui, checked the system log and saw no sign of miniupnpd.
- Changed something on the Administrator - System page (I usually enabled jffs and ssh, but during the tests, I found out changing auto-logout time was enough)
- That was when log for miniupnpd showed up, stating the service started running!
- Connect the laptop to the router, log showed miniupnpd worked properly. (Well, as the router was offline, that might not be considered "worked" - but iptables rules were created, the System Log - Port Forwarding page also listed the uPnP forwards nicely). You can see the screenshot I took on 384.7 below.
B. When the router was online (got WAN IP 192.168.5.237 from ISP modem)
B.1. On all tested firmwares:
- Right after settings things on welcome page, checked the system log and saw log show up for miniupnpd (note: different from offline mode)
B.2. On each firmware:
- 384.5: IPCamera, Plex, Emby always worked
- 384.6: Only IPCamera needed to be restarted before it would work. Everything else was fine. -> that was why I thought the issue started from 384.6 but indeed it was not. Big mistake on me, sorry!
- 384.7: uPnP didn't work. System log didn't show any lines related to the IPCamera & Emby server, only for Plex server was "Failed to add NAT-PMP..."
So, unless 384.7 requires an actual external WAN IP for miniupnpd to work, I wonder if there was still some conflicts here. Hope you can suggest some things else I can try to make it work.
Last edited: