Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
IPW2200 and wpa_supplicant
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Networking & Security
View previous topic :: View next topic  
Author Message
ninjabadger
Apprentice
Apprentice


Joined: 23 Apr 2003
Posts: 270
Location: Scotland

PostPosted: Fri Mar 03, 2006 8:21 pm    Post subject: IPW2200 and wpa_supplicant Reply with quote

OK, so after a few months of unprotected wifi, seing others come into range lately and some horror stories my boss told me at work i finally bothered my ass to secure my wirless router (A BT Voyager). I have a centrino laptop and have setup the following

in /etc/conf.d/net

Code:

modules=( "wpa_supplicant" )

wpa_supplicant_eth1="-Dipw"
wpa_timeout_ath0=60

iface_eth1="dhcp"


and in /etc/wpa_supplicant.conf

Code:
ctrl_interface=/var/run/wpa_supplicant

network={
       ssid="MYNetwork"
       scan_ssid=1
       proto=WPA
       key_mgmt=WPA-PSK
       psk=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
}


i have the folling in my kernel autoload

Code:
ipw2200
ieee80211_crypt_tkip
ieee80211_crypt_ccmp


I have been reading various documentation but it most of what i find almost seems to assume you know what the hell you are doing. Maybe its just because its friday and my brain has been scrambled by my weekly exposure to Microsoft Products and AutoCAD Electricals Evil data backend but I am just not getting this at all.

My router is set to WPA-PSK with TKIP encryption only (has the option of AES or both). Anyone got the same setup care to share?
_________________
Is Microsoft Stronger?

No, no, no. Quicker, easier, more seductive.
Back to top
View user's profile Send private message
Ctrl+Alt+Del
Guru
Guru


Joined: 04 Jul 2004
Posts: 326
Location: .de

PostPosted: Fri Mar 03, 2006 9:15 pm    Post subject: Reply with quote

same here, i have been tinkering a bit with my ipw2200 and it really appears that you need a phd in cs to get it up and running..
No help from my part, sorry :)
Back to top
View user's profile Send private message
stardotstar
l33t
l33t


Joined: 10 Feb 2006
Posts: 887
Location: 2074/SYD/NSW/AU

PostPosted: Sat Mar 04, 2006 2:42 am    Post subject: Reply with quote

It seems that the ipw2200 is becoming famous for being tricky to manage for all but the most experienced. I have been wrestling with mine on various distros for about a year now and can always get it to work eventually but never 100% especially with respect to automatic association with multiple APs.

I have been using iwconfig/wireless tools just lately and finally given up troubleshooting it with this approach so I will be trying wpa_supplicant this weekend myself. Just gotta work out how to do the switch without causing more trouble than I already have. I can always associate with my APs but it has to be by manually setting the /etc/conf.d/wireless file to specify the essid for one of my networks and leave it to auto associate for the other! I have tried all combinations I can think of and exhausted help at LinuxQs and here so I am going to follow the wpa_supp approach which will involve me losing my connection no doubt :roll:

Are you both getting the firmware failures in messages? This is apparently fixed by handing the card some kind of hardware crypto initialisation string which I think you can only do with wpa_supplicant - anyway perhaps we can figure this card out and get our own phds :)

Will

Code:

Mar  4 08:47:08 geko ipw2200: No space for Tx
Mar  4 08:47:08 geko ipw2200: Failed to send WEP_KEY: Reason -16
Mar  4 08:47:36 geko ipw2200: No space for Tx
Mar  4 08:47:36 geko ipw2200: Failed to send RTS_THRESHOLD: Reason -16
Mar  4 08:47:36 geko ipw2200: No space for Tx
Mar  4 08:47:36 geko ipw2200: Failed to send FRAG_THRESHOLD: Reason -16
Mar  4 08:47:36 geko ipw2200: No space for Tx
Mar  4 08:47:36 geko ipw2200: Failed to send POWER_MODE: Reason -16
Mar  4 08:47:36 geko ipw2200: No space for Tx
Mar  4 08:47:36 geko ipw2200: Failed to send TX_POWER: Reason -16
Mar  4 08:59:09 geko ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, git-1.0.8Mar  4 08:59:09 geko ipw2200: Copyright(c) 2003-2005 Intel Corporation
Mar  4 08:59:09 geko ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
Mar  4 09:18:18 geko ipw2200: Firmware error detected.  Restarting.
Mar  4 09:18:18 geko ipw2200: Sysfs 'error' log captured.
Mar  4 09:52:23 geko ipw2200: Unknown notification: subtype=40,flags=0xa0,size=40
Mar  4 09:52:36 geko ipw2200: Unknown notification: subtype=40,flags=0xa0,size=40
Mar  4 09:57:16 geko ipw2200: Unknown notification: subtype=40,flags=0xa0,size=40
Mar  4 09:57:28 geko ipw2200: Unknown notification: subtype=40,flags=0xa0,size=40
Mar  4 10:00:15 geko ipw2200: Unknown notification: subtype=40,flags=0xa0,size=40
Mar  4 10:00:27 geko ipw2200: Unknown notification: subtype=40,flags=0xa0,size=40
Mar  4 10:40:17 geko ipw2200: Firmware error detected.  Restarting.
Mar  4 10:40:17 geko ipw2200: Sysfs 'error' log already exists.


