FC-4 Wireless Problem

[Teilhard Knight]

----- Original Message ----- 
From: Stephen Hess
To: fedora-list at redhat.com
Sent: Tuesday, January 17, 2006 2:07 PM
Subject: FC-4 Wireless Problem


<First, don't let that error throw you. If the box is checked in the 
"system-network-config" app then it pegs on my laptop but I can still 
connect.>

That sounds good. But I haven't been able to.

<I am assuming you have installed and configured ndiswrapper to be able to 
use your wireless card. If not there is a very good link here...

http://forums.fedoraforum.org/forum/showthread.php?t=29659&highlight=ndiswrapper>

Actually, I do not need it. Fedora recognizes my card out of the box and 
installs the correctdriver.

<Even after all that - you will still get that error. I know, I spent a 
little time looking for a fix all over the internet and nothing.>

This is good to know.

<Next, you need to setup your wifi card to connect to your network. 
Everytime I tried to use the network applet it gives the error and does not 
configure the card. The commands I need I put into the /etc/rc.local which I 
have listed below.

#######################################################################
#!/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.

touch /var/lock/subsys/local
/sbin/modprobe nvidia

# wlan0 config commands...

/sbin/iwconfig wlan0 essid Nutshell
#/sbin/iwconfig wlan0 essid linksys
/sbin/iwconfig wlan0 key 2656D42A95EE03E89998FBF58C
#/sbin/iwconfig wlan0 key off
/sbin/ifconfig wlan0 up
/sbin/dhclient wlan0


#Command to correct sound setting for Enemy Territory
echo "et.x86 0 0 direct" > /proc/asound/card0/pcm0p/oss

# Entries to allow Sierra Wireless EVDO card to be enabled
modprobe usbserial  vendor=0x1199 product=0x112
mknod /dev/ttyAirCard0 c 188 0

########################################################################

Set your essid
Set your WEP key
Bring your interface up
Tell wlan0 it is dhcp>

I think I wouldn't know how to adapt, things like the last entry to my case.

<Now, I am connected. You should be too. Take a look at the man pages for 
iwconfig and the other wireless utils for all of the parameters.>

I will.

<One thing about having 2 interfaces, you need to make sure your kernel 
routing table is set up correctly if you want to surf. Make sure the correct 
one is set for the gateway. Usually, whichever one is going out to the 
internet I make sure there is no gateway set. In the case below eth0 is 
heading out to the net and wlan0 just goes to my network drive. If there is 
a conflict here you won't get out.

[stephen at localhost ~]$ netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt 
Iface
192.168.1.1     192.168.1.104   255.255.255.255 UGH       0 0          0 
eth0
92.168.1.0     0.0.0.0         255.255.255.0   U         0 0          0 eth0
192.168.0.0     0.0.0.0         255.255.255.0   U         0 0          0 
wlan0
192.168.201.0   0.0.0.0         255.255.255.0   U         0 0          0 
vmnet8
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 
eth0
0.0.0.0         192.168.1.1     0.0.0.0         UG        0 0          0 
eth0>

I try to use only the wireless interface, and not eth0.

<I don't know if this is the easiest way, but hope it helps.>

It was very helpful. I will try do decipher it in more detail, and I'll let 
you know about the results. Thanks for your feedback.

Teilhard.




-- 
fedora-list mailing list
fedora-list at redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list