Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#21464 - [netcfg] ifplugd action does not support wireless interfaces

Attached to Project: Arch Linux
Opened by Rico Moorman (rico) - Monday, 25 October 2010, 11:23 GMT
Last edited by James Rayner (iphitus) - Sunday, 21 November 2010, 02:32 GMT
Task Type Feature Request
Category Packages: Core
Status Closed
Assigned To James Rayner (iphitus)
Thomas Bächler (brain0)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
Currently the netcfg/ifplugd combo with the automatic wireless setup described here:
http://wiki.archlinux.org/index.php/Network_Profiles#Connecting_automatically
doesn't support auto plugging wireless interfaces

I followed the instructions here and could successfully connect to the configured wireless networks. But upon disabling and re-enabling the wireless connection (using the button on my laptop) the wireless connection was not restarted correctly.

In spite of this I was able to get it working properly using the following steps:
- copy the netcfg.action to netcfg-wireless.action and replacing the "ethernet|ethernet-iproute" with "wireless"
- adding the wlan0 interface to the ifplugd.conf (ifplugd specific setting)

Could the "wireless" option be added to the netcfg.action or could it at least be made configurable without adding it "inside" the action-script somewhere?


Additional info:
* package version(s)
netcfg 2.5.4-1
* config and/or log files etc.
netcfg /etc/ifplugd/netcfg.action

   netcfg.action.patch (0.5 KiB)
This task depends upon

Closed by  James Rayner (iphitus)
Sunday, 21 November 2010, 02:32 GMT
Reason for closing:  Not a bug
Comment by Rico Moorman (rico) - Monday, 25 October 2010, 11:25 GMT
The patchfile attached to the issue shows the difference between the default netcfg.action and the netcfg-wireless.action I had to create to get it working.
Comment by James Rayner (iphitus) - Sunday, 21 November 2010, 02:32 GMT
This is by design. net-auto-wired is for wired connections, not wireless.

For automatic wireless, net-auto-wireless (which uses wpa_actiond instead of ifplugd) should be used instead.

As for suspend/resume, that's covered by two other bugs.

Loading...