failed to create listening socket for 192.168.1.1: Address already in use
Mar 1 10:52:21 RT-AC86U-9988 custom_config: Appending content of /jffs/configs/dnsmasq.conf.add.
Mar 1 10:52:21 RT-AC86U-9988 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Mar 1 10:52:21 RT-AC86U-9988 rc_service: waitting "restart_dnsmasq" via ...
Mar 1 10:51:28 custom_config: Appending content of /jffs/configs/dnsmasq.conf.add.
Mar 1 10:51:28 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Mar 1 10:51:28 dnsmasq[1160]: started, version 2.90 cachesize 1500
Mar 1 10:51:28 dnsmasq[1160]: asynchronous logging enabled, queue limit is 5 messages
Mar 1 10:51:28 dnsmasq-dhcp[1160]: DHCP, IP range 192.168.102.2 -- 192.168.102.254, lease time 1d
Mar 1 10:51:28 dnsmasq-dhcp[1160]: DHCP, IP range 192.168.101.2 -- 192.168.101.254, lease time 1d
Mar 1 10:51:28 dnsmasq-dhcp[1160]: DHCP, IP range 192.168.1.32 -- 192.168.1.254, lease time 1d
Mar 1 10:51:28 dnsmasq[1160]: using only locally-known addresses for _dns.resolver.arpa
Mar 1 10:51:28 dnsmasq[1160]: using only locally-known addresses for use-application-dns.net
Mar 1 10:51:28 dnsmasq[1160]: read /etc/hosts - 22 names
Mar 1 10:51:28 dnsmasq[1160]: using only locally-known addresses for _dns.resolver.arpa
Mar 1 10:51:28 dnsmasq[1160]: using only locally-known addresses for use-application-dns.net
Mar 1 10:51:28 dnsmasq[1160]: using only locally-known addresses for _dns.resolver.arpa
Mar 1 10:51:28 dnsmasq[1160]: using only locally-known addresses for use-application-dns.net
Mar 1 10:51:32 dnsmasq[1160]: read /etc/hosts - 22 names
Mar 1 10:51:32 dnsmasq[1160]: using only locally-known addresses for _dns.resolver.arpa
Mar 1 10:51:32 dnsmasq[1160]: using only locally-known addresses for use-application-dns.net
Mar 1 10:51:32 dnsmasq[1160]: using only locally-known addresses for _dns.resolver.arpa
Mar 1 10:51:32 dnsmasq[1160]: using only locally-known addresses for use-application-dns.net
Mar 1 10:51:33 dnsmasq[1160]: read /etc/hosts - 22 names
Mar 1 10:51:33 dnsmasq[1160]: using nameserver 172.16.1.254#53
Mar 1 10:51:33 dnsmasq[1160]: using nameserver 172.16.1.254#53 for domain attlocal.net
Mar 1 10:51:33 dnsmasq[1160]: using only locally-known addresses for _dns.resolver.arpa
Mar 1 10:51:33 dnsmasq[1160]: using only locally-known addresses for use-application-dns.net
Mar 1 10:51:33 dnsmasq[1160]: using nameserver 172.16.1.254#53
Mar 1 10:51:33 dnsmasq[1160]: using nameserver 172.16.1.254#53 for domain attlocal.net
Mar 1 10:51:33 dnsmasq[1160]: using only locally-known addresses for _dns.resolver.arpa
Mar 1 10:51:33 dnsmasq[1160]: using only locally-known addresses for use-application-dns.net
Mar 1 10:52:17 dnsmasq[1160]: read /etc/hosts - 22 names
Mar 1 10:52:17 dnsmasq[1160]: using nameserver 172.16.1.254#53
Mar 1 10:52:17 dnsmasq[1160]: using nameserver 172.16.1.254#53 for domain attlocal.net
Mar 1 10:52:17 dnsmasq[1160]: using only locally-known addresses for _dns.resolver.arpa
Mar 1 10:52:17 dnsmasq[1160]: using only locally-known addresses for use-application-dns.net
Mar 1 10:52:17 dnsmasq[1160]: using nameserver 172.16.1.254#53
Mar 1 10:52:17 dnsmasq[1160]: using nameserver 172.16.1.254#53 for domain attlocal.net
Mar 1 10:52:17 dnsmasq[1160]: using only locally-known addresses for _dns.resolver.arpa
Mar 1 10:52:17 dnsmasq[1160]: using only locally-known addresses for use-application-dns.net
Mar 1 10:52:20 uiDivStats: taildns not started: dnsmasq logging is disabled
Mar 1 10:52:20 rc_service: service 2583:notify_rc restart_dnsmasq
Mar 1 10:52:20 custom_script: Running /jffs/scripts/service-event (args: restart dnsmasq)
Mar 1 10:52:22 RT-AC86U-9988 dnsmasq[3850]: started, version 2.90 cachesize 150
Mar 1 10:52:22 RT-AC86U-9988 dnsmasq[3850]: compile time options: IPv6 GNU-getopt no-RTC no-DBus no-UBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset no-nftset no-auth cryptohash DNSSEC no-ID loop-detect no-inotify no-dumpfile
Mar 1 10:52:22 RT-AC86U-9988 dnsmasq[3850]: read /etc/hosts - 22 names
Mar 1 10:52:22 RT-AC86U-9988 dnsmasq[3850]: using nameserver 172.16.1.254#53
Mar 1 10:52:22 RT-AC86U-9988 dnsmasq[3850]: using nameserver 172.16.1.254#53 for domain attlocal.net
Mar 1 10:52:22 RT-AC86U-9988 dnsmasq[3850]: using nameserver 172.16.1.254#53
Mar 1 10:52:22 RT-AC86U-9988 dnsmasq[3850]: using nameserver 172.16.1.254#53 for domain attlocal.net
Mar 1 10:52:22 RT-AC86U-9988 (dnsmasq.postconf): Updating /etc/dnsmasq.conf for unbound.....
Mar 1 10:52:22 RT-AC86U-9988 uiDivStats: dnsmasq has restarted, restarting taildns
Mar 1 10:52:22 RT-AC86U-9988 dnsmasq[3870]: failed to create listening socket for 192.168.1.1: Address already in use
Mar 1 10:52:22 RT-AC86U-9988 dnsmasq[3870]: FAILED to start up
Mar 1 10:52:31 RT-AC86U-9988 dnsmasq[3850]: exiting on receipt of SIGTERM
Mar 1 10:52:31 RT-AC86U-9988 custom_config: Appending content of /jffs/configs/dnsmasq.conf.add.
Mar 1 10:52:31 RT-AC86U-9988 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Mar 1 10:52:31 RT-AC86U-9988 dnsmasq[6856]: started, version 2.90 cachesize 150
Mar 1 10:52:31 RT-AC86U-9988 dnsmasq[6856]: compile time options: IPv6 GNU-getopt no-RTC no-DBus no-UBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset no-nftset no-auth cryptohash DNSSEC no-ID loop-detect no-inotify no-dumpfile
Mar 1 10:52:31 RT-AC86U-9988 dnsmasq[6856]: read /etc/hosts - 22 names
Mar 1 10:52:31 RT-AC86U-9988 dnsmasq[6856]: using nameserver 172.16.1.254#53
Mar 1 10:52:31 RT-AC86U-9988 dnsmasq[6856]: using nameserver 172.16.1.254#53 for domain attlocal.net
Mar 1 10:52:31 RT-AC86U-9988 dnsmasq[6856]: using nameserver 172.16.1.254#53
Mar 1 10:52:31 RT-AC86U-9988 dnsmasq[6856]: using nameserver 172.16.1.254#53 for domain attlocal.net
Mar 1 10:52:31 RT-AC86U-9988 (dnsmasq.postconf): Updating /etc/dnsmasq.conf for unbound.....
Mar 1 10:52:31 RT-AC86U-9988 uiDivStats: dnsmasq has restarted, restarting taildns
Mar 1 10:52:32 RT-AC86U-9988 dnsmasq[6873]: failed to create listening socket for 192.168.1.1: Address already in use
Mar 1 10:52:32 RT-AC86U-9988 dnsmasq[6873]: FAILED to start up
Mar 1 10:52:33 RT-AC86U-9988 rc_service: service 7653:notify_rc restart_dnsmasq
Mar 1 10:52:36 RT-AC86U-9988 custom_script: Running /jffs/scripts/service-event (args: restart dnsmasq)
Mar 1 10:52:36 RT-AC86U-9988 dnsmasq[6856]: exiting on receipt of SIGTERM
Mar 1 10:52:36 RT-AC86U-9988 custom_config: Appending content of /jffs/configs/dnsmasq.conf.add.
Mar 1 10:52:36 RT-AC86U-9988 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Mar 1 10:52:37 RT-AC86U-9988 dnsmasq[8212]: started, version 2.90 cachesize 150
Mar 1 10:52:37 RT-AC86U-9988 dnsmasq[8212]: compile time options: IPv6 GNU-getopt no-RTC no-DBus no-UBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset no-nftset no-auth cryptohash DNSSEC no-ID loop-detect no-inotify no-dumpfile
Mar 1 10:52:37 RT-AC86U-9988 dnsmasq[8212]: read /etc/hosts - 22 names
Mar 1 10:52:37 RT-AC86U-9988 dnsmasq[8212]: using nameserver 172.16.1.254#53
Mar 1 10:52:37 RT-AC86U-9988 dnsmasq[8212]: using nameserver 172.16.1.254#53 for domain attlocal.net
Mar 1 10:52:37 RT-AC86U-9988 dnsmasq[8212]: using nameserver 172.16.1.254#53
Mar 1 10:52:37 RT-AC86U-9988 dnsmasq[8212]: using nameserver 172.16.1.254#53 for domain attlocal.net
Mar 1 10:52:37 RT-AC86U-9988 (dnsmasq.postconf): Updating /etc/dnsmasq.conf for unbound.....
Mar 1 10:52:37 RT-AC86U-9988 uiDivStats: dnsmasq has restarted, restarting taildns
Mar 1 10:52:38 RT-AC86U-9988 dnsmasq[8236]: failed to create listening socket for 192.168.1.1: Address already in use
Mar 1 10:52:38 RT-AC86U-9988 dnsmasq[8236]: FAILED to start up
Perfect? what's that? If it's a stable and reliable network that functions at or beyond expectations (which in my case means transparently), both wired and wirelessly, then yes.You have achieved perfect stability as long as you are following the procedures below? I presume we're talking about Merlin FW exclusively (and full releases as you said, as in not betas), btw?
Does this mean that you are doing a full Factory reset before every incremental update, or just when it's required according to the Changelog?
What version were you upgrading from (and presumably to .12_6?), and have you been able to fix it now by doing a full Factory reset, or did you have to revert to the previous FW version also?
And you say "this time around" - can you remember other things you did not according to usual procedure that caused problems in the past? (I'm trying to map out potential causes of instability that is caused by something else than not following special procedures described in the Changelog when that is required)?
This is a Diversion issue. See the Diversion thread.Tried a couple more dirty upgrades. Same issues, DHCP is not running. Even upgraded Diversion to 5.1 in between, no help. Something about this:
Code:failed to create listening socket for 192.168.1.1: Address already in use
Not really a question that's specific to this release, but yes the ethernet ports on the node will be active.So one question: Are the wired ports active on the Airmesh Node Router? In other words, will both network wifi extension and ethernet slots be active remotely?
Thanks for the quick update, Colin!Not really a question that's specific to this release, but yes the ethernet ports on the node will be active.
I have typically found that AiMesh nodes work with either factory or Merlin. Newer factory firmware tends to have AiMesh improvements.Thanks for the quick update, Colin!
I'd still like to hear the forum wisdom on this part of the questions:
"Oh, one other thing: will the AC-5300 need to be reverted to factory FW to work as the airmesh node? This Merlin update is really running smoothly with the 5300 in the primary router mode..."
Thank you, sir!! That is good news, especially since the 5300 is EOL at ASUS.I have typically found that AiMesh nodes work with either factory or Merlin. Newer factory firmware tends to have AiMesh improvements.
With GT-AX16000 as primary router, personally I'd attach QNAP NAS to that. AC-5300 would most like degrade NAS performance.Thank you, sir!! That is good news, especially since the 5300 is EOL at ASUS.
Not necessarily true. If the NAS has a 1 GB Ethernet port the AC5300 node will just act as a switch. Does a switch slow things down?With GT-AX16000 as primary router, personally I'd attach QNAP NAS to that. AC-5300 would most like degrade NAS performance.
Agreed. I am running with an AX86U router and AC5300 nodes meshed over 5Ghz all running latest Merlin FW. The AC5300s will use 5G radio 2 for the backhaul connection unless you can hard-wire them via Ethernet which is preferable. If you cannot use Ethernet and have to have a wireless connection, you'll have to make sure the AXE-16000 5Ghz channel config is one that the AC-5300 radio 2 can use. My backhaul connection would not come up while I had my AX86U configured on channel 36 (AC5300 uses lower channel range for 5G radio 1), works fine on upper range like channel 149. Hope you can use ethernet; much simpler.I have typically found that AiMesh nodes work with either factory or Merlin. Newer factory firmware tends to have AiMesh improvements.
QNAP NAS supports link aggregation which you won't get on AC5300. I have two QNAP ports aggregated into two AX86U ports for up to 2gbps throughput. Of course if 1 gbps is enough then it doesn't really matter.Not necessarily true. If the NAS has a 1 GB Ethernet port the AC5300 node will just act as a switch. Does a switch slow things down?
And, I have 2.5 Gbps USB NIC that I use on my Synology NAS. There are all sorts of options, but GT-AXE16000 definitely supports more of them...QNAP NAS supports link aggregation which you won't get on AC5300. I have two QNAP ports aggregated into two AX86U ports for up to 2gbps throughput. Of course if 1 gbps is enough then it doesn't really matter.
Tried a couple more dirty upgrades. Same issues
Thank you. If you read back in this thread, this confirms my experiences so far. I say "so far" because I'm not a 100% certain that .10 does the trick yet because .11 seemed stable for about 2 weeks until it crashed (I downgraded to .11 from .12 which gave me more instability in the form of connection drops. And as me/Rmerlin also speculated, the difference between .11 .12.x could be caused more by restarts than actual differences in stability).I have been browsing this forum for the last two years and never bothered to make a account for some reason until now
To respond to your question on the firmware with the AC86 alot of people from what i have seen have issues with DHCP and there Aimesh setups after version .11
From my personal testing i have found .12.4 to be quite stable although with one or two hiccups with Aimesh having DHCP problems As someone with a AC86u , if your looking for firmware thats stable but quite new i suggest you do mutliple hard resets using the wps button and the gui and flash 368.10 I havent found any problems really besides the network map reading the wrong stats and breaking it
I would say more but I don't wanna make this any longer then it needs to be , hope this helps
I'm sorry to single you out buddy, but these sorts of messages are not very helpful, at least past the first day after release.Smooth upgrade to 12_6. Everything running smoothly. Thank you Eric!
Yes.Perfect? what's that? If it's a stable and reliable network that functions at or beyond expectations (which in my case means transparently), both wired and wirelessly, then yes.
CoolNo, I've not installed alphas/betas just for the cool early-adopter, bleeding edge bragging rights, and yes,
You should consider John's LTS fork for potentially better performance.Merlin gets flashed straight away on new asus routers if there is a version available. It was the very first thing I did when I brought this AC86 home after unboxing/connecting in place of the n66 it replaced (and is now acting as a media bridge, albeit back on stock firmware).
"Quite some time". So it is fair to say it's maybe a year or more ago (.9 at least) since you last updated? That's when I last found CVE mentioned in the changelog.I got in the habit of factory resets between point updates: from x.9 to x.10 to x.11 etc, not the _2, _4 etc incremental ones. those are generally just fine if you unmount the entware drive, flash, replug and reboot. In my case, I can't recall which was the last point release I upgraded to and then performed a full reset, so it must've been quite some time, and many such upgrades/updates ago; like I said, I don't keep notes.
So you had .12_4 running perfectly for a while, but failed to unplug the entware drive etc. before upgrading to .12_6 and experienced issues (which, how often - like a crash suddenly, or connection drops?), and a factory reset resolved it. Perhaps it could be because you don't have Aimesh in your setup (my speculation).yes, this factory reset has brought back the stability I had before I failed to follow established upgrade/update procedures...and it was from .12_4 to .12_6 (I prefer to stay on top of anything that's security-related, and this one was specifically for dnsmasq and their addressing of the latest CVE threats).
I'd like an example of that. I generally don't care what experience/status somebody has if they can't or won't bother to make their point clear in writing (sometimes it's a status thing, like it's beneath them or something. I despise that).I've been watching your debates with members of this forum from a distance with half a glance every so often. You've been crossing swords unnecessarily with people who have much more knowledge/familiarity/experience with merlin and networking and hardware and coding in general, I think. Sometimes, gear doesnt work in expected/anticipated ways, and you can spend a lifetime tracking it down, or you can just follow all of the best advice from the chorus who jumps up to support you in internet fora such as this and get on with things and leave the mystery alone.
No, If I go anywhere else with my n66 Media Bridge, it'll be to FreshTomato, which is still under active development. John's Fork is for all intents and purposes abandoned/EoL.Yes.
Cool
You should consider John's LTS fork for potentially better performance.
"Quite some time". So it is fair to say it's maybe a year or more ago (.9 at least) since you last updated? That's when I last found CVE mentioned in the changelog.
So you had .12_4 running perfectly for a while, but failed to unplug the entware drive etc. before upgrading to .12_6 and experienced issues (which, how often - like a crash suddenly, or connection drops?), and a factory reset resolved it. Perhaps it could be because you don't have Aimesh in your setup (my speculation).
I'd like an example of that. I generally don't care what experience/status somebody has if they can't or won't bother to make their point clear in writing (sometimes it's a status thing, like it's beneath them or something. I despise that).
I generally don't care what experience/status somebody has if they can't or won't bother to make their point clear in writing
So, Great comment! I did the power reset on both routers with the latest Merlin FW. Set up airmesh after a manual config of everything on the primary router. It worked like a charm!Agreed. I am running with an AX86U router and AC5300 nodes meshed over 5Ghz all running latest Merlin FW. The AC5300s will use 5G radio 2 for the backhaul connection unless you can hard-wire them via Ethernet which is preferable. If you cannot use Ethernet and have to have a wireless connection, you'll have to make sure the AXE-16000 5Ghz channel config is one that the AC-5300 radio 2 can use. My backhaul connection would not come up while I had my AX86U configured on channel 36 (AC5300 uses lower channel range for 5G radio 1), works fine on upper range like channel 149. Hope you can use ethernet; much simpler.
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!