Dhcpd takes ~30 seconds to hand out lease on wireless interfaces



  • I've got several WRAP boards with an OPT1 interface running as an access point.  The DHCP server is bound to that interface.  There are no firewall rules on OPT1 other than an "allow all".  All devices are running RC2.

    Wireless clients can connect to the AP running on OPT1 and get an IP automatically, but it takes about 30 seconds for them to get the lease.  In fact, it takes so long that Windows times out about a second before a lease is finally given.

    Has anyone encountered similar behavior with DHCPD on a wireless interface?  Any ideas how I could speed that up?

    Thanks!



  • Haven't seen that on my wraps with cm9. I'm connecting with clients using intel abg and atheros abg cards and running windows xp. Do you see anything special in the systemlogs? Client requesting lease and pfSense not answering or whatever?



  • I've got similar if not identical hardware on both ends…here's the DHCP log entry for one such instance:

    Aug 24 16:45:57 dhcpd: DHCPDISCOVER from 00:90:4b:6b:12:b0 (Dell_5100) via ath1
    Aug 24 16:45:57 dhcpd: DHCPOFFER on 192.168.213.197 to 00:90:4b:6b:12:b0 (Dell_5100) via ath1
    Aug 24 16:46:53 dhcpd: DHCPDISCOVER from 00:90:4b:6b:12:b0 (Dell_5100) via ath1
    Aug 24 16:46:53 dhcpd: DHCPOFFER on 192.168.213.197 to 00:90:4b:6b:12:b0 (Dell_5100) via ath1
    Aug 24 16:46:56 dhcpd: DHCPDISCOVER from 00:90:4b:6b:12:b0 (Dell_5100) via ath1
    Aug 24 16:46:56 dhcpd: DHCPOFFER on 192.168.213.197 to 00:90:4b:6b:12:b0 (Dell_5100) via ath1
    Aug 24 16:46:56 dhcpd: DHCPREQUEST for 192.168.213.197 (192.168.213.129) from 00:90:4b:6b:12:b0 (Dell_5100) via ath1
    Aug 24 16:46:56 dhcpd: DHCPACK on 192.168.213.197 to 00:90:4b:6b:12:b0 (Dell_5100) via ath1
    Aug 24 16:46:58 dhcpd: DHCPINFORM from 192.168.213.197 via ath1
    Aug 24 16:46:58 dhcpd: DHCPACK to 192.168.213.197
    Aug 24 16:47:01 dhcpd: DHCPINFORM from 192.168.213.197 via ath1
    Aug 24 16:47:01 dhcpd: DHCPACK to 192.168.213.197



  • @mastermindpro:

    Aug 24 16:45:57 dhcpd: DHCPDISCOVER from 00:90:4b:6b:12:b0 (Dell_5100) via ath1
    Aug 24 16:45:57 dhcpd: DHCPOFFER on 192.168.213.197 to 00:90:4b:6b:12:b0 (Dell_5100) via ath1

    This first OFFER from pFSense was never received by the Dell
    The Dell retries 56 secondes (??) later… (please note that we can't see DHCPDISCOVERS from the Dell that de pFsense box doesn't receive…)

    Aug 24 16:46:53 dhcpd: DHCPDISCOVER from 00:90:4b:6b:12:b0 (Dell_5100) via ath1
    Aug 24 16:46:53 dhcpd: DHCPOFFER on 192.168.213.197 to 00:90:4b:6b:12:b0 (Dell_5100) via ath1

    This second one is also lost in space

    The Dell retries 3 secondes later…

    Aug 24 16:46:56 dhcpd: DHCPDISCOVER from 00:90:4b:6b:12:b0 (Dell_5100) via ath1
    Aug 24 16:46:56 dhcpd: DHCPOFFER on 192.168.213.197 to 00:90:4b:6b:12:b0 (Dell_5100) via ath1

    This DHCPOFFER will be received by the Dell, so the sequence continues

    Aug 24 16:46:56 dhcpd: DHCPREQUEST for 192.168.213.197 (192.168.213.129) from 00:90:4b:6b:12:b0 (Dell_5100) via ath1
    Aug 24 16:46:56 dhcpd: DHCPACK on 192.168.213.197 to 00:90:4b:6b:12:b0 (Dell_5100) via ath1
    Aug 24 16:46:58 dhcpd: DHCPINFORM from 192.168.213.197 via ath1
    Aug 24 16:46:58 dhcpd: DHCPACK to 192.168.213.197

    The ACK to acknowledge the INFORM Dell won't be received

    Aug 24 16:47:01 dhcpd: DHCPINFORM from 192.168.213.197 via ath1
    Aug 24 16:47:01 dhcpd: DHCPACK to 192.168.213.197

    This ACK will be received by the Dell.

    Is this a radio (WiFi) connection ? It isn't in a good shape…. Note that when the radio signal goes flat (the Interface will be reset - like a cable-disconnect), the IP will be re-negociated.
    I would point my fingeer into the direction off the Wifi part of your network.

    Try running a Dell <-> pFsense network cable connection to exclude other issues.



  • I would have thought that, too, but I've tried different radios in the AP, different client devices and radios, short ranges between AP and client, different antenna's on the AP's, different AP's in different locations all together… you get the picture.

    Once the client device gets an IP, it has NO trouble communicating with the AP.  There are no odd timeouts, latency problems, signal fade, or throughput problems.  It just seems odd to me that the behavior is this way for about 6 AP's in different locations.  It's consistent, too.



  • 6 AP's in different locations ?

    They're not in the neighbourhood, and sharing/overlapping the same channels, are they ?

    Load this one : http://netstumbler.com/ and have a hunt down.


Locked