<version>1.2</version>

<version>1.3</version>

<date>2005-08-02</date>

<date>2005-12-21</date>

Currently we support wireless setup either by wireless-tools or wpa_supplicant.

Currently we support wireless setup either by <c>wireless-tools</c> or

The important thing to remember is that you configure for wireless networks on a

<c>wpa_supplicant</c>. The important thing to remember is that you configure for

global basis and not an interface basis.

wireless networks on a global basis and not an interface basis.

wpa_suppliant is the best choice, but it does not support all drivers. For a

<c>wpa_suppliant</c> is the best choice, but it does not support all drivers.

list of supported drivers, <uri

For a list of supported drivers, <uri

site</uri>. Also, wpa_supplicant can currently only connect to SSID's that

site</uri>. Also, <c>wpa_supplicant</c> can currently only connect to SSID's

you have configured for.

that you have configured for.

wireless-tools supports nearly all cards and drivers, but it cannot connect to

<c>wireless-tools</c> supports nearly all cards and drivers, but it cannot

WPA only Access Points.

connect to WPA only Access Points.

The linux-wlan-ng driver is not supported by baselayout at this time. This is

The <c>linux-wlan-ng</c> driver is not supported by <c>baselayout</c> at this

because linux-wlan-ng have their own setup and configuration which is completely

time. This is because <c>linux-wlan-ng</c> have their own setup and

different to everyone else's. The linux-wlan-ng devs are rumoured to be changing

configuration which is completely different to everyone else's. The

their setup over to wireless-tools - when this happens you may use linux-wlan-ng

<c>linux-wlan-ng</c> devs are rumoured to be changing their setup over to

with baselayout.

<c>wireless-tools</c> - when this happens you may use <c>linux-wlan-ng</c>

with <c>baselayout</c>.

You have to have CONFIG_PACKET enabled in your kernel for wpa_supplicant to

You have to have <c>CONFIG_PACKET</c> enabled in your kernel for

work.

<c>wpa_supplicant</c> to work.

wpa_supplicant over wireless-tools (if both are installed, wireless-tools is the

<c>wpa_supplicant</c> over <c>wireless-tools</c> (if both are installed,

default).

<c>wireless-tools</c> is the default).

If you're using the host-ap driver you will need to put the card in Managed mode

If you're using the host-ap driver you will need to put the card in <e>Managed

before it can be used with wpa_supplicant correctly. You can use

mode</e> before it can be used with <c>wpa_supplicant</c> correctly. You can use

That was simple wasn't it? However, we still have to configure wpa_supplicant

That was simple wasn't it? However, we still have to configure

itself which is a bit more tricky depending on how secure the Access Points are

<c>wpa_supplicant</c> itself which is a bit more tricky depending on how secure

that you are trying to connect to. The below example is taken and simplified

the Access Points are that you are trying to connect to. The below example is

from <path>/etc/wpa_supplicant.conf.example</path> which ships with

taken and simplified from <path>/etc/wpa_supplicant.conf.example</path> which

wpa_supplicant.

ships with <c>wpa_supplicant</c>.

  <ti>any</ti>

  <ti><c>any</c></ti>

  <ti>preferredonly</ti>

  <ti><c>preferredonly</c></ti>

  <ti>forcepreferred</ti>

  <ti><c>forcepreferred</c></ti>

  <ti>forcepreferredonly</ti>

  <ti><c>forcepreferredonly</c></ti>

  <ti>forceany</ti>

  <ti><c>forceany</c></ti>

Finally we have some blacklist_aps and unique_ap selection. blacklist_aps works

Finally we have some <c>blacklist_aps</c> and <c>unique_ap</c> selection.

in a similar way to preferred_aps. unique_ap is a yes or no value that says if a

<c>blacklist_aps</c> works in a similar way to <c>preferred_aps</c>.

second wireless interface can connect to the same Access Point as the first

<c>unique_ap</c> is a yes or no value that says if a second wireless interface

interface.

can connect to the same Access Point as the first interface.

  <ti>iwconfig_eth0</ti>

  <ti><c>iwconfig_eth0</c></ti>

  <ti>See the iwconfig man page for details on what to send iwconfig</ti>

  <ti>See the iwconfig man page for details on what to send <c>iwconfig</c></ti>

  <ti>iwpriv_eth0</ti>

  <ti><c>iwpriv_eth0</c></ti>

  <ti>See the iwpriv man page for details on what to send iwpriv</ti>

  <ti>See the iwpriv man page for details on what to send <c>iwpriv</c></ti>

  <ti>sleep_scan_eth0</ti>

  <ti><c>sleep_scan_eth0</c></ti>

  <ti>0</ti>

  <ti><c>0</c></ti>

  <ti>sleep_associate_eth0</ti>

  <ti><c>sleep_associate_eth0</c></ti>

  <ti>5</ti>

  <ti><c>5</c></ti>

  <ti>associate_test_eth0</ti>

  <ti><c>associate_test_eth0</c></ti>

  <ti>MAC</ti>

  <ti><c>MAC</c></ti>

    Some drivers do not reset the MAC address associated with to an

    Some drivers do not reset the MAC address associated with to an invalid one

    invalid one when they loose or attempt to associate.

    when they loose or attempt to associate. Some drivers do not reset the

    Some drivers do not reset the quality level when they loose

    quality level when they loose or attempt assocciation. Valid settings are

    or attempt assocciation.

    <c>MAC</c>, <c>quality</c> and <c>all</c>.

    Valid settings are MAC, quality and all.

  <ti>scan_mode_eth0</ti>

  <ti><c>scan_mode_eth0</c></ti>

    try setting ad-hoc here

    try setting <c>ad-hoc</c> here

  <ti>iwpriv_scan_pre_eth0</ti>

  <ti><c>iwpriv_scan_pre_eth0</c></ti>

    Sends some iwpriv commands to the interface before scanning.

    Sends some <c>iwpriv</c> commands to the interface before scanning.

    See the iwpriv man page for more details

    See the iwpriv man page for more details.

  <ti>iwpriv_scan_post_eth0</ti>

  <ti><c>iwpriv_scan_post_eth0</c></ti>

    Sends some iwpriv commands to the interface after scanning.

    Sends some <c>iwpriv</c> commands to the interface after scanning.

    See the iwpriv man page for more details

    See the iwpriv man page for more details.

Someones when you connect to ESSID1 you need a static IP and when you connect to

Someones when you connect to <e>ESSID1</e> you need a static IP and when you

ESSID2 you need DHCP. Infact most module variables we can change per ESSID.

connect to <e>ESSID2</e> you need DHCP. Infact most module variables we can

Here's how we do this.

change per ESSID. Here's how we do this.

You <e>will</e> need to consult the

You <e>will</e> need to consult the <uri

<uri link="?part=4&amp;chap=2#variable_name">variable name</uri>

link="?part=4&amp;chap=2#variable_name">variable name</uri> documentation.

documentation.