Subject: Re: (Revisiting) Using airport- doesn't anyone know?
From: Brice D Ruth (brice@webprojkt.com)
Date: Mon Jun 25 2001 - 13:45:37 MDT
I'm not entirely clear on what your network setup is like - your cable
modem receives an IP address from your cable provider via DHCP, right?
So you have the AirPort 'Internet' tab setup to use DHCP - then the
'Network' tab is setup to *not* give out addresses, right? So in doing
so, you have NAT setup, so that your base station is 10.0.1.1 and your
Powerbook is 10.0.1.x, right? Clear me up on this, just to make sure
there's nothing funky going on there.
As for the encryption - I haven't had *any* success using WEP on my
network unless I'm running exclusively MacOS. Don't *really* know why,
I've read all the docs, input the WEP keys manually - I even got my
laptop to the point that the WEP authentication worked, it was able to
get an IP address from the AirPort base station, but then nothing really
worked. Explain that! Very screwy - I create a closed network now
(webprojkt) which I hope nobody in my apt. building will figure out :)
My current AirPort setup is actually pretty simple - I have a firewall
that is hooked up to the cable modem via static IP which gives out IP
addresses on 10.0.0.x via its second interface. The AirPort is setup to
simply bridge - basically do nothing.
Yeah - the arp stuff isn't necessary. I only did the first time,
thereafter (when I rebooted my iMac) I forgot to do it & things still
worked.
I'll try to see if email is somehow handled differently - I use Mozilla
0.9.1 and on occasion, Netscape 4.77 for email, so if your culprit is an
M$ product, I can't be of help there. But, that would be seriously strange.
Oh - about the 5.5M - that's what I have my AirPort set to. I set it to
11M as well, measured the actual speed and got nowhere close to it, so I
dropped it down - the higher the speed setting, the lower the range, so
I traded signal strength for speed.
Sincerely,
Brice Ruth
William K. Gibson wrote:
> on 6/21/01 6:27 PM, Brice D Ruth at brice@webprojkt.com wrote:
>
> 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
> *
>
>
>
> I'm curious, why did you set your rate to 5.5 instead of the standard 11?
>
>
> 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!).
>
>
> I should mention that I am not using DHCP on the base station. I'm
> connected to a cable modem via DHCP, and using DHCP from the base
> station does not work. I have made a lan on 10.0.1.x instead with the
> Base station acting as a router over ethernet and air. Oh, I'm also
> using encryption so I have to give the airport module the encryption
> number- or whatever its called that I cannot remember right this moment.
>
>
> *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 have a few issues with this web page. One is here
>
> > # echo "1" > /proc/sys/net/ipv4/conf/tap0/proxy_arp
> > # /sbin/arp -s 192.168.0.2 FE:FD:00:00:00:00 pub
>
> He says to make an arp entry manually- but simply using tap0 will
> automatically produce an entry in the arp table- so I don't think that
> is nessesary.
>
> 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.
>
> The slowness I experienced was not so much with a web browser but in
> *downloading email*. The log in and subsequent downloading of email
> (from MS outrage express) would take many many minutes for simply one
> 2K message. I do not experience this behavior in MOL when using the
> ethernet cable connected to the base station. Try your email program
> and see what results you get.
>
> Oh, that makes me wonder. I wonder if there is a subsequent slow down
> in email on the linux side when using airport? I'll have to check.
>
>
> --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 : Mon Jun 25 2001 - 12:50:52 MDT