This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Extreme Networks
- Community List
- Legacy
- Aerohive Migrated Content
- No DCHP ACK via Wireless, all wired clients are ge...
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
No DCHP ACK via Wireless, all wired clients are getting DHCP leases but Wireless clients are not.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
06-11-2018 09:28 PM
We installed an AP121 on one location, brand new AP, it connected to the NG manager, no problem, I pushed the configuration and light was white, no problem. Then, we tried to connect to the WLAN, no IP addresses, no connection. Then another functional AP121 in another location stopped giving IP addresses, wired clients no problem, only wireless clients. Anyone having this problem?
No clients can connect via Wireless, no modification made before this started to happen. The DHCP server is on the SonicWall Router and OPNSENSE router.
Any idea what could have happened?
Thanks
Solved! Go to Solution.
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
06-12-2018 05:38 PM
Hello,
Do you have a Flat network, or are there additional vLANs that are required for the Wireless Clients?
Why I ask: since the AP can connect to Hivemanager, we know it got an IP address on it's Management vLAN and has a route to the internet. This will almost always happen if 1+2 are True OR if 1+3 are true.
1: the AP is configured for Native vLAN and Managment vLAN on vLAN 1
AND
2: the Switch-Port is either an Access port for a vLAN + a DHCP-server Listening on that vLAN
OR
3: the Switch-Port is configured for 802.1Q and there is a DHCP-server listening on the Native vLAN
Why the wireless clients do not get DHCP may be a vLAN Question. If you need additional vLANs for Wireless clients, then switches must be configured up-stream to allow those vLANs + a DHCP Server will have to be listening and configured for those vLANs.
To see the DHCP attempts and to determine if the AP is Tagging+Passing information properly, we can start with a Client Monitor for the MAC of the Client Devices failing to get IPs.
Client Monitor:
https://thehivecommunity.aerohive.com/s/article/Client-Monitor-in-NG
Then, if we can't find the solution there, we would need to look deeper at the traffic with a packet-capture.
Hope this helps, and happy to assist further,
David Souri
HiveCommunity Moderator
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
06-12-2018 08:13 PM
Thanks for your answer, the problem was VLAN tagging actually, thanks to your reply we were able to find the solution.
There was a mismatch between User Profile attribute and our Radius VLAN Tagging.
Once I setup the same attribute on the UserProfile 5 and VLAN 5 clients were able to get an DHCP offer and ack.
Many thanks for your help!
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
06-12-2018 05:38 PM
Hello,
Do you have a Flat network, or are there additional vLANs that are required for the Wireless Clients?
Why I ask: since the AP can connect to Hivemanager, we know it got an IP address on it's Management vLAN and has a route to the internet. This will almost always happen if 1+2 are True OR if 1+3 are true.
1: the AP is configured for Native vLAN and Managment vLAN on vLAN 1
AND
2: the Switch-Port is either an Access port for a vLAN + a DHCP-server Listening on that vLAN
OR
3: the Switch-Port is configured for 802.1Q and there is a DHCP-server listening on the Native vLAN
Why the wireless clients do not get DHCP may be a vLAN Question. If you need additional vLANs for Wireless clients, then switches must be configured up-stream to allow those vLANs + a DHCP Server will have to be listening and configured for those vLANs.
To see the DHCP attempts and to determine if the AP is Tagging+Passing information properly, we can start with a Client Monitor for the MAC of the Client Devices failing to get IPs.
Client Monitor:
https://thehivecommunity.aerohive.com/s/article/Client-Monitor-in-NG
Then, if we can't find the solution there, we would need to look deeper at the traffic with a packet-capture.
Hope this helps, and happy to assist further,
David Souri
HiveCommunity Moderator