and yet despite all this my wifi networking is really working - just the auto association that I can detect as a problem - so go figure eh?
_________________
]8P
Back to top
View user's profile Send private message
XmN
n00b
n00b


Joined: 20 Feb 2005
Posts: 45
Location: Belgium

PostPosted: Sat Mar 04, 2006 11:43 am    Post subject: Reply with quote

Which kernel and version of ipw do you use?

Try -Dwext as driver and set timeout to use eth1 instead of ath0
_________________
Women and Linux are alike:
You need certain skills to root them.
Back to top
View user's profile Send private message
stardotstar
l33t
l33t


Joined: 10 Feb 2006
Posts: 887
Location: 2074/SYD/NSW/AU

PostPosted: Sat Mar 04, 2006 12:36 pm    Post subject: Reply with quote

...ok - sounds good - was that (to me?) before moving to wpa_supp or after?

this is a hand rolled 2.6.15 so:

Code:

basilisk tmp # lsmod
Module                  Size  Used by
ipv6                  188544  12
ohci_hcd               15396  0
ehci_hcd               23272  0
parport_pc             28004  0
parport                22696  1 parport_pc
floppy                 45204  0
pcspkr                  2764  0
rtc                     8940  0
uhci_hcd               24368  0
xircom_cb               7872  0
yenta_socket           15208  3
firmware_class          6368  0
video                  11492  0
touchkitusb             3492  0
usbcore                76892  5 ohci_hcd,ehci_hcd,uhci_hcd,touchkitusb
s2io                   33800  0
libcrc32c               1760  0
pcmcia                 17392  4
rsrc_nonstatic          8352  1 yenta_socket
pcmcia_core            29156  3 yenta_socket,pcmcia,rsrc_nonstatic


firmware?
Code:

geko wparker # grep ipw /var/log/dmesg
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, git-1.0.8
ipw2200: Copyright(c) 2003-2005 Intel Corporation
ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection


Don't bother reading through all of this - it's just a taste of what I have going on despite the fact that I am typing this via my ipw2200!!

Code:

