Project

General

Profile

Actions
Copy link

Bug #7960

closed

Wirelss WAN can get caught in a configure loop

Added by Jim Pingle about 7 years ago. Updated about 7 years ago.

Status:
Resolved
Priority:
High
Assignee:
Jim Pingle
Category:
Wireless
Target version:
2.4.1
Start date:
10/17/2017
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.x
Affected Architecture:
All

Description

At least with some wireless devices, they send a link up event to the OS when they associate successfully. This triggers rc.linkup which in turn calls interface_configure(). For wireless interfaces, this also calls interface_wireless_configure() which tears down and rebuilds the wireless interface, which then associates again, triggers another link up event, and so on in an endless loop.

This at least affects ralink USB wifi devices with the run(4) driver.

To me, I have a fix.

Actions
Copy link
 #1

Updated by Jim Pingle about 7 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions
Copy link
 #2

Updated by Jim Pingle about 7 years ago

  • Status changed from Feedback to Resolved

This looks good now. After upgrading to the latest snap, I can have a wireless WAN assigned and working, and also edit/save/apply the interface without it falling into a loop.

Actions
Copy link

Also available in: Atom PDF