What's new in 5.0rc9 (2011-Feb-09 13:57):

*) wireless - fixed disconnect problem on long distance
802.11 40MHz links;
*) wireless nv2 - fixed station mode that broke when station-bridge
was introduced
*) wireless - more improvements for 11n compatibility;
*) kvm - fix guest starting;

http://www.mikrotik.com/download.html

About my previous post from 5.0 rc8 ... The ROS with level 6 only supported 1500 concurrent PPPoE connections... why? Regards,

About my previous post from 5.0 rc8 ... The ROS with level 6 only supported 1500 concurrent PPPoE connections... why? Regards,

It's possible that your hardware is not powerful enough. We have not heard such reports before

About my previous post from 5.0 rc8 ... The ROS with level 6 only supported 1500 concurrent PPPoE connections... why? Regards,

It's possible that your hardware is not powerful enough. We have not heard such reports before

Server Dell R410 with two processors Xeon quad-core 2.4Ghz (16 cores) with 32GB RAM DDR3... it is not powerful?

what happens when you have 1500 connected, and 1501 tries to connect ?

what happens when you have 1500 connected, and 1501 tries to connect ?

1500 connects. From 1501 only appears in the log: PPPoE connection established from (MAC).

routerboard upgrade doesn't work v5rc9

[admin@home] > system routerboard upgrade
Do you really want to upgrade firmware? [y/n]
y
firmware upgraded successfully, please reboot for changes to take effect!

< ... reboot ... >

[admin@home] > system routerboard print
routerboard: yes
model: "750"
current-firmware: "2.28"
upgrade-firmware: "2.32"

what happens when you have 1500 connected, and 1501 tries to connect ?

1500 connects. From 1501 only appears in the log: PPPoE connection established from (MAC).

did you send supout.rif file to support? what is the ticket number, I will check status. We need the file from the moment when 1501 connects. Preferrably with PPP debug logs enabled

[admin@home] > system routerboard print
routerboard: yes
model: "750"
current-firmware: "2.28"
upgrade-firmware: "2.32"

worked for me.

Hello,

I've just installed 5.0rc9 and under "Files" [Restore] button is missing...

Hello,

I've just installed 5.0rc9 and under "Files" [Restore] button is missing...

known bug

worked for me.

[admin@home] /system routerboard> print
routerboard: yes
model: "750"
current-firmware: "2.28"
upgrade-firmware: "2.32"
[admin@home] /system routerboard> upgrade
Do you really want to upgrade firmware? [y/n]
y
firmware upgraded successfully, please reboot for changes to take effect!
[admin@home] /system routerboard> print
routerboard: yes
model: "750"
current-firmware: "2.32"
upgrade-firmware: "2.32"

<... few minutes passed ... >

[admin@home] /system routerboard> print
routerboard: yes
model: "750"
current-firmware: ""
upgrade-firmware: "2.32"

<... some more minutes passed ... >

[admin@home] /system routerboard> print
routerboard: yes
model: "750"
current-firmware: "2.28"
upgrade-firmware: "2.32"

If I reboot the device I get 2.28 running on it.

what happens when you have 1500 connected, and 1501 tries to connect ?

1500 connects. From 1501 only appears in the log: PPPoE connection established from (MAC).

did you send supout.rif file to support? what is the ticket number, I will check status. We need the file from the moment when 1501 connects. Preferrably with PPP debug logs enabled

