What's new

Release Asuswrt-Merlin 386.1 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.
Shocking, I am getting GERMANY on both of my routers. Wonder if this is Brexit compliant and should I send them back?...
Send them to Boris to get them and the Brexit fixed... :cool:
 
Shocking, I am getting GERMANY on both of my routers. Wonder if this is Brexit compliant and should I send them back?...
I live in Bulgaria and my RT-AC66U B1 also shows Germany
 
Send them to Boris to get them and the Brexit fixed... :cool:
Ha ha, I wish. With equal effects one can try to glue shattered glass. But let's not divert from the thread topic :) Apologies for off-topic
 
I missed the webgui slow response and database maintenance part. I did use manual switch button to turn on/off AC3100 a two times (maybe three)
I also powered off one AiMesh node.
I wonder if the maintenance will still finish...


Does anyone know?
I can confirm even if you restarted it a few times. Wait patiently it will work. I can access webui now.
 
Hi Guys,

Found a possible bug in AiMesh on 386.1_2.

I have 2 hardwired Synology NAS's, both set using jumbo frames (MTU=9000) in conjunction with a W10 PC. When i connect them to my main AC2900 router, i'm able to open DSM (Syno Management) and use jumbo frames and shares from one to another. Things work fine.

Now when i move one of these NAS's to my AC68U AiMesh node, i can't open DSM on the remote (node) NAS or connect it to the NFS share of its brother on the main node anymore, except when i set the remote NAS to a standard MTU of 1500.
It seems as though Jumbo frames do not propagate to and from the node.

For now i'm using the standard MTU size of 1500 on the remote NAS, but i'd like to use jumbo frames because of faster throughput.

(Besides that: Adding the AiMesh node added another 3 degr. C to CPU temp on my main router)

EDIT: jumbo_frame_enable was set to 0 on node, setting it to 1 did not help
 
Last edited:
Help? re 86U
I did upgrade from 386.1 to 386.1_2 feb 14th, today router lost internet connectivity, rebooted again by power cycling , saw this in syslog Can any one tell me what is it? Thx


Feb 16 21:49:02 kernel: SHN Release Version: 2.0.1 851496c
Feb 16 21:49:02 kernel: UDB Core Version: 0.2.18
Feb 16 21:49:02 kernel: sizeof forward pkt param = 280
Trend Micro engine loading, has always been there.
 
Hi thank you for your replay but when setting AP isolation on 2.4Ghz or on 5Ghz you should access the main wired LAN from either 2.4Ghz and from 5Ghz. AP isolation should only limit access wireless clients from communicate between one to another not to the main wired LAN?

When i set AP isolation on 5Ghz and 2.4Ghz wireless clients can not communicate to my main wired LAN.

When I tested AP isolation, I was connecting from a wifi-based computer to two different wired computers. My impression was that you were saying that devices on the non-AP isolated wifi band were unable to see the network at all, but apparently you are saying that they couldn't see other devices on the non-AP isolated wifi band when both devices are on the non-AP isolated band.

I just now confirmed that two devices on the 5 GHz band can talk to each other (I used SMB file sharing between the devices) while AP Isolation is enabled on the 2.4 GHz band.
 
When I tested AP isolation, I was connecting from a wifi-based computer to two different wired computers. My impression was that you were saying that devices on the non-AP isolated wifi band were unable to see the network at all, but apparently you are saying that they couldn't see other devices on the non-AP isolated wifi band when both devices are on the non-AP isolated band.

I just now confirmed that two devices on the 5 GHz band can talk to each other (I used SMB file sharing between the devices) while AP Isolation is enabled on the 2.4 GHz band.
Hi,

Thanks again but you still did not completely understand my issue. I will just give you an example let say i set 5Ghz wifi to "AP isolation".
Now i have one client connected to 5Ghz wifi and another client connect to wired LAN on the router so they can't talk to each other and this is the problem.

"AP Isolation" means that if both clients exist on the same 5Ghz wifi they can not talk to each other but both should be able to talk to all other devices/clients that connected to wired LAN.
 
