Opened 8 years ago

Closed 8 years ago

Last modified 20 months ago

#9127 closed enhancement (fixed)

Libertas wlan0/msh0 device pairs shoud be renamed

Reported by: martin.langhoff Owned by: martin.langhoff
Priority: high Milestone:
Component: school server Version: not specified
Keywords: Cc:
Blocked By: Blocking:
Deployments affected: Action Needed: never set
Verified: no


Our AA related code assumes device pairs named wlanN/mshN.

On a machine with PCI wireless cards, the PCI device will take precedence and take the wlan0 name, so when the Libertas device comes up, it appears as wlan1/msh0. Our scripts ignore this and try to drive wlan0 as if it were the pair of msh0 -- the wlan0 driver gets confused/locked and all bets are off.

There is an easy solition for this: change our dev naming convention away from wlanX and leave wlanX for other autoconfigured wireless devices.

Change History (3)

comment:1 Changed 8 years ago by martin.langhoff

  • Milestone changed from xs-0.6 to xs-0.5.1
  • Resolution set to fixed
  • Status changed from new to closed

comment:2 Changed 8 years ago by mikus

COMMENT: I had a similar problem on my XO when using an USB-ethernet adapter for a wired connection. My bypass was to manually edit /etc/udev/rules.d/70-persistent-net.rules such that the ethernet adapter was specified to use 'eth1', and the radio wifi was specified to use 'eth0' (corresponding to the radio mesh using 'msh0').

comment:3 Changed 20 months ago by Quozl

  • Milestone xs-0.5.1 deleted

Milestone xs-0.5.1 deleted

Note: See TracTickets for help on using tickets.