Subject: Re: (Revisiting) Using airport- doesn't anyone know?
From: Brice D Ruth (brice@webprojkt.com)
Date: Thu Jun 21 2001 - 16:27:53 MDT
OK, here's where I am so far (not that this will really help you, its
mainly an FYI)
I'm running the LinuxPPC default 2.2.18-4hpmac kernel, with the included
airport module (by Ben) that creates an airport device (airport-0.9.3).
I insmod the airport.o module and use the iwconfig application provided
by wireless-tools <http://www.fasta.fh-dortmund.de/users/andy/wvlan/> .
I believe I did something like so:
*/sbin/iwconfig airport essid "webprojkt" rate 5.5M*
Running */sbin/iwconfig* again showed me that the AirPort card had
indeed found the base station (yay!). Next up was getting an IP address
- this ended up being simple enough, I simply ran */sbin/dhcpcd -d
airport* and it came back almost immediately with a valid address and
configured my DNS and all (yay!).
So, I checked out some websites via X and they seemed to come up all
right, so I figured that networking was working well. My only
disappointment was that apparently my link quality is PISS POOR despite
the 'AirPort' app in MacOS singing a different tune (when I'm booted
directly into MacOS). My quality is 14/92 ... my laptop's link quality
is 30/92 (not great either) and it doesn't have any built-in antennae
(just a PCMCIA card).
Anyway. I then rsync'd the latest MOL via Sam's directions, compiled &
built MOL w/o any problems. Configured mol for my machine and all and
then got to the networking. I used a tap device this time around - so
my netdev line looked like this:
*netdev: tap0
*Then I pretty much to the letter followed the instructions for setting
up a tapdevice found here:
http://www.turbolinux.com/~brad/mol/#net
I simply used 192.168.1.1 as my tap0 device address and changed
everything appropriately for that. I started up MOL and it booted my
MacOS 9.1 system just fine - went into my TCP/IP settings and continued
to follow the instructions listed above. I then loaded up Mozilla
(0.9.1 if you must know :)) and checked out slashdot.org - according to
Mozilla, the page finished loading after 35.545 seconds. Checking out
interactive8.webprojkt.com (a site that I own, so I know that the server
won't be bogged down or anything) loaded in about 4.864 seconds. Going
to the same site via my laptop (also wireless) loaded in 5.513 seconds.
So - at the very least, I'm not experiencing the dramatic slow down that
you're reporting, and this is a good thing. Now, I just need to get
closer to your actual environment - so I'll need to grab the kernel you
have and all that. My issues with the 2.4 series kernels previously was
that I couldn't get anything to display w/ aty128fb (almost immediately
after the kernel started to boot, the screen went blank & never came
back!). Let's hope that I can get around this now!
Regards,
Brice Ruth*
*
William K. Gibson wrote:
>on 6/19/01 5:46 PM, Brice D Ruth at brice@webprojkt.com wrote:
>
>>Just to refresh my memory, what hardware are you running and what distribution
>>are you running? As many details (however insignificant they may seem) as you
>>can provide will help.
>>
>
>Ok, thanks.
>
>I'm using a Titanium powerbook. Originally I started with YDL 1.2 but I
>upgraded to ben's kernel (Linux PPC 2.4.5) in order to take advantage of
>airport and other items. I compiled the kernel myself and tried my darndest
>to include all the options I would need - including legacy tap0 stuff and
>legacy ipchains. Well, ipchains refuses to work in spite of this so I
>switched to iptables anyway. Most of the options came with help, except for
>the airport, which did not. I still don't understand why the airport module
>comes up as eth1 instead of airport.
>
>Again, I'm using the Base Station as a router to my little private network.
>The Base Station itself connects through DHCP to a cable modem.
>
>Here is an interesting tidbit though. When ifconfig brings up both eth0 and
>eth1 and I ping a site- the ping travels from the eth0 interface in spite of
>the fact that I have set eth1 as the gateway device. I verified this by
>setting eth0 and eth1 to two seperate IP addresses and also unplugging the
>ethernet cable from the machine. If I call 'ifconfig eth0 down' and then
>ping, it uses the eth1 interface. Weird- but maybe its just how ping works?
>
>
>
>--William K. Gibson
>1stDesk Systems
>firstdesk@columbus.rr.com
>
-- WebProjkt, Inc. (ph) 773.562.1008 (fax) 608.204.7004 http://www.webprojkt.com/
This archive was generated by hypermail 2a24 : Thu Jun 21 2001 - 15:33:41 MDT