Airport in BenH's kernels

Airport in BenH's kernels

[Michel Lanners]

[-- Attachment #1: Type: TEXT/plain, Size: 518 bytes --]

Hi all,

For a few days airport doesn't work in BenH's kernels, due do an
unresolved symbol in orinoco.o.

Below is a two-line patch that fixes the problem.

Have fun!

Michel

-------------------------------------------------------------------------
Michel Lanners                 |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes            |    Ask Questions.  Make Mistakes.
L-1710 Luxembourg              |
email   mlan@cpu.lu            |
http://www.cpu.lu/~mlan        |                     Learn Always. "

[-- Attachment #2: orinoco.patch --]
[-- Type: TEXT/plain, Size: 343 bytes --]

--- /usr/src/sources/2.4/linux-2.4.benh/drivers/net/wireless/orinoco.c	Sun May  6 18:32:27 2001
+++ drivers/net/wireless/orinoco.c	Sun May  6 22:00:56 2001
@@ -3520,7 +3520,9 @@
 	return 0;
 }

+#ifdef ORINOCO_DEBUG
 EXPORT_SYMBOL(dldwd_debug);
+#endif
 EXPORT_SYMBOL(dldwd_init);
 EXPORT_SYMBOL(dldwd_xmit);
 EXPORT_SYMBOL(dldwd_tx_timeout);

Re: Airport in BenH's kernels

[Benjamin Herrenschmidt]

>Hi all,
>
>For a few days airport doesn't work in BenH's kernels, due do an
>unresolved symbol in orinoco.o.
>
>Below is a two-line patch that fixes the problem.

Thanks ! The driver have been a pretty quickly moving target lately
as Jean Tourrihles and I were working to finally have a common code
base for airport and orinoco_cs without duplicating the driver.

The new driver is getting close to completion now and things should
finally stabilize.

For those who missed part of the story, here are some tips for the
new driver:

 - it's located in drivers/net/wireless and configured from the
"wireless" sub-menu in the "network drivers" menu.

 - the interface is now always ethx (eth1 most of the time)

 - the card is no longer powered down when the inteface is off, this
caused various troubles. If you want to make sure the interface is
powered off when not used, rmmod airport.

 - typicall setup sequence:

    modprobe airport
    ifconfig eth1 <ip_address> netmask <mask> up
    iwconfig essid <network name>
    iwconfig enc <WEP key>

The driver is made of 3 different modules (hermes.o, orinoco.o and
airport.o). A fourth one (orinoco_cs.o) is used for the PCMCIA cards.
This new driver should work properly with all airport incarnations, not
only PCMCIA capables boxes.

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Airport in BenH's kernels (a few tips & tricks)

[Michel Lanners]

Hi all,

On   6 May, this message from Benjamin Herrenschmidt echoed through cyberspace:
>  - typicall setup sequence:
>
>     modprobe airport
>     ifconfig eth1 <ip_address> netmask <mask> up
>     iwconfig essid <network name>
>     iwconfig enc <WEP key>

Here is my take at integrating the configuration with a Debian system
(most of this is applicable to other systems as well, with slight
modifications):

- Add an entry for eth1 into /etc/network/interfaces, in my case with
  the same config as eth0, and since I mostly use the TiBook at home,
  default to eth1:

-------------------------------
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)

auto lo eth1

# The loopback interface
iface lo inet loopback

# The first network card - this entry was created during the Debian installation
iface eth0 inet static
        address 172.20.8.26
        netmask 255.255.255.0
        network 172.20.8.0
        broadcast 172.20.8.255
        gateway 172.20.8.1

# Airport module
iface eth1 inet static
        address 172.20.8.26
        netmask 255.255.255.0
        network 172.20.8.0
        broadcast 172.20.8.255
        gateway 172.20.8.1
---------------------------

Now, when I'm too far away in the house from the base station, or when
airport doesn't work once again (;-), I can ifdown eth1; ifup eth0 do
switch interfaces.

In order to config wireless stuff, I added this in
/etc/modutils/airport:

----------------------------
# Airport modules config file

alias eth1 airport

post-install airport /etc/network/airport-config
-----------------------------

Run update-modules, and you're in business.

The file /etc/network/airport-config contains the wireless-specific part
of the eth1 config:

-----------------------------
#!/bin/sh

# Cater for wireless tools installed locally
PATH=$PATH:/usr/local/sbin

# Airport interface config commands
# sets up crypto and stuff

ifconfig eth1 up

iwconfig eth1 nick <nick> mode Managed
iwconfig eth1 rate Auto
iwconfig eth1 essid <Network name>
iwconfig eth1 key <Encryption Key>
iwconfig eth1 enc on
iwconfig eth1 enc restricted

# This adds too much delay...
#iwconfig eth1 power on
--------------------------

With this config, everytime the airport module is inserted, all the
relevant wireless parameters are set. With the airport card not being
powered down anymore on ifconfig down, this should be all you need to
do.

Have fun!

Cheers

Michel

-------------------------------------------------------------------------
Michel Lanners                 |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes            |    Ask Questions.  Make Mistakes.
L-1710 Luxembourg              |
email   mlan@cpu.lu            |
http://www.cpu.lu/~mlan        |                     Learn Always. "


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Airport in BenH's kernels

[Paul Nasrat]

On Sun, May 06, 2001 at 10:28:01PM +0200, Benjamin Herrenschmidt wrote:
>

> Thanks ! The driver have been a pretty quickly moving target lately
> as Jean Tourrihles and I were working to finally have a common code
> base for airport and orinoco_cs without duplicating the driver.
>
> The new driver is getting close to completion now and things should
> finally stabilize.

OK - I'm not a major C hacker but I'm trying to get a good feel for the driver with my interest in 802.11b generally.  What seems interesting is that the MacOS software config's the card so that a linux box running managed mode can pick it up easily.  It seems to be the most accesible point to access to infrastructure mode.

I'd like to look into writing stuff for this - as well as potentially some user space stuff for ad-hoc networking.  I probably need some pointers on endian clean programming but just a url/book ref and I'll get stuck in.

Paul

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Airport in BenH's kernels

[Benjamin Herrenschmidt]

>
>OK - I'm not a major C hacker but I'm trying to get a good feel for the
>driver with my interest in 802.11b generally.  What seems interesting is
>that the MacOS software config's the card so that a linux box running
>managed mode can pick it up easily.  It seems to be the most accesible
>point to access to infrastructure mode.
>
>I'd like to look into writing stuff for this - as well as potentially
>some user space stuff for ad-hoc networking.  I probably need some
>pointers on endian clean programming but just a url/book ref and I'll get
>stuck in.

You should really contact Jean Tourrilhes <jt@bougret.hpl.hp.com>

He's the one who know the most about all this (and he maintains the
wireless tools)

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/