iwreless woes

[yellocj7]

after several days of work, I've got my network card working. In open mode it will do everything. in secured mode it does nothing. ive entered the correct key, it knows the access point's mac address, but will not communicate with the access point. I'm sure it's some thing silly that i cant see. here is a copy of my ifcfg file.

USERCTL=no
PEERDNS=no
GATEWAY=192.168.0.1
TYPE=wireless
DEVICE=ath0
BOOTPROTO=dhcp
ONBOOT=yes
MODE=managed
ESSID=my network
KEY=xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xx
CHANNEL=6
RATE=auto

any help is appreciated.

[Ug]

I take it your using FC3?

[Artemis]

I recently figured out that when I activate my wireless card on boot, the card will not connect to the access point. But when I activate the device manual in 'system-control-network', everything works fine.

[Brian1]

To Artemis

Let me ask you this. Do you have an internal nic on the notebook and is assigned eth0 and your wireless is eth1. Do you have eth0 starting up as well as eth1 on boot? If so make eth0 disabled and enable eth1 on boot. If that does not work I wrote a simple script to turn off the eth0 and enable eth1. You can also add the following lines to your /etc/rc.local at the end


#!/bin/sh
#
# This script will be executed *after* all the other init scripts.
# You can put your own initialization stuff in here if you don't
# want to do the full Sys V style init stuff.

sudo /sbin/ifdown eth0
ping -c2 127.0.0.1
sudo /sbin/ifup eth1


As above I am using the ping statement as a pause to allow something to finish so as not to confuse others. Also I am using sudo so as I can use the ifup command as a user for myself. You can do the same or make ifup and ifdown available to all by changing permissions.

I have created a script that I can click on the Desktop and bring down eth0 and eth1 up.


sudo /sbin/ifdown eth0
ping -c2 127.0.0.1
sudo /sbin/ifup eth1
ping -c2 127.0.0.1
xmessage -center -file /storage1/Applications/networkinfo/home_eth0_down_eth1_up.


In the above I have a txt file that says that eth0 is down and eth1 is up called networkinfo/home_eth0_down_eth1_up. This displays on the screen so I know the script completed.

Brian1
" Google the Linux way @ http://www.google.com/linux "

[yellocj7]

I'm using fedora core3 with a dlink dwl-g520 wireless card and madwifi drivers. After more searching I discovered a step that I was missing on the madwifi faq. I needed to force the authentication to restricted mode with the command
"iwpriv ath0 authmode 2" That command allowed me to communicate with the router. With a little more fiddling i am now connected to the internet (typing this post on my Fedora linux computer) thanks for the help.

[Artemis]

To Artemis

Let me ask you this. Do you have an internal nic on the notebook and is assigned eth0 and your wireless is eth1. Do you have eth0 starting up as well as eth1 on boot? If so make eth0 disabled and enable eth1 on boot. If that does not work I wrote a simple script to turn off the eth0 and enable eth1. You can also add the following lines to your /etc/rc.local at the end


Nope, I have just a tower with only a pci wireless card in it, named ra0.

[Brian1]

Just a guess but how about adding the following to your /etc/rc.local file. You could try it in a terminal and see if it works before adding to /etc/rc.local. I assume it is still called eth0 here.

/sbin/ifdown eth0
/sbin/ifup eth0

See if that brings it up. It not it will require a little more work. If I get time I might review my notes on nics.
Brian1