Airport/iBook/YDL3.0 problems

[Stefan Bruda]

Aha, we are getting somewhere. :-) First, the wireless settings are
not correct.  Indeed,

At 21:24 +0100 on 2003-5-15 Jon Atkinson wrote:
 >
 > Okay, /sbin/iwconfig eth1 gives the following output:
 > 
 > IEEE 802.11-DS ESSID:"" Nickname:"HERMES I"

You should have something like ESSID:"something" instead of ESSID:"".
It looks like you did not enter a value for ESSID or that your GUI
tool (with which I am not familiar, sorry) does not pass this value
forward (i.e., to the card).

What I can suggest is the command line for the (dreaded) iwconfig to
make things work (one hopes anyway ;-) ).  If using iwconfig leads to
a working network then at least you will know that the GUI tool is the
culprit.  So, I will assume that the ESSID of the network is the same
as for the x86 laptop, i.e. "Wireless" (if this is not so modify this
string appropriately).  Do then

    /sbin/iwconfig eth1 mode Managed essid "Wireless"

(I also assume that you do not use encryption, I seem to recall from a
previous post that you do not).

Now keep your fingers crossed and do again

    /sbin/iwconfig eth1

The information should by now be similar to the one given on your x86
machine for the same command.

 > Mode: Managed Frequency:2.422Ghz Access Point: 44:44:44:44:44:44

This is again strange, but I guess that the cause is actually the
impossibility of the Airport to join the wireless network because of
the incorrect ESSID.

 > Link Quality:0/92 signal level:134/153 noise level:134/153

Again straange and again it might just be because of the Airport
misconfiguration.

And then we get to the routes, which do not exist!

 > /sbin/route -n on the iBook is:
 > 
 > Kernel IP routing table
 > Destination  Gateway  Genmask    Flags Metric Ref Use Iface
 > 127.0.0.0    0.0.0.0  255.0.0.0  U     0      0   0   lo

That means no routes (except for the local loop which has nothing to
do with the wireless network).

Well, that may be again because of the incorrect setup of the card.
So let us postpone the discusion because this problem may
automagically go away once you bring your Airport up.

Anyway, I would suggest trying the above commands.  Get then back to
us with the result and we can go from there.

Cheers,
Stefan

-- 
If it was so, it might be; and if it were so, it would be; but as
it isn't, it ain't. That's logic.
    --Lewis Carroll, Through the Looking-Glass