100% new version of NStream (NOT backwards compatable) to include advanced polling, full QOS, reduced latency, dynamic frequency selection WITHOUT disconnecting active clients, automaticly adjusting framing policy (that does not affect QOS)
New version of NStream Dual with automatic fall back to half duplex if one link fails
full antenna diversity support for regular 802.11a/b/g mode
full support for 802.11n and WiMax
ability to read every value displayed in winbox via SNMP, plus create custom snmp OIDs for values calculated through scripts
Isn’t the next version number going to be 3.2.x or 3.1.x instead of 4.0? They had the 2.9.x, 2.8.x, 2.7.x, etc. series before 3.0.
I think Mikrotik have stated they will both be supported when they are supported in Linux with stable drivers.
A feature I would like to request is a ‘PPP IP pool’ that works like the DHCP lease table that is stored periodically. I would like my PPPoE users to get the same IP address, if available, even after rebooting my Mikrotik PPPoE server/router.
If you read the new description of this board, it states “BETA Testing and Feature Suggestions for the next RouterOS release (ROS v4)”.
you can already make PPPoE assign IPs out of a pool, if you want them to be static, assign them that way (most ISPs charge the customer a small monthly fee for a static IP).
Thanks, I found that info after posting. I haven’t been in the forums much since 3.0 final was released.
I was just wanting semi-static pool like DHCP does. DHCP tries to assign the same IP address to a machine/mac address when a DHCP client re-connects. I have setup some customer with static IP’s from my RADIUS server(s). We no longer allow dial-up users to request static IP’s, only DSL & Wireless customers can get Static IP addresses.
I saw them testing 802.11n cards at the 2007 MUM in Orlando. I also want them to support WiMax/802.16 for my network. Some of the advantages of 802.11n might not be so useful for outdoor multipoint wireless networks, but I hope support for both 802.11n & WiMax will be added when available.
in a PtMP system we are looking to lower the latency and to have a full wireless qos with nstream. We are not looking to more bandwidth.
So my vote is to a new feature in nstream that take into account the priority, it should be selected on the AP and not on the clients. We could not use it in a ptp link but it should be useful in a ptmp.
The possibility of the mark packet ttl, in the firewall to allow such ttl 128 and ttl 64, blocking the rest, avoiding the sharing of the connection linux and windows xp
02
In Winbox
A menu where I can write all of my ip Mikrotik
After Winbox connected, I can, switch to another ip automatically, simply just, click on the option.
Example
| 192.168.10.1 Base |
| 192.168.10.2 AP |
| 192.168.10.3 Hotspot |
When I click on the option chosen in Winbox, he now automatically connects at ip or Mac desired, without having to open another window winbox it going easy, clicked, connected.
A small but (at least to me) useful feature would be a tiny upgrade to Tools → Graphing.
The graphing for queues works really great, but… in Winbox you can also see the traffic transmitted for every queue. Would it be possible to include this value on the queue graph website where “Max-limit:” etc is listed?
I guess this would be pretty easy to implement. The graphs keep untouched but one more value (next to Max-limit, Limit-at, …) would be included.
This would be nice, because if the amount of transmitted traffic would be shown on the website, a customer could use the graphing facility as a “cheap” accounting tool (apart from the router reboot issue) with “allow target” enabled.
Every user could browse to the Mikrotik router and see how much traffic he/she already transmitted. A script like
:local date
:local day
:set date [/system clock get date]
:set day [:pick $date 5 6]
/queue simple
:if (day = 01) do={
reset-counters-all
}
could reset the counters on the 1st day of every month the the show starts again.
To support LACP over Bridged link’s Mikrotik will need to change to using a commercial network stack such as the one from ZebOS. The linux bridge will not support this functionality. Hell they only just added support for RSTP which has been a standard for as long as I can remember, do you think the linux dev’s will ever add LACP and MSTP support to it ?
ZebOS has it right now however, so is a good option.
this is a little new feature to put systems on date/time.
A button in /system/clock that when you click on it winbox take system time/data (of our computers) and actualize routerOS time/data with this system time. It’s to avoid putting date/time manually when no NTP service available. One click instead of put manually all data/time parameters.
