Airport/iBook/YDL3.0 problems

Sat May 17 09:17:00 2003

I tried setting the rate, but no joy.

I've been playing around with some stuff I found on the net regarding
getting this card to work; I have seen some interesting information which
I'm not sure applied to YD3. First, I've read that the Airport doesn't
support DHCP. Can anyone confirm/deny this?

Also, /sbin/ifup eth1 is giving me the following information:

Error for wireless request "Set Encode" (8B2A) :
    SET failed on device eth1 ; Operation not supported.

This coupled with the errors I was recieving in an earlier post about
differing versions of Wireless Extension leads me to believe that either
the Airport modules with YD3 or the wireless-tools is out of date.

Should I try to update the module and wireless tools? Looking at Jean's
wireless page it seems the wireless tools is up to version 20+.

To tell the truth I feel a little intimidated having to recompile my
kernel (for the airport.o module) and the wireless tools. Can anyone
suggest a method of working around this, or even somewhere I could pick up
some RPMs to do the above for me?

As a friend told me, the problem seems fixable (thanks to the fairly
verbose error messages I'm recieveing, I think I can pinpoint where I'm
going wrong). Just as an aside, does /anyone/ have a working
iBook2/Airport combo working with YDL?

Cheers,

--Jon

>>>>>> "Jon" == Jon Atkinson <jonathana@cleanstick.org> writes:
>
>     Jon> Okay, I've made some progress: Following the advice in a
>     Jon> parallel post, I added KEY="" to my
>     Jon> /etc/sysconfig/network-scripts/eth1. Now the GUI tool works
> Jon> fine, so I think we can forget about it for now :-)
>
>     Jon> As for running iwconfig, I did what you suggested.
>
>     Jon> Now the top line of my iwconfig gives ESSID "Wireless", and
> Jon> the nickname has been set to my hostname (which is 'randall',
> Jon> incidentally).
>
>     Jon> The access point is still 44:44:44:44:44:44, and the link Jon>
> quality is still at 0.
>
>     Jon> Any more ideas?
>
> I have one, it's worth a try anyway. I found after getting a linksys
> wireless hub, I had to add the rate to the iwconfig command to get the
> card to find the wireless router consistently:
>
> iwconfig eth1 .... rate 11M
>
> it might help.
> Mike
>
>     >>
>     >> 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
>     >>
>     >> _______________________________________________
>     >> yellowdog-general mailing list
>     >> yellowdog-general@lists.terrasoftsolutions.com
>     >> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
>
>
>
>     Jon> _______________________________________________
>     Jon> yellowdog-general mailing list
>     Jon> yellowdog-general@lists.terrasoftsolutions.com
>     Jon>
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
>
>
> --
> ydl@mikesoffice.com
> _______________________________________________
> yellowdog-general mailing list
> yellowdog-general@lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general