wl across mesh?

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

calzor suzay

Regular Contributor
I currently run a presence detection script that picks up a few devices to see if we're home or not and update/do something with the home automation.
This worked great when I just had an RT68U but now I have a RT86U as primary and the RT68U as a node in AiMesh, both on latest merlin build.

I migrated the script to the 86U, had to tweak eth1 and eth2 to eth5 & 6 but then noticed if I roam across to the 68U it thinks I've left the network.
I'm assuming as the wl -i eth(5&6) assoclist | awk MAC is only checking the local router not the 'mesh'.
Can it be run from 86U as one command or do I need to setup a separate cron job on the 68U.
If so the 68U no longer has a USB drive etc where would I save the script to and setup the cron job so it's not wiped on a reboot?
 

ColinTaylor

Part of the Furniture
You don't need a USB drive to run scripts. The default location for persistent scripts is /jffs/scripts so that is the obvious choice.
 

calzor suzay

Regular Contributor
Thanks, wasn't sure if that was a merlin, USB drive adding thing. Only ever had Merlin with a USB and all that jazz :)
 

calzor suzay

Regular Contributor
hmmm doesn't work.

I can see devices connected on 68U in AiMesh but when I perform wl -i eth1 assoclist & wl -i eth2 assoclist I get one mac address on both that are very similar apart from the last digit, maybe the radio cards?

Either way I can't seem to get a list of devices using the wireless on the node.
 

calzor suzay

Regular Contributor
So yeah the wo MACs I see on the 68U are the BSSID from the wireless log on the 86U
 

ColinTaylor

Part of the Furniture
I can see devices connected on 68U in AiMesh but when I perform wl -i eth1 assoclist & wl -i eth2 assoclist I get one mac address on both that are very similar apart from the last digit, maybe the radio cards?
Probably the MAC addresses of the primary router's 2.4 and 5 GHz radios.
 

calzor suzay

Regular Contributor
Why can't I see any wireless devices listed on the 68U when they are connected to it?

I thought this was a "use private address" on IOS thing but even with that turned off I see the mac come and go from 86U but not appear on the 68U.
 

ColinTaylor

Part of the Furniture
Why can't I see any wireless devices listed on the 68U when they are connected to it?
I don't know because I've never used AiMesh. Maybe it's using a virtual interface. Can you post the complete output of:
Code:
ifconfig
 

calzor suzay

Regular Contributor
Bingo bongo I think... you pushed me in the right direction

I can devices that have a matching mac on wl0.1 & wl1.1 would these be good to interrogate?

br0 Link encap:Ethernet HWaddr 9C:5C:8E:8A:1D:A8
inet addr:192.168.1.201 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:104647 errors:0 dropped:0 overruns:0 frame:0
TX packets:56311 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:16205329 (15.4 MiB) TX bytes:17478435 (16.6 MiB)

dpsta Link encap:Ethernet HWaddr 9E:5C:8E:8A:1D:A8
UP BROADCAST RUNNING NOARP ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:373599 errors:0 dropped:0 overruns:0 frame:250700
TX packets:5535 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:117891106 (112.4 MiB) TX bytes:1184323 (1.1 MiB)

eth0 Link encap:Ethernet HWaddr 9C:5C:8E:8A:1D:A8
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1183226 errors:0 dropped:0 overruns:0 frame:0
TX packets:1072496 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1289693279 (1.2 GiB) TX bytes:745164007 (710.6 MiB)
Interrupt:179 Base address:0x4000

eth1 Link encap:Ethernet HWaddr 9C:5C:8E:8A:1D:A9
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:187198 errors:0 dropped:0 overruns:0 frame:168369
TX packets:1804 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:58972279 (56.2 MiB) TX bytes:386774 (377.7 KiB)
Interrupt:163

eth2 Link encap:Ethernet HWaddr 9C:5C:8E:8A:1D:AC
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:186401 errors:0 dropped:0 overruns:0 frame:82331
TX packets:3731 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:58918827 (56.1 MiB) TX bytes:797549 (778.8 KiB)
Interrupt:169

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MULTICAST MTU:16436 Metric:1
RX packets:12540 errors:0 dropped:0 overruns:0 frame:0
TX packets:12540 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2870329 (2.7 MiB) TX bytes:2870329 (2.7 MiB)

lo:0 Link encap:Local Loopback
inet addr:127.0.1.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MULTICAST MTU:16436 Metric:1

vlan1 Link encap:Ethernet HWaddr 9C:5C:8E:8A:1D:A8
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:182618 errors:0 dropped:0 overruns:0 frame:0
TX packets:494532 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:48906721 (46.6 MiB) TX bytes:556714605 (530.9 MiB)

vlan2 Link encap:Ethernet HWaddr 9C:5C:8E:8A:1D:A8
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:1000608 errors:0 dropped:0 overruns:0 frame:0
TX packets:577964 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1234683766 (1.1 GiB) TX bytes:186672704 (178.0 MiB)

wl0.1 Link encap:Ethernet HWaddr 9C:5C:8E:8A:1D:A9
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:146146 errors:0 dropped:0 overruns:0 frame:168369
TX packets:227819 errors:3288 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:49813313 (47.5 MiB) TX bytes:185167853 (176.5 MiB)

wl1.1 Link encap:Ethernet HWaddr 9C:5C:8E:8A:1D:AC
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:96086 errors:0 dropped:0 overruns:0 frame:82331
TX packets:456720 errors:7 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:28068764 (26.7 MiB) TX bytes:526571680 (502.1 MiB)
 

ColinTaylor

Part of the Furniture
wl0.1 and wl1.1 would normally be the first guest SSIDs on the 2.4 and 5 GHz bands respectivly. If you're not running guest SSIDs on this router then maybe AiMesh re-purposes them for itself. It would be easy to check by seeing what clients are associated with them.
 

calzor suzay

Regular Contributor
Yeah they appear on there but now I have the problem with the logic.
When a device is seen by one router it turns the switch on but the other turns it off. so they end up flicking about fighting.

Is there a way to script the 86U to run the wl command remotely on the 68U easily and use the output?
 

calzor suzay

Regular Contributor
I've fudged a way around it by having a 'switch' on my home automation covering each router and then if one of the two switches per phone is on then it's home.

Bit clunky so would prefer to be able to interrogate the 68U from the 86U for the result from one router then using one switch on my home automation.
 

Similar threads

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