Standalone R700 Intermittent disconnects

  • 2
  • Question
  • Updated 2 years ago
  • Answered
Does any of this indicate what kind of issue I am having with intermittent disconnects.  It can be fixed quickly with disconnecting and connecting on wireless adapter.  A few minutes without resetting adapter on my sony laptop.  Can't reconnect for hours on my surface pro 2.

Jun  6 01:19:00 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:19:59 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:21:07 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:22:00 RuckusAP user.warn kernel: FWLOG: [121545939] WAL_DBGID_BB_WDOG_TRIGGERED ( 0x173ea4d3, 0x4300000a, 0x0, 0x21a765a )
Jun  6 01:22:00 RuckusAP user.warn kernel: FWLOG: [121545939] WAL_DBGID_STA_VDEV_XRETRY ( 0x202e0, 0x210020 )
Jun  6 01:22:00 RuckusAP user.warn kernel: FWLOG: [121545940] WAL_DBGID_STA_VDEV_XRETRY ( 0x202e4, 0xe000a )
Jun  6 01:22:00 RuckusAP user.warn kernel: FWLOG: [121545940] WAL_DBGID_STA_VDEV_XRETRY ( 0x202e8, 0x110010 )
Jun  6 01:22:05 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:23:05 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:24:04 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:25:01 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:25:46 RuckusAP user.warn kernel: FWLOG: [121777433] WAL_DBGID_BB_WDOG_TRIGGERED ( 0x17422d19, 0x4300000a, 0x0, 0x21a7d29 )
Jun  6 01:25:46 RuckusAP user.warn kernel: FWLOG: [121777433] WAL_DBGID_STA_VDEV_XRETRY ( 0x202e0, 0x210020 )
Jun  6 01:25:46 RuckusAP user.warn kernel: FWLOG: [121777433] WAL_DBGID_STA_VDEV_XRETRY ( 0x202e4, 0xe000a )
Jun  6 01:25:46 RuckusAP user.warn kernel: FWLOG: [121777433] WAL_DBGID_STA_VDEV_XRETRY ( 0x202e8, 0x110010 )
Jun  6 01:26:08 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:27:15 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:28:20 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:29:16 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:30:16 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:31:18 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:32:26 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:32:44 RuckusAP cron.notice ntpclient[17085]: Using server: time.nist.gov
Jun  6 01:32:44 RuckusAP cron.notice ntpclient[17085]: Time set from remote server
Jun  6 01:32:44 RuckusAP cron.notice ntpclient[17085]: Skew -3.1mS, freq adjust 0
Jun  6 01:33:00 RuckusAP daemon.info channel-wifi1: unable to find active wlan device for wifi1
Jun  6 01:33:27 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:34:29 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:34:44 RuckusAP user.warn kernel: FWLOG: [122328439] WAL_DBGID_BB_WDOG_TRIGGERED ( 0x174a9577, 0x4300000a, 0x0, 0x21a8d65 )
Jun  6 01:34:44 RuckusAP user.warn kernel: FWLOG: [122328439] WAL_DBGID_STA_VDEV_XRETRY ( 0x202e0, 0x210020 )
Jun  6 01:34:44 RuckusAP user.warn kernel: FWLOG: [122328439] WAL_DBGID_STA_VDEV_XRETRY ( 0x202e4, 0xe000a )
Jun  6 01:34:44 RuckusAP user.warn kernel: FWLOG: [122328439] WAL_DBGID_STA_VDEV_XRETRY ( 0x202e8, 0x110010 )
Jun  6 01:35:38 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:36:33 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:36:36 RuckusAP user.warn kernel: FWLOG: [122443473] WAL_DBGID_BB_WDOG_TRIGGERED ( 0x174c56d1, 0x4300000a, 0x0, 0x21a90c9 )
Jun  6 01:36:36 RuckusAP user.warn kernel: FWLOG: [122443473] WAL_DBGID_STA_VDEV_XRETRY ( 0x202e0, 0x210020 )
Jun  6 01:36:36 RuckusAP user.warn kernel: FWLOG: [122443473] WAL_DBGID_STA_VDEV_XRETRY ( 0x202e4, 0xe000a )
Jun  6 01:36:36 RuckusAP user.warn kernel: FWLOG: [122443473] WAL_DBGID_STA_VDEV_XRETRY ( 0x202e8, 0x110010 )
Jun  6 01:37:31 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:38:26 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:39:32 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:40:30 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:41:39 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:41:41 RuckusAP user.warn kernel: FWLOG: [122755615] WAL_DBGID_BB_WDOG_TRIGGERED ( 0x17511a1f, 0x4300000a, 0x0, 0x21a99f6 )
Jun  6 01:41:41 RuckusAP user.warn kernel: FWLOG: [122755615] WAL_DBGID_STA_VDEV_XRETRY ( 0x202e0, 0x210020 )
Jun  6 01:41:41 RuckusAP user.warn kernel: FWLOG: [122755615] WAL_DBGID_STA_VDEV_XRETRY ( 0x202e4, 0xe000a )
Jun  6 01:41:41 RuckusAP user.warn kernel: FWLOG: [122755615] WAL_DBGID_STA_VDEV_XRETRY ( 0x202e8, 0x110010 )
Jun  6 01:42:47 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:43:43 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:44:41 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:45:36 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:46:09 RuckusAP user.warn kernel: FWLOG: [123029593] WAL_DBGID_BB_WDOG_TRIGGERED ( 0x17554859, 0x4300000a, 0x0, 0x21aa205 )
Jun  6 01:46:09 RuckusAP user.warn kernel: FWLOG: [123029593] WAL_DBGID_STA_VDEV_XRETRY ( 0x202e0, 0x210020 )
Jun  6 01:46:09 RuckusAP user.warn kernel: FWLOG: [123029593] WAL_DBGID_STA_VDEV_XRETRY ( 0x202e4, 0xe000a )
Jun  6 01:46:09 RuckusAP user.warn kernel: FWLOG: [123029593] WAL_DBGID_STA_VDEV_XRETRY ( 0x202e8, 0x110010 )
Jun  6 01:46:13 RuckusAP user.warn kernel: FWLOG: [123033569] WAL_DBGID_BB_WDOG_TRIGGERED ( 0x175557e1, 0x4300000a, 0x0, 0x21aa222 )
Jun  6 01:46:13 RuckusAP user.warn kernel: FWLOG: [123033569] WAL_DBGID_STA_VDEV_XRETRY ( 0x202e0, 0x210020 )
Jun  6 01:46:13 RuckusAP user.warn kernel: FWLOG: [123033569] WAL_DBGID_STA_VDEV_XRETRY ( 0x202e4, 0xe000a )
Jun  6 01:46:13 RuckusAP user.warn kernel: FWLOG: [123033569] WAL_DBGID_STA_VDEV_XRETRY ( 0x202e8, 0x110010 )
Jun  6 01:46:34 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:47:30 RuckusAP daemon.info hostapd: wlan0: STA 28:18:78:59:37:8d IEEE 802.11: associated
Jun  6 01:47:31 RuckusAP daemon.info hostapd: wlan0: STA 28:18:78:59:37:8d WPA: pairwise key handshake completed (RSN)
Jun  6 01:47:37 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:48:42 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:49:38 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:50:33 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Jun  6 01:51:05 RuckusAP daemon.info channel-wifi0: channelfly detects interference on radio 11g/n and switches from channel 1 to channel 10
Jun  6 01:51:08 RuckusAP user.info kernel: 0x52 0x37  0x30  0x30
Jun  6 01:51:11 RuckusAP daemon.info hostapd: wlan0: STA 94:39:e5:9b:9d:9f IEEE 802.11: associated
Jun  6 01:51:11 RuckusAP daemon.info hostapd: wlan0: STA 94:39:e5:9b:9d:9f WPA: pairwise key handshake completed (RSN)
Jun  6 01:51:31 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(97) 
Photo of Jerry Westlund

