Issues with AP130s

  • 4
  • Question
  • Updated 3 years ago
Im having a strange issue with a couple of AP130's I've setup. 

Our basic setup is two Vlans - one for internal stuff and one for customer stuff. The internal is running radius and the external one is on wpa2 authorization.

Internal network - no issues at all.

Im also seeing a lot of devices connect to our external network on vlan2, but not all devices. Many constantly authorize and then deauthorize to the network. Some get a 0.0.0.0 ip address, some just plain won't connect at all.

I pulled up the vlan probe and both plan 1 and 2 is fine. Then i pulled up the log and see some of these various errors:

015-05-31 22:16:34 info    kernel: [wifi]: wl0: wlc_ampdu_tx_send_delba: tid 0 initiator 1 reason 392015-05-31 22:16:34 info    kernel: [wifi]: wl0: wlc_ampdu_watchdog: cleaning up ini tid 0 due to no progress for 2 secs tx_in_transit 1
2015-05-31 22:16:34 info    kernel: [wifi]: wl0.0: wlc_ampdu_watchdog: 14:99:e2:c9:e2:29 in PS mode may be stuck or receiver died
2015-05-31 22:16:32 info    ah_auth: detect station(a45e:60da:2925) os(Mac OS X) via DHCP fingerprint
2015-05-31 22:16:31 info    ah_auth: detect station(f0db:f8d3:4bf6) os(Apple iOS) via DHCP fingerprint
2015-05-31 22:16:29 info    kernel: [wifi]: wl0: wlc_ampdu_recv_addba_resp: Failed. status 37 wsize 64 policy 1
2015-05-31 22:16:29 info    kernel: [wifi]: wl0: wlc_ampdu_recv_addba_resp: Failed. status 37 wsize 64 policy 1
2015-05-31 22:16:28 info    ah_auth: detect station(a45e:60da:2925) os(Mac OS X) via DHCP fingerprint
2015-05-31 22:16:27 info    kernel: [wifi]: wl0: wlc_ampdu_recv_addba_resp: Failed. status 37 wsize 64 policy 1
2015-05-31 22:16:25 info    ah_auth: detect station(a45e:60da:2925) os(Mac OS X) via DHCP fingerprint
2015-05-31 22:16:24 info    ah_auth: detect station(a45e:60da:2925) os(Mac OS X) via DHCP fingerprint
2015-05-31 22:16:23 info    ah_auth: detect station(f0db:f8d3:4bf6) os(Apple iOS) via DHCP fingerprint
2015-05-31 22:16:14 info    ah_auth: detect station(f0db:f8d3:4bf6) os(Apple iOS) via DHCP fingerprint
2015-05-31 22:16:11 info    kernel: [wifi]: get_sta_info: invalid tx rate spec 0x0 used
2015-05-31 22:16:11 info    ah_auth: Station f0db:f8d3:4bf6 ip 0.0.0.0 username n/a hostname n/a OS Apple iOS, flag = DHCP
2015-05-31 22:16:11 notice  ah_auth: Station f0db:f8d3:4bf6 is authenticated to 885b:dd0b:6264 thru SSID Humac Demo vid 2
2015-05-31 22:16:08 info    kernel: [wifi]: get_sta_info: invalid tx rate spec 0x0 used
2015-05-31 22:16:08 info    kernel: [wifi]: wl0: wlc_ampdu_recv_addba_resp: Failed. status 37 wsize 64 policy 1
2015-05-31 22:16:05 info    ah_auth: detect station(f0db:f8d3:4bf6) os(Apple iOS) via DHCP fingerprint
2015-05-31 22:15:58 info    ah_auth: detect station(b038:2913:4b3b) os(unknown) via DHCP fingerprint
2015-05-31 22:15:58 info    ah_auth: station(b038:2913:4b3b) option 55:1,3,6 no mapping os in database
2015-05-31 22:15:57 info    ah_auth: detect station(f0db:f8d3:4bf6) os(Apple iOS) via DHCP fingerprint
2015-05-31 22:15:52 info    kernel: [wifi]: wl0: wlc_ampdu_recv_addba_resp: Failed. status 37 wsize 64 policy 1
2015-05-31 22:15:51 info    kernel: [wifi]: wl0: wlc_ampdu_recv_addba_resp: Failed. status 37 wsize 64 policy 1
2015-05-31 22:15:49 info    ah_auth: detect station(f0db:f8d3:4bf6) os(Apple iOS) via DHCP fingerprint
2015-05-31 22:15:46 info    ah_auth: detect station(b038:290e:ba3d) os(unknown) via DHCP fingerprint
2015-05-31 22:15:46 info    ah_auth: station(b038:290e:ba3d) option 55:1,3,6 no mapping os in database
2015-05-31 22:15:45 info    last message repeated 2 times
2015-05-31 22:15:41 info    ah_auth: detect station(f0db:f8d3:4bf6) os(Apple iOS) via DHCP fingerprint