[Ticket#2011021066000502]

regards,

A question about v5 features (btw I personally like the burst for PCQ and the gre for cisco compatibility):

In an article posted by Mikrotik (I do not have the link) it said that RouterOS supports 200 networks or aggregates in bgp announcement. Will this limitation be removed?

A question about v5 features (btw I personally like the burst for PCQ and the gre for cisco compatibility):

In an article posted by Mikrotik (I do not have the link) it said that RouterOS supports 200 networks or aggregates in bgp announcement. Will this limitation be removed?

I don't know any such limits, where did you read it ?

Struck,

Do you have problems with RX Drops like here: http://forum.mikrotik.com/viewtopic.php?f=3&t=38343

with that machine with 16 cores and 1500 PPPoE users?

Struck,

Do you have problems with RX Drops like here: http://forum.mikrotik.com/viewtopic.php?f=3&t=38343

with that machine with 16 cores and 1500 PPPoE users?

16 real cores on 8 real cores with HT??? if 8 go to the BIOS and disable HT, RouterOS benefit more on that. Did you made your IRQ management?

Yes it is better to disable HT, specially regarding rx drops.

Maybe 5.0 rc8 or rc9 can make better use of all cores ? Struck ?

IPSEC still no worky on RB1100. Works on RC7, but not 8 and 9. Doesnt matter really. Im sending it back.

Struck,

Do you have problems with RX Drops like here: http://forum.mikrotik.com/viewtopic.php?f=3&t=38343

with that machine with 16 cores and 1500 PPPoE users?

I have no problem with RX drops on this machine, only PPPoE problems...

Struck,

Do you have problems with RX Drops like here: http://forum.mikrotik.com/viewtopic.php?f=3&t=38343

with that machine with 16 cores and 1500 PPPoE users?

I have no problem with RX drops on this machine, only PPPoE problems...

And what is the bandwidth on interfaces for this machine?

Struck,

Do you have problems with RX Drops like here: http://forum.mikrotik.com/viewtopic.php?f=3&t=38343

with that machine with 16 cores and 1500 PPPoE users?

16 real cores on 8 real cores with HT??? if 8 go to the BIOS and disable HT, RouterOS benefit more on that. Did you made your IRQ management?

My machine is 8 real cores (2 processors Xeon 2.4Ghz quad core) and I don't made IRQ management.

Struck,

Do you have problems with RX Drops like here: http://forum.mikrotik.com/viewtopic.php?f=3&t=38343

with that machine with 16 cores and 1500 PPPoE users?

I have no problem with RX drops on this machine, only PPPoE problems...

And what is the bandwidth on interfaces for this machine?

Interfaces is 1Gbps full-duplex and the traffic is 75Mbps TX / 25Mbps RX.

Interfaces is 1Gbps full-duplex and the traffic is 75Mbps TX / 25Mbps RX.

Yes, when you go up to 150M+ I am sure that you will notice "rx drops". But so far it is good.

routerboard upgrade doesn't work v5rc9

[admin@home] > system routerboard upgrade
Do you really want to upgrade firmware? [y/n]
y
firmware upgraded successfully, please reboot for changes to take effect!

< ... reboot ... >

[admin@home] > system routerboard print
routerboard: yes
model: "750"
current-firmware: "2.28"
upgrade-firmware: "2.32"

Same thing happened to me. I just kept trying it over and over and over. It finally stayed.

With RC8 11n throughtput 227mbit UDP / 202 mbit tcp, with rc9 197mbit UDP / 163mbit TCP

Using Winbox, if I edit the last firewall rule in the list, then click OK or cancel, then double-click the rule again it will move itself to the top of the list. This is really bad if the rule that is last in the list is "drop everything". I am able to duplicate this every time in winbox on RC5 through RC9. I did notice that this only occurs if the list of firewall rules is longer than what can be displayed (so that there is a scroll bar). If the rule list is shorter so it fits in the Firewall window without scrolling, this issue does not occur.

With RC8 11n throughtput 227mbit UDP / 202 mbit tcp, with rc9 197mbit UDP / 163mbit TCP

how did you measure that?
What protocol, what boards used?
contact support and include detailed info with support output files.

Using Winbox, if I edit the last firewall rule in the list, then click OK or cancel, then double-click the rule again it will move itself to the top of the list. This is really bad if the rule that is last in the list is "drop everything". I am able to duplicate this every time in winbox on RC5 through RC9. I did notice that this only occurs if the list of firewall rules is longer than what can be displayed (so that there is a scroll bar). If the rule list is shorter so it fits in the Firewall window without scrolling, this issue does not occur.

Hahah yes I have this problem as well. It happens very often over RDP session on a 1280x1024 resolution. I think I was running the latest WinBox exe Im not sure.

What's new in 5.0rc9 (2011-Feb-09 13:57):

*) wireless - fixed disconnect problem on long distance
802.11 40MHz links;
*) wireless nv2 - fixed station mode that broke when station-bridge
was introduced
*) wireless - more improvements for 11n compatibility;
*) kvm - fix guest starting;

http://www.mikrotik.com/download.html

- "station-bridge"? Is this a new kind of station? Never seen it before...
- what are these improvements fo r11n compatibility?

What about ros 4.16 NV2 package? Do we get an upgrade here as well? I use these and even I use some on a ´n´- link.
Are these upgrades helping on these links?

Yes it seems this is a new feature introduced to the wide public with newsletter30.pdf:

http://wiki.mikrotik.com/wiki/Manual:Wi ... ion-bridge

About my previous post from 5.0 rc8 ... The ROS with level 6 only supported 1500 concurrent PPPoE connections... why? Regards,

It's possible that your hardware is not powerful enough. We have not heard such reports before

Server Dell R410 with two processors Xeon quad-core 2.4Ghz (16 cores) with 32GB RAM DDR3... it is not powerful?

32GB RAM??? What does "/system resource" print?

A question about v5 features (btw I personally like the burst for PCQ and the gre for cisco compatibility):

In an article posted by Mikrotik (I do not have the link) it said that RouterOS supports 200 networks or aggregates in bgp announcement. Will this limitation be removed?

I don't know any such limits, where did you read it ?

http://wiki.mikrotik.com/wiki/Manual:BG ... _routes.3F

If your don't have many routes to announce and want the best control over them, use BGP networks or aggregates. Note that both maximal BGP network and aggregate count is limited to 200.

Otherwise use route redistribution options, configurable under BGP instance settings.

