Project

General

Profile

Actions

Bug #904

closed

wpa_supplicant.conf is not working with local router

Added by Hammel almost 2 years ago. Updated 5 months ago.

Status:
Closed
Priority:
Immediate
Assignee:
Target version:
Start date:
24 Sep 2022
Due date:
% Done:

100%

Estimated time:
Severity:
01 - Critical

Description

The setup use the following:

network={
ssid="AP_SSID" 
psk="psk" 
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP
group=CCMP
}
The following changes seem necessary to do strict WPA2:
  • proto should be "RSN"
  • pairwise should be CCMP
  • group should be CCMP

For mixed mode support the group can be set to TKIP instead of CCMP.

It's not clear, after some minor testing, that this actually works with my router. This bug will remain open until I can explain this.


Related issues

Has duplicate pibox-network-config - Bug #927: RPi2 fails to connect via wifiRejectedHammel01 Dec 2022

Actions
Blocks PiBox - Testing #1099: Verify Media System and Player System properly support PiNet's web UI.ClosedHammel15 Jan 2024

Actions
Actions #1

Updated by Hammel almost 2 years ago

  • Description updated (diff)
Actions #2

Updated by Hammel over 1 year ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 20

This might be due to missing firmware.

Look in crda firmware package for
  • regulatory.db
  • regulatory.db.p7s

Update:
These may not be needed. I ran

iwlist scan > /media/mmcblk0p3/log/iwlist.log

andd searched for the router mac address. Then I looked or "group" and "pairwise" settings for that router and set the wpa_supplicant.conf on the Pi to match. That worked. So it's a matter of finding those settings and updating wpa_supplicant.conf accordingly.

I should do the following:

  • Add Ctrl-T to launcher to get terminal window (this is quick fix)
  • Add tool for finding those fields given either SSID or mac address.
  • Eventually make pinet and pnc smart enough to do this automatically.
Actions #3

Updated by Hammel over 1 year ago

  • Has duplicate Bug #927: RPi2 fails to connect via wifi added
Actions #4

Updated by Hammel about 1 year ago

It should be noted that a new router I setup worked fine with this configuration. And I've been having lots of other troubles with the older router. So maybe all my troubles are just router specific and not PiBox specific.

In any case, the RSN/CCMP/CCMP setup seems to work with the new router.

Actions #5

Updated by Hammel 5 months ago

  • Priority changed from Urgent to Immediate
  • Severity changed from 02 - High to 01 - Critical
Actions #6

Updated by Hammel 5 months ago

  • Blocks Testing #1099: Verify Media System and Player System properly support PiNet's web UI. added
Actions #7

Updated by Hammel 5 months ago

  • % Done changed from 20 to 50

I've made the change to pnc to force CCMP in the right places. The RSN change doesn't appear necessary as having the current default, "WPA RSN", seems to work with PiNet as long as the CCMP settings are there.

This needs to be rebuilt and tested on hardware.

Actions #8

Updated by Hammel 5 months ago

  • Status changed from In Progress to Closed
  • % Done changed from 50 to 100

Tested and working.

Code committed and pushed.

Closing issue.

Actions

Also available in: Atom PDF