NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
NickC44
Dec 20, 2016Aspirant
mib troubles
I am trying to find out the rssi and bssi of a WNAP320, but cannot seem to get my network monitor app (Intermapper) to recognize the particular OID. I have loaded the correct mib file, and can pull ...
- Jan 02, 2017
Hi Nick
Hope there is no obstacles or any interferences betweek two buildings. You can use third party application such as inssider to find out signal strength. .
http://www.metageek.com/products/inssider/
Regret to inform you that Our current firmware do not support remote AP signal strength in WDS mode.
Thanks
Raghu
RaghuHR
Dec 22, 2016NETGEAR Expert
Hi Nick44
Tested in v3.5.20.0 firmware. Able to get associatedBSSID and StationRSSI through MIB browser.
Following are the OIDs
Associated BSSID - .1.3.6.1.4.1.4526.100.7.9.8.1.1.6
Station RSSI - .1.3.6.1.4.1.4526.100.7.9.8.1.1.10
We are getting those information under
stationList -> stationListTable -> stationListEntry -> associatedBssid / stationRssi
- NickC44Dec 22, 2016Aspirant
Thanks for the response, RaghuHR. I just upgraded the firmware on both units (operating in bridge mode) to 3.5.20.0, and made sure I was using the WNAP320_v3.5.20.0.mib file, but still cannot get any info from section 8 "station list". I can get info from earlier sections (e.g., 5.1.1), so I know I'm formatting the OID correctly. Both 8.1.1.6 and 8.1.1.10 return "NoSuchName" no matter what I do. =(
- RaghuHRDec 28, 2016NETGEAR Expert
Hi NickC44
Could you please attach AP configuration and MIB browser details?
Have you tried without WDS?
In addition with that, you may download the logs and share it?
Thanks
Raghu
- NickC44Dec 28, 2016Aspirant
AP config file shared via Dropbox:
https://dl.dropboxusercontent.com/u/3420412/config-3I used the iReasoning MIB browser to see what you were seeing in your previous reply.
I have not tried it without WDS. I am using the two units to link buildings across a street (~130ft, clear line-of-sight), so no WDS = no point at all.
Log is filled with these messages:
Dec 28 02:41:33 hostapd: inet_connection_check 2379 {pinging gateway 172.17.1.1, status 1}
Dec 28 02:41:33 hostapd: Network Integrality: Ping Success
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!