Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
recalbox
recalbox
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 198
    • Issues 198
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 49
    • Merge Requests 49
  • Requirements
    • Requirements
    • List
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • recalbox
  • recalboxrecalbox
  • Issues
  • #1492

Closed
Open
Opened Dec 29, 2020 by Fred@ajp-lab

V7.1.1 - RECALBOX WiFi intf fails to connect if WPA2 with SHA256 is set

Hi all,

after upgrading to V7.1.1 I had the following issue:

RECALBOX WiFi could not connect anymore to my router.

Router specs: TP-LINK WDR4300, firmware DD-WRT v3.0-r44715 std (11/03/20), two SSIDs (1x 2.4 Ghz 20 Mhz, 1x 5 Ghz 40 Mhz) same named, WPA2, AES

After trying out several options on the router: channel width, password with/without special characters etc. I finally found the issue: If the option WPA2 with SHA256 is selected, RECALBOX can not connect anymore to the router and the device is being shortly shown as "LEGACY" device and disappears after a few secs.

I expected at least a fallback and connection via "normal" WPA2 since it is also selected (without SHA256), but this is not the case, therefore I propose this issue.

Technical solution for a future release of RECALBOX client could be:

  • Either enable a fallback connection to "normal" WPA2 (CCMP-128) if WPA2-SHA256 is selected and the connection fails or drops out, or better
  • Support WPA2-SHA256 in the future

Not sure if this is a bug only in V7.1.1 or WPA2-SHA256 has never been supported so far. Workaround was to de-select WPA2 with SHA256 so that RECALBOX could connect to the router.

image

(Screenshot DD-WRT router menu, wireless security settings)

Thanks & regards, Fred

Edited Dec 29, 2020 by Fred
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: recalbox/recalbox#1492