Is this not a 200 advertisments limit? The problem is we advertise a lot of /32 routes so it suddenly jumps from some prefixes to almost 180 in our case. We cannot use redistribution, it is not a viable solution.

what happens when you have 1500 connected, and 1501 tries to connect ?

so which RB is working well with at least 2000 active L2TP connection? ()

what happens when you have 1500 connected, and 1501 tries to connect ?

so which RB is working well with at least 2000 active L2TP connection? ()

Like I said, there is no such limitation, it must be some other problem

If anyone else is having trouble upgrading RouterBOOT, please send supout.rif files to support. Make sure you use rc9

Is this not a 200 advertisments limit? The problem is we advertise a lot of /32 routes so it suddenly jumps from some prefixes to almost 180 in our case. We cannot use redistribution, it is not a viable solution.

I successfully announced about 800-900 dynamic routers on 5.0rc5.

Using Winbox, if I edit the last firewall rule in the list, then click OK or cancel, then double-click the rule again it will move itself to the top of the list. This is really bad if the rule that is last in the list is "drop everything". I am able to duplicate this every time in winbox on RC5 through RC9. I did notice that this only occurs if the list of firewall rules is longer than what can be displayed (so that there is a scroll bar). If the rule list is shorter so it fits in the Firewall window without scrolling, this issue does not occur.

Which OS are you using? I can repeat this problem on Windows7 but not if using Wine on Linux, or Windows XP.

IPSEC still no worky on RB1100. Works on RC7, but not 8 and 9. Doesnt matter really. Im sending it back.

Please contact support and send them supout file from the router.

restore button is not missing, it's moved to "right click menu", so you don't accidentally click it.

What's new in 5.0rc9 (2011-Feb-09 13:57):

*) wireless - fixed disconnect problem on long distance
802.11 40MHz links;
*) wireless nv2 - fixed station mode that broke when station-bridge
was introduced
*) wireless - more improvements for 11n compatibility;
*) kvm - fix guest starting;

http://www.mikrotik.com/download.html

- "station-bridge"? Is this a new kind of station? Never seen it before...
- what are these improvements fo r11n compatibility?

What about ros 4.16 NV2 package? Do we get an upgrade here as well? I use these and even I use some on a ´n´- link.
Are these upgrades helping on these links?

Compatibility for N: when Intel chipset clients and Macbook Broadcom chipset clients connects to Mikrotik N AP.
station-bridge mode is for Nv2 if you want to bridge wireless clients but do not want to use station-wds. More infor here:
http://wiki.mikrotik.com/wiki/Manual:Wi ... ion-bridge

About my previous post from 5.0 rc8 ... The ROS with level 6 only supported 1500 concurrent PPPoE connections... why? Regards,

We just tested 1550 connections, and some more are still connecting, no problems. And we have lower power server than you, so it's neither RouterOS nor hardware problem. Maybe peculiar configuration, or maybe problem is simply not there? maybe you simply don't have more than 1500 active users?

Compatibility for N: when Intel chipset clients and Macbook Broadcom chipset clients connects to Mikrotik N AP.

Does this mean that Intel clients are finally able to use speeds higher than 54 Mbit/s for uplink?

http://wiki.mikrotik.com/wiki/Manual:BG ... _routes.3F

If your don't have many routes to announce and want the best control over them, use BGP networks or aggregates. Note that both maximal BGP network and aggregate count is limited to 200.

Otherwise use route redistribution options, configurable under BGP instance settings.

Is this not a 200 advertisments limit? The problem is we advertise a lot of /32 routes so it suddenly jumps from some prefixes to almost 180 in our case. We cannot use redistribution, it is not a viable solution.

This limitation applies only to bgp network entry count and aggregate entry count. If you are redistributing routes from the routing table then there are no hardcoded limitations. If you have specific problem write to support with detailed description of the problem and attached supout file.

Compatibility for N: when Intel chipset clients and Macbook Broadcom chipset clients connects to Mikrotik N AP.

Does this mean that Intel clients are finally able to use speeds higher than 54 Mbit/s for uplink?

correct.

restore button is not missing, it's moved to "right click menu", so you don't accidentally click it.

"right click menu" ?? Can't find it there

and also here

Upgrading from 4.16 to 5.0rc9:

In Wireless/Registrations, when client connects,
1) it (sometimes) only shows one value in Rx/Tx signal strength for a few minutes before both values are displayed.
2) for a few minutes, you cannot right-click and ping registration, it only try to ping ip 0.0.0.0. Leave it for a few minutes and it pings again.
3) If I ping it from Tools/ping and manually neter the ip, then it pings and I can ping it from registrations right-click again.

I'll send this to support as well.

Ekkas

Voip issues with 5.0rc9 (upgraded from 4.16).

Although bandwidth tests and pings look ok, we are getting more and more calls coming in from clients on our wireless network that says either VoIP call quality is bad or that calls drop.

