Do you see the same awkward firewall files in /tmp with bad WAN interface values?I experienced the same thing on RT-AC88U. Router is able to establish WAN and VPN routes/connections. But clients have no internet. RPDB rules are getting wiped. I see they are getting created in the System Log. Bouncing the VPN Clients restores the RPDB rules. No clues that I can spot in the System Log at the moment. Restoring to 386.1_2 restores internet access for clients and no issues with RPDB rules.
There were few cases already by other users, so this is definitely not an single ocurance. Maybe, it is specific for some permutation of model/settings/something else. Still looks VERY strange, as manual check of code and corresponding nvram values - shows nothing. Looks like it should work fine, but it doesnt. Already checked all sequence starting from identifying _proto and multiwan values and up to _ifname - and didnt find anything suspiciousIf it’s a compile issue, other users with the same router should see the same behavior, and it should be easy to spot.
Tnx, i'll fill my profile. I was always a reader on SnB, this is first time i have to write somethingIn your quest to help others [laudable], I would find it really useful if you included your router model and add-ons in your signature. I had to dig back to your very first post to see that your issues are with the RT-AC3100 [or as it is also known RT-AC88U].
A search of this thread reveals that there are at least 4 other members having similar problems ...
https://www.snbforums.com/search/147549/?q=ac88u&t=post&c[thread]=71038&o=date
Probably find that @dave14305 has nailed it with a compile hiccup relevant to this model only?
http://www.snbforums.com/threads/asuswrt-merlin-386-2-beta-is-now-available.71038/post-672455
If you enable Cake QoS, does the right WAN interface name get written to /etc/cake-qos.conf as variable ULIF?There were few cases already by other users, so this is definitely not an single ocurance. Maybe, it is specific for some permutation of model/settings/something else. Still looks VERY strange, as manual check of code and corresponding nvram values - shows nothing. Looks like it should work fine, but it doesnt. Already checked all sequence starting from identifying _proto and multiwan values and up to _ifname - and didnt find anything suspicious
My fault. Fumblefingered password. Works now.OpenVPN Android client fails authentication to server in AX86U. Using the Arne Schawbe Android client. User authentication set in server. 1024 bit, changed default port.
Unless they also provided the content of their firewall rules, we cannot assume they were experiencing the exact same problem. For instance, I always suspected that Asus' recent DNS routing changes may impact certain configurations.In your quest to help others [laudable], I would find it really useful if you included your router model and add-ons in your signature. I had to dig back to your very first post to see that your issues are with the RT-AC3100 [or as it is also known RT-AC88U].
A search of this thread reveals that there are at least 4 other members having similar problems ...
https://www.snbforums.com/search/147549/?q=ac88u&t=post&c[thread]=71038&o=date
Probably find that @dave14305 has nailed it with a compile hiccup relevant to this model only?
http://www.snbforums.com/threads/asuswrt-merlin-386-2-beta-is-now-available.71038/post-672455
Do you see the same awkward firewall files in /tmp with bad WAN interface values?
-A FORWARD -o eth0 ! -i br0 -j other2wan
-A FORWARD -o ! -i br0 -j other2wan
Mar 13 14:11:48 wanx: Just got eth0
Mar 13 14:11:48 wanx: 1 eth0
Mar 13 14:11:48 wanx: 2 eth0
Mar 13 14:11:48 wanx: 3 eth0
Mar 13 14:11:48 wanx: 3a eth0
Mar 13 14:11:48 wanx: 3aa eth0
Mar 13 14:11:48 wanx: 3ab
Mar 13 14:11:48 wanx: 3b
Mar 13 14:11:48 wanx: 3c
Mar 13 14:11:48 wanx: 4
Mar 13 14:11:48 wanx: 5
Mar 13 14:11:48 wanx: 6
Mar 13 14:11:48 wanx: 7
Mar 13 14:11:48 wanx: 8
Mar 13 14:11:48 wanx: 9
Mar 13 14:11:48 wanx: 10
Mar 13 14:11:48 wanx: 11
Mar 13 14:11:48 wanx: strcmp
What a great news! Waiting for a next betaFirewall rule corruption should be fixed with https://github.com/RMerl/asuswrt-merlin.ng/commit/7577702a816b62ab53a3f052c2f0cc0f6daff288 - at least it was on my own RT-AC88U.
Firewall rule corruption should be fixed with https://github.com/RMerl/asuswrt-merlin.ng/commit/7577702a816b62ab53a3f052c2f0cc0f6daff288 - at least it was on my own RT-AC88U.
So far I could only reproduce it on the RT-AC88U, works fine on AC68 and AX88, so it may be either SDK-specific, or be totally random depending on whether the nvram content is moved around or not during the firewall configuration.Is this for all models or only certain models ?
Any chance to update current builds with this fix for at least AC88 and AC3100?So far I could only reproduce it on the RT-AC88U, works fine on AC68 and AX88, so it may be either SDK-specific, or be totally random depending on whether the nvram content is moved around or not during the firewall configuration.
Probably only with the beta 2 release, unless I actually have time to generate test builds before that.Any chance to update current builds with this fix for at least AC88 and AC3100?
Sure, np. I can live some time without addons that are triggering firewall restart (like skynet), it is easy to pick file from /tmp/err_rules, fix two lines and restore with iptables-restore - that gives stable working router until firewall service will be restarted (without addons - most probably till the router reboot). Anyway - this is Beta, so we know what we are doing thereProbably only with the beta 2 release, unless I actually have time to generate test builds before that.
Unfortunately 384.19 has security issues.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!