What's new

Release [Beta] Asuswrt-Merlin 384.19 beta is now available

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Status
Not open for further replies.
Is it just me or is anyone else getting a jffs low space warning after a factory reset even with intialize ticked?
Very interesting... does JFFS show as unmounted? That's what my AC3100 did but still functioned as an AP.
 
Very interesting... does JFFS show as unmounted? That's what my AC3100 did but still functioned as an AP.
Not that I could see it's the second time I've seen it after a reset was having some werid issue where the internet was resetting every 5 minutes as if the dhcp lease was only 5.
 
Is it just me or is anyone else getting a jffs low space warning after a factory reset even with intialize ticked?

What does the Tools -> Sysinfo page shows about JFFS?
 
Interesting. I saw a similar behaviour with my AX88U, but I was running 384.18. In the morning all my IOT devices and 2.4GHz clients were off-line and not able to re-connect. 5GHz was fine. A restart of the AX88U solved it.

An upgrade to 384.19_beta1 saw that problem go away. Beta2 upgrade has been fine as well.
ah, so maybe not related to 384.19?
it's annoying and a bit random. did you get any clue at possible triggers?
thx
 
ah, so maybe not related to 384.19?
it's annoying and a bit random. did you get any clue at possible triggers?
I did not. I went through numerous resets and re-configs trying to clear it up and figure it out. I was just about to roll back to 384.17 when the .19_beta1 came out so I went with that and the issues cleared up. I don't think we can say this is related to a specific build or not, but possible something in the AX88U. Unfortunately, I don't have anything to support that hunch.
 
happened again overnight.
found the router with only 5GHz clients connected and the 2.4GHz clients unable to reconnect.
reboot fixed it.
How's your 2.4GHz, auto or manually selected channel?

couldn't find anything relevant in the logs.
there was this line, but it look innocuous to me:
Aug 13 02:00:01 RT-AX88U-8158 kernel: echo (4142): drop_caches: 3
Diversion creates this log.
 
