Hi,
I have a RB333 with 3.4 RouterOS software.
I reached 23 clients on a RB333 equipped with a level 4 license and I get some serious problem, like ping very slow and CPU at 100%.
So I discovered that the number of customer allowed on 3.0 level 4 was changed from 200 to 20 and I upgraded my RB333 to a level 6 license.
After 2 hours during which all seems working fine, I get the same problem with very slow ping even if the CPU now is about 40-50% and not more 100%.
At the moment 21 customers are registered on a 2,4Ghz antenna using 802.11b (not g) and 2 customer are registrered at 5Ghz using 802.11a.
Hello Normis,
I had a v3.x presentation made by Mikrotik. Reading well, the number of users changed with the license level was referred to the User Manager platform.
Considering that this was not our problem, I made the Torch and there isn’t anything strange.
I don’t understand why ping are so slow.
This is our situation at the moment
.
After the activation of the last 2 or 3 customers we get these stastistics:
even if the throughput of the customer involved is of 7Mb/s and there is no traffic made by it.
The miniPCI is a R52H, set to work just with 802.11b, and the sensitivity declared is the following:
Hello,
after some test we discovered two type of problems:
the first one was that our antenna was moved by a very strong wind we get in last two days, so positioning it again the signals are really improved;
there is an interference between our channel and another network which is using a channel adiacent to our one. This interference was not signalled by the antenna installed on mountain site, because of it isn’t on mountain. The interference was just 1 km. under the mountain in the direction of our signal.
So on mountain we didn’t get anything, whether we get some indication about it on a series of customers all in the same direction of the mountain as indicated in the following picture:
We spoke with the other equipments owners, they changed channel to a non interfering one and we solved the problem.
I’m still waiting some other indication by Mikrotik, but now the problem is solved…