Strange renew unicast - help needed

[Hunter Fuller]

Well this is starting to become off topic, but if you can try to swap
out the client or the AP for a different brand entirely, you could
narrow it down that way.

In any case, glad you were able to narrow it down a bit.

--
Hunter Fuller
Network Engineer
VBRH M-9B
+1 256 824 5331

Office of Information Technology
The University of Alabama in Huntsville
Systems and Infrastructure

I am part of the UAH Safe Zone LGBTQIA support network:
http://www.uah.edu/student-affairs/safe-zone


On Thu, Jul 24, 2014 at 5:54 PM, Nikolay P <nikolay.p at cos.flag.org> wrote:
> ----- "Peter Rathlev" <peter at rathlev.dk> wrote:
>
>> Have you tried seeing what the client actually sends with e.g.
>> tcpdump
>> running at the time of renew? Just to make sure it's not some
>> middlebox
>> that clears CIADDR or something like that. Something that might
>> normally
>> insert option 82 or the like.
>>
>
> Thank you Peter and Hunter.
>
> The client is innocent. I used tcpdump and Wireshark to find that client generates valid unicast renew with CIADDR value set. So now I need to find what device modifies the request - Wi-Fi bridge or access point. To achieve this I need to sniff and decrypt Wi-Fi traffic.
>
>
>
>> --
>> Peter
>>
>> _______________________________________________
>> dhcp-users mailing list
>> dhcp-users at lists.isc.org
>> https://lists.isc.org/mailman/listinfo/dhcp-users
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users