Caveats:
*) autosupout.rif generation does not work yet, it should be made by hand;
*) supout.rif generation works does not work in WinBox yet (it works only in console);
*) dropped support for Linksys HomeLink PhoneLine Network Card (10Mbps over
telephone line);
*) dropped support for PCMCIA RadioLan;
*) dropped support for telephony package;
*) ISDN does not log called and caller numbers anymore;
*) OSPF does not work with routing package;
What's new in v3.0beta1:
*) added support for SATA disks;
*) added initial support for SMP on x86 (use it on your own risk);
*) added support for up to 2Gb of memory on x86;
*) fixed time matching in firewall rules;
*) added time matching to bridge firewall rules;
*) multiple ports can be specifief in firewall as src. and dst.;
*) added support for NAT-T in IPsec;
Note, that User Manager isn’t workin in the v3.0beta yet.
also there could be lot of bugs, please email them to support@mikrotik.com and specify in the subject that you are reffering to v3.0
Is there an updated hardware compatibility list so I can see which SATA controllers are supported?
Please say LSI MegaRAID SATA/SAS (It’s an open source Linux 2.6 driver!) is supported so we can use this on Sun AMD64 systems - I really want to deploy some x4200s with the new SMP support
Multi threadings and detection several number of cpu
Backup Router (mirroring routeros configs on backup router and force to take the original router’s place when the original router is down and stand down when it is backed online) very critical when we wan’t to maintain hardware issues or replace add/removehardware or even a simple reboot.
support for USB wireless and specially USB pendrive as installation.
Event-based scripting rather than simple Schedule or Netwatch. for instance trigger a script when certain packet from specified IP address received, meaning trigger scripting on packets arrival or departure.
deeper access in scripting, instead of few console command and loops. access API functions and object oriented access to package’s interfaces.
support for various wireless cards, 70% of available cards here in this part of the world doesnt match with routeros, such as ralink chips who are very common and cheap
text web browsing to control any web-based network equipments such as reboot of the adsl or sdsl modem via web-based interface when modem hangs.
ok i can definitly say, i’m the one with the first bug…
updated my test router by FTP all the new packages to the router…
rebooted…
and nothing anymore…
no booting or so what ever…
so don’t ftp the packages… it doesn’t work on a clean RB500 install
RouterOS == Atheros, get used to it. It’s been made pretty clear on the forums that they don’t have much intrest in supporting anything else with any serious degree of effort. Atheros is an excellent product line, but there are a lot of other things out there!
Personally I’d like to see better support for Hermes (it’s old yes, but it’s GOOD! and I have a lot of them). Cisco AeroNET cards also have pretty poor support. I can’t get them to actually associate to anything However, with the age and EOL status of those particular chipsets I can understand why they don’t want to spend time on them, with so many other MUCH more important things needing done coughBGPcough.
With SMP support has the 1GB RAM limit gone the way of the dodo? The reason I ask is simple, if I have two Opterons then for the most efficient use of the the maximum 1GB RAM I must have 512MB per CPU otherwise all traffic has to go across the HT bus which increases the latency and loads up all of the traffic onto a single memory controller defeating the point of NUMA but if I use 512MB per CPU that means I need 2x256MB sticks to use which are difficult to get in Registered/ECC versions for PC-3200 or PC2-5300
…
However, with the age and EOL status of those particular chipsets I can understand why they don’t want to spend time on them, with so many other MUCH more important things needing done coughBGPcough.