Anyone else have this?
On 4.16 all was fine, since upgrade this started.
I have almost 30 highsites and 200 MT CPEs, I'd hate to have to downgrade all of them, so if there is a quick fix or something, I'd be gratefull.

Ekkas

ekkas, try disabling compression.
Try to play with the hw-retries setting - lower or increase it.
Try disabling the adaptive-noise-immunity.

Any idea when you will support the standard SATA controller or USB in Dell Poweredge RX10 systems ?

We're having trouble in R210 and R310.

Tried CD installer and then also netinstall to USB memory card.
Both give the dreaded no hard drives found error and halts.

Tried emulating USB harddrive and setting to AUTO. Running multiple USB memory cards, nothing seems to help.

Would be good if the installer was a bit more verbose of the actual errors that the installer gets.

Thanks Uldis,

Try to play with the hw-retries setting - lower or increase it.
Try disabling the adaptive-noise-immunity.

On both AP & station?


...and, is it a temporary problem (fixed in later ROS5 release) or a permanent change?


Ekkas

Major problem (for me) with 5.0rc9
Upgraded all highsites + clients.
Some (especially older RB133C3) connect, but can't ping.
If you MAC telnet to it it asks for UN/PW but then disconnect before you get the MT splash text.

Downgrade AP to 4.16, the client (RB133C3) is still on R5.0rc9 but now works fine, all clients connected again.

Ekkas

edit: It seems to be more of a problem on AP with PPC (RB333) than other.

Upgrading from 4.16 to 5.0rc9:

In Wireless/Registrations, when client connects,
1) it (sometimes) only shows one value in Rx/Tx signal strength for a few minutes before both values are displayed.
2) for a few minutes, you cannot right-click and ping registration, it only try to ping ip 0.0.0.0. Leave it for a few minutes and it pings again.
3) If I ping it from Tools/ping and manually neter the ip, then it pings and I can ping it from registrations right-click again.

I'll send this to support as well.

Ekkas

2) and 3) are normal behavior on low traffic times. Because the device that has connected and you see in registration table has not yet sent an IP packet revealing an IP address to ping.

2) and 3) are normal behavior on low traffic times.

Don't have it on 4.16 though.
Also if the AP is 5.0rc9, then some (MT ROS 5.0rc9) clients wouldn't connect.
Downgrade to 4.16, all fine again.

Torch is broken, when i double click the source ip to filter, Src. Address changes from 0.0.0.0/0 to 0.0.0.0 not the src ip.

here is a picture after i double clicked 10.10.23.4 on Src column:


Regards

Major problem (for me) with 5.0rc9
Upgraded all highsites + clients.
Some (especially older RB133C3) connect, but can't ping.
If you MAC telnet to it it asks for UN/PW but then disconnect before you get the MT splash text.

Downgrade AP to 4.16, the client (RB133C3) is still on R5.0rc9 but now works fine, all clients connected again.

Ekkas

edit: It seems to be more of a problem on AP with PPC (RB333) than other.

What wireless mode are you running? 802.11?

What wireless mode are you running? 802.11?

yes

What wireless mode are you running? 802.11?

yes

Could it be that AP & clients was on 'unspecified' causing a problem. I would assume if 'unspecified' on AP is selected, it will default to 802.11?

Voip issues with 5.0rc9 (upgraded from 4.16).

Although bandwidth tests and pings look ok, we are getting more and more calls coming in from clients on our wireless network that says either VoIP call quality is bad or that calls drop.

Anyone else have this?
On 4.16 all was fine, since upgrade this started.
I have almost 30 highsites and 200 MT CPEs, I'd hate to have to downgrade all of them, so if there is a quick fix or something, I'd be gratefull.

Ekkas

Try making sure IP firewall service ports SIP is disabled.

VOIP over WiFi can be hard...

VOIP over WiFi can be hard...

We do 1000s of VoIP calls a day for quite some time now.
Been through the learning curve. Paid the school fees.

The fact is that 4.16 works great, ROS 5.0rc9 still have major problems.
Also it seems the further the clients are from tower, the worse the problem is.
Also, the longer since last reboot, the slower far clients get. (Memory leak?)

I'd love to have ROS 100% taking in account that I just ordered 25 SXTs as a start for a NV2 network.
But I trust MT will find/fix the problem.
Only thing that concerns me is that noone else seem to experience this.

We had to downgrade all APs and busy downgrading CPEs as we get comments like :"These phones of yours is now crap!" lol

Ekkas

Compatibility for N: when Intel chipset clients and Macbook Broadcom chipset clients connects to Mikrotik N AP.

Does this mean that Intel clients are finally able to use speeds higher than 54 Mbit/s for uplink?

correct.

Great! Can I expect it to be backported to v4?

VLAN after reboot doesn't work!!
You change number starts VLAN to work after reboot again doesn't work!
5RC9 (rb411,rb433 radio nstreme nv2 wds )

VLAN after reboot doesn't work!!
You change number starts VLAN to work after reboot again doesn't work!
5RC9 (rb411,rb433 radio nstreme nv2 wds )

