Im running 2.9.3 with the post extensions....

Ive gotten 7 different reports over the past month of guests whose laptops can see and try to connect to my MT APs but never fully connect or work (they get the limited connectivity messages in windows)

BUT they ALL report being able to choose and connect to (and surf) onto a rogue linksys AP that a condo next door has.

we have 20 MT APs at this install- ppl are seeing this on all floors,all mts

the log messages we get when this occurs is the same, every where:

mac addy@wlanX connected
then about 20 sec later:
mac addy@wlanX disconnected, got disassoc: unspecified.


most of the time they will connect log enough to pull an IP addy from our DHCP server, but like i said the got disassoc: unspecified kills it.

At first it thougth this was just a few isolated issues with peoples buggy laptops, but we are seeing WAY to much of this recently with too many reports of the same ppl being able to connect to the 3 or 4 rogue linksys APs that spill over in some of our area.

any ideas? this looks MT specific.

tks

Probably it is better to contact support (support@mikrotik.com) with attached support output file (generated when issue occured).

You have to upgrade to the latest version and set "proprietary-extensions" parameter of the wireless interface to "post-2.9.25".

Eugene

eugne, thanks but read the first line of my post.
any other ideas?


serge, how close does the generation of the sup out have to be to when the incident occured.

ie, i have on one AP logs that showed this issue at about 10 hours ago from now..should i send in that supOut?

tks


joe

I read 2.9.3 and that induced the reply :)

ok i just sent the sup out to support.

thanks

2.9.3 or 2.9.30 ?
And is the laptop Centrino with Intel wi-fi card. There are lot of complaining about them, just install them latest driver from the Intels site.

The complaining is Intel wi-fi vs. Athers AP with recently new drivers and capabilities, and there is proof that the problem is with intel compatibilty, soo they released new driver.

i dont understand why ppl woudl think 2.9.3 = 2.9.03 i guessi should have put 2.9.30

where is the driver update on intel site?

thanks

Try here:
http://support.intel.com/support/wirele ... 010623.htm
Read here:
http://support.microsoft.com/kb/821442

P.S. Because 2.9.3 != 2.9.30.

P.P.S. This is another very discused theme:
http://support.intel.com/support/wirele ... 006205.htm
But I think that this is your case.