MikroTik RouterOS • View topic

sonny · **Posted:** Fri Feb 10, 2012 10:06 pm

Has anyone thought about integrating NV2 it into AirOS for Nanstation M5 or NS5?
Many ISP´s seems to have a lot of Ubiquity client stuff and consider migrating to NV2 protocol.
Mostly the hardware costs are against to do that.
There is a SDK for AirOS available, I am not an expert in software hacking bu it should not be that hard.

Any comments welcome!

rodolfo · **Posted:** Fri Feb 10, 2012 11:11 pm

it is hard as landing on the moon.

EMOziko · **Posted:** Sat Feb 11, 2012 11:30 am

Good luck mr. Gorski

Raf · **Posted:** Tue Feb 14, 2012 4:31 pm

@Sonny: NV2 and Airmax are proprietary protocols. The will *NEVER* be compatible with each other.

sonny · **Posted:** Wed Feb 15, 2012 8:49 pm

@ Raf
I know this very well! I am following mikrotik since 2002 like ROS 1.3

But AirOS is an open platform with a SDK to develop your own firmware or do modifications.
If someone will implement the wireless driver from mikrotik mibsbe paket - you are done.
Of course less features at client stations.

cheers

normis · **Posted:** Thu Feb 16, 2012 8:11 am

Quote:

someone will implement the wireless driver from mikrotik mibsbe paket

yes, but you would have to get it first. this is proprietary software, so it's not possible to get it.

Raf · **Posted:** Thu Feb 16, 2012 9:48 am

sonny wrote:

@ Raf
I know this very well! I am following mikrotik since 2002 like ROS 1.3

But AirOS is an open platform with a SDK to develop your own firmware or do modifications.
If someone will implement the wireless driver from mikrotik mibsbe paket - you are done.
Of course less features at client stations.

cheers

You're wrong. AirOS has SDK – right, but wireless driver is closed source.

pacoss · **Posted:** Fri Feb 17, 2012 1:53 am

Good luck with nv2.

It is a complete disaster in my 100% mikrotik network. Same speed like nstreme, and clients randomly freezes (you can see them in the reg-list, but no ping, winbox, ...)

sonny · **Posted:** Fri Feb 17, 2012 4:14 am

@pacoss
Something is wrong in your network. Be sure using the latest software and board firmware.
Try to reconfigure locking clients and AP from scratch.
Use if possible only n cards at AP.
Find channel with lowest interference.
Use RF shields on nearby APs.
Set NV2 distance 25% over most distant client.
Try t

imeperiod 3 or 5.
Set timeperiod the same at all APs.

Give karma it helps

are you running ospf?

Ciambot · **Posted:** Mon Feb 20, 2012 3:39 pm

pacoss wrote:

Good luck with nv2.

It is a complete disaster in my 100% mikrotik network. Same speed like nstreme, and clients randomly freezes (you can see them in the reg-list, but no ping, winbox, ...)

Use lastest version of firmware, it solves me a lot of issues.

uldis · **Posted:** Mon Feb 20, 2012 3:58 pm

pacoss, please contact support@mikrotik.com we will provide you with a new package that will improve the stability of your nv2 links if you had control frame timeout disconnection problems. You need to install that test package only on the AP.
This new update will be included in next RouterOS release.

Who is online