I have experienced something similar or exactly the same, so I reconfigured the PtP link to Layer 3 instead of bridge-wds + VLAN.

As that not from a hand all to reconstruct
At me two flights on 70 km loading nearby 80 megabit. The processor is loaded on 80 % I think that ptp will kill him


VLAN nv2 station-bridge Doesn't work


If behind the bridge and in front of the bridge to put routers that VLAN passes

ekkas, try disabling compression.
Try to play with the hw-retries setting - lower or increase it.
Try disabling the adaptive-noise-immunity.

The log are filled within a minute - errors:
disconnected ok
connected
reassociating

these people are like 300 - 600 meters from the omni antenna and using 27db grid antenna.

when on 4.16, there was no problem at all with disconnected - reconnected, but RC9 is way beyond error disconnected.

@uldis
I did follow the above guide, but no help at all.

RB433 + R52Hn one chain.

hope for quick solution please...

Whether it is possible to add in following assemblages a variable on decrease in sensitivity of the receiver?? It is rather useful in зашумлёном an ether

What wireless mode are you running? 802.11?

yes

That is the problem, unless the MT guys have fixed it with the RC9 release the NV2 package won't run in 802.11 mode without the AP interface locking up after a random period of time. What happens is the AP will stop transmitting data, the clients stay in the registration table but you can't pass any data to them. If you disable/re-enable the AP interface the clients will come back and work normally for some random amount of time before the AP interface locks up again. This is a known issue and I am not sure why MT doesn't list it as a "known issue" in the release notes. For me it is 100% repeatable, if I run the NV2 package on any of my AP's in 802.11 mode they will stop working. The recommendation MT made was for me to swap my XR2 cards for a card with an N chipset. This doesn't seem to help though because there are others here who are having the same issue with the N cards.

It is definitely a problem with the AP side because you can leave NV2 package installed on the clients but roll the AP back to a version of the old wireless package and the problems go away. The last I heard from Uldis is that they were working on it but I haven't heard anything in several weeks. Is there any update on this Uldis?

But to run a mixed Ubiquity/MT CPE network and ROS 5, what other option is there except 802.11?
Ekkas

But to run a mixed Ubiquity/MT CPE network and ROS 5, what other option is there except 802.11?
Ekkas

No there isn't. The only option you have is to roll back to V4.x and run the standard wireless package.

What wireless mode are you running? 802.11?

yes

That is the problem, unless the MT guys have fixed it with the RC9 release the NV2 package won't run in 802.11 mode without the AP interface locking up after a random period of time. What happens is the AP will stop transmitting data, the clients stay in the registration table but you can't pass any data to them. If you disable/re-enable the AP interface the clients will come back and work normally for some random amount of time before the AP interface locks up again. This is a known issue and I am not sure why MT doesn't list it as a "known issue" in the release notes. For me it is 100% repeatable, if I run the NV2 package on any of my AP's in 802.11 mode they will stop working. The recommendation MT made was for me to swap my XR2 cards for a card with an N chipset. This doesn't seem to help though because there are others here who are having the same issue with the N cards.

It is definitely a problem with the AP side because you can leave NV2 package installed on the clients but roll the AP back to a version of the old wireless package and the problems go away. The last I heard from Uldis is that they were working on it but I haven't heard anything in several weeks. Is there any update on this Uldis?

I have had similar issues with non-N wireless cards on my RB600A running 5.0betas. No NV or NV2 in use just a regular 802.11a/802.11b and in "any" mode. Only solution was to reboot the box as disabling/enabling the affected interface didn't do anything. Downgrade to 4.16 fixed that one for me.

What wireless mode are you running? 802.11?

yes

That is the problem, unless the MT guys have fixed it with the RC9 release the NV2 package won't run in 802.11 mode without the AP interface locking up after a random period of time. What happens is the AP will stop transmitting data, the clients stay in the registration table but you can't pass any data to them. If you disable/re-enable the AP interface the clients will come back and work normally for some random amount of time before the AP interface locks up again. This is a known issue and I am not sure why MT doesn't list it as a "known issue" in the release notes. For me it is 100% repeatable, if I run the NV2 package on any of my AP's in 802.11 mode they will stop working. The recommendation MT made was for me to swap my XR2 cards for a card with an N chipset. This doesn't seem to help though because there are others here who are having the same issue with the N cards.

It is definitely a problem with the AP side because you can leave NV2 package installed on the clients but roll the AP back to a version of the old wireless package and the problems go away. The last I heard from Uldis is that they were working on it but I haven't heard anything in several weeks. Is there any update on this Uldis?

FYI, I have been battling this problem at several locations with RB493AH/RB433AHs and R2n cards at several sites. Standard 802.11N, single chain, no extension channel. Even dropping down to G only doesnt fix it. The registrations are just locked and nobody can connect until the interface is stopped/started.

