On Sunday 31 July 2005 04:51 pm, John Wilson wrote: > On July 31, 2005 02:21 pm, Dennis Myers wrote: > > On Sunday 31 July 2005 09:59 am, Mikkel L. Ellertson wrote: > > > Dennis Myers wrote: > > > > On Saturday 30 July 2005 04:50 pm, John Wilson wrote: > > > >>On July 30, 2005 02:01 pm, Mikkel L. Ellertson wrote: > > > >>> You have lost me here. What do you mean when you say ifcfg-wlan0 is > > > >>>pointing to the MAC address? If you are using "HWADDR=<MAC > > > >>> address>", you still need the correct "DEVICE=<something>" > > > >>> statment. > > > >>> > > > >>>The "DEVICE=<something>" statment in the ifcfg-wlan0 file is what > > > >>>determins what device is being set. If it is something like > > > >>>"DEVICE=eth0" instead of "DEVICE=wlan0", then you will get the type > > > >>> of errors you have reported. > > > >>> > > > >>>Here is one that works: > > > >>>DEVICE=wlan0 > > > >>>BOOTPROTO=dhcp > > > >>>ONBOOT=no > > > >>>MII_NOT_SUPPORTED=no > > > >>>WIRELESS_MODE=Managed > > > >>>WIRELESS_ESSID="AP_ROUTER" > > > >>>WIRELESS_ENC_KEY=1234-5678-6804-3A0D-BDCB-487E-00 > > > >>>WIRELESS_IWCONFIG="key restricted" > > > >>>NEEDHOSTNAME=no > > > >>> > > > >>>It is for a loptop cardbus card. For a built-in card, you would > > > >>> probably want to change ONBOOT=no to ONBOOT=yes. > > > >>> > > > >>>You may want to read the section in > > > >>>/usr/share/doc/initscripts-7.61.1/sysconfig.txt about ifcfg-<device> > > > >>>files. > > > >>> > > > >>>Mikkel > > > >> > > > >>I fixed it up and the file now reads: > > > >>DEVICE=wlan0 > > > >>BOOTPROTO=dhcp > > > >>ONBOOT=yes > > > >>#HWADDR=00:11:f5:61:56:dc > > > >>METRIC=0 > > > >>MII_NOT_SUPPORTED=no > > > >>#USERCTL=no > > > >>WIRELESS_MODE=Managed > > > >>WIRELESS_ESSID="yrr18itta3" > > > >>DHCP_CLIENT=dhclient > > > >>NEEDHOSTNAME=no > > > >>#PEERDNS=yes > > > >>#PEERYP=no > > > >>#PEERNTPD=no > > > >> > > > >>The DEVICE=wlan0 was always there. Let me try this and see. > > > >> > > > >>The other issue was that the ESSID wasn't contained in quotes and > > > >> that was set in the wizard in MCC that way. So I'm wondering about > > > >> that too now. If that has messed this up then I guess a bug report > > > >> is in order. > > > >> > > > >>ttfn > > > >> > > > >>John > > > > > > > > I believe that METRIC=0 should be METRIC =1 or 5 or such but not 0. > > > > and also my ifcfg-wlan0 file does not have the ESSID=any or netmare > > > > or whatever I call my network in quotes, so that appears a bit out of > > > > the ordinary. must be about there. > > > > > > Quotes around the entry are optional unless the value has a space in > > > it. Then you have to have the quotes or it is treated as more then one > > > value. The same rules apply as when setting shell varables in a scrip. > > > The ifcfg-<device> files are basicly script files that are sourced by > > > the ifup and ifdown scripts in order to get the different values > > > needed. > > > > > > Mikkel > > > > Ah, Thanks for that explanation. What about the METRIC number? That > > should have a value greater than 0 should it not? > > If 0 is ok then the scripts should be giving him a connection. > > Part of the problem seems to be that wlan0 is being mapped to eth0 > somewhere because on network restart I'm getting a message that says my > EXTERNAL eth0 fails to come up. > > Now, forgive me if I'm thick, but my eth0, internal I assume, is connected > to the router by a cable at the moment and it seems to be working because > I'm sending this. > > I've looked over all the config files and can't see it. Or I'm missing the > blazingly obvious because I've looked at it so many times. Either is > possible. > > Another possibility is that it isn't correctly using the driver for my card > which is ath_pci. One remaining possibility is the script that supplies > the information to the card. > > Anyway, I'm taking a day off of this battle because I need it. :-) > > There is such a thing as looking at it so long that you can no longer see > the dog dodo you're about to step in. :-) > > ttfn > > John John, do you per chance have the lan cable plugged in to the laptop? -- Dennis M. linux user #180842
____________________________________________________ Want to buy your Pack or Services from Mandriva? Go to http://store.mandriva.com Join the Club : http://www.mandrivaclub.com ____________________________________________________
