Lease renewal time

Thu Nov 6 20:23:53 UTC 2014

> Something is wrong !
> Next step is to fire up a traffic sniffer on each end and see if the
> Ack packets are getting back to the client or not. I assume the two
> devices can communicate via other protocols ? The biggest difference
> (networking wise) between the renewals (Request-Ack) and the "full
> monty" (Discover-Offer-Request-Ack, or DORA for short) is that the
> packet sin the DORA exchange are broadcast while the short renewal
> uses unicast packets.

I think there's some kind of problem with WLAN interfaces on clients, or maybe it's
just my wifi adapter. Below is a short test.

Wire interface:

===========CLIENT===========
Nov  6 21:02:54 red-viper dhclient: DHCPDISCOVER on bond0 to 255.255.255.255 port 67 interval 6
Nov  6 21:02:55 red-viper dhclient: DHCPREQUEST on bond0 to 255.255.255.255 port 67
Nov  6 21:02:55 red-viper dhclient: DHCPOFFER from 192.168.1.1
Nov  6 21:02:55 red-viper dhclient: DHCPACK from 192.168.1.1
Nov  6 21:02:55 red-viper dhclient: bound to 192.168.1.150 -- renewal in 26 seconds.
Nov  6 21:03:21 red-viper dhclient: DHCPREQUEST on bond0 to 192.168.1.1 port 67
Nov  6 21:03:21 red-viper dhclient: DHCPACK from 192.168.1.1
Nov  6 21:03:21 red-viper dhclient: bound to 192.168.1.150 -- renewal in 28 seconds.
Nov  6 21:03:49 red-viper dhclient: DHCPREQUEST on bond0 to 192.168.1.1 port 67
Nov  6 21:03:49 red-viper dhclient: DHCPACK from 192.168.1.1
Nov  6 21:03:49 red-viper dhclient: bound to 192.168.1.150 -- renewal in 29 seconds.
Nov  6 21:04:18 red-viper dhclient: DHCPREQUEST on bond0 to 192.168.1.1 port 67
Nov  6 21:04:18 red-viper dhclient: DHCPACK from 192.168.1.1
Nov  6 21:04:18 red-viper dhclient: bound to 192.168.1.150 -- renewal in 27 seconds.
===========SERVER===========
Nov  6 21:02:54 the-mountain dhcpd: DHCPDISCOVER from 3c:4a:92:00:4c:5b via br-lan
Nov  6 21:02:55 the-mountain dhcpd: DHCPOFFER on 192.168.1.150 to 3c:4a:92:00:4c:5b (red-viper) via br-lan
Nov  6 21:02:55 the-mountain dhcpd: DHCPREQUEST for 192.168.1.150 (192.168.1.1) from 3c:4a:92:00:4c:5b (red-viper) via br-lan
Nov  6 21:02:55 the-mountain dhcpd: DHCPACK on 192.168.1.150 to 3c:4a:92:00:4c:5b (red-viper) via br-lan
Nov  6 21:03:22 the-mountain dhcpd: DHCPREQUEST for 192.168.1.150 from 3c:4a:92:00:4c:5b (red-viper) via br-lan
Nov  6 21:03:22 the-mountain dhcpd: DHCPACK on 192.168.1.150 to 3c:4a:92:00:4c:5b (red-viper) via br-lan
Nov  6 21:03:49 the-mountain dhcpd: DHCPREQUEST for 192.168.1.150 from 3c:4a:92:00:4c:5b (red-viper) via br-lan
Nov  6 21:03:49 the-mountain dhcpd: DHCPACK on 192.168.1.150 to 3c:4a:92:00:4c:5b (red-viper) via br-lan
Nov  6 21:04:19 the-mountain dhcpd: DHCPREQUEST for 192.168.1.150 from 3c:4a:92:00:4c:5b (red-viper) via br-lan
Nov  6 21:04:19 the-mountain dhcpd: DHCPACK on 192.168.1.150 to 3c:4a:92:00:4c:5b (red-viper) via br-lan

And everything is just fine. Now test the wireless one:

