Ruckus Access Points Heartbeat lost in LAN
-
Did the clients grab the reservation? Can you not set them static on the devices?
-
I rebooted both the AP's and they picked up the reservation. That was 1.5 hours ago, so in the next 30 mins or so, we'll see if they drop again.
Strange they were needing a new IP each time?
Also, am I right in thinking IP's become available again in 24 hours if not used based on default settings?
-
Depends on your settings... But once a lease has expired, then yes it should be made available again... You can always just clear out all your old lease that might be stuck in the leases file.
As to why they were getting new IPs - because for whatever reason their request for renewal was not working, ie from your log they were asking for lease, but dhcpd was saying have no idea what that lease is "unknown" so can not renew... So client would have to do a new discover to get get an IP..
If you set your reservation, and your lease time still 2 hours.. Then they should of already renewed, right around the 1 hour mark.
-
@johnpoz said in Ruckus Access Points Heartbeat lost in LAN:
Depends on your settings... But once a lease has expired, then yes it should be made available again... You can always just clear out all your old lease that might be stuck in the leases file.
Is that done direct through the 'Edit file' options? FYI - I've not changed any of the lease time time settings.
As to why they were getting new IPs - because for whatever reason their request for renewal was not working, ie from your log they were asking for lease, but dhcpd was saying have no idea what that lease is "unknown" so can not renew... So client would have to do a new discover to get get an IP..
Hmm, strange. So is that the WAP or the router not playing nice?
If you set your reservation, and your lease time still 2 hours.. Then they should of already renewed, right around the 1 hour mark.
Here's what I'm seeing in the logs so far for the same WAP. Does it look right?
-
@WannabeMKII said in Ruckus Access Points Heartbeat lost in LAN:
Is packet capture quite straightforward, as it's not something I've done before...
Go into Diagnostic > Packet Capture.
Select LAN
Enter port number 67 or 68
Start the capture.After capturing the DHCP traffic, you can download the capture file, to examine with Wireshark.
-
No that is not right... Once you see a discover and send the offer the client should send back ack..
-
@johnpoz said in Ruckus Access Points Heartbeat lost in LAN:
No that is not right... Once you see a discover and send the offer the client should send back ack..
Here's the other WAP. Is the DHCPACK we see here what we're looking for?
-
It looks like that .4091 isn't recognizing the offers and then, when it does accept and goes through the request and ack, it's doing the discover again. First off, when it gets the ack, it shouldn't be doing anything for about 1/2 - 2/3 of the lease time, but it's doing a discover again just seconds later. That is not normal! What happens if you try with a computer? If it gets an address and holds onto it, then the problem is with the switches.
-
I've just checked a selection of other wired devices and you're right, every hour they're going through the process and that's it.
So you think it's the switches between the pfsense box and the WAP's causing the issue?
FYI - 2 hours (16:27) have passed since the IP reservations and here are the logs and no drop-off. But then as you say, it starts talking again...
-
@WannabeMKII said in Ruckus Access Points Heartbeat lost in LAN:
FYI - 2 hours (16:27) have passed since the IP reservations and here are the logs and no drop-off. But then as you say, it starts talking again...
The default lease time is 2 hours (7200 seconds). So, you should see accepts and acks about 1 - 1.5 hours after that.
The normal process, when the device doesn't have an address, is discover, offer, request and ack. Then at interval, renewing the lease with requests and acks.
-
There is something with those clients, and the way dhcpd and those clients... If you send back ack, you sure and the F should not discover again..
Those clients seemed hosed if you ask me... I would get on their forums about this behavior... Are they on the lastest firmware, etc..
Once a client sends ack, he is telling the dhcp server - hey I accepted the lease, thanks! So why is he sending discover again?
-
Many thanks for your continued help on this, much appreciated and glad we got to the bottom of it!
It's been running fine for the last few days, which is great news!
They're both running the latest firmware, but, I'm going to provide the feedback to the manufacturer to get their feedback as to why it's happening in the first place.
Many thanks once again!
