Diamond67
Senior Member
I would be more shocked if there were UK/EU...Shocking, I am getting GERMANY on both of my routers. Wonder if this is Brexit compliant and should I send them back?...
I would be more shocked if there were UK/EU...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...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 GermanyShocking, I am getting GERMANY on both of my routers. Wonder if this is Brexit compliant and should I send them back?...
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-topicSend them to Boris to get them and the Brexit fixed...
I can confirm even if you restarted it a few times. Wait patiently it will work. I can access webui now.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?
Trend Micro engine loading, has always been there.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
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.
Hi,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.
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.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.
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 can confirm 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.
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
Is that a comment to my previous message?Yes but in that case, the intenet traffic on the network map page is corrupt.
It is a good idea to get a small UPS for your router and modem.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
Dont think it was the power outage as I had a similar issue a few weeks back.It is a good idea to get a small UPS for your router and modem.
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
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!