11:01 p.m.
I thought it was resolved, but it turned out the WAP had not restored WEP
encryption like I thought it had. So, the wireless card works fine with WEP
turned off, but not when it's turned on. I've tried:
# iwconfig wlan0 key XXXXXXXXXX restricted
which generates this error:
Error for wireless request "Set Encode" (8B2A):
SET failed on device wlan0 ; Invalid argument.
My Googling indicates that this might mean that the card does not support
encryption, which I find unlikely since it certainly does under Windows.
I also tried:
# iwconfig wlan0 key 0xXXXXXXXXXX restricted
That generated no errors, but did not give me connectivity.
--
Slainte,
Richard S. Crawford (mailto: rscrawford(a)mossroot.com)
AIM: Buffalo2K / http://www.mossroot.com
"You can't depend on your judgment when your imagination is out of focus."
-Mark Twain
GPG Public Key located at: http://www.mossroot.com/rscrawford.asc
11:14 p.m.
Richard,
what card are you using? I'm running the internat IPW2100 card (Intel stuff)
on my ThinkPad. It started to work fine after I got the firmware downloaded
and installed correctly.
To get it going I used the GUI netconfig tool (Under System Tools -> Network
Device Control in KDE). I set up the key and all that stuff there. Be careful
to use the right number of characters for WEP. the 64-bit WEP used 5 bytes
(actually only 40 bit encryption). The 160 bit (I think that what it is) uses
13 bytes for encryption.
Since the card works without WEP, my initial thought of checking your MAC
filtering on the WAP would be a moot point, but I mention it anyway.
Also, make sure that you're actually talking to your WAP and not some other
thing that one of your neighbors uses.
Best regards,
Chris
On Wednesday 30 March 2005 00:01, Richard S. Crawford wrote:
I thought it was resolved, but it turned out the WAP had not restored
WEP
encryption like I thought it had. So, the wireless card works fine with
WEP turned off, but not when it's turned on. I've tried:
# iwconfig wlan0 key XXXXXXXXXX restricted
which generates this error:
Error for wireless request "Set Encode" (8B2A):
SET failed on device wlan0 ; Invalid argument.
My Googling indicates that this might mean that the card does not support
encryption, which I find unlikely since it certainly does under Windows.
I also tried:
# iwconfig wlan0 key 0xXXXXXXXXXX restricted
That generated no errors, but did not give me connectivity.
11:25 p.m.
On Tuesday 29 March 2005 9:14 pm, Chris Ruprecht flailed at a keyboard and
produced this:
Richard,
what card are you using? I'm running the internat IPW2100 card (Intel stuff)
on my ThinkPad. It started to work fine after I got the firmware downloaded
and installed correctly.
I'm using a Linksys WPC54GS (with something called "speedbooster", whatever
the heck that is).
To get it going I used the GUI netconfig tool (Under System Tools
-> Network
Device Control in KDE). I set up the key and all that stuff there. Be
careful
to use the right number of characters for WEP. the 64-bit WEP used 5
bytes
(actually only 40 bit encryption). The 160 bit (I think that what it is)
uses
13 bytes for encryption.
Yeah, I've quadruple-checked that. Heh. Thanks, though.
Since the card works without WEP, my initial thought of checking your
MAC
filtering on the WAP would be a moot point, but I mention it anyway.
I do filter on MAC addresses, but I've made sure the MAC address for my
wireless card is on the list of allowed cards.
Also, make sure that you're actually talking to your WAP and not
some other
thing that one of your neighbors uses.
Yup.
Dang it.
Thanks, though.
--
Slainte,
Richard S. Crawford (mailto: rscrawford(a)mossroot.com)
AIM: Buffalo2K / http://www.mossroot.com
"You can't depend on your judgment when your imagination is out of focus."
-Mark Twain
GPG Public Key located at: http://www.mossroot.com/rscrawford.asc
12:22 a.m.
do you know what authentification you are using Open System or Shared
Keys? Some drivers used not to support Shared Keys (and this mode is
belived to be less secure, nevertheless the name - vole MS even
doesn't recommend to use it). Check what you have in your AP settings
and try to use open system mode if it's not set up yet.
3:14 a.m.
Chris Ruprecht wrote:
Richard,
what card are you using? I'm running the internat IPW2100 card (Intel stuff)
on my ThinkPad. It started to work fine after I got the firmware downloaded
and installed correctly.
i have a thinkpad r51 with 802.11b & ipw2100.
i have been trying using frealek's howto and get it working.
which is your kernel and distro version?
please point me to the relevant links.
i will be grateful if you could outline the exact procedure that u
followed.
i am using FC3 and upgraded to 2.6.10.-1.770FC3 kernel.
thank you for your time.
--
Raghavendra Moktali
7:39 a.m.
On Apr 1, 2005 4:14 AM, Raghavendra Moktali <rmoktali(a)vsnl.net> wrote:
Chris Ruprecht wrote:
> Richard,
>
> what card are you using? I'm running the internat IPW2100 card (Intel stuff)
> on my ThinkPad. It started to work fine after I got the firmware downloaded
> and installed correctly.
>
>
i have a thinkpad r51 with 802.11b & ipw2100.
i have been trying using frealek's howto and get it working.
which is your kernel and distro version?
please point me to the relevant links.
i will be grateful if you could outline the exact procedure that u
followed.
i am using FC3 and upgraded to 2.6.10.-1.770FC3 kernel.
thank you for your time.
--
Raghavendra Moktali
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
Wireless page http://fedoranews.org
http://fedoranews.org/contributors/jim_lawrence/wireless/
--
Jim Lawrence
Registered Linux User: #376813
********************************************************
When I'm feeling down, I like to whistle.
It makes the neighbor's dog run to the end of his chain and gag himself.
************************************
1:05 a.m.
jim lawrence wrote:
On Apr 1, 2005 4:14 AM, Raghavendra Moktali <rmoktali(a)vsnl.net>
wrote:
>Chris Ruprecht wrote:
>
>>Richard,
<snip>
almost missed that 2 lines.
anyway thanks. got eth1 up. now have to try to connect with a accesspoint.
--
Raghavendra Moktali
11:30 p.m.
New subject: Wireless connectivity - was resolved, then unresolved, now RESOLVED!!!
Hah! Got it.
Deep in the heart of /etc/sysconfig/networking/devices, I found two files:
ifcfg-wlan0, and keys-wlan0. I made sure that ifcfg-wlan0 had the right
entry for my WAP under ESSID; then in keys-wlan0, I found that the line for
KEY= was blank. I put in my encryption key, reactivated wlan0 and
deactivated eth0 (and even unplugged the cable), restarted networking, and
even rebooted for the hell of it. SUCCESS!
That was the longest eight hours I've ever spent trying to get a wireless card
working under Linux. But now I'm finally MS free on my new laptop (well,
mostly; still using a Windows driver for my wireless under ndiswrapper, of
course, but what the hell).
--
Slainte,
Richard S. Crawford (mailto: rscrawford(a)mossroot.com)
AIM: Buffalo2K / http://www.mossroot.com
"You can't depend on your judgment when your imagination is out of focus."
-Mark Twain
GPG Public Key located at: http://www.mossroot.com/rscrawford.asc
6:51 a.m.
New subject: Wireless connectivity - was resolved, then unresolved, now RESOLVED!!!
Richard S. Crawford wrote:
Deep in the heart of /etc/sysconfig/networking/devices, I found two
files:
ifcfg-wlan0, and keys-wlan0. I made sure that ifcfg-wlan0 had the right
entry for my WAP under ESSID; then in keys-wlan0, I found that the line
for
KEY= was blank. I put in my encryption key, reactivated wlan0 and
deactivated eth0 (and even unplugged the cable), restarted networking, and
even rebooted for the hell of it. SUCCESS!
I didn't think this file was normally read when booting;
I thought /etc/sysconfig/network-scripts/ifcfg-wlan0
would be the relevant file.
WiFi under Fedora/Linux is a bit of a mess, in my opinion.
Files all over the place are looked at,
without any documentation listing them.
In your case, I would have looked at /etc/pcmcia/wireless.opts
and set the WEP key there.
But I use the standard orinoco_cs kernel driver,
which may be different.
--
Timothy Murphy
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
7:22 a.m.
New subject: Wireless connectivity - was resolved, then unresolved, now RESOLVED!!!
On Wed, 30 Mar 2005 13:51:05 +0100
Timothy Murphy <tim(a)birdsnest.maths.tcd.ie> wrote:
Richard S. Crawford wrote:
> Deep in the heart of /etc/sysconfig/networking/devices, I found two files:
> ifcfg-wlan0, and keys-wlan0. I made sure that ifcfg-wlan0 had the right
> entry for my WAP under ESSID; then in keys-wlan0, I found that the line
> for
> KEY= was blank. I put in my encryption key, reactivated wlan0 and
> deactivated eth0 (and even unplugged the cable), restarted networking, and
> even rebooted for the hell of it. SUCCESS!
I didn't think this file was normally read when booting;
I thought /etc/sysconfig/network-scripts/ifcfg-wlan0
would be the relevant file.
WiFi under Fedora/Linux is a bit of a mess, in my opinion.
Files all over the place are looked at,
without any documentation listing them.
In your case, I would have looked at /etc/pcmcia/wireless.opts
and set the WEP key there.
But I use the standard orinoco_cs kernel driver,
which may be different.
Tim,
The ifcfg-eth* files are all the same file:
find /etc/sysconfig -name 'ifcfg-eth?' -exec /bin/ls -l {} \;
-rw-r--r-- 3 root root 195 Feb 13 21:03
/etc/sysconfig/network-scripts/ifcfg-eth0
-rw-r--r-- 3 root root 195 Feb 13 21:03
/etc/sysconfig/networking/devices/ifcfg-eth0
-rw-r--r-- 3 root root 195 Feb 13 21:03
/etc/sysconfig/networking/profiles/default/ifcfg-eth0
(my mailer will have broken the output lines, sorry)
The "3" in the second column is the count of links to the data - the different
files are hard links to the same data. Edit one and you edit them all... Your
comment about this being a bit of a mess is right on target... I think that it's
the result of different tools looking in different places or the design of the
profile mechanism (which is also a mess and seems only partially implemented).
Dave
7:08 p.m.
New subject: Wireless connectivity - was resolved, then unresolved, now RESOLVED!!!
Dave Gavin wrote:
-rw-r--r-- 3 root root 195 Feb 13 21:03
/etc/sysconfig/network-scripts/ifcfg-eth0
-rw-r--r-- 3 root root 195 Feb 13 21:03
/etc/sysconfig/networking/devices/ifcfg-eth0
-rw-r--r-- 3 root root 195 Feb 13 21:03
/etc/sysconfig/networking/profiles/default/ifcfg-eth0
(my mailer will have broken the output lines, sorry)
The "3" in the second column is the count of links to the data - the
different
files are hard links to the same data. Edit one and you edit them all...
Your comment about this being a bit of a mess is right on target... I
think that it's the result of different tools looking in different places
or the design of the profile mechanism (which is also a mess and seems
only partially implemented).
In my case the relevant files are not the same
[tim@martha ~]$ ls -ls /etc/sysconfig/network-scripts/ifcfg-eth0
4 -rw-r--r-- 1 root root 211 Mar 30
19:24 /etc/sysconfig/network-scripts/ifcfg-eth0
[tim@martha ~]$ ls -ls /etc/sysconfig/networking/devices/ifcfg-eth0
4 -rw-r--r-- 4 root root 115 Mar 30
16:44 /etc/sysconfig/networking/devices/ifcfg-eth0
Admittedly that may be my fault, or rather the fault
of an ancient version of NetworkManager.
However, my point was that the file actually looked at is (I believe)
/etc/sysconfig/network-scripts/ifcfg-eth0 .
I'm not really clear why there should be 3 or 4 linked files.
--
Timothy Murphy
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
11:33 a.m.
On Tue, 29 Mar 2005 21:01:35 -0800, Richard S. Crawford
<rscrawford(a)mossroot.com> wrote:
I thought it was resolved, but it turned out the WAP had not restored
WEP
encryption like I thought it had. So, the wireless card works fine with WEP
turned off, but not when it's turned on. I've tried:
# iwconfig wlan0 key XXXXXXXXXX restricted
Try using open mode instead of restricted. I know I have to use open
for my card to work:
# iwconfig wlan0 key XXXXXXXXXX open
which generates this error:
Error for wireless request "Set Encode" (8B2A):
SET failed on device wlan0 ; Invalid argument.
My Googling indicates that this might mean that the card does not support
encryption, which I find unlikely since it certainly does under Windows.
I also tried:
# iwconfig wlan0 key 0xXXXXXXXXXX restricted
As far as I know, you should not have the 0x in front. What happens
when you just run "iwconfig" after trying to set the key? Can you see
the key set properly? Has it associated with your AP (do you see the
ESSID set)?
That generated no errors, but did not give me connectivity.
Jonathan
6982
days inactive
6985
days old
11 comments
8 participants
participants (8)
-
Chris Ruprecht -
G S -
Gavin David -
jim lawrence -
Jonathan Berry -
Raghavendra Moktali -
Richard S. Crawford -
Timothy Murphy