Hello,
There is a big bug in 2.9rc5, not all users couldn’t assosiate to the AP, this happend as seen by me only on the i386 platform not on the MIPS platform. On multiple routers from routerboards to P4 systems.
So don’t upgrade until this is fixed if you want to use the router as AP
Does anyone no it is simple to downgrade to 2.8 without loosing de config
The bug is already reported to Mikrotik. Radius Mac authorisation doesn’t work to.
to downgrade u must switch all 2.9 features
country , tx-power, tx-power-modes
then
/system package downgrade
if u have athreos u could change txpower mode .
check it
/interface wireless
then print and monitor u will see what power u have if bigger than 20 then u must change it
Has someone at Mikrotik confirmed this as a bug for you? I sent in an e-mail explaining the same problem and have a ticket number, but have not received a reply just yet. I’m glad someone else is able to confirm seeing the same thing, as it can be difficult to convince people there is a problem when you are the only one.
We don’t currently use RADIUS MAC Authentication, but were planning on deploying it real soon. What problem were you seeing?
Thanks,
Dave
It is not confirmed but i tried everything but the problem stays.
Then i tried it with Remote MAC auth on and het did’nt ask the radius server at all.
Best regards
Johan
RC7 just came out. Has anyone experiencing this problem upgraded and can you confirm/deny that this bug is fixed? The changelog isn’t detailed enough to know if this problem is corrected or not. There is one entry, “*) fixed bug - wireless scan sometimes did not work;” that looks like it could be it, but without more detail, it’s impossible to know. I’d try it myself, but I can only reproduce the problem on our production network, and with the problems the last RC release gave us (the other problems we experienced are clearly fixed according to the changelog), I’ll be torched if I roll this out without knowing this association problem is corrected first.
Thanks in advance to anyone who is willing to be the guinea pig and report the results to us.
Dave
I have just upgraded a 266MHz platform used as an AP from RC6 to RC7, with regular windows XP PC clients (indoors) running from it using PCMCIA and USB wireless G adaptors.
It is running 128bit (104) WEP security (not very secure I know)
No problems yet, seems fine.
Regards
Were you experiencing the problem that others in this thread were reporting? We all had clients that connected and operated perfectly under 2.8.x, but after upgrading to 2.9rcX, were unable to connect. For us, it happened under rc2 and rc5. Downgrading to 2.8.x fixed the problem both times.
The customers it seemed to affect were the furthest from the AP. We use our APs in a WAN environment. Furthest from the AP to us means 8+ miles. On one AP, out of 150 clients (off multiple radios, but one tower) we had only 1 affected customer. Off another AP, we had 3. So the percentage of clients that were affected was very low. So low, we didn’t relate their inability to connect with the software upgrade for some time. We swapped out radios and antennas. When we downgraded due to other issues (which are fixed in this release), the few customers who were unable to connect immediately were able to do so. Only then did we realize that their inability to connect was a software-released bug in the Mikrotik.
I’m wondering if this problem is fixed in this release. I’m hoping that someone else who was experiencing the problem previously will be able to confirm/deny that the problem exists in this release.
Thanks,
Dave
Probably my results aren’t helpful to you.
I have Mikrotik AP at home (2 sites) where I always use the latest beta to test it. I have never had 2.8 on them. Clients are laptops. What CPEs are you using - MT or not?
The main (serious) testing we do on 2.9 at work is for P2P bridge applications, MT to MT router, and the latest RCs are fine. I had one on all weekend with 57Mbps bandwidth test running through it.
At home I have one problem with my laptop with a specific Netgear driver that doesn’t associate reliably (can be forced) but the later Netgear drivers fix this (but don’t allow VPN passthrough, so I’m stuck with the old one). Don’t think I can blame that on MT, it’s almost certainly a “Netgear problem”.
Regards
Please upagrade to the latest version (v2.9rc7) and if the clients still can’t connect to the v2.9 then make the support output file when they are trying to connect and send it to support@mikrotik.com
That would help to find the problem and fix it.