Package: ifupdown Version: 0.6.10 Severity: wishlist Hi
some wlan drivers trigger uevents, whenever the user presses/toggles the rf killswitch. if would make perfect sense to hand this over to ifup/down if this is wanted by the user. i suggest putting a file, say 99-rfkill.rules, containing the following lines (or similar) into /etc/udev/rules.d/. ACTION=="change", \ ENV{RFKILL_TYPE}=="wlan", ENV{RFKILL_STATE}=="1",SUBSYSTEM=="rfkill", \ RUN+="/sbin/ifup --allow=rfkill wlan0" ACTION=="change", \ ENV{RFKILL_TYPE}=="wlan", ENV{RFKILL_STATE}=="2",SUBSYSTEM=="rfkill", \ RUN+="/sbin/ifdown --allow=rfkill wlan0" this reduces te configuation overhead of the end user to adding "allow-rfkill wlan0" to her interface file, and doesnt do any harm to someone who doesnt like it. unfortunately, i am lacking a method to find the correct ifname (wlan0 here). i leave this open, since i dont have many rfkill switches to test anyway. the proposed rules work with Intel N WiFi Link 5300 (iwlagn) Thank you felix -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ifupdown depends on: ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii lsb-base 3.2-23.1 Linux Standard Base 3.2 init scrip ii net-tools 1.60-23 The NET-3 networking toolkit ifupdown recommends no packages. Versions of packages ifupdown suggests: ii dhcp3-client 3.1.3-2 DHCP client ii iproute 20100224-5 networking and traffic control too pn ppp <none> (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org