Jerry Westlund

  • 5 Posts
  • 1 Reply Like

Posted 3 years ago

  • 2
Photo of John D

John D, AlphaDog

  • 499 Posts
  • 137 Reply Likes
Can you try turning off ChannelFly (e.g. SmartSelect channel selection) and manually assign a channel on 2.4GHz and 5GHz? It seems like the client disconnecting and reconnecting happens right after a ChannelFly switch.
Photo of Jerry Westlund

Jerry Westlund

  • 5 Posts
  • 1 Reply Like
Purchased new Laptop with Windows 8.1.  Has similar issue to Surface Pro 2.  Once disconnected can't reconnect to R700.  Troubleshooting says there is a problem with the access point.  How much does it cost to get an answer to what the above messages mean.  It is hard for me to believe that it logs this message and I have to pay an additional amount to find out what it means.  It should be in the manual that comes with the unit at purchase under "troubleshooting" log messages.  I purchased this for a home office because of the number of wireless devices between three employees.  While great when connected, totally useless when you can't reconnect.
Photo of Michael Brado

Michael Brado, Official Rep

  • 2183 Posts
  • 301 Reply Likes
Jerry, I've searched our engineering bug database and cannot find a match for your set of log messages...  What version of firmware are you running?  Can you try doing a factory default (press the indented hard reset button by the Eth ports for 8 seconds before release), and does that clear up/restore your AP?
Photo of Jerry Westlund

