Unfortunately, I don't have a correct explanation either. With DHCP problems, it must always be clarified whether the requests reach the server and whether the responses reach the client.
You write that you have seen the MAC addresses of the clients in the switch in the correct VLAN. During the controller test with DHCP IP in the client VLAN, the controller MAC address was also visible. This indicates that the controller was working correctly and the problem was in the wired network or in the DHCP server.
You then changed the controller IP and rebooted the controller and everything has worked since then. This in turn indicates that the problem was caused by the controller.
If the problem occurs again, pull a tcpdump - on the switch port where the controller is connected. Then you can see whether the controller is really sending out DHCP requests and whether the DHCP server is answering them with a reponse.
Original Message:
Sent: Jun 18, 2025 09:56 AM
From: Matteo Zaccarini
Subject: DHCP request not working in new WLAN
Hi all, sorry for the late answer:
- login to the Aruba Gateway CLI and get the output for "show user-table"
- I can see the user as authenticated
Have you checked whether the user really has the authenticated role?Yes, I can see the user as authenticated
Have you checked the logs in the DHCP server to see whether DHCP requests are being received and processed there?
I don't have access and I have asked to check: they didin't receive nothing from my testingYou can also switch the IP address to DHCP in the gateway in the client VLAN for testing purposes and check whether it can obtain an IP.I have done this, I don't have received an IP but i can see the mac address of the gateway in the mac address table.
After i changed the controller IP address (with reboot of the controller) all started working. To be sure i revert the IP to the one before and is still working.
Now is working (wlan, ssid, dhcp, splash portal)
Someone with some idea?
------------------------------
Zakka
Original Message:
Sent: Jun 14, 2025 02:50 AM
From: Waldemar Ryll
Subject: DHCP request not working in new WLAN
If the client MAC address is displayed in the correct VLAN in the switch, then the gateway has done its job successfully.
Have you checked whether the user really has the authenticated role?
Have you checked the logs in the DHCP server to see whether DHCP requests are being received and processed there?
You can also switch the IP address to DHCP in the gateway in the client VLAN for testing purposes and check whether it can obtain an IP.
------------------------------
Regards,
Waldemar
ACCX # 1377, ACEP, ACX - Network Security
If you find my answer useful, consider giving kudos and/or mark as solution
Original Message:
Sent: Jun 13, 2025 10:51 AM
From: NHN
Subject: DHCP request not working in new WLAN
login to the Aruba Gateway CLI and get the output for "show user-table"
------------------------------
Harendra | ACEX165 | ACEP | CWDP | CWSP
If you find my answer useful, consider giving kudos and/or mark it as the solution.
Original Message:
Sent: Jun 13, 2025 10:34 AM
From: Matteo Zaccarini
Subject: DHCP request not working in new WLAN
Yes, the SSID is in tunnel mode.
Yes, the Aruba Gateway is in trunk with the vlan allowed and an IP assigned, I can ping the gateway/dhcp server from the controller.
Yes, I can see the mac address that I'm using for the test.
Another step that I have tried is to set a static IP on the wireless adapter, I can see the broadcast traffic in the vlan but i can't ping the gateway from the PC. But from the Gateway I can.
------------------------------
Zakka
Original Message:
Sent: Jun 13, 2025 10:15 AM
From: harendra nishshanka
Subject: DHCP request not working in new WLAN
I assumed that you have configured the SSID in Tunnel mode
Please check and verify below
Aruba Gateway
1. The user table on the Aruba gateway to verify the connectivity
2. Aruba Gateway uplink port and make sure you have allowed the SSID vlan, and the port mode is set to trunk
Core Switch
1. The MAC address table on the specific VLAN assigned to the SSID, and make sure that the connected device is visible.
------------------------------
Harendra | ACEX165 | ACEP | CWDP | CWSP
If you find my answer useful, consider giving kudos and/or mark it as the solution.
Original Message:
Sent: Jun 12, 2025 10:50 AM
From: Matteo Zaccarini
Subject: DHCP request not working in new WLAN
Hello Airheads,
I'm trying to set up a new Aruba Gateway 9240 with 8.11.2.0, one of the first request is a SSID open where you connect and an already existing machine assign you an IP and push a captive portal.
I have configurated the vlan on the controller, created a wlan open TEST, assigned the ap group, assigned the vlan where the dhcp is (I even give the controller an IP in it and verified the connectivity), set the security as Open and the default role as authenticated. I can see the SSID, i can connect but I'm not receving an IP.
The SSID, dhcp are on the same vlan with the IP of the dhcp as default gateway, the ap are on a dedicated vlan.
Do you have some input to help?
------------------------------
Zakka
------------------------------