FS#33630 - [netcfg] net-auto-wireless start only after WIRELESS_INTERFACE is available

Attached to Project: Arch Linux
Opened by Christoph Glaubitz (chrigl) - Tuesday, 29 January 2013, 22:10 GMT
Last edited by Eric Belanger (Snowman) - Tuesday, 30 April 2013, 01:04 GMT
Task Type Feature Request
Category Arch Projects
Status Closed
Assigned To Jouke Witteveen (jouke)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
It net-auto-wireless.service is enabled, but the device is not yet available, it ends in failed state. So net-auto-wireless.service should only start if WIRELESS_INTERFACE is available.

I added a patch for the issue.

Additional info:
* 3.0-1
* also the latest git version


Steps to reproduce:
I have an usb device and it does not come up on each boot. But starting net-auto-wireless.service by hand, always works.
Bus 001 Device 002: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter
   0001-added-dependency-to-the-... (1 KiB)
This task depends upon

Closed by  Eric Belanger (Snowman)
Tuesday, 30 April 2013, 01:04 GMT
Reason for closing:  Won't fix
Additional comments about closing:  netcfg has been moved to AUR
Comment by Christoph Glaubitz (chrigl) - Friday, 01 February 2013, 14:06 GMT
Ok. It does not reliable work. And BindsTo is only documented to be used in section [Unit].

Maybe a solution is to provide net-auto-wireless@.service like described here:
https://github.com/brain0/netcfg/blob/working/systemd/net-auto-wireless%40.service
Comment by Lars Kellogg-Stedman (larsks) - Tuesday, 05 March 2013, 22:05 GMT
Why is this a feature request and not a bug? This is a bad interaction between udev and net-auto-wireless and should be fixed.
Comment by Jouke Witteveen (jouke) - Wednesday, 06 March 2013, 10:29 GMT
This bug is fixed in netctl, which is more or less netcfg for systemd setups. At the moment, netctl is in [testing].

Loading...