PSA: 10.41.14 - AP radio stuck in channel select if PSK length > 48

[Ronald_Dvorak]

Hi,

looks like the software has some issues with a PSK that is > 48 characters.

In that case if the WLAN service is enabled on the AP radio (1 or 2 or both) the radio will stay in scanning and don't provide service.

Test setup:
-AP3915i-ROW, AP3825e
-Country Austria
-PSK with 49 characters:
1234567890123456789012345678901234567890123456789
-WDS & WPAv2-AES WLAN service

AP log:
Mar 10 21:41:31 cap: total VNSs /tmp/seccfg_00_0.cfg
Mar 10 21:41:31 hostapd0: 1552254091.808100: Configuration file: /tmp/seccfg_00_0.cfg
Mar 10 21:41:31 hostapd0: 1552254091.809415: Line 7: invalid WPA passphrase length 64 (expected 8..63)
Mar 10 21:41:31 hostapd0: 1552254091.809763: WPA-PSK enabled, but PSK or passphrase is not configured.
Mar 10 21:41:31 hostapd0: 1552254091.809885: 2 errors found in configuration file '/tmp/seccfg_00_0.cfg'
Mar 10 21:41:31 hostapd0: 1552254091.809989: Failed to set up interface with /tmp/seccfg_00_0.cfg
Mar 10 21:41:31 hostapd0: 1552254091.810106: Failed to initialize interface

File from the AP log:
AP3915i-2# cat seccfg_00_0.cfg

ssid=WDS_test_49
interface=ath0
bridge=br0
beacon=100 5
tkiphack_opts=2 2147483647
enc_wpa_passphrase=f300a5f5ab1ac73f53d30de21eb1b52420c0b442876cc74c8546ccbf9e316bf15a142c4ea5a5bd262c7750e8a41fec0f7f0d3cea7e3ff706447728b2b0b69923
wpa_key_mgmt=WPA-PSK
wpa=2
wpa_pairwise=CCMP
wpa_group_rekey=3600
AP3915i-2#

I've run into this issue after the upgrade from 10.41.13 to 10.41.14 because my WDS link wasn't working anymore.

This was also tested it with a normal PSK WLAN service with the same result.

I'll create a new ticket for this issue by tomorrow.

-Ron

[AG1]

See article "https://gtacknowledge.extremenetworks.com/articles/Solution/AP-radios-stuck-in-channel-select-if-PSK-length-is-more-than-48-characters"
Upgrade software to 10.41.14.0009 or higher.

[Ronald_Dvorak]

Anton,

my ticket# is 01824597 and I've mentioned the open ticket from you.

Shouldn't require any data as you could reproduce it with only one controller & AP (ROW-Austria) and PSK length of >48


-Ron

[AntonS]

We have the same issue.
I already opened a ticket.

Mar 7 20:29:03 cap: total VNSs /tmp/seccfg_01_0.cfg /tmp/seccfg_01_1.cfg
Mar 7 20:29:03 hostapd0: 1551990543.262160: Configuration file: /tmp/seccfg_00_0.cfg
Mar 7 20:29:03 hostapd0: 1551990543.276015: Line 7: invalid WPA passphrase length 64 (expected 8..63)
Mar 7 20:29:03 hostapd0: 1551990543.276449: WPA-PSK enabled, but PSK or passphrase is not configured.
Mar 7 20:29:03 hostapd0: 1551990543.276745: 2 errors found in configuration file '/tmp/seccfg_00_0.cfg'
Mar 7 20:29:03 hostapd0: 1551990543.276824: Failed to set up interface with /tmp/seccfg_00_0.cfg
Mar 7 20:29:03 hostapd0: 1551990543.276862: Failed to initialize interface
Mar 7 20:29:03 cap: total VNSs /tmp/seccfg_00_0.cfg /tmp/seccfg_00_2.cfg
Mar 7 20:29:03 hostapd1: 1551990543.302103: Configuration file: /tmp/seccfg_01_0.cfg
Mar 7 20:29:03 hostapd1: 1551990543.302959: Line 7: invalid WPA passphrase length 64 (expected 8..63)
Mar 7 20:29:03 hostapd1: 1551990543.308863: WPA-PSK enabled, but PSK or passphrase is not configured.
Mar 7 20:29:03 hostapd1: 1551990543.309165: 2 errors found in configuration file '/tmp/seccfg_01_0.cfg'
Mar 7 20:29:03 hostapd1: 1551990543.309455: Failed to set up interface with /tmp/seccfg_01_0.cfg
Mar 7 20:29:03 hostapd1: 1551990543.309761: Failed to initialize interface