How's your 2.4GHz, auto or manually selected channel?
manual selected ch 11, 20Mhz
no fancy stuff either, ax, time to wake, agile, beam forming, fairness, etc, are all off.
never happened to me until b2. logs offer no clue :-(
 
manual selected ch 11, 20Mhz
no fancy stuff either, ax, time to wake, agile, beam forming, fairness, etc, are all off.
never happened to me until b2. logs offer no clue :-(
From ax88u firmware .18 to .19a/b was different wireless drivers maybe you need a reset.
 
From ax88u firmware .18 to .19a/b was different wireless drivers maybe you need a reset.
i did a full factory reset, jffs format, usb stick format, all scripts reinstalled fresh when I upgraded from .18 to .19B1.
for B2 i did a dirty upgrade, but i don't think a full reset to go from B1 to B2 would be granted
 
i did a full factory reset, jffs format, usb stick format, all scripts reinstalled fresh when I upgraded from .18 to .19B1.
for B2 i did a dirty upgrade, but i don't think a full reset to go from B1 to B2 would be granted
It's weird indeed and I have not seen this problem myself. Can you try to change the channel and see if it stabilizes?
 
Last edited:
It's weird indeed and I have not seen this problem myself. Can you try to change the channel and see if it stabilizes?
ch 11 is the least crowded around me, but if this continues, i'll try a different one to see if it helps.
 
i did a full factory reset, jffs format, usb stick format, all scripts reinstalled fresh when I upgraded from .18 to .19B1.
for B2 i did a dirty upgrade, but i don't think a full reset to go from B1 to B2 would be granted
Did you try resetting the wifi connection in the IoT devices?
If wifi drivers changed on .19b, connection on clients probably needs/should be reset to the new driver as well.
 
RX-88 - When updating to B1, and also updating to B2 in both cases the wifi radios were turned off. Since I have a mesh (wired backhaul) it took me a while to figure out that there was a problem and what the problem actually was. Need to go to the wireless/professional tab and turn your radios back on. Makes a big difference, lol.
Elmer,

I was also seeing the same no 2.4 devices... I went to wireless/professional tab and turn the 2.4 "off" and then back "on" and the devices starting appearing.

I was having problems with all my 2.4 devices and HomeKit with iOS v13.6.1 and getting "no Response" with the 2.4 devices.

After the turning 2.4 "off" and then back "on" the devices have been working great. Homekit now sees all the 2.4 devices.

Hope this helps...
 
Did you try resetting the wifi connection in the IoT devices?
If wifi drivers changed on .19b, connection on clients probably needs/should be reset to the new driver as well.
it was every single 2.4 client. not just IOT. desktop, laptop, ipad, etc.
monitoring for now. it only happened twice since b2 came out.
will do more tests with the funky state, if it happens again
 
VPN CLIENT ISSUE (After UPGRADE):

@RMerlin

I upgraded to 384.19 Beta 2 and have the following issue with my VPN -> VPN Client Config:

- If I go to Crypto Settings -> Keys and Certificates and go to 'Edit' ...my 'Static Key' and 'Certificate Authority' were both wiped out after the upgrade.
- Trying to add them back, I click 'Save' and 'Apply.' I go back in, and they're wiped out.

- Tried resetting the VPN Client profile to default, and re-added everything. It still will NOT save any of my Keys and Certificates.

This comes from the log now as well:

1597355409947.png


EDIT: Disregard, it looks like my JFFS got screwed up during the upgrade. I reformatted it, and it's now saving.
 
Last edited:
@RMerlin

VPN SERVER ISSUE (After Upgrade):

Separately, as another issue, after upgrading to 384.19 my VPN Server is no longer working. I get this error:

1597355354031.png


EDIT: Disregard, it looks like my JFFS got screwed up during the upgrade. I reformatted it, and it's now saving.
 
Last edited:
it was every single 2.4 client. not just IOT. desktop, laptop, ipad, etc.
monitoring for now. it only happened twice since b2 came out.
will do more tests with the funky state, if it happens again


happened 3rd time with b2.
2.4GHz get disconnected and can't connect back on, until a wireless restart.
the only thing in the logs is this:

Aug 13 22:21:45 RT-AX88U-8158 WLCEVENTD: Deauth_ind 98:xx:xx:xx:xx:xx
Aug 13 22:22:41 RT-AX88U-8158 WLCEVENTD: Deauth_ind 88:xx:xx:xx:xx:xx
Aug 13 22:23:33 RT-AX88U-8158 WLCEVENTD: Deauth_ind B0:xx:xx:xx:xxxx
Aug 13 22:23:36 RT-AX88U-8158 WLCEVENTD: Deauth_ind 44:xx:xx:xx:xx:xx
Aug 13 22:27:21 RT-AX88U-8158 WLCEVENTD: Deauth_ind 7C:xx:xx:xx:xx:xx
Aug 13 22:27:21 RT-AX88U-8158 WLCEVENTD: Deauth_ind D8:42:xx:xx:xx:xx
Aug 13 22:27:21 RT-AX88U-8158 WLCEVENTD: Deauth_ind D8:42:xx:xx:xx:xx
Aug 13 22:32:41 RT-AX88U-8158 WLCEVENTD: Deauth_ind 98:da:xx:xx:xx:xx
Aug 13 22:21:35 RT-AX88U-8158 hostapd: eth6: STA 98:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to local deauth request
Aug 13 22:22:41 RT-AX88U-8158 hostapd: eth6: STA 88:xx:xx:xx:xx:xx IEEE 802.11: disassociated
Aug 13 22:23:33 RT-AX88U-8158 hostapd: eth6: STA b0:xx:xx:xx:xx:xx IEEE 802.11: disassociated
Aug 13 22:23:36 RT-AX88U-8158 hostapd: eth6: STA 44:xx:xx:xx:xx:xx IEEE 802.11: disassociated
Aug 13 22:27:21 RT-AX88U-8158 hostapd: eth6: STA 7c:70:xx:xx:xx:xx IEEE 802.11: disassociated
Aug 13 22:27:21 RT-AX88U-8158 hostapd: eth6: STA d8:42:xx:xx:xx:xx IEEE 802.11: disassociated
Aug 13 22:27:21 RT-AX88U-8158 hostapd: eth6: STA d8:42:xx:xx:xx:xx IEEE 802.11: disassociated
Aug 13 22:32:41 RT-AX88U-8158 hostapd: eth6: STA 98:da:xx:xx:xx:xx IEEE 802.11: disassociated
 
Last edited:
Hi guys anyone know what this is ?????
----

Is someone trying to hack me ?

Aug 14 03:38:41 dnsmasq[415]: Insecure DS reply received for 8ok1o9s8m1va083anpj0tg0fhph76v8h.online, check domain configuration and upstream DNS server DNSSEC support
Aug 14 04:39:29 dnsmasq[415]: possible DNS-rebind attack detected: n3dmfcgy-a41dab50b7e96a73e4426e22c981d685230e1139-mob.d.aa.online-metrix.net
Aug 14 06:22:51 dnsmasq[415]: possible DNS-rebind attack detected: n3dmfcgy-ba82104f9f966a5463a4f070817ab8f992a14ca3-mob.d.aa.online-metrix.net
 
Status
Not open for further replies.

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top