I just upgraded one of the sites to RC9 to see if that fixes it. But All the RCs so far have done this. I think it is only certain types of clients, but I dont know which ones. I havent ever had a problem in my office, even swapping the hardware with hardware that has exhibited the problem at a customer site. So Im leaning towards certain client cards. Non NV2, as a standard AP.

I also have same problem, without downgrade on 4.16 I can not solve it.

I think it is only certain types of clients

I suspect it is distance related. Even with VoIP problems we have on 5.0rc9, the further the client, the worse the problem.
It also seems that further clients have higher probability to connect but not pass traffic.
All nearby clients have neither problem(bad VoIP call quality nor stale connection).
I suspect that is why same hardware in office setup would not show the same problem.

Well, when it happens, NO clients can connect. What kind of signal are you seeing when it happens, ill check.

Seems like there are a few issues still unresolved.
I upgraded because I read it is final RC and my impression was that basic issues are resolved.

Problem is clients tend to remember a few hours or day offline, but doesn't remember the 24/7 reliability they've had the other 364 days.
I even have users that run permanent ping software and want discount for the hours they were offline in a month!
Damn 'users'. If only everyone was geeks... lol

Edit: I still think ROS 5 & NV2 will be fantastic once wrinkles are ironed out. Waiting in patient anticipation.

Yes, I totally understand your point. End users are very demanding. And in turn, we also demand rock-solid networks to give them service with

Have you tried to convince with "good" those users who monitor with permanent ping, not to do it?

PRoblems still with ROS5 is just on (some)wireless links?
So I can leave wired routers on ROS5 safely?
Got a few hotspot/usermanager routers that I'd hate to downgrade again.

It isn't a client problem it is an AP problem, as I mentioned you can leave the clients running the NV2 package in 802.11 mode and roll back the AP to 4.x or earlier with the standard wireless package and the problems go away. I gave MT support access to one of our AP's running 4.16 while it was in this locked up state they said the AP interface wasn't moving any data but didn't know why.

There are still some severe glaring issues with the new wireless package, especially with 802.11 mode. They have known of this issue for over a month now and still haven't resolved it. Why, I don't know but I do know they could save a lot of people a lot of time and frustration if they would just add it as a known issue until they can get it fixed.

On a side note I do have an AP that I have been running 4.16 in NV2 mode with a few clients on it that has been performing very well for the last month,. The caveat to running NV2 for me has been that clients have to have a SNR of at least 30db to avoid having issues with timing related disconnects. Even with an SNR of 25db clients will chain disconnect with timing error messages in the log. It seems like 30db is the magic number for some reason.

FYI, I have been battling this problem at several locations with RB493AH/RB433AHs and R2n cards at several sites. Standard 802.11N, single chain, no extension channel. Even dropping down to G only doesnt fix it. The registrations are just locked and nobody can connect until the interface is stopped/started.

I just upgraded one of the sites to RC9 to see if that fixes it. But All the RCs so far have done this. I think it is only certain types of clients, but I dont know which ones. I havent ever had a problem in my office, even swapping the hardware with hardware that has exhibited the problem at a customer site. So Im leaning towards certain client cards. Non NV2, as a standard AP.

I have a 17km 5ghz link. I get near 100% ccq in A mode. Enabling any Mimo based modes drops ccq to <35% and I get lower throughput and connection drops.

The problem is, a 54mbit A mode link is too slow to handle the load I need and enabling mimo and extension channel makes it worse.

The Mimo capable cards will not do turbo mode.

Yes, Atheros f**ed us by not including turbo mode.

When you enabled the MIMO modes, what antennas did you use and how were they set up? Have toy tested each set of antennas with A mode?

Using Winbox, if I edit the last firewall rule in the list, then click OK or cancel, then double-click the rule again it will move itself to the top of the list. This is really bad if the rule that is last in the list is "drop everything". I am able to duplicate this every time in winbox on RC5 through RC9. I did notice that this only occurs if the list of firewall rules is longer than what can be displayed (so that there is a scroll bar). If the rule list is shorter so it fits in the Firewall window without scrolling, this issue does not occur.

Which OS are you using? I can repeat this problem on Windows7 but not if using Wine on Linux, or Windows XP.

I am also using Windows 7. I also just tested on Mac OS X and Linux both with Wine and both seem fine. Problem only occurs in Windows 7.

I'm having stability issues with 5.0RC9 and a 493AH with one R52n using any mode (802.11, NV2 or anything in bridge mode) ... After about an hour or two it will lock up completely requiring a power off / power on. Anyone else having a stability issue?

everyone who has problems with wireless in RouterOS v5.0rc9, please contact the support@mikrotik.com about it - include the support output file from RouterOS v5.0rc9.

