On the GL-MT6000, Full Cone NAT works perfectly after I enable the option in the GUI.
However, after a reboot, it stops working. To make it work again, I have to disable and then re-enable the option.
I'm on the latest stable firmware
Our office does not provide a NAT1/Full Cone network environment, so we can only be simulated by tools, but it has not been reproduced.
Please share the router via the GoodCloud, and see if there are any problems with the configuration.
Or you have check first:
cat /etc/config/fullconenat
After rebooting, check if it is still enable '1'?
If it really reverts (which would be some firmware bug then?) you can use an workaround. Add the following lines to /etc/rc.local at the end but before exit 0
uci set fullconenat.global.enable=1
uci commit fullconenat
If this does not work, you can try
uci set fullconenat.global.enable=0
uci commit fullconenat
uci set fullconenat.global.enable=1
uci commit fullconenat
as well, which should be the same like turning it off and on again.
rc.local runs after every boot.
Yes.
I did a fresh install, problem solved on reboots. The issue only happens after a firmware update then I need to switch on the option again
Did you remember that upgrade firmware from which version to version? and find the fullconenat has issue.
Just tested and this happens after ANY firmware upgrades. I just updated from 4.6.8 to 4.7.0 and full cone nat stopped working. Needed to disable and re-enable again.
Hi,
I have tried to reproduce on my router, MT6000, enabled the Full Cone NAT, upgrade it from v4.6.4 -> 4.6.8 -> 4.7.0, keep settings, the Full Cone NAT is normal when it upgraded.
If you reproduce this issue, please do not disable/re-enable the Full Cone NAT option, and share the router via GoodCloud with us to check it.
Ok, just tested here, and in every upgrade ow downgrade, full cone nat stopped working.
Tested both ways, not working. I don't know way, full cone nat only works again after change the button on GUI (thru webpage or gl inet app).
@bruce I don't know if you are testing it properly, I'm using the nintendo switch to test, and with full cone nat active, the NAT type is "A". Otherwise, is "B".
Also, I just found a app to test full cone nat on android: STUNner. Here's the link:
Note that not all endpoints in this apps are working, but which are working will show the NAT type.
Also, I can simulate the error after an energy outage (just unplug and plug again MT6000 from the power)
uhmm I did not know if my test environment is same as yours, but I try my best to reproduce.
But please try this workaround to see if it works:
vi /etc/rc.local
sleep 150
uci set fullconenat.global.enable=0
uci commit fullconenat
sleep 5
uci set fullconenat.global.enable=1
uci commit fullconenat
Your fix worked. Also, I found a more elegant script:
sleep 60
service fullconenat reload
60 seconds is enough.
I suggest you test simulating an energy outage, since I noted that upgrading firmware sometimes does not trigger the issue. Energy outage always trigger the issue.
1 Like
Is it possible this issue will also appear when the router reboots softly (means reboot on the GL GUI)?
Remember # reload commands on the rc.local.
Hey @bruce merry Christmas. Just tested, the issue does not happen on soft reboot. Only happens on hard reboot (energy outage) and sometimes, firmware upgrade/downgrade
Merry Christmas!
Let me try again and see if we can replicate it.
Thanks.
