RE: Connection to a WPA2 Wi-Fi router fails

Hi Waldemar,
> 
> Hi Sven,
> Dembianny Sven (BSH GDE-EDSD7) wrote,
> 
> > Hi Michael,
> >
> > I don't think so, e.g., if AP does not support SAE but repeater does, roaming will fail.
> > This will also break certification tests.
> >
> > @ François do you have more info about your setup, e.g. MFP setting on AP/wpa_supplicant
> config/WPA-PSK-SHA256 instead of WPA-PSK?
> 
> Sorry for the late reply. Francois seems not to answered your question and I see no fixes for this
> problem in GIT master either.
> 
> My AP is a standard Vodafone AP with WPA2.
> How can I give you better information about the details of this AP?
What model is being used?
It is possible that MFP is additionally configured as optional. Could you please check the AP settings or the beacon frames?

Also, what firmware version is running on the Raspberry Pi 4? The firmware files should be located under:
/lib/firmware/

Best regards,  Sven
> best regards
>  Waldemar
> 
> > Best regards, Sven
> >
> > > -----Original Message-----
> > > From: Michael Nazzareno Trimarchi <[email protected]>
> > > Sent: Dienstag, 12. Mai 2026 11:33
> > > To: François Galea <[email protected]>; Dembianny Sven (BSH GDE-EDSD7)
> > > <[email protected]>
> > > Cc: [email protected]; [email protected]
> > > Subject: Re: Connection to a WPA2 Wi-Fi router fails
> > >
> > > Hi
> > >
> > > On Tue, May 12, 2026 at 11:14 AM François Galea <[email protected]> wrote:
> > > >
> > > > Hello,
> > > >
> > > > This was tested on a Zynq (Cortex-A9) and a RPi4, on a 32-bit Arm
> > > > Buildroot Linux system.
> > > >
> > > > The Wi-Fi router uses WPA2 Personnal authentication.
> > > >
> > > > Problem starts from buildroot releases including connman 1.45.
> > > > Previous releases using connman 1.44 and prior are working fine.
> > > > Also switching from 1.45 to 1.44 in a buildroot version that includes connman 1.45 works.
> > > >
> > > >
> > > > If a connection was previously successfully set up, for instance
> > > > from connman 1.44 or older, `/var/log/messages` contains:
> > > >
> > > > Jan  1 00:00:11 zest daemon.info connmand[141]: Adding interface
> > > > wlan0 [ wifi ] Jan  1 00:00:11 zest daemon.info connmand[141]:
> > > > eth0 {update} flags
> > > > 36867 <UP>
> > > > Jan  1 00:00:11 zest daemon.info connmand[141]: eth0 {newlink}
> > > > index 2 address 9A:8F:85:81:67:B4 mtu 1500 Jan  1 00:00:11 zest
> > > > daemon.info
> > > > connmand[141]: eth0 {newlink} index 2 operstate 2 <DOWN> Jan  1
> > > > 00:00:11 zest daemon.info dbus-daemon[120]: [system] Successfully
> > > > activated service 'fi.w1.wpa_supplicant1'
> > > > Jan  1 00:00:11 zest daemon.info connmand[141]: wlan0 {update}
> > > > flags
> > > > 36931 <UP,RUNNING>
> > > > Jan  1 00:00:11 zest daemon.info connmand[141]: wlan0 {newlink}
> > > > index
> > > > 4 address 8C:3D:16:20:0E:4A mtu 1500 Jan  1 00:00:11 zest
> > > > daemon.info
> > > > connmand[141]: wlan0 {newlink} index 4 operstate 0 <UNKNOWN> Jan
> > > > 1
> > > > 00:00:11 zest daemon.info connmand[141]: wlan0 {update} flags
> > > > 36867 <UP>
> > > > Jan  1 00:00:11 zest daemon.info connmand[141]: wlan0 {newlink}
> > > > index
> > > > 4 address 8C:3D:16:20:0E:4A mtu 1500 Jan  1 00:00:11 zest
> > > > daemon.info
> > > > connmand[141]: wlan0 {newlink} index 4 operstate 2 <DOWN> Jan  1
> > > > 00:00:11 zest daemon.info connmand[141]: wlan0 {newlink} index 4
> > > > address 8C:3D:16:20:0E:4A mtu 1500 Jan  1 00:00:11 zest
> > > > daemon.info
> > > > connmand[141]: wlan0 {newlink} index 4 operstate 2 <DOWN> Jan  1
> > > > 00:00:11 zest daemon.info connmand[141]: Interface wlan0 [ wifi ]
> > > > state is association Jan  1 00:00:11 zest daemon.warn connmand[141]:
> > > > Interface wlan0 [ wifi ] error "invalid-key"
> > > > Jan  1 00:00:11 zest daemon.info connmand[141]: Interface wlan0 [
> > > > wifi ] state is failure
> > > >
> > > >
> > > > Otherwise, when creating a new connection:
> > > >
> > > > # connmanctl
> > > > Error getting VPN connections: The name net.connman.vpn was not
> > > > provided by any .service files
> > > > connmanctl> services
> > > >
> > > > connmanctl> enable wifi
> > > > Enabled wifi
> > > > connmanctl> scan wifi
> > > > Scan completed for wifi
> > > > connmanctl> services
> > > >      Kamoulox             wifi_8c3d16200e4a_4b616d6f756c6f78_managed_psk
> > > >      Livebox-D050
> > > > wifi_8c3d16200e4a_4c697665626f782d44303530_managed_psk
> > > >      Freebox-3B4B3C
> > > > wifi_8c3d16200e4a_46726565626f782d334234423343_managed_psk
> > > >      patetalex            wifi_8c3d16200e4a_7061746574616c6578_managed_psk
> > > >      DRAME                wifi_8c3d16200e4a_4452414d45_managed_psk
> > > > connmanctl> agent on
> > > > Agent registered
> > > > connmanctl> connect wifi_8c3d16200e4a_4b616d6f756c6f78_managed_psk
> > > > Agent RequestInput wifi_8c3d16200e4a_4b616d6f756c6f78_managed_psk
> > > >    Passphrase = [ Type=psk, Requirement=mandatory, Alternates=[ WPS ] ]
> > > >    WPS = [ Type=wpspin, Requirement=alternate ] Passphrase?
> > > > my_wifi_passphrase Agent ReportError
> > > > wifi_8c3d16200e4a_4b616d6f756c6f78_managed_psk
> > > >    invalid-key
> > > > connmanctl> Retry (yes/no)? no
> > > > Error
> > > > /net/connman/service/wifi_8c3d16200e4a_4b616d6f756c6f78_managed_psk:
> > > > Input/output error
> > > > connmanctl>
> > >
> > >
> > > I think that change only asks the agent who established the
> > > connection to try the various method. Is the patch in attach work?
> > > * sven *: Does it cover your use case too?
> > >
> > > Michael
> > >
> > >
> > > >
> > > >
> > > >
> > > >  From both situations it appears the wifi passphrase is not accepted.
> > > >
> > > > wbx (as CC of this email) noticed that reverting commit
> > > > 5e73b55e00b97e1867397258b72f0d6e5ad7d31d allows connections to work again.
> > > >
> > > > Is it a known situation? Is there a patch available?
> > > >
> > > > Best,
> > > >
> > > > François
> > > >
> > > >
> > >
> > >
> > > --
> > > Michael Nazzareno Trimarchi
> > > Co-Founder & Chief Executive Officer M. +39 347 913 2170
> > > [email protected] __________________________________
> > >
> > > Amarula Solutions BV
> > > Joop Geesinkweg 125, 1114 AB, Amsterdam, NL T. +31 (0)85 111 9172
> > > [email protected]
> > > https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww
> > > .amarulasolutions.com%2F&data=05%7C02%7Csven.dembianny%40bshg.com%7C
> > > 00a2bd14c2d74f32f2c208def5e13e36%7C0ae51e1907c84e4bbb6d648ee58410f4%
> > > 7C0%7C0%7C639218544918069416%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGk
> > > iOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjo
> > > yfQ%3D%3D%7C0%7C%7C%7C&sdata=kxL6P7SRricrBgLeS4U18xAwP250HMfWS3uDowQ
> > > ZDaA%3D&reserved=0
> > > &data=05%7C02%7Csven.dembianny%40bshg.com%7Cf4aa618e280e45c3d76e08de
> > > b0096f57%7C0ae5
> > > 1e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C639141751758647935%7CUnknown%
> > > 7CTWFpbGZsb3
> > > d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIj
> > > oiTWFpbCIsIldUIjoyfQ
> > > %3D%3D%7C0%7C%7C%7C&sdata=8tD7KmAQSPxg%2BRZ0yB7MYBeWVudCjvw4T4MJhOHy
> > > 3%2Fk%3D
> > > &reserved=0