For those that have problems with 802.11 protocol mode (isn't working in RouterOS v5.0rc9 and v4.16 with wireless-nv2 package) please check if the problem begins when client with a big distance connects, check if you remove form the registration table the situation improves. If you already downgraded your router to v4.16 regular wireless package, check if those clients that had big distance has also big ack-timeout values.
One fix/workaround would be to lower the hw-retries setting to 4 or 7 and check if the situation improves when those clients with big distance connects.
Please report with all that information to support.

VLAN nv2 station-bridge Doesn't work
If behind the bridge and in front of the bridge to put routers that VLAN passes

Just tested and it works in both cases if the Nv2 bridged interfaces passes Vlan traffic and also if the Vlan interface is on the wireless interface.
Please contact support about your problem.

http://wiki.mikrotik.com/wiki/Manual:BG ... _routes.3F

If your don't have many routes to announce and want the best control over them, use BGP networks or aggregates. Note that both maximal BGP network and aggregate count is limited to 200.

Otherwise use route redistribution options, configurable under BGP instance settings.

Is this not a 200 advertisments limit? The problem is we advertise a lot of /32 routes so it suddenly jumps from some prefixes to almost 180 in our case. We cannot use redistribution, it is not a viable solution.

This limitation applies only to bgp network entry count and aggregate entry count. If you are redistributing routes from the routing table then there are no hardcoded limitations. If you have specific problem write to support with detailed description of the problem and attached supout file.

Is there no way to bypass this limit? As I was saying we cannot redistribute as the routes go into the bgp network entry count. Why is there such a limit?

Thank you.

I cannot imagine any setup where you would need more than 200 BGP network entries. Typically you have assigned one to two address block not hundreds.

Well, is that a really a valid point for the limit?

In our case we announce /32 IP blocks from the network area. That is the setup, that is what we need, and that is why we do not use Cisco, but Mikrotik, as we have the flexibility to use scripting to our own interest, so it is automated by scripts. So if we have a /20 IP block and we get 100 IPs which have to be announced as /32 we suddenly get a +100 on the 200 maximal count. If we segment the /20 to /27 blocks, and we want to null route the gateway IPs without redistribution (as that WILL result in loops if IGP is involved) so they cannot be reached from the Internet, imagine that we already broke that 200 limit.

So, can't it simply be removed for flexibility of such setups?

When will function for the System Health Routeros x86?

everyone who has problems with wireless in RouterOS v5.0rc9, please contact the support@mikrotik.com about it - include the support output file from RouterOS v5.0rc9.

For those that have problems with 802.11 protocol mode (isn't working in RouterOS v5.0rc9 and v4.16 with wireless-nv2 package) please check if the problem begins when client with a big distance connects, check if you remove form the registration table the situation improves. If you already downgraded your router to v4.16 regular wireless package, check if those clients that had big distance has also big ack-timeout values.
One fix/workaround would be to lower the hw-retries setting to 4 or 7 and check if the situation improves when those clients with big distance connects.
Please report with all that information to support.

What does these settings should to do to eliminate total radio freeze?
My RB600A just had that wireless interface lockup (tried scanning for other APs and frequency scan, all returned "silence") running ROS 4.16 even without any clients connected to it nor likely not even attempting to do so, so that retry/ack-timeout/distance is likely not the root cause of it.
A suppout.rif file:
http://ra.vendomar.ee/~ivo/mikrotik/4.1 ... supout.rif
And the same system after reboot (wlan2 is working again):
http://ra.vendomar.ee/~ivo/mikrotik/4.1 ... supout.rif

Ivoshiee, please upgrade the Routerboard bios to v2.27.
Are you using RB604 board or RB502?
wlan2 wireless card failed to respond and also RouterOS wasn't able to reset the card. In which slot the wireless card is seated? As it looks more like hardware problem as it is also happening for you in v4.16 with regular wireless package.

When will function for the System Health Routeros x86?

I have 7 x86 routers with different motherboards and health is running only on 4. Mikrotik says try to upgrade bios, but i cant do it now beacause it is production routers and i dont have replacement.one of them had showed health with 4.16 but after upgrade to 5rc9 system health show nothing

we would like to know as well
looks like health only shows for old m/boards

RB532 - No routerboard info

the routing process crash / restart have been fixed?

the last version i tried was 5.0rc7 , on x86 the ospf / bgp process restart just after some ospf neighbor goes down, and the routerboard version mipsbe the routing process gets 100% and nevers came back..

may be I'm off from the topic here,
but I do have problem with UserManager on v5.0rc9, i don't know its is a bug or just am miss setting something.
the major problem is, when i active the payment gateway (in this case i use paypal) and everytime the user try to buy
credit from me via paypal on user-manager and click purchase button and it proses to paypal account, the router/usermanager
automatically accept the user with status "started" even the payment not accepted yet (not approved yet) and the worse here
even the user not made any payment at all (not go to paypal to pay it bill, but just ignore it and get back to login page and login and enjoying internet in free). I already disable accept pending option on payment gateway setting. is anyone here have the same problem or it just me? could all you guys give me a hand here... T.T

i'm use RB750 | v5.0rc9

Ivoshiee, please upgrade the Routerboard bios to v2.27.

Done that. Does older ROS work with newer firmwares and vice versa?

Are you using RB604 board or RB502?

I have a RB502.

wlan2 wireless card failed to respond and also RouterOS wasn't able to reset the card. In which slot the wireless card is seated?

wlan1 and wlan2 are on that very same RB502.

As it looks more like hardware problem as it is also happening for you in v4.16 with regular wireless package.

What piece of hardware is to blame? RB600A, RB502, wireless cards, power, ...?

the routing process crash / restart have been fixed?

the last version i tried was 5.0rc7 , on x86 the ospf / bgp process restart just after some ospf neighbor goes down, and the routerboard version mipsbe the routing process gets 100% and nevers came back..

Please contact support about this problem.

Ivoshiee, please upgrade the Routerboard bios to v2.27.

Done that. Does older ROS work with newer firmwares and vice versa?

Are you using RB604 board or RB502?

I have a RB502.

wlan2 wireless card failed to respond and also RouterOS wasn't able to reset the card. In which slot the wireless card is seated?

wlan1 and wlan2 are on that very same RB502.

As it looks more like hardware problem as it is also happening for you in v4.16 with regular wireless package.

What piece of hardware is to blame? RB600A, RB502, wireless cards, power, ...?

please check if you have this fix on RB502:
http://forum.mikrotik.com/viewtopic.php ... 34#p218834

the routing process crash / restart have been fixed?

the last version i tried was 5.0rc7 , on x86 the ospf / bgp process restart just after some ospf neighbor goes down, and the routerboard version mipsbe the routing process gets 100% and nevers came back..

Please contact support about this problem.

Ticket#2011021566000226

Ivoshiee, please upgrade the Routerboard bios to v2.27.

Done that. Does older ROS work with newer firmwares and vice versa?

Are you using RB604 board or RB502?

I have a RB502.

wlan2 wireless card failed to respond and also RouterOS wasn't able to reset the card. In which slot the wireless card is seated?

wlan1 and wlan2 are on that very same RB502.

As it looks more like hardware problem as it is also happening for you in v4.16 with regular wireless package.

What piece of hardware is to blame? RB600A, RB502, wireless cards, power, ...?

please check if you have this fix on RB502:
http://forum.mikrotik.com/viewtopic.php ... 34#p218834

Interesting. I'll try to implement that fix and report back any improvements. Still, it does not explain my other RB433AH similar radio freeze issue under ROS 5.0betas.

ok, well, I rolled back to 4.16 but now my wireless card functions very weak!

Customers nearby that were -55 db is now -89 db, and card noise floor were -79 is now -51!

what might be wrong here?

I even did card "Reset Configuration"

Card is R52Hn

thanks,

Are you running the NV2 wireless package? If so do you have a noise floor threshold set?

ok, well, I rolled back to 4.16 but now my wireless card functions very weak!

Customers nearby that were -55 db is now -89 db, and card noise floor were -79 is now -51!

what might be wrong here?

I even did card "Reset Configuration"

Card is R52Hn

thanks,

Are you running the NV2 wireless package? If so do you have a noise floor threshold set?

No i ma not running "NV2 wireless", I tried to run it on 4.16, but again I got disconnect, reconnect problem so I left that and went to regular wireless package.

If I run the "NV2 wireless", the noise floor is like -90, but the regular wireless package is like -50. Total Noise!!!

With RC8 11n throughtput 227mbit UDP / 202 mbit tcp, with rc9 197mbit UDP / 163mbit TCP

That is really good throughput. Can I ask what setup you have? Our best link is at 270/270Mbps, with throughput of up to 150mbit. I have to use NV2 on that, because with regular Nstreme, it will only link at 65/65Mbps, even with 2 chains.

small workaround for '/system ssh user% problem'

use

/system ssh <host or address> user<tab>

that way auto-completion will work correctly

Ivoshiee, please upgrade the Routerboard bios to v2.27.

Done that. Does older ROS work with newer firmwares and vice versa?

Are you using RB604 board or RB502?

I have a RB502.

wlan2 wireless card failed to respond and also RouterOS wasn't able to reset the card. In which slot the wireless card is seated?

wlan1 and wlan2 are on that very same RB502.

As it looks more like hardware problem as it is also happening for you in v4.16 with regular wireless package.

What piece of hardware is to blame? RB600A, RB502, wireless cards, power, ...?

please check if you have this fix on RB502:
http://forum.mikrotik.com/viewtopic.php ... 34#p218834

I haven't managed to implement that fix yet, but now the affected interface is wlan4. I expect any RB502 issues not to affect any other interfaces not connected to it, so that RB502 is not to be blamed at this case.
Supout.rif files as well:
http://ra.vendomar.ee/~ivo/mikrotik/4.1 ... supout.rif
http://ra.vendomar.ee/~ivo/mikrotik/4.1 ... supout.rif
What is the official stance of MT about that issue? For me personally it is a showstopper bug. How to mitigate that issue?

first you need to implement that fix in order to use PCI correctly. After that test again.