public inbox for iwd@lists.linux.dev
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>, iwd@lists.linux.dev
Subject: Re: Wrong source MAC for DHCP requests with AddressRandomization=network
Date: Fri, 24 Nov 2023 11:09:34 -0600	[thread overview]
Message-ID: <c3854a08-c529-46e2-81ed-29cd4046de4f@gmail.com> (raw)
In-Reply-To: <87plzzhz4g.fsf@toke.dk>

Hi Toke,

> 
> Yup, that resolves the issue so that I can connect. However, this is the
> DHCP packets I see when moving between two networks (back and forth):
> 

Excellent.

> 
> 17:49:59.040639 1e:aa:ca:6d:0d:e0 > 92:0a:9a:27:ca:65, ethertype IPv4 (0x0800), length 342: 10.42.3.52.68 > 10.42.3.33.67: BOOTP/DHCP, Request from 1e:aa:ca:6d:0d:e0, length 300

Looking at the timestamps, are you sure this isn't a DHCP RELEASE going out to 
the old network?  Enabling DHCP client debugging might be helpful:

export IWD_DHCP_DEBUG=debug
<start iwd>

> 
> As you can see, in each case, there's an initial unicast request that

iwd should be sending a DHCP release when we start to leave the network.  Maybe 
it is being sent at the wrong time (after we queue the CMD_DISCONNECT), but it 
should never makes it out to the new AP over the air since the client is stopped 
once the disassociation is detected.

> contains the old MAC and IP. Which seems to be a bit counter productive
> if this is supposed to be a privacy feature that doesn't leak addresses
> across networks? :)

Definitely.  Can you provide more detailed logs if you still suspect this is 
happening?

Regards,
-Denis


  reply	other threads:[~2023-11-24 17:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-24 11:58 Wrong source MAC for DHCP requests with AddressRandomization=network Toke Høiland-Jørgensen
2023-11-24 16:23 ` Denis Kenzior
2023-11-24 16:53   ` Toke Høiland-Jørgensen
2023-11-24 17:09     ` Denis Kenzior [this message]
2023-11-24 17:51       ` Toke Høiland-Jørgensen
2023-11-24 19:21         ` Rhys Perry
2023-11-25 23:30           ` Denis Kenzior

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c3854a08-c529-46e2-81ed-29cd4046de4f@gmail.com \
    --to=denkenz@gmail.com \
    --cc=iwd@lists.linux.dev \
    --cc=toke@toke.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox