This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

New smart phone does not recieve DHCP address after WiFi authentication

FormerMember
FormerMember
Hi there,

our customer has an active wireless network. One worker recieved a new smart phone that need to be connected to the wireless network. The device is visible in the wireless protection logs, but does not recieve an IP address via DHCP. There is no output in the DHCP.

The device is listed in the WebMail unter "Wireless Clients" without IP address. Other devices work just fine.

Those are the wireless protection log entries regarding the device.

2014:05:28-15:05:47 192.168.100.64 hostapd: wlan0: AP-STA-DISCONNECTED 78:4b:87:75:6d:0a

2014:05:28-15:05:47 192.168.100.64 hostapd: wlan1: STA 78:4b:87:75:6d:0a IEEE 802.11: disassociated
2014:05:28-15:05:47 192.168.100.64 awelogger[1746]: id="4102" severity="info" sys="System" sub="WiFi" name="STA disconnected" ssid="IWLAN" ssid_id="WLAN1.0" bssid="00:1a:8c:06:2c:a1" sta="78:4b:87:75:6d:0a"
2014:05:28-15:05:48 192.168.100.64 hostapd: wlan1: STA 78:4b:87:75:6d:0a IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
2014:05:28-15:09:22 192.168.100.64 hostapd: wlan0: AP-STA-AUTH 78:4b:87:75:6d:0a0
2014:05:28-15:09:22 192.168.100.64 hostapd: wlan1: STA 78:4b:87:75:6d:0a IEEE 802.11: authenticated
2014:05:28-15:09:22 192.168.100.64 hostapd: wlan0: AP-STA-ASSOC 78:4b:87:75:6d:0a0
2014:05:28-15:09:22 192.168.100.64 hostapd: wlan1: STA 78:4b:87:75:6d:0a IEEE 802.11: associated (aid 1)
2014:05:28-15:09:22 192.168.100.64 awelogger[1746]: id="4103" severity="info" sys="System" sub="WiFi" name="STA authentication" ssid="IWLAN" ssid_id="WLAN1.0" bssid="00:1a:8c:06:2c:a1" sta="78:4b:87:75:6d:0a" status_code="0"
2014:05:28-15:09:22 192.168.100.64 awelogger[1746]: id="4104" severity="info" sys="System" sub="WiFi" name="STA association" ssid="IWLAN" ssid_id="WLAN1.0" bssid="00:1a:8c:06:2c:a1" sta="78:4b:87:75:6d:0a" status_code="0"
2014:05:28-15:09:22 192.168.100.64 hostapd: wlan0: AP-STA-CONNECTED 78:4b:87:75:6d:0a
2014:05:28-15:09:22 192.168.100.64 hostapd: wlan1: STA 78:4b:87:75:6d:0a RADIUS: starting accounting session 5384B894-000000CF
2014:05:28-15:09:22 192.168.100.64 hostapd: wlan1: STA 78:4b:87:75:6d:0a WPA: pairwise key handshake completed (RSN)
2014:05:28-15:09:22 192.168.100.64 awelogger[1746]: id="4101" severity="info" sys="System" sub="WiFi" name="STA connected" ssid="IWLAN" ssid_id="WLAN1.0" bssid="00:1a:8c:06:2c:a1" sta="78:4b:87:75:6d:0a"
2014:05:28-15:09:27 192.168.100.64 hostapd: wlan0: AP-STA-DISCONNECTED 78:4b:87:75:6d:0a
2014:05:28-15:09:27 192.168.100.64 hostapd: wlan1: STA 78:4b:87:75:6d:0a IEEE 802.11: disassociated
2014:05:28-15:09:27 192.168.100.64 awelogger[1746]: id="4102" severity="info" sys="System" sub="WiFi" name="STA disconnected" ssid="IWLAN" ssid_id="WLAN1.0" bssid="00:1a:8c:06:2c:a1" sta="78:4b:87:75:6d:0a"
2014:05:28-15:09:28 192.168.100.64 hostapd: wlan1: STA 78:4b:87:75:6d:0a IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE) 


This thread was automatically locked due to age.
Parents
  • Hi Haedrig,

    which DHCP server do you use? If it is the UTM maybe you can post the corresponding part of the dhcpd.log? The first question in this case is,
    if the dhcp request was received by the UTM/DHCP Server. 
    Is the IP Range of DHCP server large enough?

    Regards,
    Emanuel
Reply
  • Hi Haedrig,

    which DHCP server do you use? If it is the UTM maybe you can post the corresponding part of the dhcpd.log? The first question in this case is,
    if the dhcp request was received by the UTM/DHCP Server. 
    Is the IP Range of DHCP server large enough?

    Regards,
    Emanuel
Children
No Data