Martin-Éric RACINE

It doesn't explain how dhcpcd interacts with wpasupplicant. The config option is for an SSID-specific block of options, but the above Arch Linux documentation suggests that dhcpcd really is matching...

A new upstream version that supports the -M option seemingly isn't widely distributed: due to regressions in 2.11, some distributions still ship with 2.10. Anyhow, whatever seems self-evident to you...

> https://w1.fi/cgit/hostap/commit/wpa_supplicant/wpa_supplicant.c?id=2e997eece5776eca0a99d53893e343539f9f8eb2 > > I’m pretty sure there has been a release in the past 10 years. Thanks. Here's what Debian has: ``` $ sudo wpa_supplicant --help wpa_supplicant: invalid option...

> So that sounds like a Debian issue? Possibly. A quick googling shows that other distributions ship with an even more spartan list of enabled command line options. Either way,...

I still think that the manual page should say that dhcpcd will request a similarily-named wpa_supplicant configuration using wpa_supplicant's -M flag. Comments in the exit script should state that the...

Given how your above explanations make the purpose and mechanics of ssid profiles even more confusing than before for this downstream maintainer, you might wanna ponder how drastically more opaque...

Yes. The above dhcpcd.conf example should be added to the manual page, along with the explanation below it, to emphasize that it merely defines the network configuration performed on the...

Thanks That's somewhat more clear. I made the following change in Debian: ``` dhcpcd (1:10.2.2-6) experimental; urgency=medium * [control] + dhcpcd: Recommends: wpasupplicant | iwd | wireless-tools dhcpcd uses netlink's...

I'd like to return to this issue. If I understood correctly, one can make a configuration block per SSID as above, but not pass any PSK passphrase i.e. We do...

That's already a tad more clear. Lemme think of where this could go in the manual page. I'll probably have an MR at some point.