Im pretty stuck by now. I have the same policy running on a whole range of other devices, AP120, A121, AP330, AP230 etc. All work perfectly. Just not the two new AP130 I've setup.

To troubleshoot, ive reset the AP130's completely -  same issue. Ive tried resetting everything i could think of and I've run through all our settings once more. But as stated it works perfectly on all other AH's.

Any ideas whats behind this stange behaviour?
Photo of Jesper Dehnhardt

Jesper Dehnhardt

  • 3 Posts
  • 0 Reply Likes

Posted 3 years ago

  • 4
Photo of Knarf

Knarf

  • 18 Posts
  • 2 Reply Likes
Hey Jesper,

Have you tried running a client monitor with a client device connecting to the external on VLAN2? Also, what is providing DHCP?
Photo of Jesper Dehnhardt

Jesper Dehnhardt

  • 3 Posts
  • 0 Reply Likes
I havnt set up a client monitor on any devices. We are seeing the failure on iOS devices only. DHCP is provided by a Dell Sonicwall - currently using 27 out of 240 available dynamic leases.
Photo of Jesper Dehnhardt

Jesper Dehnhardt

  • 3 Posts
  • 0 Reply Likes
This is what im getting from the client monitor:

06/01/2015 08:51:30 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  DETAIL  (30)Rx <broadcast> probe req (rssi -62dB)06/01/2015 08:51:30 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  BASIC   (31)Tx probe resp (pwr 14dBm)
06/01/2015 08:51:30 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  BASIC   (32)Tx probe resp (pwr 14dBm)
06/01/2015 08:51:30 AM  F0DBF8D34BF6  885BDD0B6265  DK-AH-AP-ROS  DETAIL  (33)Rx <broadcast> probe req (rssi -62dB)
06/01/2015 08:51:30 AM  F0DBF8D34BF6  885BDD0B6265  DK-AH-AP-ROS  BASIC   (34)Tx probe resp (pwr 14dBm)
06/01/2015 08:51:30 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  BASIC   (35)Tx probe resp (pwr 14dBm)
06/01/2015 08:51:31 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  BASIC   (36)Rx auth <open> (frame 1, rssi -55dB)
06/01/2015 08:51:31 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  BASIC   (37)Tx auth <open> (frame 2, status 0, pwr 14dBm)
06/01/2015 08:51:31 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  BASIC   (38)Rx assoc req (rssi -55dB)
06/01/2015 08:51:31 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  BASIC   (39)Tx assoc resp <accept> (status 0, pwr 14dBm)
06/01/2015 08:51:31 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (40)WPA-PSK auth is starting (at if=wifi1.1)
06/01/2015 08:51:31 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (41)Sending 1/4 msg of 4-Way Handshake (at if=wifi1.1)
06/01/2015 08:51:31 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (42)Received 2/4 msg of 4-Way Handshake (at if=wifi1.1)
06/01/2015 08:51:31 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (43)Sending 3/4 msg of 4-Way Handshake (at if=wifi1.1)
06/01/2015 08:51:31 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (44)Received 4/4 msg of 4-Way Handshake (at if=wifi1.1)
06/01/2015 08:51:31 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (45)PTK is set (at if=wifi1.1)
06/01/2015 08:51:31 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  BASIC   (46)Authentication is successfully finished (at if=wifi1.1)
06/01/2015 08:51:31 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (47)station sent out DHCP DISCOVER message
06/01/2015 08:51:31 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (48)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:31 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (49)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:31 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (50)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:31 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (51)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:33 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (52)station sent out DHCP DISCOVER message
06/01/2015 08:51:33 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (53)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:33 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (54)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:33 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (55)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:33 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (56)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:35 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (57)station sent out DHCP DISCOVER message
06/01/2015 08:51:35 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (58)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:35 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (59)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:35 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (60)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:35 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (61)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:39 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (62)station sent out DHCP DISCOVER message
06/01/2015 08:51:39 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (63)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:39 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (64)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:39 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (65)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:39 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (66)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:48 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (67)station sent out DHCP DISCOVER message
06/01/2015 08:51:48 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (68)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:48 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (69)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:48 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (70)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:48 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (71)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:56 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (72)station sent out DHCP DISCOVER message
06/01/2015 08:51:57 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (73)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:57 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (74)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:57 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (75)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:57 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (76)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:52:05 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (77)station sent out DHCP DISCOVER message
06/01/2015 08:52:05 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (78)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:52:05 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (79)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:52:05 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (80)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:52:05 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (81)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:52:13 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (82)station sent out DHCP DISCOVER message
06/01/2015 08:52:13 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (83)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:52:13 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (84)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:52:13 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (85)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:52:13 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (86)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:52:22 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (87)station sent out DHCP DISCOVER message
06/01/2015 08:52:22 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (88)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:52:22 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (89)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:52:22 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (90)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:52:22 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (91)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:52:30 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (92)station sent out DHCP DISCOVER message
06/01/2015 08:52:30 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (93)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:52:30 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (94)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:52:30 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (95)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:52:30 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (96)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:52:31 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (97)Rx disassoc (reason 8 <assoc-leave>, rssi -55dB)
06/01/2015 08:52:31 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (98)Tx disassoc (reason 7 <not-associated>, pwr 14dBm)
06/01/2015 08:52:31 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (99)Rx deauth (reason 6 <not-authed>, rssi -55dB)
06/01/2015 08:52:31 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  BASIC   (100)Sta(at if=wifi1.1) is de-authenticated because of notification of driver
06/01/2015 08:52:31 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  BASIC   (101)Sta(at if=wifi1.1) is de-authenticated because of notification of driver
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
Based on the repeated pattern of:

06/01/2015 08:51:31 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (47)station sent out DHCP DISCOVER message
06/01/2015 08:51:31 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (48)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:31 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (49)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:31 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (50)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:31 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (51)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:33 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (52)station sent out DHCP DISCOVER message
06/01/2015 08:51:33 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (53)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:33 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (54)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:33 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (55)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:33 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (56)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:35 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (57)station sent out DHCP DISCOVER message
06/01/2015 08:51:35 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (58)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:35 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (59)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:35 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (60)DHCP server sent out DHCP OFFER message to station
06/01/2015 08:51:35 AM  F0DBF8D34BF6  885BDD0B6264  DK-AH-AP-ROS  INFO    (61)DHCP server sent out DHCP OFFER message to station

... I'd certainly advise you to look in detail at what DHCP is getting up to with a packet capture.
Photo of BJ

BJ, Champ

  • 374 Posts
  • 45 Reply Likes
Jesper,
I would follow Nick's advice. As you continue to troubleshoot with client monitor, I would also suggest you check the "filter probes" box to streamline the output.

Best,
BJ 
Photo of Paul Finlay

Paul Finlay

  • 2 Posts
  • 1 Reply Like
We are seeing this exact behavior on two sites running AP130s on 6.5r1. Did you discover what the issue was?
Photo of Crowdie

Crowdie, Champ

  • 972 Posts
  • 272 Reply Likes
I had an Aruba site where the clients were doing almost exactly the same thing.  The DHCP source was the customer's LAN firewall so I enabled a Windows Server DHCP source and the issue disappeared.
Photo of John Fielding

John Fielding

  • 12 Posts
  • 0 Reply Likes
Hi Guys,
Don't want to hijack this thread but I have the exact same problem on five sites all using AP130's.
Has anyone made any progress on this?

I have tried replacing the in situ Windows2012 DHCP Server with a MacBook Pro running DHCP. Result was that all the apple devices successfully obtained an IP address after what appeared to be a long delay but the Windows clients appeared to go into a "sulking" state and start broadcasting a 169.x.x.x address. I then isolated the access point on a separate poe switch with the MBP DHCP, mirrored a port, put wire shark on the mirrored port and repeated the exercise. Same result apple devices obtained IP address, albeit that they took their sweet time to do so, and the windows client went back into the "sulk" state. I have captured the resultant wire shark trace if anyone wants to have a look at it.

I suppose this raises a few questions...
Is this an something that others have/are experiencing on AP130's?
Is this because multicast packets are being discarded by the access point?
Is there a way around this issue rather than going into a de-authing/rebooting frenzy!!
Photo of Knarf

Knarf

  • 18 Posts
  • 2 Reply Likes
Is this an something that others have/are experiencing on AP130's?

On HiveOS 6.5r1, yes. If you are on that HiveOS version, I would strongly advise upgrading to 6.5r3 or 6.6r2

Is this because multicast packets are being discarded by the access point?

No.

Is there a way around this issue rather than going into a de-authing/rebooting frenzy!!

Upgrading the HiveOS.
Photo of John Fielding

John Fielding

  • 12 Posts
  • 0 Reply Likes
Nice one. Will try this and get back to you.
Photo of John Fielding

John Fielding

  • 12 Posts
  • 0 Reply Likes
That looks like it has done the trick. Early days but client devices appear to be connecting and picking up an IP address.
Photo of Splif in

Splif in

  • 1 Post
  • 0 Reply Likes
Hey John,

How has everything gone so far?
Photo of John Fielding

John Fielding

  • 12 Posts
  • 0 Reply Likes
Looks like the the move from 6.5r1 has done the trick. Client devices are now "seeing" the DHCP offer and responding and ultimately obtaining an IP address.
Photo of Edwin Boesten

Edwin Boesten

  • 3 Posts
  • 0 Reply Likes
I had the same problem running 6.5r3, MBP running osx no DHCP IP, (same) MBP running windows 10 no problem. Upgraded to 6.6r2 and no problem sofar