From: James Prestwood <prestwoj@gmail.com>
To: Denis Kenzior <denkenz@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH] RFC: Support full profile sharing via DPP 3rd party attributes
Date: Thu, 16 Nov 2023 07:49:06 -0800 [thread overview]
Message-ID: <73c2acb7-dcaa-4498-8eb4-4fa21923d7fd@gmail.com> (raw)
In-Reply-To: <fcb4e7bf-7947-4db0-aac7-990aff70542f@gmail.com>
Hi Denis,
On 11/16/23 07:29, Denis Kenzior wrote:
> Hi James,
>
> On 11/13/23 12:28, James Prestwood wrote:
>> If an IWD profile contains network-specific settings which are
>> required to utilize the network correctly configuring via DPP
>> will not carry over those settings to the enrollee. The DPP
>> configuration object only contains the SSID/PSK to connect and
>> anything else set in the configurators profile is not included.
>>
>> This is likely something that the majority of users will not
>> need (most networks don't need additional settings) but if the
>> network does it would be convenient for the configurator to send
>> over its exact configuration to the enrollee. This is useful for
>> an automated use case where a configuration should be consistent
>> across all devices.
>>
>> DPP allows for arbitrary 3rd party attributes in the configuration
>> object (section 4.5.2) which can be used to communicate additional
>> settings.
>>
>> The plan is to define a new object within the overall
>> configuration object who's keys are IWD profile groups and values
>> are objects containing settings for those groups:
>>
>> {
>> "ssid": "my_ssid",
>> ... main configuration object ...
>>
>> ... The IWD profile, converted to JSON ...
>> "/net/connman/iwd": {
>> "Network": {
>> "MutlicastDNS": "true"
>> },
>> "IPv4": {
>> "SendHostname": "true"
>> },
>> ... etc ...
>> }
>> }
>>
>> The "/net/connman/iwd" object could then be parsed by the enrollee
>> (potentially if the feature is enable in main.conf?) and set to
>> the profile as it is now with the passphrase/psk.
>>
>> Several profile values don't apply here like MAC/IP address
>> overrides. Mainly the settings that do matter would be:
>>
>> [IPv4].SendHostname
>
> Yeah I can see this one since this might be a network-wide DHCP server
> quirk...
To be completely honest SendHostname is all I actually needed. I was
trying to make it more generic and allow any setting but it certainly
simplifies the implementation if we just pick individual settings we want.
Thanks,
James
prev parent reply other threads:[~2023-11-16 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 18:28 [PATCH] RFC: Support full profile sharing via DPP 3rd party attributes James Prestwood
2023-11-16 15:29 ` Denis Kenzior
2023-11-16 15:49 ` James Prestwood [this message]
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=73c2acb7-dcaa-4498-8eb4-4fa21923d7fd@gmail.com \
--to=prestwoj@gmail.com \
--cc=denkenz@gmail.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