how to run wireless-legacy in 2.8.16?

jonmansey · Sat Sep 18, 2004 3:49 am

Hi

I am having the by-now-infamous disconnects issue with 2.8.13 and would like to try 2.8.16 as Ive read it helps certain folks on the board here.

However, I tried upgrading to 2.8.16 with wireless and wireless-legacy package loaded, but got the also-by-now-infamous slowness issue, which shows up for me right away as sites pinging off the omni at up to 500ms!

So I tried removing the wireless package thinking I shoudnt have both loaded, which simply left me with no wireless interface.

Sooo, how does one activate and use wireless-legacy? I have atheros 5211 and dont want to use nstreme. If just by having it loaded along with wireless activates "legacy", then Im confused as to why Im getting the "slowness" feature.

Thx for any tips,

Jon Mansey

dorijan · Sat Sep 18, 2004 6:05 am

all you have to do is put wireless-legacy package in ftp and reset router..

jonmansey · Sat Sep 18, 2004 6:23 am

so only wireless-legacy, not wireless as well? When i did that the router had no wireless interface. Hmm, ill try it again.

jm

mag · Sat Sep 18, 2004 12:21 pm

we found, that for switching it is necessary to remove wireless or wireless-legacy package, and then installing the other one.

jonmansey · Sun Sep 19, 2004 12:45 am

Thanks for the tips friends, the first time I had uploaded both wireless and wireless-legacy, found it to be terrrible in latency, so un-installed wireless, leaving wireless-legacy, but in fact what this did upon reboot is leave me with no wireless interface.

This time I only FTPd wireless-legacy along with the other 2.8.16 packages, rebooted and now wireless-legacy is working fine under 2.8.16, low latency etc.

The big question of course is, will this fix my site disconnects problem? ill let you know.

Did it fix yours?

TIA,

Jon

mag · Sun Sep 19, 2004 12:01 pm

we are working with the 2.8.16 wireless package, no problems yet.

Borage · Sun Sep 26, 2004 10:26 pm

So I tried removing the wireless package thinking I shoudnt have both loaded, which simply left me with no wireless interface.

Using both wireless packages will cause huge problems.

mp3turbo2 · Mon Sep 27, 2004 7:52 am

excellent, Borage - wanna share some more detailed info? Just telling that wiless will cause huge problems is super-dooper, but has no info at all.

So, post what was/is wrong, what you feel is broken, what is your configuration (be as specific as you could be), etc, etc. Ya know, wireless is 'ghost' technology, one improper rg-213 / lmr-400 cable will cause you headaches.

bye, mp3turbo.

Borage · Mon Sep 27, 2004 9:30 am

excellent, Borage - wanna share some more detailed info? Just telling that wiless will cause huge problems is super-dooper, but has no info at all.

Well, I only repeated what Mikrotik told me, never install both wireless packages because it will cause problems. I installed both packages and I realized that the settings in the wireless was not available anymore (2.4GHz-B/G etc.). When I uninstalled the wireless-legacy package, everytime I rebooted my router, I saw a few script errors in the boot sequence.

tully · Mon Sep 27, 2004 2:37 pm

We have found the problem of 'disconnects and then reconnects ~1s' -- it only affects some 5211 Ath cards in station mode. It usually affects less than 10% of clients on big APs with 20 to 30 clients and sometimes occurs very infrequently (once every day or two -- or sometimes every hour or less). Hence, it has been difficult to isolate -- it may be that only some chips show this behaivor or some characteristics of the multipath environment of the specific installaion make this issue show up. The problem does not exist with 5212 and newer chipsets. We have made a workaround that fixes the disconnects and shows normal data throughput. We will put it in the next version of 2.8.

Another 'work around,' would be to put affected stations in WDS mode to connect to the AP -- as our APs already have such a workaround for other issues (to do with non-Atheros chipsets and non-MikroTik systems).

John

