Re: systemd-networkd managed wireless networks

Top of the morning,

Thank you both for your responses.

On Tue, Mar 4, 2025 at 6:54 AM Denis Kenzior <[email protected]> wrote:
> > Do the iwd dev team strongly recommend having iwd manage the wireless
> > interface with:
>
> This greatly depends on your use case.  If you are integrating iwd with another
> network manager that doesn't support iwd's NetworkConfigurationAgent APIs
> (ConnMan, systemd-networkd), then using EnableNetworkConfiguration=true is not
> what you want.  Recent versions of NetworkManager do support this feature and
> are thus able to let iwd figure out the network configuration details and apply
> the settings to the system.
>
> >
> > [General]
> > EnableNetworkConfiguration=true
> >
> > I am asking as I am using iwd in conjunction with systemd-networkd,
> > and was caught by surprise that disconnecting from my ap in iwd:
> >
> > iwctl station wlan0 disconnect
> >
> > does not result in the associated networkd instance from being degraded:
> >
>
> That may be a question for systemd-networkd folks.  'station disconnect' should
> result in iwd bringing the interface down.  I don't see why it would continue
> having addresses assigned.
>
> >                     Link File: n/a
> >                  Network File: /etc/systemd/network/wireless.network
> >                         State: routable (configured)
> >                  Online state: online
> >                          Type: wlan
> >                          MTU: 1500 (min: 68, max: 1500)
> >                         QDisc: pfifo_fast
> > IPv6 Address Generation Mode: eui64
> >            Wi-Fi access point: (null) (00:00:00:00:00:00)
> >      Number of Queues (Tx/Rx): 1/1
> >                       Address: 192.168.50.153 (DHCPv4 via 192.168.50.1)
> >                                fe80::ea4f:25ff:fe44:f60b
> >                       Gateway: 192.168.50.1
> >                           DNS: 192.168.50.240
> >                                1.1.1.1
> >                                192.168.50.1
> >                                2600:1700:7c10:d0ff::1
> >                           NTP: 192.168.50.1
> >
> > It is interesting to me that networkd has enough insight to know the
> > ap's name, but still does not change the state off of: routable
> > (configured) or adjust the online state.
> >
>
> Perhaps it has to do with some roaming hacks that systemd-networkd introduced
> recently?

I have 2 discrete products running the same yocto stack. One runs 6.13
and appears to work:

● 3: wlan0
                   Link File: n/a
                Network File: /etc/systemd/network/wireless.network
                       State: no-carrier (configured)
                Online state: offline
                        Type: wlan
                        Path: platform-2198000.mmc-platform-wl18xx.0.auto
                      Driver: wl18xx_driver
            Hardware Address: f0:45:da:25:20:ed (Texas Instruments)
                         MTU: 1500 (min: 256, max: 2304)
                       QDisc: noqueue
IPv6 Address Generation Mode: eui64
          Wi-Fi access point: (null) (00:00:00:00:00:00)
    Number of Queues (Tx/Rx): 1/1
                     Address: fe80::f245:daff:fe25:20ed
           Activation Policy: up
         Required For Online: yes
          DHCPv6 Client IAID: 0xac2b916a
          DHCPv6 Client DUID: DUID-EN/Vendor:0000ab11e9977b7ff6c76c1e

the other device runs on 5.10.35, and provides the originally shared
line on disconnect:

● 3: wlan0
                   Link File: n/a
                Network File: /etc/systemd/network/wireless.network
                       State: routable (configured)
                Online state: online
                        Type: wlan
                        Path: platform-30b40000.mmc
                      Driver: brcmfmac
            Hardware Address: e8:4f:25:44:f6:0b (Murata Manufacturing Co., Ltd.)
                         MTU: 1500 (min: 68, max: 1500)
                       QDisc: pfifo_fast
IPv6 Address Generation Mode: eui64
          Wi-Fi access point: (null) (00:00:00:00:00:00)
    Number of Queues (Tx/Rx): 1/1
                     Address: 192.168.50.153 (DHCPv4 via 192.168.50.1)
                              2600:1700:7c10:d0ff:ea4f:25ff:fe44:f60b
                              fe80::ea4f:25ff:fe44:f60b
                     Gateway: 192.168.50.1
                              fe80::7e10:c9ff:fee5:7cc8
                         DNS: 192.168.50.240
                              1.1.1.1
                              192.168.50.1

So this does appear to be a function of kernel version. I will
continue to spelunk and follow up here if I gain any insight.

Yours sincerely,
Donald