No. Different firmware code base.
[Release 384/NG] Asuswrt-Merlin 384.5 is now available
- Thread starter RMerlin
- Start date
No. Different firmware code base.
cmkelley
Very Senior Member
384.5 here on an 86U - I've found if I leave the router page open for a "long" time, it inevitably becomes unresponsive. I figure it's a bug in the httpd version used, I've been thinking about trying the entware lighttpd, but that may be more time than I wish to spend at the moment. If you have ssh set up for your router you don't have to reboot the router, just ssh in and:
Code:
service restart_httpd
skeal
Part of the Furniture
I had this problem once but I disabled letsencrypt and reset to defaults and setup manually. There is something about letsencrypt and https access even if its set to not be accessed from the web.
Nop. After 8+ hours I'm no longer able to connect to 2.4GHz. Back to scratching my head.
madfusker
Regular Contributor
Awesome! Thanks for that tip!
I exchanged for a new router and had almost 24 hours solid before another crash so I am stupified at what it could be. I reset the new router to defaults, flashed merlin, initialized to defaults again, and then setup manually. Not sure what else I can do. Hard to believe I got a second router that is bad as well. I did see in the logs there is a time warp that doesn't look normal and happens at the crash. Take a look... NTP server is set to pool.ntp.org.
Duh Dude
New Around Here
First & foremost I want to thank RMerlin & John9527 for all their personal time & work devoted to development. RMerlin's your custom f/w's are awesome & rock solid; also grateful for the continual f/w updates. John your NVRAM backup script is the best; turns 2-4 hours into 20 minutes, is migratable & turnkey. Additionally, I want to thank the Moderators, Regular Contributors & everyone else for all their contributions.
My AC87R & f/w 380.67 are both dated but rock solid w/ 3 VPN's w/ strict policy based routing, both 2.4Ghz & 5Ghz stable & fast and very few issues if any. A factory update ver 3.0.0.4.382.50010 was released 2018.1.25 w/ quite a few fixed CVE's, a few new features & bug fixes (but w/o any factory driver updates I think) and Merlin's f/w 384.5 is also now available with updated OpenVPN, Openssl, nano, miniupnpd & Dropbear. I know some of the factory fixes apply to my setup, but don;t use AICloud or remote management, however, I get lost in in the heap overflows, bug collisions, session tokens & such. There also always seems to be limitations imposed significant w/factory updates that inherently effect Merlin updated f/w builds. I read SNB's, Merlin's github & a few other sources frequently & am having a hard time deciding weather to update everything or "don't fix it if it ain't broke." I think I have read myself into a black hole with a side of the paradox the more one learns the less one realizes they know. Argh!
1.) NVRAM now have maximum lengths enforced... means some very long lists of settings might no longer be possible on 384.xx. What's "very long?"
2.) Removed Firewall setting... firewall rules now auto created but "postconf" can override. Does that mean the entire GUI Firewall setting & 5 tabs of sub-settings have been removed or...?
3.) Removed option to respond to DNS queries - enabling the option to Push DNS will also handle it? Does that mean enabling Push DNS will respond to DNS?
4.) I use Gibson Research to regularly scan for a few select vulnerabilities as well as nmap & one other i cant remember off the top of my head. Would that identify if the unfixed CVE's & bug fixes had been exploited?
5.) Added support for the RT-AC87U.
Cheers & Thanks
My AC87R & f/w 380.67 are both dated but rock solid w/ 3 VPN's w/ strict policy based routing, both 2.4Ghz & 5Ghz stable & fast and very few issues if any. A factory update ver 3.0.0.4.382.50010 was released 2018.1.25 w/ quite a few fixed CVE's, a few new features & bug fixes (but w/o any factory driver updates I think) and Merlin's f/w 384.5 is also now available with updated OpenVPN, Openssl, nano, miniupnpd & Dropbear. I know some of the factory fixes apply to my setup, but don;t use AICloud or remote management, however, I get lost in in the heap overflows, bug collisions, session tokens & such. There also always seems to be limitations imposed significant w/factory updates that inherently effect Merlin updated f/w builds. I read SNB's, Merlin's github & a few other sources frequently & am having a hard time deciding weather to update everything or "don't fix it if it ain't broke." I think I have read myself into a black hole with a side of the paradox the more one learns the less one realizes they know. Argh!
1.) NVRAM now have maximum lengths enforced... means some very long lists of settings might no longer be possible on 384.xx. What's "very long?"
2.) Removed Firewall setting... firewall rules now auto created but "postconf" can override. Does that mean the entire GUI Firewall setting & 5 tabs of sub-settings have been removed or...?
3.) Removed option to respond to DNS queries - enabling the option to Push DNS will also handle it? Does that mean enabling Push DNS will respond to DNS?
4.) I use Gibson Research to regularly scan for a few select vulnerabilities as well as nmap & one other i cant remember off the top of my head. Would that identify if the unfixed CVE's & bug fixes had been exploited?
5.) Added support for the RT-AC87U.
Cheers & Thanks
cmkelley
Very Senior Member
I don't use letsencrypt, but I do have access type set to "both". Not that I ever use https anyways. Right now I'm trying leaving the page open in Microsoft Edge to see if maybe it's some weird Chrome problem.
In case it helps anyone else. Looks like the dhcp issue i observed is what is causing the degredation of service on the 2.4ghz wireless network. Not sure why i'm only getting it on the ac88u and only on the 2.4ghz band. I pretty much isolated every device where i noticed the dhcprequest and dhcpack over and over and moved them to other ssid's. I updated the drivers in where they were available. In some instances like an older dell xps all in one i replaced the nic card, but the problem still occured. I'm going to see if I can get a network packet capture of the problem. Moving devices to other ssid and then back to the 2.4ghz ssid on the ac88u didn't make a difference either. Most of the devices are older n wifi adapters, but the one in the logs i attached is a newer intel ac adapter.
I was seeing the same thing over and over in my ac3100 and my ac88. Not sure what i did that fixed it. I ended up wiping and re-configuring my devices and repeaters completely from scratch multiple times. I have to ask, did you do a full wipe?
Can you enable debug logging and see what the logs show around when the time starts? I curios to see if you are having the same dhcp issues i was observing.
systemlog - enable debug logging for default message log and log only messages more urgent than click apply
Duh Dude
New Around Here
First & foremost I would make a backups of all settings twice (that's 2 x backups of everything) on different media, regardless, just to be safe.
What happens when you try and connect on router side and device side? Can you turn on debug &/or check what the standard system log?
1.) If so please locate the within the system log the exact time of failure to connect.
2.) Make mental note of that time or export/copy full log to text editor for convenience, so your can markup and keep a record.
3.) Next located 8 hours before failure to connect in syslog which I am assuming is last reboot, as well.
4.) See if you can spot the issue, anything unusual or a pattern in syslog between last reboot and failure to connect.
You could also try:
1.) Disable beam forming (explicit & universal). Disable airtime fairness.
2.) Manually plush DNS, Internet/Browser, etc cache's on your all devices.
3.) Unplug everything everything modem, router, NAS, & computers & turn off all phones/devices that can't be unplugged. Then unplug yourself (that's what i would do lol) grab a cup of coffee or wait a good 10 min. Everything off &/or unplugged.
4.) Boot up modem & wait until completely booted up; then wait another 60 sec.
5.) Boot up router & wait until completely booted up; then wait another 60 sec.
6.) Turn on only one of the device(s) or device that was unable to connect after 8 hours & wait until completely booted up; then wait another 60 sec.
7.) Logon to router check the wan connection, DHCP, syslog make sure everything is normal. Everything should be ok at this point.
8.) Depending on your networks demand and setup, if you can leave just that one device connected for 8+ hours (overnight maybe) come back and see if still connected.
9.) If so try to connect another device & while monitoring syslog. The culprit hopefully would reveal it's self by know.
Basically, anytime one is trouble shooting one must eliminate as many variables a possible; ideally down to 1 variable. Because it becomes exponentially more difficult to diagnose anything with just 2 or more variables.
NUCLEAR APPROACH: Clear NVRAM a few times, Factory reset, manually reconfigure (do not flash a backup unless using Johns NVRAM backup) or defeats the purpose.
Cheers
BuckyBucky
New Around Here
Installed 384.5 a few days ago,
While it works fine, my AC86-U now reboots by itself every day or so for unknown reason. My uptime with the previous firmware was 20 days +.
I have this constant error showing up in my logs.
Any input on how to fix this ?
While it works fine, my AC86-U now reboots by itself every day or so for unknown reason. My uptime with the previous firmware was 20 days +.
I have this constant error showing up in my logs.
Any input on how to fix this ?
Code:
May 21 10:51:39 Mastiff: init
May 21 10:52:16 kernel: pgd = ffffffc011d98000
May 21 10:52:16 kernel: [36223a2e] *pgd=00000000147d3003, *pud=00000000147d3003, *pmd=0000000000000000
May 21 10:52:16 kernel: CPU: 0 PID: 4293 Comm: mastiff Tainted: P O 4.1.27 #2
May 21 10:52:16 kernel: Hardware name: Broadcom-v8A (DT)
May 21 10:52:16 kernel: task: ffffffc0192b00c0 ti: ffffffc011c98000 task.ti: ffffffc011c98000
May 21 10:52:16 kernel: PC is at 0xf6d6b218
May 21 10:52:16 kernel: LR is at 0x0
May 21 10:52:16 kernel: pc : [<00000000f6d6b218>] lr : [<0000000000000000>] pstate: 60010010
May 21 10:52:16 kernel: sp : 00000000ffc574a0
May 21 10:52:16 kernel: x12: 00000000ffc574c4
May 21 10:52:16 kernel: x11: 00000000f6e387a8 x10: 00000000f6e387d8
May 21 10:52:16 kernel: x9 : 0000000036223a22 x8 : 0000000000000018
May 21 10:52:16 kernel: x7 : 0000000000222820 x6 : 0000000000222808
May 21 10:52:16 kernel: x5 : 0000000000000070 x4 : 0000000000222798
May 21 10:52:16 kernel: x3 : 00000000f6007d22 x2 : 0000000000000131
May 21 10:52:16 kernel: x1 : 0000000000000000 x0 : 0000000000000000
May 21 10:52:40 rc_service: watchdog 854:notify_rc stop_aae
May 21 10:52:40 rc_service: watchdog 854:notify_rc start_mastiff
May 21 10:52:40 rc_service: waitting "stop_aae" via watchdog ...
May 21 10:52:40 NAT_Tunnel: AAE Service is stopped
May 21 10:52:40 NAT_Tunnel: AAE Service is stopped
May 21 10:52:40 NAT_Tunnel: AAE Service is stopped
May 21 10:52:40 AAE: AAE Service is started
May 21 10:52:40 Mastiff: init
May 21 10:53:17 kernel: pgd = ffffffc011c0f000
May 21 10:53:17 kernel: [36223a2e] *pgd=000000001444c003, *pud=000000001444c003, *pmd=0000000000000000
May 21 10:53:17 kernel: CPU: 0 PID: 4351 Comm: mastiff Tainted: P O 4.1.27 #2
May 21 10:53:17 kernel: Hardware name: Broadcom-v8A (DT)
May 21 10:53:17 kernel: task: ffffffc0170ba180 ti: ffffffc012f8c000 task.ti: ffffffc012f8c000
May 21 10:53:17 kernel: PC is at 0xf7138218
May 21 10:53:17 kernel: LR is at 0x0
May 21 10:53:17 kernel: pc : [<00000000f7138218>] lr : [<0000000000000000>] pstate: 60010010
May 21 10:53:17 kernel: sp : 00000000ff8dcba0
May 21 10:53:17 kernel: x12: 00000000ff8dcbc4
May 21 10:53:17 kernel: x11: 00000000f72057a8 x10: 00000000f72057d8
May 21 10:53:17 kernel: x9 : 0000000036223a22 x8 : 0000000000000010
May 21 10:53:17 kernel: x7 : 000000000030fa68 x6 : 000000000030fa58
May 21 10:53:17 kernel: x5 : 0000000000000070 x4 : 000000000030f9e8
May 21 10:53:17 kernel: x3 : 00000000f7007d22 x2 : 00000000000000e9
May 21 10:53:17 kernel: x1 : 0000000000000000 x0 : 0000000000000000
May 21 10:53:40 rc_service: watchdog 854:notify_rc stop_aae
May 21 10:53:40 rc_service: watchdog 854:notify_rc start_mastiff
May 21 10:53:40 rc_service: waitting "stop_aae" via watchdog ...
May 21 10:53:40 NAT_Tunnel: AAE Service is stopped
May 21 10:53:40 NAT_Tunnel: AAE Service is stopped
May 21 10:53:41 NAT_Tunnel: AAE Service is stopped
May 21 10:53:41 AAE: AAE Service is started
May 21 10:53:41 Mastiff: init
May 21 10:54:17 kernel: pgd = ffffffc012f2b000
May 21 10:54:17 kernel: [36223a2e] *pgd=0000000011e5a003, *pud=0000000011e5a003, *pmd=0000000000000000
May 21 10:54:17 kernel: CPU: 1 PID: 4401 Comm: mastiff Tainted: P O 4.1.27 #2
May 21 10:54:17 kernel: Hardware name: Broadcom-v8A (DT)
May 21 10:54:17 kernel: task: ffffffc01e022b80 ti: ffffffc011cac000 task.ti: ffffffc011cac000
May 21 10:54:17 kernel: PC is at 0xf6c7e218
May 21 10:54:17 kernel: LR is at 0x0
May 21 10:54:17 kernel: pc : [<00000000f6c7e218>] lr : [<0000000000000000>] pstate: 60010010
May 21 10:54:17 kernel: sp : 00000000ffcd0f10
May 21 10:54:17 kernel: x12: 00000000ffcd0f34
May 21 10:54:17 kernel: x11: 00000000f6d4b7a8 x10: 00000000f6d4b7d8
May 21 10:54:17 kernel: x9 : 0000000036223a22 x8 : 0000000000000018
May 21 10:54:17 kernel: x7 : 000000000017b820 x6 : 000000000017b808
May 21 10:54:17 kernel: x5 : 0000000000000070 x4 : 000000000017b798
May 21 10:54:17 kernel: x3 : 00000000f6007d22 x2 : 0000000000000131
May 21 10:54:17 kernel: x1 : 0000000000000000 x0 : 0000000000000000
May 21 10:54:42 rc_service: watchdog 854:notify_rc stop_aae
May 21 10:54:42 rc_service: watchdog 854:notify_rc start_mastiff
May 21 10:54:42 rc_service: waitting "stop_aae" via watchdog ...
May 21 10:54:42 NAT_Tunnel: AAE Service is stopped
May 21 10:54:42 NAT_Tunnel: AAE Service is stopped
May 21 10:54:43 NAT_Tunnel: AAE Service is stopped
May 21 10:54:43 AAE: AAE Service is started
May 21 10:54:43 Mastiff: init
Makaveli
Very Senior Member
Anyone know what this error is
May 21 14:24:51 odhcp6c[22917]: Failed to send DHCPV6 message to ff02::1:2 (Cannot assign requested address)
Actually nevermind.
When I view the IPv6 log it looks be to down there is no WAN IP address assigned.
Rebooting Cable modem solved this issue.
May 21 14:24:51 odhcp6c[22917]: Failed to send DHCPV6 message to ff02::1:2 (Cannot assign requested address)
Actually nevermind.
When I view the IPv6 log it looks be to down there is no WAN IP address assigned.
Rebooting Cable modem solved this issue.
Last edited:
Asad Ali
Very Senior Member
Note: I don't know if it's a bug or that's how it supposed to look but I think it's a bug.
Hello, I have two routers, one is AC86u ( 384.5_0 ) which is a main router and second is AC68u (384.5_0) which I'm using as Access Point connected to main router via LAN.
The problem is on Access Point router ( AC68u ) the wireless log page under System Log doesn't show proper client's IP addresses and hostnames but only show <unknown> ( Picture below )
The AP router does show proper IP addresses when I check from Network MAP, the <unknown> error only present in Wireless Log page, furthermore if I directly connect the devices to my main router ( AC86u ) the wireless log page on that router shows proper IP addresses and hostnames for the devices so the issue is only on AP router.
I've tried after complete factory reset with Intialize and setting it up from scratch but the issue persists, I've even tried with firmware 384.4_2 and it's behaving same way on that firmware too so it's not 384.5 specific issue.
Any input from someone with a similar setup is highly appreciated.
Hello, I have two routers, one is AC86u ( 384.5_0 ) which is a main router and second is AC68u (384.5_0) which I'm using as Access Point connected to main router via LAN.
The problem is on Access Point router ( AC68u ) the wireless log page under System Log doesn't show proper client's IP addresses and hostnames but only show <unknown> ( Picture below )
The AP router does show proper IP addresses when I check from Network MAP, the <unknown> error only present in Wireless Log page, furthermore if I directly connect the devices to my main router ( AC86u ) the wireless log page on that router shows proper IP addresses and hostnames for the devices so the issue is only on AP router.
I've tried after complete factory reset with Intialize and setting it up from scratch but the issue persists, I've even tried with firmware 384.4_2 and it's behaving same way on that firmware too so it's not 384.5 specific issue.
Any input from someone with a similar setup is highly appreciated.
Note: I don't know if it's a bug or that's how it supposed to look but I think it's a bug.
Hello, I have two routers, one is AC86u ( 384.5_0 ) which is a main router and second is AC68u (384.5_0) which I'm using as Access Point connected to main router via LAN.
The problem is on Access Point router ( AC68u ) the wireless log page under System Log doesn't show proper client's IP addresses and hostnames but only show <unknown> ( Picture below )
The AP router does show proper IP addresses when I check from Network MAP, the <unknown> error only present in Wireless Log page, furthermore if I directly connect the devices to my main router ( AC86u ) the wireless log page on that router shows proper IP addresses and hostnames for the devices so the issue is only on AP router.
I've tried after complete factory reset with Intialize and setting it up from scratch but the issue persists, I've even tried with firmware 384.4_2 and it's behaving same way on that firmware too so it's not 384.5 specific issue.
Any input from someone with a similar setup is highly appreciated.
I can confirm similar behavior of the Wireless Log on a AC66U setup as AP running 380.70 fw.
If it's supposed to be like that or not, I can't say. But I think it's been like that for quite a while in AP mode.
Last edited:
Sanna1967
Senior Member
Not a bug, many times discussed ..
Did you try to reconnect the clients?
Asad Ali
Very Senior Member
Done that too many times, and I know about the Network MAP issue and the discussions about it but I'm not talking about that, its for Wireless LOG page.
If you can point me to some discussions regarding Wireless Log page too I'll be grateful.
Similar threads
Similar threads
Similar threads
-
-
-
-
Tera Term can't SSH connect to router running Merlin 384, but works when flash back to ASUS stock FW
- Started by WishForTheStars
- Replies: 6
-
-
RT-AC3200 Merlin 384.13.10 - e2fsck abort with 'Memory Allocation failed' (10 GB swapfile!)
- Started by itibi
- Replies: 14
-
Unable to establish VPN connection to my PiVPN (ovpn) from my Asus RT-AC86U running Asuswrt-Merlin 386.14
- Started by B0GDAN
- Replies: 1
-
Several Questions Re:Asuswrt-Merlin Feature Implementation
- Started by fenixreign
- Replies: 2
-
-
Beta Asuswrt-Merlin 3006.102.2 Beta is now available for Wifi 7 devices
- Started by RMerlin
- Replies: 69