Same issue here with the N66u, i will try to provide more info soon (wasting my life at work right now )Thanks for new release.
I have just tested DFS channels on RT-AC56U and it's not working. (v25e1)
Set DFS checkbox not stick and no extended channels only 36-48.
Maby I doing it wrong way....
nvram get wl_dfs_enable=1
I think I've fixed it:Hi, I have 25J1 on my AC56U. dnsmasq dies unexpectedly. This did not happen in 24J3. I have 6in4 tunneling.
nano /tmp/mnt/Optware/adblocking/scripts/ab_dnsmasq_postconf.sh
and comment out two lines like this:
#pc_append address=/0.0.0.0/0.0.0.0 $CONFIG
#pc_append ptr-record=0.0.0.0.in-addr.arpa,0.0.0.0 $CONFIG
Interesting.....I think I've fixed it:
Code:nano /tmp/mnt/Optware/adblocking/scripts/ab_dnsmasq_postconf.sh and comment out two lines like this: #pc_append address=/0.0.0.0/0.0.0.0 $CONFIG #pc_append ptr-record=0.0.0.0.in-addr.arpa,0.0.0.0 $CONFIG
Dec 31 19:00:12 kernel: ctf: module license 'Proprietary' taints kernel.
Dec 31 19:00:12 kernel: Disabling lock debugging due to kernel taint
Those lines addInteresting.....
There was a dnsmasq update in V25, but I've been running various drops of the new 2.77 for over a month without any problems (and I need the new level to fix a problem I was having on my Linux boxes).
Those lines look like part of ab-solution? I'm not sure what they are trying to accomplish....might be worthwhile to post there as well.
address=/0.0.0.0/0.0.0.0
ptr-record=0.0.0.0.in-addr.arpa,0.0.0.0
I think what John was suggesting, is you following up with @thelonelycoder perhaps to ask him if those lines are coming from AB. Then if so, what AB is accomplishing with it.Those lines add
to /etc/dnsmasq.confCode:address=/0.0.0.0/0.0.0.0 ptr-record=0.0.0.0.in-addr.arpa,0.0.0.0
I've had both those lines in my routers (first an N66U, now an AC68U) for a couple of years and never had a problem with dnsmasq dying.Those lines add
to /etc/dnsmasq.confCode:address=/0.0.0.0/0.0.0.0 ptr-record=0.0.0.0.in-addr.arpa,0.0.0.0
With that, you just kill the core function of AB-Solution.I think I've fixed it:
Code:nano /tmp/mnt/Optware/adblocking/scripts/ab_dnsmasq_postconf.sh and comment out two lines like this: #pc_append address=/0.0.0.0/0.0.0.0 $CONFIG #pc_append ptr-record=0.0.0.0.in-addr.arpa,0.0.0.0 $CONFIG
https://github.com/RMerl/asuswrt-merlin/blob/master/release/src/router/openvpn/Changes.rstJust updated to the latest fork v25E1 on my AC68U and I'm getting a handshake error when connecting from my OpenVPN client version 2.42. It comes up asking for the username and password but then just hangs after the warning below. Not sure what that means or where I should change any settings to allow it to complete the handshake. Thanks.
Wed May 17 14:09:15 2017 WARNING: --ns-cert-type is DEPRECATED. Use --remote-cert-tls instead.
I have nothing in my custom config. Just a generated key from the router and basic username/password authentication. I did notice something at the bottom of the config file the router generated in the last fork that I'm using. See below if that's what's making a difference. Thanks very much.
ns-cert-type server ==>> change to "remote-cert-tls server"
resolv-retry infinite
nobind
And just to add, you appear not to run pixelserv, install it through AB, your out-commented lines will no longer be needed if they indeed are a problem for your dnsmasq.I think I've fixed it:
Code:nano /tmp/mnt/Optware/adblocking/scripts/ab_dnsmasq_postconf.sh and comment out two lines like this: #pc_append address=/0.0.0.0/0.0.0.0 $CONFIG #pc_append ptr-record=0.0.0.0.in-addr.arpa,0.0.0.0 $CONFIG
Why? I have pixelserv running at 192.168.2.3. blocking_file has 192.168.2.3 and :: , no 0.0.0.0.With that, you just kill the core function of AB-Solution.
Can't post it, forum says I'm blocked.Do not change that file, it is dynamically regenerated every time you change something in the AB UI that involves dnsmasq or cron jobs.
I'm 99.99 percent sure that's not your problem. Which AB version are you running?
Post complete dnsmasq.conf file, you can use the show file function in the AB sub menu.
Then you run an old version or have a conflicting manually added command in dnsmasq.conf.addWhy? I have pixelserv running at 192.168.2.3. blocking_file has 192.168.2.3 and :: , no 0.0.0.0.
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!