From: James Prestwood <prestwoj@gmail.com>
To: Hannes von Haugwitz <hannes@vonhaugwitz.com>
Cc: Grant Erickson <gerickson@nuovations.com>, iwd@lists.linux.dev
Subject: Re: IPv6 Privacy Extension support?
Date: Mon, 5 Aug 2024 05:44:39 -0700 [thread overview]
Message-ID: <70e5936f-c789-4f56-a275-e1b559ea27fe@gmail.com> (raw)
In-Reply-To: <20240804210103.GA25@magnesium.vonhaugwitz.com>
Hi Hannes,
On 8/4/24 2:01 PM, Hannes von Haugwitz wrote:
> On Wed, Mar 06, 2024 at 04:19:41AM -0800, James Prestwood wrote:
>> On 3/4/24 1:40 PM, Grant Erickson wrote:
>>> On Mar 4, 2024, at 11:32 AM, Hannes von Haugwitz <hannes@vonhaugwitz.com> wrote:
>>>> On Mon, Mar 04, 2024 at 04:30:27AM -0800, James Prestwood wrote:
>>>>> I'm not familiar with the privacy extensions specifically, but you can
>>>>> enable MAC address randomization which should hide the MAC for you. You can
>>>>> check the man pages for more details but in main.conf something like:
>>>>>
>>>>> [Settings]
>>>>> AddressRandomization=network
>>>> MAC address randomization hides the physical MAC address but does not
>>>> prevent device tracking (within the same network). With privacy extension
>>>> enabled, the IPv6 address is randomly regenerated every few hours.
>>>>
>>>> For more details see [RFC_4941].
>>>>
>>>> Best regards
>>>>
>>>> Hannes
>>> James:
>>>
>>> I believe it’s handled in connman with these APIs:
>>>
>>> https://git.kernel.org/pub/scm/network/connman/connman.git/tree/src/ipconfig.c#n528
>>>
>>> with the Linux kernel “use_tempaddr” sysctl setting. I assume iwd would have to replicate this infrastructure, or pull it into ELL and share it that way.
>> Hmm, if this is all that's required then shouldn't this already work if
>> Hannes is setting "use_tempaddr" externally to IWD? Of course having this
>> within an IWD profile setting would be nice, but I think there must be more
>> too it than this right?
> Is there any news about this feature request?
I was still not sure exactly what needs to be done. If the sysctl
setting is all thats needed, this is an easy feature, but you had said
setting that manually still doesn't enable the privacy extensions? Is
the issue maybe that IWD removes the wlan0 interface on startup? So
setting that sysctl setting manually, then starting IWD, is clearing it?
Is use_tempaddr still set as expected after IWD start?
Thanks,
James
>
> Best regards
>
> Hannes
next prev parent reply other threads:[~2024-08-05 12:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 14:46 IPv6 Privacy Extension support? Hannes von Haugwitz
2024-03-04 12:30 ` James Prestwood
2024-03-04 19:32 ` Hannes von Haugwitz
2024-03-04 21:40 ` Grant Erickson
2024-03-06 12:19 ` James Prestwood
2024-08-04 21:01 ` Hannes von Haugwitz
2024-08-05 12:44 ` James Prestwood [this message]
2024-08-06 17:38 ` Hannes von Haugwitz
2024-08-09 17:54 ` Hannes von Haugwitz
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=70e5936f-c789-4f56-a275-e1b559ea27fe@gmail.com \
--to=prestwoj@gmail.com \
--cc=gerickson@nuovations.com \
--cc=hannes@vonhaugwitz.com \
--cc=iwd@lists.linux.dev \
/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