REDTDI · Tue Sep 28, 2004 10:58 pm

Hi John:

We have two links that only use Atheros 5212 interfaces that have the same connect disconnect problem. The links both connect and disconnect about 4 or 5 times a day. I will send support files to the support email address for you to look at.

Thanks,
Ken

ghmorris · Tue Sep 28, 2004 10:59 pm

We are having the disconnect problem with both 5211 and 5212 cards.

The problem incidence increases with link variability, in other words, if the link has a somewhat variable rssi, the chance of the link suffering disconnects increases. We originally put the problem down to fade, but since we've been tracing rssi in PRTG fade has been ruled out as a problem.

One link in particular disconnects about once every five hours for between one and 30 seconds. It uses 5212 cards and, other than the disconnects, performs well. Another using 5212s usually disconnects for two seconds per instance, several times per day.

George

tully · Wed Sep 29, 2004 10:04 am

The work around will work with all chipsets, so it will address these issues also.

John

Michaelg · Mon Oct 11, 2004 8:37 pm

Does anyone have a followup on this issue? Upgrading my systems to 2.8.17 only made tings more unreliable. I have a mix of 5211 and 5212 on varius hardware platforms.
With erlier versions (2.8 and 2.7) this never was a problem. When trying to downgrade the systems back to an older vs. only made more problems... ie. kernel panics and crashes.
This problem makes me look at other solutions than MT.

rgs
Michaelg

cmit · Mon Oct 11, 2004 9:13 pm

That sounds rather odd. I'm led to suppose there might be another problem - bad hardware perhaps? I've not seen big issues with 2.8.17 wireless. And downgrading should be causing no hurt, either.

Perhaps try a complete re-install with the software version you intend to use (I'd suggest trying a fresh install of 2.8.17) - you won't loose your license, if you re-install via the netinstall and check the appropriate checkbox.

Michaelg · Mon Oct 11, 2004 11:41 pm

Yes, i admit it sounds weird. I dont think it's a hardware problem as i'm using both RB230, intel, and VIA mainboards and it dossent seem to matter witch platform running. Radios are all MT brand.

Of course i could reinstall all of it... but i have about 40 MT's most of then in towers.

Michaelg · Tue Oct 12, 2004 6:29 pm

I finaly found the problem. It is a problem with the RB14 board. Installing 4 RB11 instead, solved the disconnect problem. I never had this problem with earlier versions.

pauljatho · Mon Oct 25, 2004 2:49 pm

I run my entire network with the RB230 and Atheros 5212 cards, when I uploaded 2.8.17 without wireless-legacy I only experienced problems on my 5.8Ghz links !! and not my 2.4Ghz links. I uploaded wireless-legacy without removing the wireless package and all of my problems were solved. I do not have any issues running both wireless and wireless-legacy and I have about 15 RB230's out there with this config.

I also get no errors when running /system check-install.

jober · Tue Oct 26, 2004 12:06 am

I just upgraded from 2.8.11 to 2.8.18 and it caused the 5.8 wireless link to slow to 1.5 meg. I ftped the wireless-legacy up and rebooted but it dident change a thing.
I see that maybe I should remove the wireless package and upload the wireless-legacy package again but I am scared it will mess up the essid s and routing like it did on the last upgrade. I had to drive to the tower and redo the names,routers,etc.

Also if I look in the WinBox Package List wireless-legacy does not show up.

djape · Sat Nov 06, 2004 8:55 pm

I have the same issue with 2.8.16 ping arround 500ms. I noticed two packages: wireless and wirelless legacy. My other AP's works just fine with wireless only. So, should I remove wireless legacy? Is thos going to leave me withot wireless so I need to configure it again?
I am asking to much?

Cheers...

how to run wireless-legacy in 2.8.16?

how to run wireless-legacy in 2.8.16?

Re: how to run wireless-legacy in 2.8.16?

5212 has same problem...

Disconnects

speed problems

Who is online