Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
On Du, 12 iul 20, 03:56:57, Marco d'Itri wrote: > On Jul 11, Jonas Smedegaard wrote: > > > > (Way more people should switch from wpa_supplicant to iwd.) > > > > Difficult when network-manager depends (not recommends) wpa-supplicant: > > https://bugs.debian.org/919619 > How to switch to iwd: > > apt install iwd > cat << END > /etc/NetworkManager/conf.d/iwd.conf > [device] > wifi.backend=iwd > END > systemctl restart NetworkManager At least for me, on buster, it was also necessary to stop wpa_supplicant.service before restarting Network Manager. I'm guessing the wpa_supplicant service should also be 'disable'd in order to prevent it from starting at next reboot (didn't test, I disabled it anyway). Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
Quoting Marc Haber (2020-07-14 16:05:28) > On Sun, 12 Jul 2020 03:56:57 +0200, Marco d'Itri wrote: > >On Jul 11, Jonas Smedegaard wrote: > > > >> > (Way more people should switch from wpa_supplicant to iwd.) > >> > >> Difficult when network-manager depends (not recommends) wpa-supplicant: > >> https://bugs.debian.org/919619 > >How to switch to iwd: > > > >apt install iwd > >cat << END > /etc/NetworkManager/conf.d/iwd.conf > >[device] > >wifi.backend=iwd > >END > >systemctl restart NetworkManager > > Does iwd have a clickable frontend like for GNOME or KDE? Yes, via connman (connman-gtk, connman-ui, cmst), or via network-manager (network-manager-gnome, kylin-nm, nm-tray, plasma-nm). Support in network-manager is known to be suboptimal. I am unaware of the quality for of connman integration. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
On Sun, 12 Jul 2020 03:56:57 +0200, Marco d'Itri wrote: >On Jul 11, Jonas Smedegaard wrote: > >> > (Way more people should switch from wpa_supplicant to iwd.) >> >> Difficult when network-manager depends (not recommends) wpa-supplicant: >> https://bugs.debian.org/919619 >How to switch to iwd: > >apt install iwd >cat << END > /etc/NetworkManager/conf.d/iwd.conf >[device] >wifi.backend=iwd >END >systemctl restart NetworkManager Does iwd have a clickable frontend like for GNOME or KDE? Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber | " Questions are the | Mailadresse im Header Mannheim, Germany | Beginning of Wisdom " | Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834
Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
Quoting Russell Stuart (2020-07-13 00:16:01) > On Sat, 2020-07-11 at 22:12 -0400, The Wanderer wrote: > > I don't run either systemd or NetworkManager, and I'm not currently > > interested in changing either of those things, but I am interested > > in trying out an alternative to wpa_supplicant. Is there an > > appropriate similar procedure for such an environment, or would I > > have to experiment and play around trying to get things to work? > > I don't use network manager, so I'm in a similar position. > > From what I can see iwd lacks two features of wpa_supplicant. > > Firstly, there doesn't seem to be a way to attach iwd to a particular > wireless interface. Iwctl doesn't provide one, and I don't see any > other way to tell it. Most people have just one wireless interface so > it may not be a huge issue but it is an impedance miss-match with > things like ifupdown that are focused on interfaces. Maybe that's the > problem with network manager too. > > Secondly, it doesn't support wpa_supplicant's priorities. I use them > a fair bit. For example, I tell wpa_supplicant to favour my phone > WiFi hotspot over others, so if I have a connectivity issue I can just > turn it on. That said, I guess I could just use iwctl to manually > connect to the phone. Generally, IWD by design aims at being lightweight, which implies leaving high-level management to systemd-networkd (the default) or Network-Manager or connman or ifupdown or... The features you describe seems indeed not support by IWD currently: I suggest filing bugreports for IWD upstream developers. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
Quoting Luca Capello (2020-07-14 13:44:17) > Hi there, > > On Sun, 12 Jul 2020 19:15:47 +, Jeremy Stanley wrote: > > On 2020-07-12 20:35:56 +0200 (+0200), Jonas Smedegaard wrote: > > [...] > > > What is (unusual but) usable, however, is to *not* use Network > > > Manager for wifi, but use IWD+systemd or IWD standalone for wifi, > > > and use Network Manager to manage _other_ network components. > > > > > > In such unusual-but-real setup, wpa-supplicant would be dead > > > weight. Lightweight, arguably, but a daemon and therefore > > > additional risk of hair-pulling confusions: If wpa-supplicant > > > daemon is running, IWD fails to work. > > [...] > > > On Debian you can only remove the wpa-supplicant if you also > > > remove network-manager - which I find is an unnecessary tight > > > coupling. > > [...] > > > > Worth considering is that it still may in fact not be *too* unusual > > to have systems with no wireless network interface at all. > > FWIW, and without defending NetworkManager, wpa_supplicant is *not* > only for wireless networks, but it could be needed for other networks > as well (e.g. because of 802.1x). IWD optionally supports wired 802.1x networing as well, but seemingly that feature is currently not enabled. If encourage anyone reading this with access and skills to test wired 802.1x networing to file a wishlist request against iwd to pass configure option "--enable-wired" - and then help test that it works. Similarly, IWD optionally supports linking with ofono, for people interested in using it e.g. on phones. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
Hi there, On Sun, 12 Jul 2020 19:15:47 +, Jeremy Stanley wrote: > On 2020-07-12 20:35:56 +0200 (+0200), Jonas Smedegaard wrote: > [...] > > What is (unusual but) usable, however, is to *not* use Network > > Manager for wifi, but use IWD+systemd or IWD standalone for wifi, > > and use Network Manager to manage _other_ network components. > > > > In such unusual-but-real setup, wpa-supplicant would be dead > > weight. Lightweight, arguably, but a daemon and therefore > > additional risk of hair-pulling confusions: If wpa-supplicant > > daemon is running, IWD fails to work. > [...] > > On Debian you can only remove the wpa-supplicant if you also > > remove network-manager - which I find is an unnecessary tight > > coupling. > [...] > > Worth considering is that it still may in fact not be *too* unusual > to have systems with no wireless network interface at all. FWIW, and without defending NetworkManager, wpa_supplicant is *not* only for wireless networks, but it could be needed for other networks as well (e.g. because of 802.1x). Thx, bye, Gismo / Luca signature.asc Description: PGP signature
Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
On Sat, 2020-07-11 at 22:12 -0400, The Wanderer wrote: > I don't run either systemd or NetworkManager, and I'm not currently > interested in changing either of those things, but I am interested in > trying out an alternative to wpa_supplicant. Is there an appropriate > similar procedure for such an environment, or would I have to > experiment and play around trying to get things to work? I don't use network manager, so I'm in a similar position. From what I can see iwd lacks two features of wpa_supplicant. Firstly, there doesn't seem to be a way to attach iwd to a particular wireless interface. Iwctl doesn't provide one, and I don't see any other way to tell it. Most people have just one wireless interface so it may not be a huge issue but it is an impedance miss-match with things like ifupdown that are focused on interfaces. Maybe that's the problem with network manager too. Secondly, it doesn't support wpa_supplicant's priorities. I use them a fair bit. For example, I tell wpa_supplicant to favour my phone WiFi hotspot over others, so if I have a connectivity issue I can just turn it on. That said, I guess I could just use iwctl to manually connect to the phone. signature.asc Description: This is a digitally signed message part
Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
On 2020-07-12 20:35:56 +0200 (+0200), Jonas Smedegaard wrote: [...] > What is (unusual but) usable, however, is to *not* use Network > Manager for wifi, but use IWD+systemd or IWD standalone for wifi, > and use Network Manager to manage _other_ network components. > > In such unusual-but-real setup, wpa-supplicant would be dead > weight. Lightweight, arguably, but a daemon and therefore > additional risk of hair-pulling confusions: If wpa-supplicant > daemon is running, IWD fails to work. [...] > On Debian you can only remove the wpa-supplicant if you also > remove network-manager - which I find is an unnecessary tight > coupling. [...] Worth considering is that it still may in fact not be *too* unusual to have systems with no wireless network interface at all. I have quite a few in my possession running current releases of Debian. Granted I've been eschewing NM on them in favor of ifupdown for simplicity, but I could foresee wanting to install it on them and having zero use for either wpa-supplicant or iwd. I've actually grown quite fond of nmcli, once NM mostly got over its (lengthy) rough patch. -- Jeremy Stanley signature.asc Description: PGP signature
Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
Quoting Andrey Rahmatullin (2020-07-12 20:00:23) > On Sun, Jul 12, 2020 at 08:29:08PM +0300, Andrei POPESCU wrote: > > > Network-Manager needing wpa-supplicant in _most_ situations is a reason > > > to _recommend_ it not a reason to _depend_ on it, per Debian Policy! > > > > If Network Manager needs to depend on the wireless component, that could > > probably be: > > > > Depends: wpasupplicant | iwd > As discussed in the bug report linked earlier, this can only work if NM > supports iwd by default, which it currently doesn't and apparently isn't > going to. Yes: Network Manager needs a _specific_ wireless component for _specific_ network management tasks. It would therefore be wrong for network-manager do declare a fallback dependency on iwd because network-manager cannot (reliably or at all) use iwd the same way as it uses wpa-supplicant. What is (unusual¹ but) usable, however, is to *not* use Network Manager for wifi, but use IWD+systemd or IWD standalone for wifi, and use Network Manager to manage _other_ network components. In such unusual-but-real setup, wpa-supplicant would be dead weight. Lightweight, arguably, but a daemon and therefore additional risk of hair-pulling confusions: If wpa-supplicant daemon is running, IWD fails to work. Simpler if possible to avoid having wpa-supplicant installed on systems where wpa-supplicant is never used anyway: On Debian² you can only remove the wpa-supplicant if you also remove network-manager - which I find is an unnecessary tight coupling. - Jonas ¹ Debian Policy § 7.2 says that packages needed "in all but unusual installations" should be _recommended_ not depended on. ² Using equivs is not Debian but a slight fork of Debian. -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
On Sun, Jul 12, 2020 at 08:29:08PM +0300, Andrei POPESCU wrote: > > Network-Manager needing wpa-supplicant in _most_ situations is a reason > > to _recommend_ it not a reason to _depend_ on it, per Debian Policy! > > If Network Manager needs to depend on the wireless component, that could > probably be: > > Depends: wpasupplicant | iwd As discussed in the bug report linked earlier, this can only work if NM supports iwd by default, which it currently doesn't and apparently isn't going to. -- WBR, wRAR signature.asc Description: PGP signature
Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
On Du, 12 iul 20, 13:33:13, Jonas Smedegaard wrote: > > Network-Manager needing wpa-supplicant in _most_ situations is a reason > to _recommend_ it not a reason to _depend_ on it, per Debian Policy! If Network Manager needs to depend on the wireless component, that could probably be: Depends: wpasupplicant | iwd > It could be even simpler by providing a package with a config snippet > for network-manager. +1 Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
Quoting Andrey Rahmatullin (2020-07-12 16:27:16) > On Sun, Jul 12, 2020 at 01:07:37PM +0200, Jonas Smedegaard wrote: > > How to use iwd without NetworkManager or systemd: > > > > apt install iwd resolvconf > > cat << END > /etc/NetworkManager/conf.d/iwd.conf > "without NetworkManager" yet "/etc/NetworkManager/conf.d"? What will read > this config? Whoops, copy-paste error: Should be /etc/iwd/main.conf Thanks for spotting it, Andrey! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
On Sun, Jul 12, 2020 at 01:07:37PM +0200, Jonas Smedegaard wrote: > How to use iwd without NetworkManager or systemd: > > apt install iwd resolvconf > cat << END > /etc/NetworkManager/conf.d/iwd.conf "without NetworkManager" yet "/etc/NetworkManager/conf.d"? What will read this config? -- WBR, wRAR signature.asc Description: PGP signature
Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
Quoting Andrey Rahmatullin (2020-07-12 09:34:32) > On Sun, Jul 12, 2020 at 02:02:50AM +0200, Jonas Smedegaard wrote: > > > > Difficult when network-manager depends (not recommends) wpa-supplicant: > > > > https://bugs.debian.org/919619 > > > That Depends is not a problem. > > > > Yes a problem, but not a unsurmountable one: You can... > > > > a) pollute your Debian system using equivs, or > > > > b) install the dependency but then disable the daemon > You still need manual action to use iwd, so disabling wpa-supplicant is > just another command. Yes, iwd requires configuration. We should _minimize_ the need for configuration: iwd needing configuration of NetworkManager is no reason to _depend_ on wpa-supplicant. Network-Manager needing wpa-supplicant in _most_ situations is a reason to _recommend_ it not a reason to _depend_ on it, per Debian Policy! Current minimal fresh installation with network-manager and iwd: 1) apt install network-manager iwd 2) Configure Network-Manager to use iwd 3) Stop wpa-supplicant 4) Disable wpa-supplicant 5) Restart iwd 6) Restart network-manager This would be simpler if network-manager followed Debian Policy in acknowledging that wpa-supplicant is not *ALWAYS* needed, by recommending not depending on it: 1) apt install network-manager iwd wpa-supplicant- 2) Configure Network-Manager to use iwd 3) Restart network-manager It could be even simpler by providing a package with a config snippet for network-manager. It *cannot* be much simpler with a helper pacakge while network-manager depends on wpa-supplicant, because such helper package would then need to Provide: wpa-supplicant which is not Policy compliant, and such package could therefore not be part of Debian. Using equivs could not be part of Debian. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
Quoting Marco d'Itri (2020-07-12 03:56:57) > On Jul 11, Jonas Smedegaard wrote: > > > > (Way more people should switch from wpa_supplicant to iwd.) > > > > Difficult when network-manager depends (not recommends) wpa-supplicant: > > https://bugs.debian.org/919619 > How to switch to iwd: > > apt install iwd > cat << END > /etc/NetworkManager/conf.d/iwd.conf > [device] > wifi.backend=iwd > END > systemctl restart NetworkManager Above is not enough - also needs either disabling the wpa-supplicant daemon or force-avoid it e.g. using equivs. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
Quoting The Wanderer (2020-07-12 04:12:54) > On 2020-07-11 at 21:56, Marco d'Itri wrote: > > > On Jul 11, Jonas Smedegaard wrote: > > > >>> (Way more people should switch from wpa_supplicant to iwd.) > >> > >> Difficult when network-manager depends (not recommends) wpa-supplicant: > >> https://bugs.debian.org/919619 > > > > How to switch to iwd: > > > > apt install iwd > > cat << END > /etc/NetworkManager/conf.d/iwd.conf > > [device] > > wifi.backend=iwd > > END > > systemctl restart NetworkManager > > I don't run either systemd or NetworkManager, and I'm not currently > interested in changing either of those things, but I am interested in > trying out an alternative to wpa_supplicant. Is there an appropriate > similar procedure for such an environment, or would I have to experiment > and play around trying to get things to work? > > I also have quite a few network definitions in wpa_supplicant.conf, and > I wouldn't want to have to re-enter them manually into a new system if I > could avoid it. Is there a migration procedure, other convenient way to > bring those settings across into iwd? > > (I'm not at the computer involved at the moment, so I can't easily check > things to see whether any of the answers might be quickly obvious.) How to use iwd without NetworkManager or systemd: apt install iwd resolvconf cat << END > /etc/NetworkManager/conf.d/iwd.conf [General] EnableNetworkConfiguration = true [Network] NameResolvingService = resolvconf END You then also need to start iwd as a daemon somehow - and consider filing patches to support those: Debian package provides hooks for systemd but not sysv or runit. Debian package includes hooks for connman, but I am not sure which iwd or connman configuration changes that involves. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
On Sun, Jul 12, 2020 at 12:34:32PM +0500, Andrey Rahmatullin wrote: > On Sun, Jul 12, 2020 at 02:02:50AM +0200, Jonas Smedegaard wrote: > > > > Difficult when network-manager depends (not recommends) wpa-supplicant: > > > > https://bugs.debian.org/919619 > > > That Depends is not a problem. > > > > Yes a problem, but not a unsurmountable one: You can... > > > > a) pollute your Debian system using equivs, or > > > > b) install the dependency but then disable the daemon > You still need manual action to use iwd, so disabling wpa-supplicant is > just another command. > > > > -- > WBR, wRAR FWIW I think that Andrey is happy with a disabled wpa-supplicant and that Jonas is right for asking wpa-supplicant not required by network-manager. Groeten Geert Stappers -- Silence is hard to parse
Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
On Sun, Jul 12, 2020 at 02:02:50AM +0200, Jonas Smedegaard wrote: > > > Difficult when network-manager depends (not recommends) wpa-supplicant: > > > https://bugs.debian.org/919619 > > That Depends is not a problem. > > Yes a problem, but not a unsurmountable one: You can... > > a) pollute your Debian system using equivs, or > > b) install the dependency but then disable the daemon You still need manual action to use iwd, so disabling wpa-supplicant is just another command. -- WBR, wRAR signature.asc Description: PGP signature
Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
On 2020-07-11 at 21:56, Marco d'Itri wrote: > On Jul 11, Jonas Smedegaard wrote: > >>> (Way more people should switch from wpa_supplicant to iwd.) >> >> Difficult when network-manager depends (not recommends) wpa-supplicant: >> https://bugs.debian.org/919619 > > How to switch to iwd: > > apt install iwd > cat << END > /etc/NetworkManager/conf.d/iwd.conf > [device] > wifi.backend=iwd > END > systemctl restart NetworkManager I don't run either systemd or NetworkManager, and I'm not currently interested in changing either of those things, but I am interested in trying out an alternative to wpa_supplicant. Is there an appropriate similar procedure for such an environment, or would I have to experiment and play around trying to get things to work? I also have quite a few network definitions in wpa_supplicant.conf, and I wouldn't want to have to re-enter them manually into a new system if I could avoid it. Is there a migration procedure, other convenient way to bring those settings across into iwd? (I'm not at the computer involved at the moment, so I can't easily check things to see whether any of the answers might be quickly obvious.) -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
On Jul 11, Jonas Smedegaard wrote: > > (Way more people should switch from wpa_supplicant to iwd.) > > Difficult when network-manager depends (not recommends) wpa-supplicant: > https://bugs.debian.org/919619 How to switch to iwd: apt install iwd cat << END > /etc/NetworkManager/conf.d/iwd.conf [device] wifi.backend=iwd END systemctl restart NetworkManager -- ciao, Marco signature.asc Description: PGP signature
Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
Quoting Andrey Rahmatullin (2020-07-11 22:21:22) > On Sat, Jul 11, 2020 at 10:08:11PM +0200, Jonas Smedegaard wrote: > > > (Way more people should switch from wpa_supplicant to iwd.) > > > > Difficult when network-manager depends (not recommends) wpa-supplicant: > > https://bugs.debian.org/919619 > That Depends is not a problem. Yes a problem, but not a unsurmountable one: You can... a) pollute your Debian system using equivs, or b) install the dependency but then disable the daemon Neither option is helpful in getting "way more people" to switch. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
On Sun, Jul 12, 2020 at 01:21:22AM +0500, Andrey Rahmatullin wrote: > On Sat, Jul 11, 2020 at 10:08:11PM +0200, Jonas Smedegaard wrote: > > > (Way more people should switch from wpa_supplicant to iwd.) > > > > Difficult when network-manager depends (not recommends) wpa-supplicant: > > https://bugs.debian.org/919619 > That Depends is not a problem. Please elaborate how a Depends is not a problem for a switch. @marco: Thanks for telling there is `iwd`. $ apt show iwd 2> /dev/null | sed --silent '/^Description/,$p' Description: wireless daemon for Linux Minimalistic wireless daemon that uses modern Linux interfaces like cfg80211 and nl80211 (netlink). The daemon provides a D-Bus API. . The daemon can be controlled from the command line with the included iwctl client utility. . The included iwmon utility can be used to monitor the 802.11 subsystem generic netlink commands and events. It uses the nlmon kernel driver from Linux 3.10 and later. Groeten Geert Stappers -- Silence is hard to parse
Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
On Sat, Jul 11, 2020 at 10:08:11PM +0200, Jonas Smedegaard wrote: > > (Way more people should switch from wpa_supplicant to iwd.) > > Difficult when network-manager depends (not recommends) wpa-supplicant: > https://bugs.debian.org/919619 That Depends is not a problem. -- WBR, wRAR signature.asc Description: PGP signature
Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
Quoting Marco d'Itri (2020-07-11 19:48:03) > On Jun 28, Jaime wrote: > > > Given that this is guaranteed to fail, isn't it worth "not doing"? Is > > there anyway that I can get dhclient to wait for a successful > > connection *before* sending out any DHCPDISCOVERs? (In the wired > > world, it doesn't make sense to issue a DHCPDISCOVER before plugging > > the cable in.) > This is not a complete solution, but if you switch from wpa_supplicant > to iwd then probably the connection will be setup fast enough to allow > the DHCP client to send the packet. > > (Way more people should switch from wpa_supplicant to iwd.) Difficult when network-manager depends (not recommends) wpa-supplicant: https://bugs.debian.org/919619 - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
On Jun 28, Jaime wrote: > Given that this is guaranteed to fail, isn't it worth "not doing"? Is > there anyway that I can get dhclient to wait for a successful > connection *before* sending out any DHCPDISCOVERs? (In the wired > world, it doesn't make sense to issue a DHCPDISCOVER before plugging > the cable in.) This is not a complete solution, but if you switch from wpa_supplicant to iwd then probably the connection will be setup fast enough to allow the DHCP client to send the packet. (Way more people should switch from wpa_supplicant to iwd.) -- ciao, Marco signature.asc Description: PGP signature
Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
On 29/06/2020, Simon Richter wrote:
> Hi Jaime,
> Yes, that's a long-standing issue.
> A less portable or featureful client has a greater chance of supporting
> this directly.
>Simon
Timo, Simon and Simon,
Thank you all for your replies. Now that I understand the
issues/background, I'm happy to leave things the way they are and
stick with debian's ("built-in") ifupdown.
Thanks again, Jaime
Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
Hi Jaime, On Sun, Jun 28, 2020 at 12:06:02PM +0100, Jaime wrote: > I noticed that my debian wireless clients never get a DHCPOFFER from > their first DHCPDISCOVER, and looking at the log shows why: Yes, that's a long-standing issue. The difficulty is that the ISC client is written to be very portable, and there is no common interface for a program to be notified of interface status changes, so implementing this properly would require larger changes in both the client and the underlying support libraries that are shared with the ISC DHCP server, the ISC DHCP relay and the ISC bind nameserver. A less portable or featureful client has a greater chance of supporting this directly. Simon
Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
On Sun, 28 Jun 2020 at 12:06:02 +0100, Jaime wrote: > I noticed that my debian wireless clients never get a DHCPOFFER from > their first DHCPDISCOVER ... > So it's clear that dhclient is sending out the first DHCPDISCOVER > *before* wpa_supplicant has authenticated/associated/connected to the > AP. This is a property of whatever larger network management component you are using that controls wpasupplicant and dhclient, which might be NetworkManager, wicd, ifupdown, systemd-networkd (maybe? I'm not sure whether it has wpasupplicant integration), your own code (shell scripts or something), or something else. If you think that component (whatever it is) is doing the wrong thing, please report a bug in it or talk to its maintainers. Debian does not require a specific network management component, although some configurations of Debian have a default (for example, the GNOME desktop recommends NetworkManager and works best with that). Typically people use NetworkManager or wicd on portable devices, systemd-networkd or ifupdown on servers, and either of those on desktops/workstations. smcv
Re: isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
On Sun, 28 Jun 2020, Jaime wrote: Given that this is guaranteed to fail, isn't it worth "not doing"? Is there anyway that I can get dhclient to wait for a successful connection *before* sending out any DHCPDISCOVERs? (In the wired world, it doesn't make sense to issue a DHCPDISCOVER before plugging the cable in.) NetworkManager should be at least one such way. When the funciton supplicant_iface_state_cb is called with state NM_SUPPLICANT_INTERFACE_STATE_COMPLETED it will call nm_device_activate_schedule_stage3_ip_config_start that will end up starting dhclient only when wpa_supplicant has done its job. At least last time I tried using ifupdown for wifi I hit all sorts of odd race conditions that probably still exist: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587634
isc-dhcp-client sends DHCPDISCOVER *before* wpa_supplicant authenticates/associates/connects.
Hi all. I noticed that my debian wireless clients never get a DHCPOFFER from their first DHCPDISCOVER, and looking at the log shows why: journalctl output (very much shortened/redacted): 09:34:30 sudo[4373]: COMMAND=/usr/sbin/ifup wlp4s0 09:34:30 wpa_supplicant[4384]: Successfully initialized wpa_supplicant 09:34:30 dhclient[4395]: Internet Systems Consortium DHCP Client 4.4.1 09:34:30 dhclient[4395]: Copyright 2004-2018 Internet Systems Consortium. 09:34:30 dhclient[4395]: All rights reserved. 09:34:30 dhclient[4395]: For info, please visit https://www.isc.org/... 09:34:30 dhclient[4395]: 09:34:30 dhclient[4395]: Listening on LPF/wlp4s0/ab:cd:ab:cd:ab:cd 09:34:30 dhclient[4395]: Sending on LPF/wlp4s0/ab:cd:ab:cd:ab:cd 09:34:30 dhclient[4395]: Sending on Socket/fallback 09:34:30 dhclient[4395]: DHCPDISCOVER on wlp4s0 to 255.255.255.255... 09:34:31 kernel: wlp4s0: authenticate with 12:34:12:34:12:34 09:34:31 wpa_supplicant[4385]: wlp4s0: SME: Trying to authenticate... 09:34:31 kernel: wlp4s0: send auth to 12:34:12:34:12:34 (try 1/3) 09:34:31 kernel: wlp4s0: authenticated 09:34:31 wpa_supplicant[4385]: wlp4s0: Trying to associate with ... 09:34:31 kernel: wlp4s0: associate with 12:34:12:34:12:34 (try 1/3) 09:34:31 kernel: wlp4s0: RX AssocResp from 12:34:12:34:12:34... 09:34:31 kernel: wlp4s0: associated 09:34:31 wpa_supplicant[4385]: wlp4s0: Associated with 12:34:12:34:12:34 09:34:31 wpa_supplicant[4385]: wlp4s0: CTRL-EVENT-SUBNET-STATUS-UPDATE... 09:34:31 wpa_supplicant[4385]: wlp4s0: WPA: Key negotiation completed... 09:34:31 wpa_supplicant[4385]: wlp4s0: CTRL-EVENT-CONNECTED... 09:34:34 dhclient[4395]: DHCPDISCOVER on wlp4s0 to 255.255.255.255... 09:34:34 dhclient[4395]: DHCPOFFER of 192.168.0.6 from 192.168.0.1 09:34:34 dhclient[4395]: DHCPREQUEST for 192.168.0.6 on wlp4s0... 09:34:34 dhclient[4395]: DHCPACK of 192.168.0.6 from 192.168.0.1 So it's clear that dhclient is sending out the first DHCPDISCOVER *before* wpa_supplicant has authenticated/associated/connected to the AP. Given that this is guaranteed to fail, isn't it worth "not doing"? Is there anyway that I can get dhclient to wait for a successful connection *before* sending out any DHCPDISCOVERs? (In the wired world, it doesn't make sense to issue a DHCPDISCOVER before plugging the cable in.) (FWIW, I sent this same question to debian-user 18 months ago, but I didn't get anywhere so I thought I'd try again here). TIA, Jaime
