I have a couple of Ubiquity APs in my home and have an instance of PRTG running. I was looking for a good way to monitor the access points.
Out of the box Ubquiti supports SNMP and SSH. I wanted a way to monitor how many clients are connected. If you want to monitor the access points configure SNMP on the device, feed the string in to PRTG and the SSH credentials.
Then I wrote a simple shell script below that extracts information from the mca-dump table for connected clients. I’m sure there are different and probably more efficient ways to do this, but this works for me. Essentially the code greps the number and formats the return correctly for PRTG to read, including a status code.
1) Create the directory /var/prtg/scripts/
2) Using VI on the access point create the following file with the code below in /var/prtg/scripts/
3) Save it as wifiusers.sh
4) Add a custom SSH sensor for your access point.(I called mine Wifi Clients)
5) Set the primary channel to “Value (#)”
cmd1=`mca-dump | grep num_sta | tail -n1 | sed 's/[^0-9]*//g`
It’s cold in Michigan! About a week ago my seat heaters stopped working in my 2013 F-150. I have the My Ford Touch (MFT) with heated and cooled seats.
- Both seats stopped working.
- The MFT light comes on saying the seat heaters are running
- I can hear the blower kick on under the seat
- No Heat
I reseated the wiring harness under the drivers side seat. Swapped a few fuses around under the hood (the seat heater/cooler is a 30 amp cartridge fuse per the manual)
Nothing. Still the same symptoms.
I finally disconnected the negative of the battery and let it sit for about a half hour. Reconnected and now the issue is resolved. Maybe something with the body control module? Maybe Ford will release a software update.
I couldn’t find much documentation on this from other sources, so hopefully this will help someone else. If you ever need to re-ip a windows DHCP server and they are reporting the wrong address in the DHCP manager do the following (from an elevated/administrative command prompt.) At no point did the DHCP server seem to stop serving IPs, it looks like it was really just displaying the wrong IP.
netsh dhcp delete server <FQDN> <Old IP Address>
netsh dhcp add server <FQDN> <New IP Address>
Changes will replicate across your domain.