I have the problem with obtaining of IP address on AP clients. I have following infrastructure.
AP (WAP4410N) --- switch --- ASA --- Windows 2008 (DHCP server)
Then I connect laptop by Ethernet port to switch I can get IP address from Windows 2008 (super scope). It means that ASA is configured correctly as DHCP relay. The laptop can not get IP address from AP - WiFi. It could connect to Internet when IP address is set up manually. I installed temporary the DHCP server is the same network as AP (WAP4410N) but it is not solution for me. The AP (WAP4410N) has to use Windows server as DHCP server.
Logs from ASA
asa-1fw-mfhq# DHCPRA: relay binding found for client 5046.5d7e.acf5.
DHCPD: setting giaddr to 10.0.3.250.
dhcpd_forward_request: request from 5046.5d7e.acf5 forwarded to 10.0.1.150.
DHCPD/RA: Punt 10.0.1.150/17152 --> 10.0.3.250/17152 to CP
DHCPRA: Received a BOOTREPLY from interface 3
DHCPRA: relay binding found for client 5046.5d7e.acf5.
DHCPRA: forwarding reply to client 5046.5d7e.acf5.
DHCPRA: relay binding found for client 5046.5d7e.acf5.
DHCPD: setting giaddr to 10.0.3.250.
dhcpd_forward_request: request from 5046.5d7e.acf5 forwarded to 10.0.1.150.
DHCPD/RA: Punt 10.0.1.150/17152 --> 10.0.3.250/17152 to CP
DHCPRA: Received a BOOTREPLY from interface 3
DHCPRA: relay binding found for client 5046.5d7e.acf5.
DHCPRA: forwarding reply to client 5046.5d7e.acf5.
DHCPD: setting giaddr to 10.0.2.250.
dhcpd_forward_request: request from 801f.0200.188f forwarded to 10.0.1.150.
DHCPRA: relay binding found for client 5046.5d7e.acf5.
DHCPD: setting giaddr to 10.0.3.250.
dhcpd_forward_request: request from 5046.5d7e.acf5 forwarded to 10.0.1.150.
DHCPD/RA: Punt 10.0.1.150/17152 --> 10.0.3.250/17152 to CP
DHCPRA: Received a BOOTREPLY from interface 3
DHCPRA: relay binding found for client 5046.5d7e.acf5.
DHCPRA: forwarding reply to client 5046.5d7e.acf5.
DHCPRA: relay binding created for client f0cb.a102.bd0d.
DHCPD: setting giaddr to 10.0.2.250.
dhcpd_forward_request: request from f0cb.a102.bd0d forwarded to 10.0.1.150.
DHCPD/RA: Punt 10.0.1.150/17152 --> 10.0.2.250/17152 to CP
DHCPRA: Received a BOOTREPLY from interface 3
DHCPRA: relay binding found for client f0cb.a102.bd0d.
DHCPRA: exchange complete - relay binding deleted for client f0cb.a102.bd0d.
DHCPD: returned relay binding 10.0.2.250/f0cb.a102.bd0d to address pool.
DHCPRA: forwarding reply to client f0cb.a102.bd0d.
DHCPRA: relay binding found for client 5046.5d7e.acf5.
DHCPD: setting giaddr to 10.0.3.250.
Hi,
I know this topic is rather old, but here are my two cents. I think I found the problem, seems there is a bug in the way ACL works (Through seems to work fine on most situations).
But wait, first of all, and maybe the reason to appear this problem 'randomly': WHY I should set "Wireless Connection Control" to LOCAL to be allowed to see the wireless clients connected????? That option should be always available!
The apparent reason for DHCP not working is:
- When you activate "wireless connection control", I.E.: see who is connected.
- AND even if you check "PREVENT following MAC addresses from connecting to wireless network"
- AND you leave the MAC list empty
- AND after some.. hours?
It stops relaying DHCP requests
I have latest firmware version: 2.0.7.8
Easy solution: disable at all Wireless connection control if you don't need it.
If you connect by SSH you can see the configuracion is correct so maybe the concept of MAC table "TRUSTED stations list" is not working perfectly.
Is somebody able to verify it too?