Mar  3 20:54:05 geko ipw2200: Sysfs 'error' log already exists.
Mar  3 20:54:09 geko ipw2200: Firmware error detected.  Restarting.
Mar  3 20:54:09 geko ipw2200: Sysfs 'error' log already exists.
Mar  3 20:54:15 geko ipw2200: Firmware error detected.  Restarting.
Mar  3 20:54:15 geko ipw2200: Sysfs 'error' log already exists.
Mar  3 20:54:19 geko ipw2200: Firmware error detected.  Restarting.
Mar  3 20:54:19 geko ipw2200: Sysfs 'error' log already exists.
Mar  3 20:54:45 geko ipw2200: Firmware error detected.  Restarting.
Mar  3 20:54:45 geko ipw2200: Sysfs 'error' log already exists.
Mar  3 20:55:05 geko ipw2200: Firmware error detected.  Restarting.
Mar  3 20:55:05 geko ipw2200: Sysfs 'error' log already exists.
Mar  3 20:55:17 geko ipw2200: Firmware error detected.  Restarting.
Mar  3 20:55:17 geko ipw2200: Sysfs 'error' log already exists.
... (and so on...)
Mar  3 21:50:17 geko ipw2200: Sysfs 'error' log already exists.
Mar  4 08:40:54 geko ipw2200: Failed to send RTS_THRESHOLD: Command timed out.
Mar  4 08:40:55 geko ipw2200: Failed to send FRAG_THRESHOLD: Command timed out.
Mar  4 08:40:56 geko ipw2200: Failed to send POWER_MODE: Command timed out.
Mar  4 08:40:57 geko ipw2200: Failed to send TX_POWER: Command timed out.
Mar  4 08:41:00 geko ipw2200: Failed to send WEP_KEY: Command timed out.
Mar  4 08:41:00 geko ipw2200: No space for Tx
Mar  4 08:41:00 geko ipw2200: Failed to send WEP_KEY: Reason -16
Mar  4 08:41:00 geko ipw2200: No space for Tx
Mar  4 08:41:00 geko ipw2200: Failed to send ASSOCIATE: Reason -16
Mar  4 08:41:14 geko ipw2200: No space for Tx
Mar  4 08:41:14 geko ipw2200: Failed to send RTS_THRESHOLD: Reason -16
Mar  4 08:41:14 geko ipw2200: No space for Tx
Mar  4 08:41:14 geko ipw2200: Failed to send FRAG_THRESHOLD: Reason -16
Mar  4 08:41:14 geko ipw2200: No space for Tx
Mar  4 08:41:14 geko ipw2200: Failed to send POWER_MODE: Reason -16
Mar  4 08:41:14 geko ipw2200: No space for Tx
Mar  4 08:41:14 geko ipw2200: Failed to send TX_POWER: Reason -16
Mar  4 08:43:17 geko ipw2200: No space for Tx
Mar  4 08:43:17 geko ipw2200: Failed to send WEP_KEY: Reason -16
Mar  4 08:47:08 geko ipw2200: No space for Tx
Mar  4 08:47:08 geko ipw2200: Failed to send RTS_THRESHOLD: Reason -16
Mar  4 08:47:08 geko ipw2200: No space for Tx
Mar  4 08:47:08 geko ipw2200: Failed to send FRAG_THRESHOLD: Reason -16
Mar  4 08:47:08 geko ipw2200: No space for Tx
Mar  4 08:47:08 geko ipw2200: Failed to send POWER_MODE: Reason -16
Mar  4 08:47:08 geko ipw2200: No space for Tx
Mar  4 08:47:08 geko ipw2200: Failed to send TX_POWER: Reason -16
Mar  4 08:47:08 geko ipw2200: No space for Tx
Mar  4 08:47:08 geko ipw2200: Failed to send WEP_KEY: Reason -16
Mar  4 08:47:08 geko ipw2200: No space for Tx
Mar  4 08:47:08 geko ipw2200: Failed to send WEP_KEY: Reason -16
Mar  4 08:47:36 geko ipw2200: No space for Tx
Mar  4 08:47:36 geko ipw2200: Failed to send RTS_THRESHOLD: Reason -16
Mar  4 08:47:36 geko ipw2200: No space for Tx
Mar  4 08:47:36 geko ipw2200: Failed to send FRAG_THRESHOLD: Reason -16
Mar  4 08:47:36 geko ipw2200: No space for Tx
Mar  4 08:47:36 geko ipw2200: Failed to send POWER_MODE: Reason -16
Mar  4 08:47:36 geko ipw2200: No space for Tx
Mar  4 08:47:36 geko ipw2200: Failed to send TX_POWER: Reason -16
Mar  4 08:59:09 geko ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, git-1.0.8
Mar  4 08:59:09 geko ipw2200: Copyright(c) 2003-2005 Intel Corporation
Mar  4 08:59:09 geko ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
Mar  4 09:18:18 geko ipw2200: Firmware error detected.  Restarting.
Mar  4 09:18:18 geko ipw2200: Sysfs 'error' log captured.
Mar  4 09:52:23 geko ipw2200: Unknown notification: subtype=40,flags=0xa0,size=40
Mar  4 09:52:36 geko ipw2200: Unknown notification: subtype=40,flags=0xa0,size=40
Mar  4 09:57:16 geko ipw2200: Unknown notification: subtype=40,flags=0xa0,size=40
Mar  4 09:57:28 geko ipw2200: Unknown notification: subtype=40,flags=0xa0,size=40
Mar  4 10:00:15 geko ipw2200: Unknown notification: subtype=40,flags=0xa0,size=40
Mar  4 10:00:27 geko ipw2200: Unknown notification: subtype=40,flags=0xa0,size=40
Mar  4 10:40:17 geko ipw2200: Firmware error detected.  Restarting.
Mar  4 10:40:17 geko ipw2200: Sysfs 'error' log already exists.
Mar  4 16:58:37 geko ipw2200: Firmware error detected.  Restarting.
Mar  4 16:58:37 geko ipw2200: Sysfs 'error' log already exists.
Mar  4 18:40:01 geko ipw2200: Firmware error detected.  Restarting.
Mar  4 18:40:01 geko ipw2200: Sysfs 'error' log already exists.
Mar  4 19:05:39 geko ipw2200: Unknown notification: subtype=40,flags=0xa0,size=40
Mar  4 19:06:06 geko ipw2200: Unknown notification: subtype=40,flags=0xa0,size=40
Mar  4 19:12:37 geko ipw2200: Unknown notification: subtype=40,flags=0xa0,size=40
Mar  4 19:12:50 geko ipw2200: Unknown notification: subtype=40,flags=0xa0,size=40
Mar  4 21:46:53 geko ipw2200: Firmware error detected.  Restarting.
Mar  4 21:46:53 geko ipw2200: Sysfs 'error' log already exists.
Mar  4 21:59:37 geko ipw2200: Firmware error detected.  Restarting.
Mar  4 21:59:37 geko ipw2200: Sysfs 'error' log already exists.


