Re: Connection to a WPA2 Wi-Fi router fails

Waldemar Brodkorb <[email protected]>
Newsgroups dev.linux.lists.connman
Message-ID <[email protected]>
Hi Sven,
Dembianny Sven (BSH GDE-EDSD7) wrote,

> 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?

Vodafone Wifi 6.
It is this one:
https://www.vodafone.de/downloadarea/CGA6444VF-DMS3-CTC-25-593_v2.0_German_public_20210511.pdf

> It is possible that MFP is additionally configured as optional. Could you please check the AP settings or the beacon frames?

It seems not.
See:
sudo iw dev wlan0 scan | grep -A20 -B2 'Vodafone-C30C'
	last seen: 84 ms ago
	Information elements from Probe Response frame:
	SSID: Vodafone-C30C
	Supported rates: 1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0
	DS Parameter set: channel 11
	Country: DE	Environment: Indoor/Outdoor
		Channels [1 - 13] @ 20 dBm
	TPC report: TX power: 18 dBm
	ERP: Barker_Preamble_Mode
	Extended supported rates: 6.0 9.0 12.0 48.0
	RSN:	 * Version: 1
		 * Group cipher: CCMP
		 * Pairwise ciphers: CCMP
		 * Authentication suites: PSK
		 * Capabilities: 16-PTKSA-RC 1-GTKSA-RC (0x000c)
	BSS Load:
		 * station count: 2
		 * channel utilisation: 31/255
		 * available admission capacity: 0 [*32us]
	RM enabled capabilities:
		Capabilities: 0x72 0x00 0x00 0x00 0x00
			Neighbor Report
			Beacon Passive Measurement
--
	signal: -72.00 dBm
	last seen: 3208 ms ago
	SSID: Vodafone-C30C
	Supported rates: 6.0* 9.0 12.0* 18.0 24.0* 36.0 48.0 54.0
	TIM: DTIM Count 0 DTIM Period 1 Bitmap Control 0x0 Bitmap[0] 0x0
	Country: DE	Environment: Indoor/Outdoor
		Channels [36 - 64] @ 23 dBm
		Channels [100 - 140] @ 30 dBm
	Power constraint: 0 dB
	TPC report: TX power: 23 dBm
	RSN:	 * Version: 1
		 * Group cipher: CCMP
		 * Pairwise ciphers: CCMP
		 * Authentication suites: PSK
		 * Capabilities: 16-PTKSA-RC 1-GTKSA-RC (0x000c)
	BSS Load:
		 * station count: 6
		 * channel utilisation: 6/255
		 * available admission capacity: 0 [*32us]
	RM enabled capabilities:
		Capabilities: 0x72 0x00 0x00 0x00 0x00
			Neighbor Report
			Beacon Passive Measurement

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

That is the dmesg output after loading the Wifi driver in Buildroot:
[  249.369934] brcmfmac: F1 signature read @0x18000000=0x15264345
[  249.373427] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[  249.382449] usbcore: registered new interface driver brcmfmac
[  249.618723] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2)
[  249.626771] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Aug 29 2023 01:47:08 version 7.45.265 (28bca26 CY) FWID 01-b677b91b

But at the moment I am fighting with connmanctl, it seems I cannot
scan wifi anymore:
# connmanctl scan wifi
Error /net/connman/technology/wifi: Not supported
# connmanctl enable wifi
wifi is already enabled
# connmanctl scan wifi
Error /net/connman/technology/wifi: Not supported
# connmanctl technologies
/net/connman/technology/ethernet
  Name = Wired
  Type = ethernet
  Powered = True
  Connected = False
  Tethering = False
  TetheringFreq = 2412
/net/connman/technology/wifi
  Name = WiFi
  Type = wifi
  Powered = True
  Connected = False
  Tethering = False
  TetheringFreq = 2412

I can scan wifi with iw on the RPI4.

best regards
 Waldemar
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.