I did a clean install before upgrading to 386.1_2 and I also replaced my USB with a new one - just in case . Temperature still high.
I'll give it another try over the weekend with a nuclear resert and I'll post the outcome.
Cheers.
Nuclear reset is not needed and for the most part, a waste of time. Hard Factory Reset ( https://www.asus.com/support/FAQ/1039074/ ) on the other hand followed by manual configuration is the way to go.
Please do not use old saved configurations unless you plan to go back to a prior firmware version.
 
Anybody else noticed after upgrading AC68U to 386.1_2, user Auto Logout not working?

I changed it from default 10 to 11 minutes and went back to 10 and in any case, I could log straight into the web panel after couple of days without entering user credentials.
Before the feature was working fine.
 
Hi,

Thanks again but you still did not completely understand my issue. I will just give you an example let say i set 5Ghz wifi to "AP isolation".
Now i have one client connected to 5Ghz wifi and another client connect to wired LAN on the router so they can't talk to each other and this is the problem.

"AP Isolation" means that if both clients exist on the same 5Ghz wifi they can not talk to each other but both should be able to talk to all other devices/clients that connected to wired LAN.

ok. I'll test that later today. However, as you suggest, "Set AP Isolated" may or may not be different than "Access Intranet". I don't know the answer to that.
 
Anybody else noticed after upgrading AC68U to 386.1_2, user Auto Logout not working?

I changed it from default 10 to 11 minutes and went back to 10 and in any case, I could log straight into the web panel after couple of days without entering user credentials.
Before the feature was working fine.
I can confirm that.

If you don't manually log out from Merlin GUI and just close your browser and open the brower next day you are immediately in. No need to login again.
 
Yes but in that case, the intenet traffic on the network map page is corrupt.
 
RT-AC86U running 386.1_2.

Had a power cut so everything rebooted. Router comes up, then crashes and reboots. From the LAN I managed to disable 2.4Ghz wifi, and this stopped it crashing. As soon as I enable it, it crashes. Enabled it with a new SSID and everything was ok.

Scanned network and saw an Amazon Fire Stick (disconnected) had its own WiFi (to enable setup) on the same wireless channel (11). Unplugged this, and this stopped the crashes and everything else reconnected.

Any idea why this was causing the router to crash constantly? I can see a crash log dump in the logs. Here is the last bit of it...

Code:
May  5 06:05:08 crashlog: <6>IDPfw: IDPfw is ready
May  5 06:05:08 crashlog: <4>sizeof forward pkt param = 280
May  5 06:05:08 crashlog: <6>protocol 0800 is buggy, dev eth5
May  5 06:05:08 crashlog: <6>protocol 0800 is buggy, dev eth5
May  5 06:05:08 crashlog: <6>protocol 0800 is buggy, dev eth5
May  5 06:05:08 crashlog: <6>protocol 0800 is buggy, dev eth5
May  5 06:05:08 crashlog: <6>protocol 0800 is buggy, dev eth5
May  5 06:05:08 crashlog: <6>protocol 0800 is buggy, dev eth5
May  5 06:05:08 crashlog: <6>protocol 0800 is buggy, dev eth5
May  5 06:05:08 crashlog: <6>protocol 0800 is buggy, dev eth5
May  5 06:05:08 crashlog: <4>DROP IN=ppp0 OUT= MAC= SRC=54.194.205.210 DST=31.51.134.197 LEN=83 TOS=0x00 PREC=0x00 TTL=220 ID=60599 DF PROTO=TCP SPT=443 DPT=35946 SEQ=1927592794 ACK=2389956866 WINDOW=118 RES=0x00 ACK PSH URGP=0 OPT (0101080AA5ECF6DB000A5530) MARK=0x8000000
May  5 06:05:08 crashlog: <4>DROP IN=ppp0 OUT= MAC= SRC=185.137.234.205 DST=31.51.134.197 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=12489 PROTO=TCP SPT=40546 DPT=3394 SEQ=2945891150 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0x8000000
May  5 06:05:08 crashlog: <6>protocol 0800 is buggy, dev eth5
May  5 06:05:08 crashlog: <6>protocol 0800 is buggy, dev eth5
May  5 06:05:08 crashlog: <4>BUG: failure at mm/slab.c:2744/cache_free_debugcheck()!
May  5 06:05:08 crashlog: <0>Kernel panic - not syncing: BUG!
May  5 06:05:08 crashlog: <4>CPU: 0 PID: 1819 Comm: httpd Tainted: P           O    4.1.27 #2
May  5 06:05:08 crashlog: <4>Hardware name: Broadcom-v8A (DT)
May  5 06:05:08 crashlog: <0>Call trace:
May  5 06:05:08 crashlog: <4>[<ffffffc0000876d8>] dump_backtrace+0x0/0x150
May  5 06:05:08 crashlog: <4>[<ffffffc00008783c>] show_stack+0x14/0x20
May  5 06:05:08 crashlog: <4>[<ffffffc00050a704>] dump_stack+0x90/0xb0
May  5 06:05:08 crashlog: <4>[<ffffffc000508594>] panic+0xd8/0x220
May  5 06:05:08 crashlog: <4>[<ffffffc000138f30>] cache_free_debugcheck+0x268/0x348
May  5 06:05:08 crashlog: <4>[<ffffffc000139880>] kfree+0xa0/0x158
May  5 06:05:08 crashlog: <4>[<ffffffc0003af8f0>] skb_free_head+0x88/0xc8
May  5 06:05:08 crashlog: <4>[<ffffffc0003afa14>] skb_release_data+0xe4/0x1b8
May  5 06:05:08 crashlog: <4>[<ffffffc0003afb20>] __kfree_skb+0x38/0x108
May  5 06:05:08 crashlog: <4>[<ffffffc0003afc10>] kfree_skb+0x20/0x48
May  5 06:05:08 crashlog: <4>[<ffffffc00047872c>] ipmr_destroy_unres+0xec/0xf0
May  5 06:05:08 crashlog: <4>[<ffffffc0004799c4>] ipmr_expire_process+0x94/0x150
May  5 06:05:08 crashlog: <4>[<ffffffc0000dbe20>] call_timer_fn.isra.7+0x28/0x98
May  5 06:05:08 crashlog: <4>[<ffffffc0000dc054>] run_timer_softirq+0x1c4/0x230
May  5 06:05:08 crashlog: <4>[<ffffffc0000973f0>] __do_softirq+0x100/0x238
May  5 06:05:08 crashlog: <4>[<ffffffc0000977ec>] irq_exit+0x9c/0xe0
May  5 06:05:08 crashlog: <4>[<ffffffc0000cdc60>] __handle_domain_irq+0x60/0xb8
May  5 06:05:08 crashlog: <4>[<ffffffc000080c20>] gic_handle_irq+0x38/0x90
May  5 06:05:08 crashlog: <4>Exception stack(0xffffffc0155afeb0 to 0xffffffc0155affd0)
May  5 06:05:08 crashlog: <4>fea0:                                     00400000 00000000 00000000 00000000
May  5 06:05:08 crashlog: <4>fec0: ffffffff ffffffff f6c0fdf8 00000000 ff8bf1b8 00000000 f72e14c4 00000000
May  5 06:05:08 crashlog: <4>fee0: 000004ff 00000000 f72e14c4 00000000 00000000 00000000 f72e14c4 00000000
May  5 06:05:08 crashlog: <4>ff00: 000004ff 00000000 f72cfd85 00000000 ff8bf2d4 00000000 ff8bf260 00000000
May  5 06:05:08 crashlog: <4>ff20: f72cfd7f 00000000 f72cfd85 00000000 f6cddbc0 00000000 ff8bf190 00000000
May  5 06:05:08 crashlog: <4>ff40: f6c09a20 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May  5 06:05:08 crashlog: <4>ff60: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May  5 06:05:08 crashlog: <4>ff80: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May  5 06:05:08 crashlog: <4>ffa0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May  5 06:05:08 crashlog: <4>ffc0: 00000000 00000000 00000000 00000000
May  5 06:05:08 crashlog: <2>CPU1: stopping
May  5 06:05:08 crashlog: <4>CPU: 1 PID: 2823 Comm: sh Tainted: P           O    4.1.27 #2
May  5 06:05:08 crashlog: <4>Hardware name: Broadcom-v8A (DT)
May  5 06:05:08 crashlog: <0>Call trace:
May  5 06:05:08 crashlog: <4>[<ffffffc0000876d8>] dump_backtrace+0x0/0x150
May  5 06:05:08 crashlog: <4>[<ffffffc00008783c>] show_stack+0x14/0x20
May  5 06:05:08 crashlog: <4>[<ffffffc00050a704>] dump_stack+0x90/0xb0
May  5 06:05:08 crashlog: <4>[<ffffffc00008e730>] handle_IPI+0x190/0x1a0
May  5 06:05:08 crashlog: <4>[<ffffffc000080c70>] gic_handle_irq+0x88/0x90
May  5 06:05:08 crashlog: <4>Exception stack(0xffffffc01558fac0 to 0xffffffc01558fbe0)
May  5 06:05:08 crashlog: <4>fac0: 00000721 00000000 00000000 00000000 1558fc00 ffffffc0 00138aec ffffffc0
May  5 06:05:08 crashlog: <4>fae0: 0000006b 00000000 00000720 00000000 00000010 00000000 80042800 00000000
May  5 06:05:08 crashlog: <4>fb00: 00000000 00000000 00000001 00000000 0085e1fc 00000000 000000c3 00000000
May  5 06:05:08 crashlog: <4>fb20: 00000000 00000000 000a0a90 00000000 00000001 00000000 00000000 00000000
May  5 06:05:08 crashlog: <4>fb40: 000a0f70 00000000 ffa403fc 00000000 0004159c 00000000 00000000 00000000
May  5 06:05:08 crashlog: <4>fb60: 00145020 ffffffc0 00000000 00000000 00000000 00000000 00000721 00000000
May  5 06:05:08 crashlog: <4>fb80: 00000000 00000000 00001000 00000000 0000006b 00000000 000000a5 00000000
May  5 06:05:08 crashlog: <4>fba0: 00000fff 00000000 19174000 ffffffc0 1e81c740 ffffffc0 006245d8 ffffffc0
May  5 06:05:08 crashlog: <4>fbc0: 19174000 ffffffc0 1558fc00 ffffffc0 0013a03c ffffffc0 1558fc00 ffffffc0
May  5 06:05:08 crashlog: <4>[<ffffffc000083da8>] el1_irq+0x68/0xd8
May  5 06:05:08 crashlog: <4>[<ffffffc00013a03c>] cache_alloc_debugcheck_after.isra.27+0x21c/0x2f0
May  5 06:05:08 crashlog: <4>[<ffffffc00013ac5c>] kmem_cache_alloc+0xa4/0x130
May  5 06:05:08 crashlog: <4>[<ffffffc00014ee7c>] getname_flags+0x34/0x178
May  5 06:05:08 crashlog: <4>[<ffffffc00014f8b8>] user_path_at_empty+0x30/0xa0
May  5 06:05:08 crashlog: <4>[<ffffffc00014f938>] user_path_at+0x10/0x18
May  5 06:05:08 crashlog: <4>[<ffffffc000144ad4>] vfs_fstatat+0x5c/0xb8
May  5 06:05:08 crashlog: <4>[<ffffffc000145044>] SyS_stat64+0x24/0x48
May  5 06:05:08 crashlog:
May  5 06:05:08 crashlog:
May  5 06:05:08 crashlog:
May  5 06:05:08 crashlog:
May  5 06:05:08 crashlog:
May  5 06:05:08 kernel: ^[[0;33;41m[ERROR pktrunner] runnerUcast_inet6addr_event,202: Could not rdpa_ucast_ipv6_host_address_table_find^[[0m
 
RT-AC86U running 386.1_2.

Had a power cut so everything rebooted. Router comes up, then crashes and reboots. From the LAN I managed to disable 2.4Ghz wifi, and this stopped it crashing. As soon as I enable it, it crashes. Enabled it with a new SSID and everything was ok.

Scanned network and saw an Amazon Fire Stick (disconnected) had its own WiFi (to enable setup) on the same wireless channel (11). Unplugged this, and this stopped the crashes and everything else reconnected.

Any idea why this was causing the router to crash constantly? I can see a crash log dump in the logs. Here is the last bit of it...

Code:
May  5 06:05:08 crashlog: <6>IDPfw: IDPfw is ready
May  5 06:05:08 crashlog: <4>sizeof forward pkt param = 280
May  5 06:05:08 crashlog: <6>protocol 0800 is buggy, dev eth5
May  5 06:05:08 crashlog: <6>protocol 0800 is buggy, dev eth5
May  5 06:05:08 crashlog: <6>protocol 0800 is buggy, dev eth5
May  5 06:05:08 crashlog: <6>protocol 0800 is buggy, dev eth5
May  5 06:05:08 crashlog: <6>protocol 0800 is buggy, dev eth5
May  5 06:05:08 crashlog: <6>protocol 0800 is buggy, dev eth5
May  5 06:05:08 crashlog: <6>protocol 0800 is buggy, dev eth5
May  5 06:05:08 crashlog: <6>protocol 0800 is buggy, dev eth5
May  5 06:05:08 crashlog: <4>DROP IN=ppp0 OUT= MAC= SRC=54.194.205.210 DST=31.51.134.197 LEN=83 TOS=0x00 PREC=0x00 TTL=220 ID=60599 DF PROTO=TCP SPT=443 DPT=35946 SEQ=1927592794 ACK=2389956866 WINDOW=118 RES=0x00 ACK PSH URGP=0 OPT (0101080AA5ECF6DB000A5530) MARK=0x8000000
May  5 06:05:08 crashlog: <4>DROP IN=ppp0 OUT= MAC= SRC=185.137.234.205 DST=31.51.134.197 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=12489 PROTO=TCP SPT=40546 DPT=3394 SEQ=2945891150 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0x8000000
May  5 06:05:08 crashlog: <6>protocol 0800 is buggy, dev eth5
May  5 06:05:08 crashlog: <6>protocol 0800 is buggy, dev eth5
May  5 06:05:08 crashlog: <4>BUG: failure at mm/slab.c:2744/cache_free_debugcheck()!
May  5 06:05:08 crashlog: <0>Kernel panic - not syncing: BUG!
May  5 06:05:08 crashlog: <4>CPU: 0 PID: 1819 Comm: httpd Tainted: P           O    4.1.27 #2
May  5 06:05:08 crashlog: <4>Hardware name: Broadcom-v8A (DT)
May  5 06:05:08 crashlog: <0>Call trace:
May  5 06:05:08 crashlog: <4>[<ffffffc0000876d8>] dump_backtrace+0x0/0x150
May  5 06:05:08 crashlog: <4>[<ffffffc00008783c>] show_stack+0x14/0x20
May  5 06:05:08 crashlog: <4>[<ffffffc00050a704>] dump_stack+0x90/0xb0
May  5 06:05:08 crashlog: <4>[<ffffffc000508594>] panic+0xd8/0x220
May  5 06:05:08 crashlog: <4>[<ffffffc000138f30>] cache_free_debugcheck+0x268/0x348
May  5 06:05:08 crashlog: <4>[<ffffffc000139880>] kfree+0xa0/0x158
May  5 06:05:08 crashlog: <4>[<ffffffc0003af8f0>] skb_free_head+0x88/0xc8
May  5 06:05:08 crashlog: <4>[<ffffffc0003afa14>] skb_release_data+0xe4/0x1b8
May  5 06:05:08 crashlog: <4>[<ffffffc0003afb20>] __kfree_skb+0x38/0x108
May  5 06:05:08 crashlog: <4>[<ffffffc0003afc10>] kfree_skb+0x20/0x48
May  5 06:05:08 crashlog: <4>[<ffffffc00047872c>] ipmr_destroy_unres+0xec/0xf0
May  5 06:05:08 crashlog: <4>[<ffffffc0004799c4>] ipmr_expire_process+0x94/0x150
May  5 06:05:08 crashlog: <4>[<ffffffc0000dbe20>] call_timer_fn.isra.7+0x28/0x98
May  5 06:05:08 crashlog: <4>[<ffffffc0000dc054>] run_timer_softirq+0x1c4/0x230
May  5 06:05:08 crashlog: <4>[<ffffffc0000973f0>] __do_softirq+0x100/0x238
May  5 06:05:08 crashlog: <4>[<ffffffc0000977ec>] irq_exit+0x9c/0xe0
May  5 06:05:08 crashlog: <4>[<ffffffc0000cdc60>] __handle_domain_irq+0x60/0xb8
May  5 06:05:08 crashlog: <4>[<ffffffc000080c20>] gic_handle_irq+0x38/0x90
May  5 06:05:08 crashlog: <4>Exception stack(0xffffffc0155afeb0 to 0xffffffc0155affd0)
May  5 06:05:08 crashlog: <4>fea0:                                     00400000 00000000 00000000 00000000
May  5 06:05:08 crashlog: <4>fec0: ffffffff ffffffff f6c0fdf8 00000000 ff8bf1b8 00000000 f72e14c4 00000000
May  5 06:05:08 crashlog: <4>fee0: 000004ff 00000000 f72e14c4 00000000 00000000 00000000 f72e14c4 00000000
May  5 06:05:08 crashlog: <4>ff00: 000004ff 00000000 f72cfd85 00000000 ff8bf2d4 00000000 ff8bf260 00000000
May  5 06:05:08 crashlog: <4>ff20: f72cfd7f 00000000 f72cfd85 00000000 f6cddbc0 00000000 ff8bf190 00000000
May  5 06:05:08 crashlog: <4>ff40: f6c09a20 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May  5 06:05:08 crashlog: <4>ff60: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May  5 06:05:08 crashlog: <4>ff80: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May  5 06:05:08 crashlog: <4>ffa0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May  5 06:05:08 crashlog: <4>ffc0: 00000000 00000000 00000000 00000000
May  5 06:05:08 crashlog: <2>CPU1: stopping
May  5 06:05:08 crashlog: <4>CPU: 1 PID: 2823 Comm: sh Tainted: P           O    4.1.27 #2
May  5 06:05:08 crashlog: <4>Hardware name: Broadcom-v8A (DT)
May  5 06:05:08 crashlog: <0>Call trace:
May  5 06:05:08 crashlog: <4>[<ffffffc0000876d8>] dump_backtrace+0x0/0x150
May  5 06:05:08 crashlog: <4>[<ffffffc00008783c>] show_stack+0x14/0x20
May  5 06:05:08 crashlog: <4>[<ffffffc00050a704>] dump_stack+0x90/0xb0
May  5 06:05:08 crashlog: <4>[<ffffffc00008e730>] handle_IPI+0x190/0x1a0
May  5 06:05:08 crashlog: <4>[<ffffffc000080c70>] gic_handle_irq+0x88/0x90
May  5 06:05:08 crashlog: <4>Exception stack(0xffffffc01558fac0 to 0xffffffc01558fbe0)
May  5 06:05:08 crashlog: <4>fac0: 00000721 00000000 00000000 00000000 1558fc00 ffffffc0 00138aec ffffffc0
May  5 06:05:08 crashlog: <4>fae0: 0000006b 00000000 00000720 00000000 00000010 00000000 80042800 00000000
May  5 06:05:08 crashlog: <4>fb00: 00000000 00000000 00000001 00000000 0085e1fc 00000000 000000c3 00000000
May  5 06:05:08 crashlog: <4>fb20: 00000000 00000000 000a0a90 00000000 00000001 00000000 00000000 00000000
May  5 06:05:08 crashlog: <4>fb40: 000a0f70 00000000 ffa403fc 00000000 0004159c 00000000 00000000 00000000
May  5 06:05:08 crashlog: <4>fb60: 00145020 ffffffc0 00000000 00000000 00000000 00000000 00000721 00000000
May  5 06:05:08 crashlog: <4>fb80: 00000000 00000000 00001000 00000000 0000006b 00000000 000000a5 00000000
May  5 06:05:08 crashlog: <4>fba0: 00000fff 00000000 19174000 ffffffc0 1e81c740 ffffffc0 006245d8 ffffffc0
May  5 06:05:08 crashlog: <4>fbc0: 19174000 ffffffc0 1558fc00 ffffffc0 0013a03c ffffffc0 1558fc00 ffffffc0
May  5 06:05:08 crashlog: <4>[<ffffffc000083da8>] el1_irq+0x68/0xd8
May  5 06:05:08 crashlog: <4>[<ffffffc00013a03c>] cache_alloc_debugcheck_after.isra.27+0x21c/0x2f0
May  5 06:05:08 crashlog: <4>[<ffffffc00013ac5c>] kmem_cache_alloc+0xa4/0x130
May  5 06:05:08 crashlog: <4>[<ffffffc00014ee7c>] getname_flags+0x34/0x178
May  5 06:05:08 crashlog: <4>[<ffffffc00014f8b8>] user_path_at_empty+0x30/0xa0
May  5 06:05:08 crashlog: <4>[<ffffffc00014f938>] user_path_at+0x10/0x18
May  5 06:05:08 crashlog: <4>[<ffffffc000144ad4>] vfs_fstatat+0x5c/0xb8
May  5 06:05:08 crashlog: <4>[<ffffffc000145044>] SyS_stat64+0x24/0x48
May  5 06:05:08 crashlog:
May  5 06:05:08 crashlog:
May  5 06:05:08 crashlog:
May  5 06:05:08 crashlog:
May  5 06:05:08 crashlog:
May  5 06:05:08 kernel: ^[[0;33;41m[ERROR pktrunner] runnerUcast_inet6addr_event,202: Could not rdpa_ucast_ipv6_host_address_table_find^[[0m
It is a good idea to get a small UPS for your router and modem.
 
I hesitate with this because I haven't captured it in the logs and or it may be AIMesh closed source code. But the activity is different from 386.1

Occasionally, as I move through the house I correlate Dissaoc/ReAssoc of my iPhone in the logs. But after a few minutes I lose my IPADDR. Still have good signal strength just no layer 3, no Internet, no local access. Not sure what to look for or how to test and even if I did, whether this was going to be closed source. I have the roaming assistant enabled, set to disconnect clients with an RSSI lower than -65 dBm. Tx power adjustment set to performance. No Smart connect. I can see the iPhone coming off or coming on the router or AIMesh nodes in wlceventd.log and roamast.log. Now after losing my IP, if I go back and connect back to the original location I was on, local and Internet connectivity resume. If I toggle WiFi on the phone I get it back. 2.4Ghz or 5Ghz no difference after this happens, I'm working again. Under 386.1 this happened very infrequently to the point where I thought just adjusting the threshold on the roaming assist would do the trick, and for the most part I felt it did. Under 386.1_2 this is happening much more often. What I have yet to try is if waiting long enough do I get the IPADDR back, I think I do, but need to be sure.

At this point not sure what to look for, where to look and a test scenario to capture, open to ideas...
Thinking of using the laptop, wireshark and roaming as a first step, to try to get a little more detail to correlate with the logs on the router, grab the arp table at the router, nodes and laptop and compare before, during and after. Taking suggestions.

Got this but I think that's related to AIMesh closed source;
Feb 17 18:12:58 AC5300-MBR kernel: br0: received packet on wl1.1 with own address as source address
Feb 17 18:26:09 AC5300-CP kernel: br0: received packet on wl2.1 with own address as source address
Feb 17 18:26:12 AX88U-MAIN kernel: br0: received packet on eth7 with own address as source address
Feb 17 18:54:03 AC5300-MBR kernel: br0: received packet on wl0.1 with own address as source address
Feb 17 18:54:43 AX88U-MAIN kernel: br0: received packet on eth6 with own address as source address
Feb 17 18:55:11 AC5300-MBR kernel: br0: received packet on wl0.1 with own address as source address
Feb 17 18:56:54 AX88U-MAIN kernel: br0: received packet on eth7 with own address as source address
Feb 17 18:56:58 AC5300-MBR kernel: br0: received packet on wl1.1 with own address as source address
Feb 17 18:57:12 AX88U-MAIN kernel: br0: received packet on eth7 with own address as source address
Feb 17 18:57:21 AC5300-MBR kernel: br0: received packet on wl1.1 with own address as source address
Feb 17 18:58:15 AX88U-MAIN kernel: br0: received packet on eth7 with own address as source address
Feb 17 18:58:19 AX88U-MAIN kernel: br0: received packet on eth7 with own address as source address
Feb 17 19:16:32 AC5300-CP kernel: br0: received packet on wl2.1 with own address as source address
Feb 17 19:16:33 AC5300-MBR kernel: br0: received packet on wl1.1 with own address as source address
Feb 17 19:16:53 AC5300-CP kernel: br0: received packet on wl2.1 with own address as source address
Feb 17 19:16:54 AX88U-MAIN kernel: br0: received packet on eth7 with own address as source address
 
Last edited:
Anyone else have these entries in the logs every 12 hrs? AX88U main router with a AX58U node,

Code:
Feb 17 07:42:34 kernel: wfd_unregisterdevice Successfully unregistered ifidx 2 wfd_idx 0
Feb 17 07:42:34 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,652: Failed to delete VLAN device wds0.0.1.501^[[0m
Feb 17 07:42:34 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,652: Failed to delete VLAN device wds0.0.1.0^[[0m
Feb 17 07:42:34 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,652: Failed to delete VLAN device wds0.0.1.502^[[0m
Feb 17 07:42:34 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,652: Failed to delete VLAN device wds0.0.1.0^[[0m
Feb 17 07:42:34 kernel: wfd_registerdevice Successfully registered dev wds0.0.1 ifidx 2 wfd_idx 0
Feb 17 07:42:34 kernel: Register interface [wds0.0.1]  MAC: 24:4b:fe:xx:xx:xx
Feb 17 07:42:34 kernel: netdev path : wds0.0.1.0 -> wds0.0.1
Feb 17 07:42:34 kernel: BCMVLAN : wds0.0.1 mode was set to RG
Feb 17 07:42:34 kernel: netdev path : wds0.0.1.501 -> wds0.0.1
Feb 17 07:42:34 kernel: BCMVLAN : wds0.0.1 mode was set to RG
Feb 17 07:42:34 kernel: netdev path : wds0.0.1.502 -> wds0.0.1
Feb 17 07:42:34 kernel: BCMVLAN : wds0.0.1 mode was set to RG
Feb 17 07:42:56 kernel: wfd_unregisterdevice Successfully unregistered ifidx 2 wfd_idx 1
Feb 17 07:42:56 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,652: Failed to delete VLAN device wds1.0.1.501^[[0m
Feb 17 07:42:56 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,652: Failed to delete VLAN device wds1.0.1.0^[[0m
Feb 17 07:42:56 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,652: Failed to delete VLAN device wds1.0.1.502^[[0m
Feb 17 07:42:56 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,652: Failed to delete VLAN device wds1.0.1.0^[[0m
Feb 17 07:42:58 kernel: wfd_registerdevice Successfully registered dev wds1.0.1 ifidx 2 wfd_idx 1
Feb 17 07:42:58 kernel: Register interface [wds1.0.1]  MAC: 24:4b:fe:xx:xx:xx
Feb 17 07:42:58 kernel: netdev path : wds1.0.1.0 -> wds1.0.1
Feb 17 07:42:58 kernel: BCMVLAN : wds1.0.1 mode was set to RG
Feb 17 07:42:58 kernel: netdev path : wds1.0.1.501 -> wds1.0.1
Feb 17 07:42:58 kernel: BCMVLAN : wds1.0.1 mode was set to RG
Feb 17 07:42:58 kernel: netdev path : wds1.0.1.502 -> wds1.0.1
Feb 17 07:42:58 kernel: BCMVLAN : wds1.0.1 mode was set to RG
Feb 17 19:42:36 kernel: wfd_unregisterdevice Successfully unregistered ifidx 2 wfd_idx 0
Feb 17 19:42:36 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,652: Failed to delete VLAN device wds0.0.1.501^[[0m
Feb 17 19:42:36 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,652: Failed to delete VLAN device wds0.0.1.0^[[0m
Feb 17 19:42:36 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,652: Failed to delete VLAN device wds0.0.1.502^[[0m
Feb 17 19:42:36 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,652: Failed to delete VLAN device wds0.0.1.0^[[0m
Feb 17 19:42:36 kernel: wfd_registerdevice Successfully registered dev wds0.0.1 ifidx 2 wfd_idx 0
Feb 17 19:42:36 kernel: Register interface [wds0.0.1]  MAC: 24:4b:fe:xx:xx:xx
Feb 17 19:42:36 kernel: netdev path : wds0.0.1.0 -> wds0.0.1
Feb 17 19:42:36 kernel: BCMVLAN : wds0.0.1 mode was set to RG
Feb 17 19:42:36 kernel: netdev path : wds0.0.1.501 -> wds0.0.1
Feb 17 19:42:36 kernel: BCMVLAN : wds0.0.1 mode was set to RG
Feb 17 19:42:36 kernel: netdev path : wds0.0.1.502 -> wds0.0.1
Feb 17 19:42:36 kernel: BCMVLAN : wds0.0.1 mode was set to RG
Feb 17 19:43:00 kernel: wfd_unregisterdevice Successfully unregistered ifidx 2 wfd_idx 1
Feb 17 19:43:00 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,652: Failed to delete VLAN device wds1.0.1.501^[[0m
Feb 17 19:43:00 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,652: Failed to delete VLAN device wds1.0.1.0^[[0m
Feb 17 19:43:00 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,652: Failed to delete VLAN device wds1.0.1.502^[[0m
Feb 17 19:43:00 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,652: Failed to delete VLAN device wds1.0.1.0^[[0m
Feb 17 19:43:02 kernel: wfd_registerdevice Successfully registered dev wds1.0.1 ifidx 2 wfd_idx 1
Feb 17 19:43:02 kernel: Register interface [wds1.0.1]  MAC: 24:4b:fe:xx:xx:xx
Feb 17 19:43:02 kernel: netdev path : wds1.0.1.0 -> wds1.0.1
Feb 17 19:43:02 kernel: BCMVLAN : wds1.0.1 mode was set to RG
Feb 17 19:43:02 kernel: netdev path : wds1.0.1.501 -> wds1.0.1
Feb 17 19:43:02 kernel: BCMVLAN : wds1.0.1 mode was set to RG
Feb 17 19:43:02 kernel: netdev path : wds1.0.1.502 -> wds1.0.1
Feb 17 19:43:02 kernel: BCMVLAN : wds1.0.1 mode was set to RG
 
Status
Not open for further replies.

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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