NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Insight Management App
15 TopicsIOS Apple Devices Dropping
I have WAX625, WAX610, & 605. For a number of months now, my IOS devices continue to drop their WIFI and then takes 2-5min to reconnect. I originally had Load Balance and Remove Sticky Clients configured. I have put everything back. Firmware on the AP is 10.8.13.2 I am a technical guy and I feel I have tried all the other things that have been mentioned in posts that sort of sound like mine. I think this is only happening on my 5/6ghz SSID. I Have a SSID for 2.4 and one for 5/6. Any suggestions? Anyone else seeing this? Im so frustrated that I'm looking at a different vendor for the house. I am managing these in Insight.55Views0likes3CommentsMAC Address to Device Name / Hostname
I saw a previous discussion from a few years ago but never saw an answer. I have three APs (WBE710 and a WAX610Y) all insight managed for now. They only show the device's MAC address. How can I change this to show an actual device name that I'll have to create elsewhere? If I log into a WBE710 directly, go to connected clients, I can see for example my iphone. MAC, IP, Hostname, OS....it looks like I can edit the hostname to whatever, but seems to be blocked as Insight has control. Can this be edited in Insight? Can this only be done if I kill off Insight? Would this only be in effect on that specific AP? If I roam to another AP would that name follow? SonicWall is my router and providing DHCP, this coming from SonicWall, ie I need to create address objects...and assign a name in that?Solved71Views0likes2CommentsDevices from AP to AP results "Bad Password"
I have a weird on going issue that im hoping someone can help with. I have two Access points in the home, one upstairs (WAX615 on ch3 / ch36 ) and one downstairs (WAC510 on ch1 / ch161) Both are providing the same SSID's: "1930Networks" - This is only the 5G band "1930Networks (2.4G)" - This is the only 2.4 band The idea is that you should be able to travel anywhere around the house and the AP's should hand off to one another. However when connected to one AP (doesn't matter which one) and then moving far away from the AP, the device tries to jump onto the other AP but the device always says "Bad Password" -- the passwords are the same for the same SSID. What could be causing this?Solved1.1KViews0likes1CommentAccount switched to trial mode despite having a valid subscription
My account was converted from my annual Premium support subscription to Trial mode w/o any notice or explanation. I've submitted a ticket but support sucks. No one there seems to know what to do. This happened in conjunction with some back end maintenance that happened around July 6th. Did anyone else experience this and how were they able to get this resolved?707Views0likes0CommentsWAX630E firmware update failing again
When I bought these three units in October I couldn’t get them to firmware update except my by removing them from Insight, updating the firmware through the web ui, and then repairing them to insight. Now there are new updates (I’m on 10.2 still) and they similarly just can’t be installed. How can I get upgrade logs to see why it is failing? I really don’t want to have to remove these devices from management every time a new firmware comes out. Previous issue: https://community.netgear.com/t5/Business-Wireless/WAX630E-Firmware-Update-Failure/m-p/2264528#M10031Solved3.2KViews0likes4CommentsWAX630 Firmware issue 10.2.0.16
My network just updated it's firmware from 9.x to the new 10.2.0.16 and I have been having many issues with devices no longer connecting/staying connected or being able to access the internet through the WIFI. Nothing else in the system has changed other than the firmware . Range has been decreased, speed tests also sometimes don't work now as well. I did not enable any of the new features and confirmed the Power Saver is off through Insight. I seemed to have some partial success by turning off, and back on the individual SSIDs. This is happening to multiple VLAN s and SSIDs coming through these WAPs. Is there a way to roll back the FIrmware using the Cloud Portal or do I need to reflash each individual unit to the older firmware. Was working fine prior to the firmware update... Will rolling back disable my Insight Cloud Portal?2.4KViews0likes5CommentsWiFi 6E 6Ghz Access Point WAX630E with NETGEAR Insight Remote Management
Today NETGEAR has announced a new Insight Managed WiFi 6E Access Point. The new WAX630E is a 6Ghz Tri-band, multi-gig access point that brings the latest WiFi 6E performance to small and medium-sized businesses at an affordable price. Discover our first WiFi 6E Access Point WAX630E. “Wi-Fi 6E provides a wide, open, fast superhighway to provide the required capacity and speed. The new WAX630E is the perfect onramp for SMBs.” NETGEAR's Doug Cheung - Direct of Product Line Management of SMB wireless. In Doug's latest business blog we compare WAX630E WiFi 6E AP to the WAX630 WiFi 6 AP Read the Forbes preview of the WAX630E AP. Watch a short interview with Doug - NETGEAR Director of SMB Wireless20KViews4likes0CommentsAirbridges act erratic then drop completely until power cycle.
I have 3 WBC502 airbridges (firmware is the latest version as of this posting on 10/4). One of them is mounted to my main building one and two are across a parking lot as satilittles in an airbridge group. They are setup in my insight managment portal. The main unit will only stay up for about 10-20 minutes or so after a boot up. After that it becomes unresponsive to pings or web requests or insight management and thus the other 2 fall off as well. The only way I can fix it is to physically go and power cycle the power brick that came packaged with the unit (Yes I am using the designated power bricks that shipped with the units.) So i'll walk over, power cycle it, a minute later they all come back up in my insight portal and I can ping them again and reach their web interfaces. Then about 10-20 minutes later down they all go. I sat in the web interface of both the master and one of the satillites as long as I could before it dropped off so I could copy as much of the log files as I could. Keep in mind that this is the 2nd master unit I've had. I spent a ton of time with support and eventually after turning off spanning tree on the switchport that the power brick is plugged into which is ALSO a netgear switch that is in my insight portal by the way (GS752TPP). Also have all POE turned off on port the brick is in as well. I've tried turning the spanning tree on and off on the bridges themselves that doesn't help either. So a few things i'm noticing in the MAIN (Master Unit) before it goes down everytime there are a large number of association events in the log right before it dies that look like this 2021-10-04T15:49:52.342989-05:00Z WBC502 daemon.info hostapd: Ham-WiFi-Bridge: STA bc:a5:11:7f:0b:97 IEEE 802.11: disassociated 2021-10-04T15:49:43.207844-05:00Z WBC502 daemon.info hostapd: Ham-WiFi-Bridge: STA bc:a5:11:7f:0b:97 WPA: WPA/WPA2 authentication successful 2021-10-04T15:49:43.205747-05:00Z WBC502 daemon.info hostapd: Ham-WiFi-Bridge: STA bc:a5:11:7f:0b:97 WPA: pairwise key handshake completed (RSN) 2021-10-04T15:49:43.132099-05:00Z WBC502 daemon.info hostapd: Ham-WiFi-Bridge: STA bc:a5:11:7f:0b:97 IEEE 802.11: associated 2021-10-04T15:49:42.914799-05:00Z WBC502 daemon.info hostapd: Ham-WiFi-Bridge: STA bc:a5:11:7f:0b:97 IEEE 802.11: disassociated 2021-10-04T15:49:40.897861-05:00Z WBC502 kern.info kernel: [ 219.400214] br-lan: topology change detected, propagating 2021-10-04T15:49:40.897437-05:00Z WBC502 kern.info kernel: [ 219.393344] br-lan: port 2(wifijet1) neighbor 8000.bc:a5:11:7f:0a:4b lost 2021-10-04T15:49:21.097321-05:00Z WBC502 daemon.info hostapd: Ham-WiFi-Bridge: STA bc:a5:11:7f:0b:97 WPA: WPA/WPA2 authentication successful 2021-10-04T15:49:21.095493-05:00Z WBC502 daemon.info hostapd: Ham-WiFi-Bridge: STA bc:a5:11:7f:0b:97 WPA: pairwise key handshake completed (RSN) 2021-10-04T15:49:21.023148-05:00Z WBC502 daemon.info hostapd: Ham-WiFi-Bridge: STA bc:a5:11:7f:0b:97 IEEE 802.11: associated 2021-10-04T15:49:07.648787-05:00Z WBC502 daemon.info hostapd: Ham-WiFi-Bridge: STA bc:a5:11:7f:0b:97 IEEE 802.11: disassociated 2021-10-04T15:49:03.602813-05:00Z WBC502 daemon.info hostapd: Ham-WiFi-Bridge: STA bc:a5:11:7f:0b:97 IEEE 802.11: associated 2021-10-04T15:49:03.591558-05:00Z WBC502 daemon.info hostapd: Ham-WiFi-Bridge: STA bc:a5:11:7f:0b:97 IEEE 802.11: disassociated 2021-10-04T15:48:55.990154-05:00Z WBC502 daemon.info hostapd: Ham-WiFi-Bridge: STA bc:a5:11:7f:0b:97 IEEE 802.11: disassociated 2021-10-04T15:48:51.942471-05:00Z WBC502 daemon.info hostapd: Ham-WiFi-Bridge: STA bc:a5:11:7f:0b:97 IEEE 802.11: associated 2021-10-04T15:48:51.721508-05:00Z WBC502 daemon.info hostapd: Ham-WiFi-Bridge: STA bc:a5:11:7f:0b:97 IEEE 802.11: disassociated 2021-10-04T15:48:51.301303-05:00Z WBC502 daemon.info hostapd: Ham-WiFi-Bridge: STA bc:a5:11:7f:0b:97 IEEE 802.11: disassociated 2021-10-04T15:48:50.894555-05:00Z WBC502 daemon.info hostapd: Ham-WiFi-Bridge: STA bc:a5:11:7f:0b:97 IEEE 802.11: disassociated 2021-10-04T15:48:48.656219-05:00Z WBC502 daemon.info hostapd: Ham-WiFi-Bridge: STA bc:a5:11:7f:0a:4d WPA: WPA/WPA2 authentication successful 2021-10-04T15:48:48.654803-05:00Z WBC502 daemon.info hostapd: Ham-WiFi-Bridge: STA bc:a5:11:7f:0a:4d WPA: pairwise key handshake completed (RSN) 2021-10-04T15:48:48.581231-05:00Z WBC502 daemon.info hostapd: Ham-WiFi-Bridge: STA bc:a5:11:7f:0a:4d IEEE 802.11: associated 2021-10-04T15:48:48.360898-05:00Z WBC502 daemon.info hostapd: Ham-WiFi-Bridge: STA bc:a5:11:7f:0a:4d IEEE 802.11: disassociated 2021-10-04T15:48:33.661997-05:00Z WBC502 daemon.info hostapd: Ham-WiFi-Bridge: STA bc:a5:11:7f:0b:97 WPA: WPA/WPA2 authentication successful 2021-10-04T15:48:33.660056-05:00Z WBC502 daemon.info hostapd: Ham-WiFi-Bridge: STA bc:a5:11:7f:0b:97 WPA: pairwise key handshake completed (RSN) 2021-10-04T15:48:32.821898-05:00Z WBC502 daemon.info hostapd: Ham-WiFi-Bridge: STA bc:a5:11:7f:0b:97 IEEE 802.11: associated 2021-10-04T15:48:32.613243-05:00Z WBC502 daemon.info hostapd: Ham-WiFi-Bridge: STA bc:a5:11:7f:0b:97 IEEE 802.11: associated 2021-10-04T15:48:32.601436-05:00Z WBC502 daemon.info hostapd: Ham-WiFi-Bridge: STA bc:a5:11:7f:0b:97 IEEE 802.11: disassociated 2021-10-04T15:48:23.525662-05:00Z WBC502 daemon.info hostapd: Ham-WiFi-Bridge: STA bc:a5:11:7f:0b:97 IEEE 802.11: disassociated 2021-10-04T15:48:22.255669-05:00Z WBC502 daemon.info hostapd: Ham-WiFi-Bridge: STA bc:a5:11:7f:0b:97 IEEE 802.11: disassociated 2021-10-04T15:48:21.682032-05:00Z WBC502 daemon.info hostapd: Ham-WiFi-Bridge: STA bc:a5:11:7f:0b:97 IEEE 802.11: disassociated 2021-10-04T15:48:21.263239-05:00Z WBC502 daemon.info hostapd: Ham-WiFi-Bridge: STA bc:a5:11:7f:0b:97 IEEE 802.11: disassociated I also got the info from one of the Satillite logs before i lost contact with it and it had this to say :50:13.350559-05:00Z WBC502 kern.info kernel: [280321.961129] sysctl (24040): drop_caches: 3 2021-10-04T15:50:12.960158-05:00Z WBC502 user.notice memory: freemem=18752, totalmem=125292, rate=14, Need to free memory caches!! 2021-10-04T15:49:43.274108-05:00Z WBC502 kern.info kernel: [280291.896020] br-lan: topology change detected, propagating 2021-10-04T15:49:43.273697-05:00Z WBC502 kern.info kernel: [280291.890853] br-lan: port 1(ath55) received tcn bpdu 2021-10-04T15:49:42.278788-05:00Z WBC502 kern.info kernel: [280290.903597] br-lan: topology change detected, propagating 2021-10-04T15:49:42.278370-05:00Z WBC502 kern.info kernel: [280290.898435] br-lan: port 1(ath55) received tcn bpdu 2021-10-04T15:49:19.246394-05:00Z WBC502 kern.info kernel: [280267.870563] br-lan: port 1(ath55) entered forwarding state 2021-10-04T15:49:19.245965-05:00Z WBC502 kern.info kernel: [280267.864870] br-lan: topology change detected, propagating 2021-10-04T15:49:04.203620-05:00Z WBC502 kern.info kernel: [280252.824873] br-lan: port 1(ath55) entered learning state 2021-10-04T15:48:57.024923-05:00Z WBC502 user.notice connect: Ham-WiFi-Bridge BC:A5:11:7F:0B:D6 IEEE802.11: associated 2021-10-04T15:48:49.201062-05:00Z WBC502 kern.info kernel: [280237.824738] br-lan: port 1(ath55) entered listening state 2021-10-04T15:48:49.200655-05:00Z WBC502 kern.info kernel: [280237.818981] br-lan: port 1(ath55) entered listening state 2021-10-04T15:48:49.171315-05:00Z WBC502 daemon.notice netifd: Network device 'ath55' link is up 2021-10-04T15:48:49.170861-05:00Z WBC502 kern.info kernel: [280237.793224] br-lan: port 1(ath55) entered disabled state 2021-10-04T15:48:49.170460-05:00Z WBC502 kern.info kernel: [280237.786779] br-lan: port 1(ath55) entered listening state 2021-10-04T15:48:49.170022-05:00Z WBC502 kern.info kernel: [280237.781020] br-lan: port 1(ath55) entered listening state 2021-10-04T15:48:49.148627-05:00Z WBC502 kern.warn kernel: [280237.770009] Number of STA VAPs connected: 1 2021-10-04T15:48:49.147855-05:00Z WBC502 kern.warn kernel: [280237.770009] 2021-10-04T15:48:49.147138-05:00Z WBC502 kern.warn kernel: [280237.763756] Beacon mode set to staggered. Cannot enable FD 2021-10-04T15:48:49.145868-05:00Z WBC502 kern.warn kernel: [280237.759043] send_vdev_up_cmd_non_tlv for vap 0 2021-10-04T15:48:49.145452-05:00Z WBC502 kern.warn kernel: [280237.751601] su bfee 1 mu bfee 1 su bfer 1 mu bfer 0 impl bf 0 sounding dim 1 2021-10-04T15:48:49.144975-05:00Z WBC502 kern.warn kernel: [280237.747385] send_wmm_update_cmd_non_tlv: 2021-10-04T15:48:48.676795-05:00Z WBC502 kern.warn kernel: [280237.299597] send_wmm_update_cmd_non_tlv: 2021-10-04T15:48:48.675951-05:00Z WBC502 kern.warn kernel: [280237.294105] ol_vdev_start_resp_ev for vap 0 (85b64000) 2021-10-04T15:48:48.675400-05:00Z WBC502 kern.warn kernel: [280237.290518] OL vap_start - 2021-10-04T15:48:48.674692-05:00Z WBC502 kern.warn kernel: [280237.287977] VDEV START 2021-10-04T15:48:48.673831-05:00Z WBC502 kern.warn kernel: [280237.285029] OL vap_start + 2021-10-04T15:48:48.672955-05:00Z WBC502 kern.warn kernel: [280237.274894] ieee80211_match_rsn_info[830] pairwise 0x8, gtk 0x8 , keymgmt 0x2 2021-10-04T15:48:48.634118-05:00Z WBC502 kern.warn kernel: [280237.254947] Warning:Stop during VAP Init ! 2021-10-04T15:48:48.620231-05:00Z WBC502 kern.warn kernel: [280237.236970] send_wmm_update_cmd_non_tlv: 2021-10-04T15:48:48.619804-05:00Z WBC502 kern.warn kernel: [280237.236942] ol_vdev_start_resp_ev for vap 0 (85b64000) 2021-10-04T15:48:48.619405-05:00Z WBC502 kern.warn kernel: [280237.228369] OL vap_start - 2021-10-04T15:48:48.619007-05:00Z WBC502 kern.warn kernel: [280237.228363] VDEV START 2021-10-04T15:48:48.618610-05:00Z WBC502 kern.warn kernel: [280237.228355] OL vap_start + 2021-10-04T15:48:48.618208-05:00Z WBC502 kern.warn kernel: [280237.220539] ieee80211_match_rsn_info[830] pairwise 0x8, gtk 0x8 , keymgmt 0x2 2021-10-04T15:48:48.617773-05:00Z WBC502 kern.warn kernel: [280237.213357] [ieee80211_ioctl_setmlme] set desired bssid bc:a5:11:7f:0b:d6 2021-10-04T15:48:48.617364-05:00Z WBC502 kern.warn kernel: [280237.205821] DES SSID SET=Ham-WiFi-Bridge 2021-10-04T15:48:48.616930-05:00Z WBC502 kern.warn kernel: [280237.205821] 2021-10-04T15:48:48.616512-05:00Z WBC502 kern.warn kernel: [280237.199350] [DEBUG] vap-0(ath55):set SIOC80211NWID, 15 characters 2021-10-04T15:48:17.946757-05:00Z WBC502 user.warn insight-brokerd[2614]: Device state is offline. Skip collecting monitoring data. 2021-10-04T15:47:55.292680-05:00Z WBC502 user.notice connect: Ham-WiFi-Bridge BC:A5:11:7F:0B:D6 IEEE802.11: disassociated 2021-10-04T15:47:47.945936-05:00Z WBC502 user.warn insight-brokerd[2614]: Device state is offline. Skip collecting monitoring data. 2021-10-04T15:47:47.553912-05:00Z WBC502 kern.info kernel: [280176.177476] br-lan: port 1(ath55) entered disabled state 2021-10-04T15:47:47.553178-05:00Z WBC502 daemon.notice netifd: Network device 'ath55' link is down 2021-10-04T15:47:47.544796-05:00Z WBC502 kern.warn kernel: [280176.165080] STOPPED EVENT for vap 0 (85b64000) 2021-10-04T15:47:44.530277-05:00Z WBC502 user.notice connect: Ham-WiFi-Bridge BC:A5:11:7F:0B:D6 IEEE802.11: associated 2021-10-04T15:47:43.536049-05:00Z WBC502 kern.info kernel: [280172.156881] br-lan: port 1(ath55) entered listening state 2021-10-04T15:47:43.535526-05:00Z WBC502 kern.info kernel: [280172.151086] br-lan: port 1(ath55) entered listening state 2021-10-04T15:47:43.534962-05:00Z WBC502 kern.warn kernel: [280172.139935] Number of STA VAPs connected: 1 2021-10-04T15:47:43.534323-05:00Z WBC502 kern.warn kernel: [280172.139935] 2021-10-04T15:47:43.533787-05:00Z WBC502 daemon.notice netifd: Network device 'ath55' link is up 2021-10-04T15:47:43.533228-05:00Z WBC502 kern.warn kernel: [280172.133656] Beacon mode set to staggered. Cannot enable FD 2021-10-04T15:47:43.518877-05:00Z WBC502 kern.warn kernel: [280172.128946] send_vdev_up_cmd_non_tlv for vap 0 2021-10-04T15:47:43.516084-05:00Z WBC502 kern.warn kernel: [280172.121511] su bfee 1 mu bfee 1 su bfer 1 mu bfer 0 impl bf 0 sounding dim 1 2021-10-04T15:47:43.515534-05:00Z WBC502 kern.warn kernel: [280172.117298] send_wmm_update_cmd_non_tlv: 2021-10-04T15:47:43.255813-05:00Z WBC502 kern.warn kernel: [280171.879478] send_wmm_update_cmd_non_tlv: 2021-10-04T15:47:43.255285-05:00Z WBC502 kern.warn kernel: [280171.874014] ol_vdev_start_resp_ev for vap 0 (85b64000) 2021-10-04T15:47:43.254752-05:00Z WBC502 kern.warn kernel: [280171.870513] OL vap_start - 2021-10-04T15:47:43.254159-05:00Z WBC502 kern.warn kernel: [280171.867980] VDEV START 2021-10-04T15:47:43.253582-05:00Z WBC502 kern.warn kernel: [280171.865061] OL vap_start + 2021-10-04T15:47:43.252485-05:00Z WBC502 kern.warn kernel: [280171.854914] ieee80211_match_rsn_info[830] pairwise 0x8, gtk 0x8 , keymgmt 0x2 2021-10-04T15:47:43.222644-05:00Z WBC502 kern.warn kernel: [280171.844218] STOPPED EVENT for vap 0 (85b64000) 2021-10-04T15:47:43.222095-05:00Z WBC502 kern.warn kernel: [280171.840175] Unable to process RX info 2021-10-04T15:47:43.221570-05:00Z WBC502 kern.warn kernel: [280171.833946] Beacon mode set to staggered. Cannot enable FD 2021-10-04T15:47:43.221041-05:00Z WBC502 kern.warn kernel: [280171.829230] send_vdev_up_cmd_non_tlv for vap 0 2021-10-04T15:47:43.220500-05:00Z WBC502 kern.warn kernel: [280171.821781] su bfee 1 mu bfee 1 su bfer 1 mu bfer 0 impl bf 0 sounding dim 1 2021-10-04T15:47:43.219865-05:00Z WBC502 kern.warn kernel: [280171.817558] send_wmm_update_cmd_non_tlv: 2021-10-04T15:47:43.219335-05:00Z WBC502 kern.warn kernel: [280171.795850] send_wmm_update_cmd_non_tlv: 2021-10-04T15:47:43.218808-05:00Z WBC502 kern.warn kernel: [280171.795825] ol_vdev_start_resp_ev for vap 0 (85b64000) 2021-10-04T15:47:43.218245-05:00Z WBC502 kern.warn kernel: [280171.787344] OL vap_start - 2021-10-04T15:47:43.185427-05:00Z WBC502 kern.warn kernel: [280171.787339] VDEV START 2021-10-04T15:47:43.185031-05:00Z WBC502 kern.warn kernel: [280171.787331] OL vap_start + 2021-10-04T15:47:43.184623-05:00Z WBC502 kern.warn kernel: [280171.779553] ieee80211_match_rsn_info[830] pairwise 0x8, gtk 0x8 , keymgmt 0x2 2021-10-04T15:47:43.184216-05:00Z WBC502 kern.warn kernel: [280171.772370] [ieee80211_ioctl_setmlme] set desired bssid bc:a5:11:7f:0b:d6 2021-10-04T15:47:43.139205-05:00Z WBC502 kern.warn kernel: [280171.763241] DES SSID SET=Ham-WiFi-Bridge 2021-10-04T15:47:43.138805-05:00Z WBC502 kern.warn kernel: [280171.763241] 2021-10-04T15:47:43.138401-05:00Z WBC502 kern.warn kernel: [280171.756710] [DEBUG] vap-0(ath55):set SIOC80211NWID, 15 characters 2021-10-04T15:47:23.545303-05:00Z WBC502 user.notice connect: Ham-WiFi-Bridge BC:A5:11:7F:0B:D6 IEEE802.11: disassociated 2021-10-04T15:47:17.945409-05:00Z WBC502 user.warn insight-brokerd[2614]: Device state is offline. Skip collecting monitoring data. 2021-10-04T15:47:15.975446-05:00Z WBC502 kern.info kernel: [280144.597458] br-lan: port 1(ath55) entered disabled state 2021-10-04T15:47:15.973092-05:00Z WBC502 daemon.notice netifd: Network device 'ath55' link is down 2021-10-04T15:47:15.964831-05:00Z WBC502 kern.warn kernel: [280144.585166] STOPPED EVENT for vap 0 (85b64000) 2021-10-04T15:47:12.714722-05:00Z WBC502 user.notice connect: Ham-WiFi-Bridge BC:A5:11:7F:0B:D6 IEEE802.11: associated 2021-10-04T15:47:11.777402-05:00Z WBC502 kern.info kernel: [280140.396753] br-lan: port 1(ath55) entered listening state 2021-10-04T15:47:11.776723-05:00Z WBC502 kern.info kernel: [280140.390980] br-lan: port 1(ath55) entered listening state 2021-10-04T15:47:11.775262-05:00Z WBC502 kern.warn kernel: [280140.380017] Number of STA VAPs connected: 1 2021-10-04T15:47:11.774602-05:00Z WBC502 kern.warn kernel: [280140.380017] 2021-10-04T15:47:11.773858-05:00Z WBC502 kern.warn kernel: [280140.373783] Beacon mode set to staggered. Cannot enable FD 2021-10-04T15:47:11.772816-05:00Z WBC502 kern.warn kernel: [280140.369068] send_vdev_up_cmd_non_tlv for vap 0 2021-10-04T15:47:11.758810-05:00Z WBC502 daemon.notice netifd: Network device 'ath55' link is up 2021-10-04T15:47:11.755428-05:00Z WBC502 kern.warn kernel: [280140.361621] su bfee 1 mu bfee 1 su bfer 1 mu bfer 0 impl bf 0 sounding dim 1 2021-10-04T15:47:11.755019-05:00Z WBC502 kern.warn kernel: [280140.357405] send_wmm_update_cmd_non_tlv: 2021-10-04T15:47:11.285717-05:00Z WBC502 kern.warn kernel: [280139.909381] send_wmm_update_cmd_non_tlv: 2021-10-04T15:47:11.285197-05:00Z WBC502 kern.warn kernel: [280139.903873] ol_vdev_start_resp_ev for vap 0 (85b64000) 2021-10-04T15:47:11.284673-05:00Z WBC502 kern.warn kernel: [280139.900481] OL vap_start - 2021-10-04T15:47:11.284101-05:00Z WBC502 kern.warn kernel: [280139.897947] VDEV START 2021-10-04T15:47:11.282914-05:00Z WBC502 kern.warn kernel: [280139.895030] OL vap_start + 2021-10-04T15:47:11.282420-05:00Z WBC502 kern.warn kernel: [280139.884894] ieee80211_match_rsn_info[830] pairwise 0x8, gtk 0x8 , keymgmt 0x2 2021-10-04T15:47:11.241852-05:00Z WBC502 kern.warn kernel: [280139.864942] Warning:Stop during VAP Init ! 2021-10-04T15:47:11.241455-05:00Z WBC502 kern.warn kernel: [280139.854746] send_wmm_update_cmd_non_tlv: 2021-10-04T15:47:11.241062-05:00Z WBC502 kern.warn kernel: [280139.854720] ol_vdev_start_resp_ev for vap 0 (85b64000) 2021-10-04T15:47:11.240661-05:00Z WBC502 kern.warn kernel: [280139.846194] OL vap_start - 2021-10-04T15:47:11.240262-05:00Z WBC502 kern.warn kernel: [280139.846189] VDEV START 2021-10-04T15:47:11.239826-05:00Z WBC502 kern.warn kernel: [280139.846180] OL vap_start + 2021-10-04T15:47:11.239431-05:00Z WBC502 kern.warn kernel: [280139.838374] ieee80211_match_rsn_info[830] pairwise 0x8, gtk 0x8 , keymgmt 0x2 2021-10-04T15:47:11.239023-05:00Z WBC502 kern.warn kernel: [280139.831194] [ieee80211_ioctl_setmlme] set desired bssid bc:a5:11:7f:0b:d6 2021-10-04T15:47:11.198302-05:00Z WBC502 kern.warn kernel: [280139.822474] DES SSID SET=Ham-WiFi-Bridge 2021-10-04T15:47:11.197877-05:00Z WBC502 kern.warn kernel: [280139.822474] 2021-10-04T15:47:11.197470-05:00Z WBC502 kern.warn kernel: [280139.816071] [DEBUG] vap-0(ath55):set SIOC80211NWID, 15 characters 2021-10-04T15:47:00.086626-05:00Z WBC502 daemon.notice netifd: Network device 'ath55' link is down 2021-10-04T15:47:00.084871-05:00Z WBC502 kern.warn kernel: [280128.705081] STOPPED EVENT for vap 0 (85b64000) 2021-10-04T15:46:55.973700-05:00Z WBC502 kern.info kernel: [280124.590275] br-lan: port 1(ath55) entered disabled state 2021-10-04T15:46:55.971732-05:00Z WBC502 daemon.notice netifd: Network device 'ath55' link is up 2021-10-04T15:46:55.971197-05:00Z WBC502 kern.info kernel: [280124.583660] br-lan: port 1(ath55) entered listening state 2021-10-04T15:46:55.970661-05:00Z WBC502 kern.info kernel: [280124.577928] br-lan: port 1(ath55) entered listening state 2021-10-04T15:46:55.970099-05:00Z WBC502 kern.warn kernel: [280124.571169] Number of STA VAPs connected: 1 2021-10-04T15:46:55.969568-05:00Z WBC502 kern.warn kernel: [280124.571169] I noticed a few things there - namely the memory notices and also all the messages about bpdus. A long time ago I had some Cisco point to point Aironets and i remember Bridge Packet Datagram Units causing the interfaces to just shut off on me sometimes. Anyway I have no idea what to do at this point ANY help is appreciated.1.3KViews0likes0CommentsWAC720 CLI Clear Statistics
Is there a way to clear the statistics from the CLI without rebooting the whole access point? I need a method to quickly and accurately monitor the RX and TX packets (which appear after I run the "ifconfig" command) which I can automate which is why I am using the CLI to send commands to the device.1.7KViews0likes1Comment