Jerry Westlund

  • 5 Posts
  • 1 Reply Like
Device Name: RuckusAP
Device Location:
GPS Coordinates:
MAC Address: 2C:5D:93:0D:20:50 Serial Number: 961403000612
Software Version: 100.1.0.0.194 Uptime: 3 days 19 hrs 16 mins 37 secs Current Time (GMT): Tue Jun 9 22:55:08 2015

If I had access to the code I would look up the routine that appended that message to the system log file.  Then I would look to see if that message was just informational or if it was generated by an error.  It says error in the message so I assume it is an error.  Then I would look for the routine that trapped that error that generated the routine that appended it to the system log file.  Eventually I would get back to the code that determined something was wrong and started the sequence that generated the code.  I happens every minute approximately so that would be another clue to trace out.  Of course I have reset to factory defaults after upgrading to the latest firmware.  I did use the software default as the AP is in the ceiling. If the pushbutton provides a better reset than the software then I haven't done that.  I have seen other posts that indicate this release has some issues with disconnects.  I also noticed 100.2 was just released for the 710.  I assume this will be available soon for the R700 as it is listed in the manual/release notes.  When that comes out I will install and then do a factory reset with the hard reset button.  If you wanted to send me the code I'm sure I could identify the message for your bug database.  No charge.
Photo of Michael Brado

Michael Brado, Official Rep

  • 2183 Posts
  • 301 Reply Likes
Jerry, you're welcome to send your resume to our HR department, as Engineering is always looking for talented programmers!

But if you have continued to see this message after soft or hard resets, I think an RMA might be in order, as you may have a bad 5g radio.

daemon.info channel-wifi1: unable to find active wlan device for wifi1
Photo of Jerry Westlund

Jerry Westlund

  • 5 Posts
  • 1 Reply Like
Thanks,  I keep the job opportunity in mind :)
I'll watch for the update and if doesn't happen by the weekend I will hard reset.
I'm a home office with a couple employees with BYOD.  It was more than my old AP could handle.  Looked really hard to find this unit.  I'm patient, just wanted be able to detect what's happening.
Photo of Benjamin Britton

Benjamin Britton

  • 1 Post
  • 0 Reply Likes
Jerry - I had this same log issue when upgrading to 100.1.0.0.194 and ended up back at 9.8.1.0.101 to resolve the reconnection issues, but I'm still hunting for the a stable version as 9.8.1.0.101 seems to dump the clients from the 5G networks occasionally (whereas before both clients would dump).

Has anyone seen the warning: WAL_DBGID_RX_LOCAL_DROP_LARGE_MGMT ( 0xcce )?  Thats my next trace.
Photo of Michael Brado

Michael Brado, Official Rep

  • 2183 Posts
  • 301 Reply Likes
That string finds no hits in our bug database Benjamin.
Photo of Nathan Nogic

Nathan Nogic

  • 1 Post
  • 0 Reply Likes
I am seeing this issue consistently on my R500 along with constant 2.4G and 5G wireless drops on the 100.1.0.0.194 firmware. Definitely not isolated to this one device.
Photo of Jerry Westlund

Jerry Westlund

  • 5 Posts
  • 1 Reply Like
Downgraded to version 9.8.2.0.15 on June 16th.  Not 1 drop since then.  Log is completely empty.  I guess there wasn't any reason to upgrade.  Could be this version just doesn't log anything.  I going with that it's stable and works.
Photo of scurrier03

scurrier03

  • 10 Posts
  • 1 Reply Like
Jerry, I share your pain of having issues with Surface Pro (in my case Surface Pro 3) and Ruckus products.  I also had an SP2 that had issues with WiFi as well.  I think it's on Microsoft's side but not certain.  Anyway, I have an R500 and just found that Standalone AP Software 9.8.3.0.14 (All APs) firmware is available for it on the R700 (not R500!) firmware page.  The firmware zip file also has a file for R500 in it despite it not being present on the R500 page, so go figure.  Anyway, on your information I'm going to go to 9.8.3.0.14 since these maintenace releases in the 9.8 train sound like they are more stable.