FC-6 and wireless

Where can I get information on the settings for ifcfg-wifi0 configuration
file?

I have the wireless working with a script that I wrote but I want to
automate it so it follows the setup of an ethernet card on boot up.
When using the ifcfg-wifi0 settings it starts slowly and when it does come
up ping doesn't work(destination unreachable). ifconfig shows it up and
iwconfig shows it working. Route shows the proper default gw.

here is my script - it works
#!/bin/sh
/sbin/modprobe ath_pci
/sbin/modprobe wlan_scan_sta
/sbin/ifconfig ath0 up
/usr/local/bin/wlanconfig ath0 list scan
/sbin/iwconfig ath0 essid "linksys"
/sbin/ifconfig ath0 192.168.1.25 netmask 255.255.255.0 up
route add default gw 192.168.1.1

Here if my ifcfg-wifi0 - this doesn't
I have changed the onboot to no so it won't hang on bootup, I change it to
yes and then issue a /etc/rc/d/init.d/network restart and it fails. This
is after a fresh boot and without running my script.

client@client ~]$ cat /etc/sysconfig/network-scripts/ifcfg-wifi0

# Atheros Communications, Inc. AR5005G 802.11abg NIC
DEVICE=wifi0
ONBOOT=no
BOOTPROTO=static
HWADDR=00:13:f7:41:22:88
IPADDR=192.168.1.20
NETMASK=255.255.255.0
BROADCAST=192.168.1.255
NETWORK=192.168.1.0
GATEWAY=192.168.1.1
TYPE=Ethernet
USERCTL=no
IPV6INIT=no
PEERDNS=yes
WIRELESS_ESSID='linksys'
STARTMODE=auto

--
Dancin in the ruins tonight
Tayo'y Mga Pinoy

On 2006-12-29, Baho Utot <(E-Mail Removed)> wrote:
> here is my script - it works
> #!/bin/sh
> /sbin/modprobe ath_pci
> /sbin/modprobe wlan_scan_sta

You'll have to have the modprobes done in /etc/modprobe.conf

> /sbin/iwconfig ath0 essid "linksys"
> /sbin/ifconfig ath0 192.168.1.25 netmask 255.255.255.0 up
> route add default gw 192.168.1.1
>
> # Atheros Communications, Inc. AR5005G 802.11abg NIC
> DEVICE=wifi0

if your device is ath0, why is here defined as wifi0?

> ONBOOT=no

Having 'onboot=no' means that the network card will not be activate
in autometic.

> IPADDR=192.168.1.20

in the previous configuration the ip was .25, not .20

> GATEWAY=192.168.1.1

The gateway is not defined per-network card, is a global configuration
on the whole machine, so do not put 'gateway' in there.

> WIRELESS_ESSID='linksys'

the parameter is just 'ESSID'

Davide

--
Windows: an Unrecoverable Acquisition Error!

Davide Bianchi wrote:

> On 2006-12-29, Baho Utot <(E-Mail Removed)> wrote:
>> here is my script - it works
>> #!/bin/sh
>> /sbin/modprobe ath_pci
>> /sbin/modprobe wlan_scan_sta
>
> You'll have to have the modprobes done in /etc/modprobe.conf

OK, but I think this is what FC6 is looking at
from /etc/modprobe.conf
alias wifi0 ath_pci

FC6 setup the ifcfg.wifi0, I didn't and don't understand it.

>
>> /sbin/iwconfig ath0 essid "linksys"
>> /sbin/ifconfig ath0 192.168.1.25 netmask 255.255.255.0 up
>> route add default gw 192.168.1.1
>>
>> # Atheros Communications, Inc. AR5005G 802.11abg NIC
>> DEVICE=wifi0
>
> if your device is ath0, why is here defined as wifi0?
>

That's what FC6 did, I followed madwifi's instructions for my script so they
are separate. I hope it cause no trouble.

>> ONBOOT=no
>
> Having 'onboot=no' means that the network card will not be activate
> in autometic.

Yes I change it after I bootup so it won't hang then I issue a network
restart from ..../init.d

>
>> IPADDR=192.168.1.20
>
> in the previous configuration the ip was .25, not .20

I farted that up they should be the same. Thanks

>
>> GATEWAY=192.168.1.1
>
> The gateway is not defined per-network card, is a global configuration
> on the whole machine, so do not put 'gateway' in there.
>

Ok, I`ll kill it

>> WIRELESS_ESSID='linksys'
>
> the parameter is just 'ESSID'
>

OK, I`ll try that.

> Davide
>

Thanks for the help, I may just get this working.
I hope it doesn't kill me

--
Dancin in the ruins tonight
Tayo'y Mga Pinoy

On 2006-12-29, Baho Utot <(E-Mail Removed)> wrote:
> OK, but I think this is what FC6 is looking at
> from /etc/modprobe.conf
> alias wifi0 ath_pci

Ah, ok this bit was missing in your original post. So, when the module
ath_pci is loaded, is wifi0 created or not?

Davide


--
Me: When I start my motorbike I'm sitting ON it, not standing in front of
it and looking at the light.
He: This is the difference between a Sysadmin and a Developer I guess...

Davide Bianchi wrote:

> On 2006-12-29, Baho Utot <(E-Mail Removed)> wrote:
>> OK, but I think this is what FC6 is looking at
>> from /etc/modprobe.conf
>> alias wifi0 ath_pci
>
> Ah, ok this bit was missing in your original post. So, when the module
> ath_pci is loaded, is wifi0 created or not?
>
> Davide
>
>

Yes
I continued to do some digging and found out that the madwifi driver always
makes ath0 and wifi0 when loaded (modprobe ath_pci)

I found out that the wifi0 is useless, why it is made I don't know.
I`ll fixup ifcfgwifi0 to use ath0 and let it fly and see what happens

Thanks
--
Dancin in the ruins tonight
Tayo'y Mga Pinoy

On 2006-12-29, Baho Utot <(E-Mail Removed)> wrote:
> I continued to do some digging and found out that the madwifi driver always
> makes ath0 and wifi0 when loaded (modprobe ath_pci)

hummm... madwifi... I remember something about it, if I remember
correctly, the wifi0 is a 'middle' device that is then used to create
the ath0 one that is the correct one to use.

Davide

--
Have you ever noticed that at trade shows Microsoft is always the
one giving away stress balls...
-- From a Slashdot.org post

Davide Bianchi wrote:

> On 2006-12-29, Baho Utot <(E-Mail Removed)> wrote:
>> I continued to do some digging and found out that the madwifi driver
>> always makes ath0 and wifi0 when loaded (modprobe ath_pci)
>
> hummm... madwifi... I remember something about it, if I remember
> correctly, the wifi0 is a 'middle' device that is then used to create
> the ath0 one that is the correct one to use.
>
> Davide
>

Changing the DEVICE=wifi0 to DEVICE=ath0
in /etc/sysconfig/networking-scripts/ifcfg-wifi0 made it work.

Thanks

--
Dancin in the ruins tonight
Tayo'y Mga Pinoy