Finished: CALL FOR TESTERS Intel wireless 5100/5300 iwn(4) driver for FreeBSD

LesJen said:
I've now set 7200 sec (two hours) and if I'm right the disconnection should appear after four hours.
Click to expand...

I think I'm right :-) Now I had the computer on for more than four hours and it lost connection right after
Code: 
WPA: Group rekeying completed with 00:21:91:02:e9:13 [GTK=TKIP]
 
I have loss of connection while using a different router (AVM Fritz Box, 802.11n), whereas my old Links WRT54GL works like a charm for days. So imho it depends on the AP/router.
 
oliverh said:
I have loss of connection while using a different router (AVM Fritz Box, 802.11n), whereas my old Links WRT54GL works like a charm for days. So imho it depends on the AP/router.
Click to expand...

True. It's very hard for me to reproduce this issue with the hardware I have. It runs for days without a single packet loss..

Anyway, for those who have the issue with rekeying, apply
Code: 
Index: sys/net80211/ieee80211_crypto_tkip.c
===================================================================
--- sys/net80211/ieee80211_crypto_tkip.c	(revision 203242)
+++ sys/net80211/ieee80211_crypto_tkip.c	(working copy)
@@ -144,6 +144,8 @@ tkip_setkey(struct ieee80211_key *k)
 		return 0;
 	}
 	k->wk_keytsc = 1;		/* TSC starts at 1 */
+	if (k->wk_flags & IEEE80211_KEY_GROUP)
+		ctx->rx_phase1_done = 0;
 	return 1;
 }
and rebuild your kernel and driver.

Let me know whether that does help.
 
bschmidt said:
Anyway, for those who have the issue with rekeying, apply
Code: 
Index: sys/net80211/ieee80211_crypto_tkip.c
===================================================================
--- sys/net80211/ieee80211_crypto_tkip.c	(revision 203242)
+++ sys/net80211/ieee80211_crypto_tkip.c	(working copy)
@@ -144,6 +144,8 @@ tkip_setkey(struct ieee80211_key *k)
 		return 0;
 	}
 	k->wk_keytsc = 1;		/* TSC starts at 1 */
+	if (k->wk_flags & IEEE80211_KEY_GROUP)
+		ctx->rx_phase1_done = 0;
 	return 1;
 }
and rebuild your kernel and driver.

Let me know whether that does help.
Click to expand...

I need instructions on how to apply, sorry.
 
LesJen said:
I need instructions on how to apply, sorry.
Click to expand...

Copy the content from the post to a file rekey.diff, go to /usr/src and apply the patch, after that rebuild your kernel.
# cd /usr/src
# patch -p0 < /path/to/rekey.diff
# make buildkernel
# make installkernel

Finally rebuild the iwn driver as you did before and reboot.
 
OK! That's done, rebooted and changed the negotiation time in the firewall to 900 sec (15 min) so in half a hour I should see a disconnetion again. What information do you need from me then?

One comment about the hardware. I'm also using W7 on the same machine and I've not seen this problem when running W7. I'm aware that it's no guaranty of anyhting, so Please no flame war ;-) I'm just trying to help :-)
 
LesJen said:
I've now been connected for over an hour and should have lost connection twice but there's been no disconnection so far.

:-)
Click to expand...

That is good news ;)

Btw, you can do # wlandebug +crypto which will log rekeying events.
 
Will this be available in RELENG_8?

Thanks for the port, with the addition of the tkip patch I haven't seen any issues yet. Any chance we will see this in RELENG_8 soon?
 
Hello!
Recently upgrade my FreeNAS by Intel 5100 ABG mini PCI-e WLAN card. But in FreeNas system I haven't any compiler, and I need precompiled (Intel 64) drivers iwn5000fw.ko and if_iwn.ko
Can anyone help me?
Thanks.
Yuri.
 
YuriS said:
Hello!
Recently upgrade my FreeNAS by Intel 5100 ABG mini PCI-e WLAN card. But in FreeNas system I haven't any compiler, and I need precompiled (Intel 64) drivers iwn5000fw.ko and if_iwn.ko
Can anyone help me?
Thanks.
Yuri.
Click to expand...

$ uname -a please, including SVN revision.
 
drbsd said:
Hi,

I have a Thinkpad SL510 with Intel 1000 link wireless card and I had to modify if_iwn.c in the code found on svn co http://svn.techwires.net/svn/projects/freebsd/ to make it works (otherwise it panic)

Apparently the problem is, for this chip, the driver try to read a OTPROM in place of an EEPROM, then I comment line 1479 :

Code: 
		// sc->sc_flags |= IWN_FLAG_HAS_OTPROM;

to workaround this... And it works well, I downloaded the entire FreeBSD sources and ports with the computer.

I know it's bad but it works, and I am not good enough to do something else, but maybe someone could make something better.
Click to expand...

Revision 38 should read the EEPROM correctly. Can you verify this?
 
bschmidt said:
True. It's very hard for me to reproduce this issue with the hardware I have. It runs for days without a single packet loss..

Anyway, for those who have the issue with rekeying, apply
Code: 
Index: sys/net80211/ieee80211_crypto_tkip.c
===================================================================
--- sys/net80211/ieee80211_crypto_tkip.c	(revision 203242)
+++ sys/net80211/ieee80211_crypto_tkip.c	(working copy)
@@ -144,6 +144,8 @@ tkip_setkey(struct ieee80211_key *k)
 		return 0;
 	}
 	k->wk_keytsc = 1;		/* TSC starts at 1 */
+	if (k->wk_flags & IEEE80211_KEY_GROUP)
+		ctx->rx_phase1_done = 0;
 	return 1;
 }
and rebuild your kernel and driver.

Let me know whether that does help.
Click to expand...

I hope this is going to be committed to 8-HEAD/STABLE eventually?
 
dpetrov said:
I hope this is going to be committed to 8-HEAD/STABLE eventually?
Click to expand...

Sure, I'll poke net@ in a couple of days. I just want to make sure that this is a correct fix and I'm not missing something else. I'm also waiting on reply from the PR.
 
I just want to report that after the rekey.diff I've had no problem what so ever :-)

I do have one question: How would you solve that at boot I have ntpd, noipd and bsdstats complaining of no network. I'm aware that it has to do with the time it takes for the network to get on line. Is there a way for checking or waiting to start services untill the network is up?

Thanks again
/Leslie
 
LesJen said:
I just want to report that after the rekey.diff I've had no problem what so ever :-)

I do have one question: How would you solve that at boot I have ntpd, noipd and bsdstats complaining of no network. I'm aware that it has to do with the time it takes for the network to get on line. Is there a way for checking or waiting to start services untill the network is up?

Thanks again
/Leslie
Click to expand...

It might be as easy as replacing DHCP with SYNCDHCP in /etc/rc.conf
 
Yesterday I saw that the newest version is 39. I was on 33 with the rekey.diff. I upgraded to 39 and the disconnections are back. Do I have to apply the rekey.diff even to the latest version?

Thanks
 
You must log in or register to reply here.
Back
Top