Please note: This project is no longer active. The website is kept online for historic purposes only.
If you´re looking for a Linux driver for your Atheros WLAN device, you should continue here .

Changes between Version 17 and Version 18 of UserDocs/Distro/Debian/ConfiguringtheMadWifidevice

Author:
mentor (IP: 0.0.0.0)
Timestamp:
06/14/07 21:53:45 (12 years ago)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • UserDocs/Distro/Debian/ConfiguringtheMadWifidevice

    v17 v18  
    33== Automated VAP creation == 
    44 
    5 MadWifi support multiple VAP's. If you are using MadWifi-old, this section is no good to you, it deals with the handling of these special abilities of MadWifi within the Debian networking scripts. 
     5MadWifi support multiple VAPs. If you are using MadWifi-old, then this section is not useful, as it deals with the handling of the special abilities of MadWifi-NG within the Debian networking scripts. 
    66 
    77Any snapshot more recent than r1407 will create a '''sta''' mode VAP for each atheros device by default. If a madwifi-ng-base package is currently installed, please remove it and upgrade your madwifi packages. 
    1919}}} 
    2020 
    21 [http://www.mattb.net.nz/ Matt Brown] has written some more advanced scripts to nicely integrate the madwifi-ng setup with the Debian ifupdown framework. They use the wireless-tools extensions to determine the mode to create the interface in. These are most useful for creating multiple VAP's, especially in ap mode. It may be useful to disable the autocreation of the sta VAP when using these. They are included in the [wiki:UserDocs/Distro/Debian#DebianMadWifingPackages madwifi-tools package] and are also available separately from: 
     21[http://www.mattb.net.nz/ Matt Brown] has written some more advanced scripts to nicely integrate the madwifi-ng setup with the Debian ifupdown framework. They use the wireless-tools extensions to determine the mode to create the interface in. These are most useful for creating multiple VAPs, especially in ap mode. It may be useful to disable the autocreation of the sta VAP when using these. They are included in the [wiki:UserDocs/Distro/Debian#DebianMadWifingPackages madwifi-tools package] and are also available separately from: 
    2222 
    2323 * [http://www.mattb.net.nz/patches/madwifi/madwifi-if-pre-up.d] install to /etc/network/if-pre-up.d/madwifi 
    5757The following paragraphs will consist of a handful of example interfaces entries for using MadWifi devices. For each possible command parameter of iwconfig you can include an option in /etc/network/interfaces named like that parameter with a "wireless-" prefix. Wireless devices are more complex to setup correctly, because of the nature of their usage, and the broad range of features available to them. For example, some of them are removeable and some support multiple VAP's (madwifi-ng). Therefore, some special handling is required to exploit as much as possible out of these features. 
    5858 
    59 Client to an access point (essid of "wep.net") with '''wep security''', using '''wireless-tools''' and obtaining an ip via dhcp
     59Client to an access point (essid of "wep.net") with '''WEP security''', using '''wireless-tools''' and obtaining an IP via DHCP
    6060{{{ 
    6161auto ath0 
    7272Debian users who have wpasupplicant >=0.4.8-1 installed can take advantage of ifupdown integration via the following examples: 
    7373 
    74 Client to an WPA/WPA2 encrypted access point via '''wpa_supplicant''' and obtaining an ip via dhcp
     74Client to an WPA/WPA2 encrypted access point via '''wpa_supplicant''' and obtaining an IP via DHCP
    7575{{{ 
    7676auto ath0 
    8282}}} 
    8383 
    84 A '''cardbus''' card is hot-pluggable, and not always present. This is when the `allow-hotplug` class of net.agent (hotplug/udev) becomes useful: 
     84A '''CardBus''' card is hot-pluggable, and not always present. This is when the `allow-hotplug` class of net.agent (hotplug/udev) becomes useful: 
    8585{{{ 
    8686allow-hotplug ath0 
    8989        wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf 
    9090}}} 
    91 So when the cardbus card generates a hotplug event, the networking scripts are hooked and bring it up.  This can be useful even if you're wireless device is permanently installed, for instance, if you have a laptop and want to be remove and reload the kernel modules, e.g., during sleep states. 
     91So when the CardBus card generates a hotplug event, the networking scripts are hooked and bring it up.  This can be useful even if you're wireless device is permanently installed, for instance, if you have a laptop and want to be remove and reload the kernel modules, e.g., during sleep states. 
    9292 
    9393== Advanced Mobile Users Configuration ==