On 2010-11-15, Ing. Alexander Kr??ek <mer...@gremlin.cz> wrote: > On Fri, 2010-11-12 at 21:38 +0000, Stuart Henderson wrote: >> On 2010-11-12, David Coppa <dco...@gmail.com> wrote: >> > On Fri, Nov 12, 2010 at 4:52 PM, stolendata.net >> ><stolen.data....@gmail.com> wrote: >> >> I've been using the RAL(4) driver and a wifi card with the RT2561 >> >> chipset (Linksys WMP54g) for a few years as my wifi access point, and >> >> have had no problems at all. Recently I switched to an 802.11n card >> >> with RT2860 chipset (Edimax EW-7728in) in hopes of getting some higher >> >> transfer speeds to my server storage, only to find out that OpenBSD's >> >> 802.11 stack doesn't have any 11n functionality at all and thusly runs >> >> as 11g only. Since I switched to using the RT2860 chipset, first on >> >> obsd 4.3 and currently on 4.8, I've started to experience a recurring >> >> problem: every now and then, after disconnecting a machine from the >> >> access point, RAL(4) will refuse further connections from that machine >> >> (I'm not sure if it depends on the IP of the client or its MAC address >> >> etc.), resulting in only getting a "connection timed out" when trying >> >> to associate with the AP, until I down/up the RAL(4) interface or >> >> simply "restart" it using /etc/netstart. >> >> >> >> Any ideas? Anyone seen this with before with RAL(4) and/or the RT2860 >> >> family? I'm currently netstart'ing the interface every 24 hours via >> >> cron to solve the problem, but it feels like jumping through hoops, so >> >> to speak - this is after all a bug of some sort. >> > >> > Yes, it's a known problem with table of associated clients not being >> > refreshed properly in our 802.11 stack. >> > For what I know, some dev should be working on fixing it... >> > >> > ciao, >> > david >> > >> > >> >> hmm. well, the fact that this didn't happen with RT2561 is interesting... >> > > Well, it did happen on RT2561 to me (-current, compiled all system every > 1-3 weeks) every now and then (in variable interval from one day to > several days), till about 1-2 months ago. > So, for RT2561 it seems (to me) to be fixed, after all.
ah, interesting... in that case, "stolendata.net" whoever you are, try pulling sys/net80211/ieee80211_ioctl.c up to -current and see if that helps at all.