===========CLIENT===========
Nov  6 21:12:06 red-viper dhclient: DHCPDISCOVER on wlan2 to 255.255.255.255 port 67 interval 7
Nov  6 21:12:06 red-viper dhclient: DHCPREQUEST on wlan2 to 255.255.255.255 port 67
Nov  6 21:12:06 red-viper dhclient: DHCPOFFER from 192.168.1.1
Nov  6 21:12:06 red-viper dhclient: DHCPACK from 192.168.1.1
Nov  6 21:12:06 red-viper dhclient: bound to 192.168.1.151 -- renewal in 24 seconds.
Nov  6 21:12:30 red-viper dhclient: DHCPREQUEST on wlan2 to 192.168.1.1 port 67
Nov  6 21:12:35 red-viper dhclient: DHCPREQUEST on wlan2 to 192.168.1.1 port 67
Nov  6 21:12:45 red-viper dhclient: DHCPREQUEST on wlan2 to 192.168.1.1 port 67
Nov  6 21:13:00 red-viper dhclient: DHCPREQUEST on wlan2 to 255.255.255.255 port 67
Nov  6 21:13:07 red-viper dhclient: DHCPDISCOVER on wlan2 to 255.255.255.255 port 67 interval 6
Nov  6 21:13:07 red-viper dhclient: DHCPREQUEST on wlan2 to 255.255.255.255 port 67
Nov  6 21:13:07 red-viper dhclient: DHCPOFFER from 192.168.1.1
Nov  6 21:13:07 red-viper dhclient: DHCPACK from 192.168.1.1
Nov  6 21:13:07 red-viper dhclient: bound to 192.168.1.151 -- renewal in 32 seconds.
===========SERVER===========
Nov  6 21:12:07 the-mountain dhcpd: DHCPDISCOVER from e8:de:27:1d:4c:a5 via br-lan
Nov  6 21:12:07 the-mountain dhcpd: DHCPOFFER on 192.168.1.151 to e8:de:27:1d:4c:a5 (red-viper) via br-lan
Nov  6 21:12:07 the-mountain dhcpd: DHCPREQUEST for 192.168.1.151 (192.168.1.1) from e8:de:27:1d:4c:a5 (red-viper) via br-lan
Nov  6 21:12:07 the-mountain dhcpd: DHCPACK on 192.168.1.151 to e8:de:27:1d:4c:a5 (red-viper) via br-lan
Nov  6 21:12:30 the-mountain dhcpd: DHCPREQUEST for 192.168.1.151 from e8:de:27:1d:4c:a5 (red-viper) via br-lan
Nov  6 21:12:30 the-mountain dhcpd: DHCPACK on 192.168.1.151 to e8:de:27:1d:4c:a5 (red-viper) via br-lan
Nov  6 21:12:35 the-mountain dhcpd: DHCPREQUEST for 192.168.1.151 from e8:de:27:1d:4c:a5 (red-viper) via br-lan
Nov  6 21:12:35 the-mountain dhcpd: DHCPACK on 192.168.1.151 to e8:de:27:1d:4c:a5 (red-viper) via br-lan
Nov  6 21:12:46 the-mountain dhcpd: DHCPREQUEST for 192.168.1.151 from e8:de:27:1d:4c:a5 (red-viper) via br-lan
Nov  6 21:12:46 the-mountain dhcpd: DHCPACK on 192.168.1.151 to e8:de:27:1d:4c:a5 (red-viper) via br-lan
Nov  6 21:13:01 the-mountain dhcpd: DHCPREQUEST for 192.168.1.151 from e8:de:27:1d:4c:a5 (red-viper) via br-lan
Nov  6 21:13:01 the-mountain dhcpd: DHCPACK on 192.168.1.151 to e8:de:27:1d:4c:a5 (red-viper) via br-lan
Nov  6 21:13:07 the-mountain dhcpd: DHCPDISCOVER from e8:de:27:1d:4c:a5 (red-viper) via br-lan
Nov  6 21:13:07 the-mountain dhcpd: DHCPOFFER on 192.168.1.151 to e8:de:27:1d:4c:a5 (red-viper) via br-lan
Nov  6 21:13:07 the-mountain dhcpd: DHCPREQUEST for 192.168.1.151 (192.168.1.1) from e8:de:27:1d:4c:a5 (red-viper) via br-lan
Nov  6 21:13:07 the-mountain dhcpd: DHCPACK on 192.168.1.151 to e8:de:27:1d:4c:a5 (red-viper) via br-lan

Should this happen when it comes to wifi cards?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20141106/4f51c97e/attachment.bin>