Will
_________________
]8P


Last edited by stardotstar on Sun Mar 05, 2006 10:44 am; edited 1 time in total
Back to top
View user's profile Send private message
nicta2
n00b
n00b


Joined: 08 Oct 2002
Posts: 30

PostPosted: Sun Mar 05, 2006 6:54 am    Post subject: hwcrypto=0 Reply with quote

Add hwcrypto=0 to the options line in /etc/modules.d/ipw2200

Hardware crypto is broken. That's what causes those firmware errors.
Back to top
View user's profile Send private message
stardotstar
l33t
l33t


Joined: 10 Feb 2006
Posts: 887
Location: 2074/SYD/NSW/AU

PostPosted: Sun Mar 05, 2006 10:42 am    Post subject: Reply with quote

I have heard about the hwcrypto flag fixing firmware errors but havn't been able to work out how to use it with the in kernel ipw2200 driver and wireless-tools/iwconfig setup.

I don't have any ipw2200 module...

Code:

geko modules.d # ls -al
total 24
drwxr-xr-x   2 root root 4096 Mar  2 19:38 .
drwxr-xr-x  59 root root 4096 Mar  5 08:22 ..
-rw-r--r--   1 root root    0 Oct 20 22:04 .keep
-rw-r--r--   1 root root 1310 Feb 21 23:39 aliases
-rw-r--r--   1 root root 1100 Feb 24 08:02 alsa
-rw-r--r--   1 root root  122 Feb 21 23:39 i386
-rw-r--r--   1 root root   93 Mar  2 19:38 ibm_acpi


It looks like I will have to switch to wpa-supplicant to be able to use the genuine ipw2200 module and pass it this option...

Do I need to do anything complicated to switch from wireless tools to wpa-supp???

(I am very sorry Ninja and ctrl-alt-del to have hijacked this thread - I will ensure I report all my results here for the original posters to benefit)

we really need to get this wireless card sorted for the inexperienced - although I have learned everything I know about wireless because it didn't "just work" so... :? mixed blessing me thinks.
_________________
]8P
Back to top
View user's profile Send private message
stardotstar
l33t
l33t


Joined: 10 Feb 2006
Posts: 887
Location: 2074/SYD/NSW/AU

PostPosted: Mon Mar 06, 2006 2:23 am    Post subject: Reply with quote

I have switched to wpa_supplicant and added the hwcrypto=0 flag.

The configuration and subsequent association happened without any drama to my work network. I will monitor these firmware errors and see if they abate.

edit: association with my home network is fine and there is no more sign of the firmware errors - so this looks like a great solution...

seeing this though now:

Code:

geko wparker # tail /var/log/messages
Mar  6 17:56:13 geko bridge-eth1: disabling the bridge
Mar  6 17:56:13 geko bridge-eth1: down
Mar  6 17:56:14 geko bridge-eth1: enabling the bridge
Mar  6 17:56:14 geko bridge-eth1: up
Mar  6 17:56:18 geko dhcpcd[10260]: infinite IP address lease time. Exiting
Mar  6 17:57:17 geko bridge-eth1: disabling the bridge
Mar  6 17:57:17 geko bridge-eth1: down
Mar  6 17:57:18 geko bridge-eth1: enabling the bridge
Mar  6 17:57:18 geko bridge-eth1: up
Mar  6 17:57:22 geko dhcpcd[11103]: infinite IP address lease time. Exiting


Not sure why this is happening or who is responsible.

Will
_________________
]8P
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Networking & Security All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum