What's new in 6.28rc14 (2015-Mar-17 15:41):

*) tile - rare situation when CCR devices failed to auto-negotiate ethernet link (introduced in v6.25);
*) route - using ldp could cause connected routes with
invalid interface nexthop;
*) added support for SiS 190/191 PCI Ethernet adapter;
*) made metarouter work on boards with 802.11ac support or usb LTE;
*) sstp server - allow ADH only when no certificate set;
*) make fat32 disk formatting support disks bigger than 134GiB;
*) fixed tunnels - could crash when clamp-tcp-mss was enabled;
*) added basic counters for ipv4/bridge fast path, also show status weather fast
path is active at all;
*) console - added 'comment' parameter for '/system script'
*) api - return sentences can have property ~.section~ that groups values
from commands such as ~monitor~, ~traceroute~,
~print~ (with non-zero 'interval' value);
*) cloud - add time zone detection feature ~/system clock time-zone-autodetect~;
*) cloud - rename ~/ip cloud enabled~ to ~/ip cloud ddns-enabled~;
*) cloud - make ~/ip cloud update-time~ independent from ~/ip cloud ddns-enabled~
*) cloud - when setting ~/ip cloud ddns-enabled~ to ~no~ router will send
message to server to disable DNS name for this routerboard;
*) cloud - ~/ip cloud force-update~ command now will work also when
~/ip cloud ddns-enabled = no~. usefull if user wants to disable DDNS;
*) RB4xxGL - improved ethernet throughput (less dropped packets);
*) trafflow: - fixed crash on disable;
*) pppoe - fixed crash when big ppp packets with were sent over EOIP;
*) tilegx - fixed memory leak when queue settings are changed;
*) ar9888 - fixed crash when hw reports invalid rate;
*) console - fixed "in" operator in console;
*) console - make "/system package update print" work again.

What's new in 6.27 (2015-Feb-11 13:24):

*) console - added 'comment' parameter for '/system script'
*) api - return sentences can have property ".section" that groups values
from commands such as "monitor", "traceroute",
"print" (with non-zero 'interval' value);
*) cloud - add time zone detection feature "/system clock time-zone-autodetect";
*) cloud - rename "/ip cloud enabled" to "/ip cloud ddns-enabled";
*) cloud - make "/ip cloud update-time" independent from "/ip cloud ddns-enabled"
*) cloud - when setting "/ip cloud ddns-enabled" to "no" router will send
message to server to disable DNS name for this routerboard;
*) cloud - "/ip cloud force-update" command now will work also when
"/ip cloud ddns-enabled = no". usefull if user wants to disable DDNS;
*) RB4xxGL - improved ethernet throughput (less dropped packets);
*) RouterBOARD - fixed health reporting;
*) check-installation: fixed wrong kernel crc on powerpc boards
*) watchdog: fix software watchdog for x86
*) ssh - check conn state before sending disconnect message;
*) ipsec - fixed crash that happened in specific situation;

What's new in 6.28rc14 (2015-Mar-17 15:41):

*) tile - rare situation when CCR devices failed to auto-negotiate ethernet link (introduced in v6.25);
*) route - using ldp could cause connected routes with
invalid interface nexthop;
*) added support for SiS 190/191 PCI Ethernet adapter;
*) made metarouter work on boards with 802.11ac support or usb LTE;
*) sstp server - allow ADH only when no certificate set;
*) make fat32 disk formatting support disks bigger than 134GiB;
*) fixed tunnels - could crash when clamp-tcp-mss was enabled;
*) added basic counters for ipv4/bridge fast path, also show status weather fast
path is active at all;
*) console - added 'comment' parameter for '/system script'
*) api - return sentences can have property ~.section~ that groups values
from commands such as ~monitor~, ~traceroute~,
~print~ (with non-zero 'interval' value);
*) cloud - add time zone detection feature ~/system clock time-zone-autodetect~;
*) cloud - rename ~/ip cloud enabled~ to ~/ip cloud ddns-enabled~;
*) cloud - make ~/ip cloud update-time~ independent from ~/ip cloud ddns-enabled~
*) cloud - when setting ~/ip cloud ddns-enabled~ to ~no~ router will send
message to server to disable DNS name for this routerboard;
*) cloud - ~/ip cloud force-update~ command now will work also when
~/ip cloud ddns-enabled = no~. usefull if user wants to disable DDNS;
*) RB4xxGL - improved ethernet throughput (less dropped packets);
*) trafflow: - fixed crash on disable;
*) pppoe - fixed crash when big ppp packets with were sent over EOIP;
*) tilegx - fixed memory leak when queue settings are changed;
*) ar9888 - fixed crash when hw reports invalid rate;
*) console - fixed "in" operator in console;
*) console - make "/system package update print" work again.

Sending e-mail is still broken for me. The issue is described here:
System Error sending email timeout occurred

Any chance to get that fixed?

Problem in system health on 2011UAS v6.28rc15 (not tested on other boards)

1) From gui menu I see an empty window

2) config export stuck on that with ..

Code: Select all

..(cut)..
set time-zone-autodetect=no time-zone-name=Europe/Rome
#error exporting /system health
/system identity
..(cut)..

tile - rare situation when CCR devices failed to auto-negotiate ethernet link (introduced in v6.25);

errors occuring while opening plz help.

I'm missing the Capsman2 v6.28 package. Where can I download it?

basically been waiting for 6.28 and cancelled a trip to make sure i load it in person 'this week' as posted in the 1st commend.

Normis, can we still expect it this week? you guys push new updates on saturdays?

We have a bunch of NetMetal radios in place as a "backup link" for our AirFiber24 which drops out during rain. We had the first heavy rain since I upgraded the backup links to Mikrotik AC, and it performed horrible. I thought maybe upgrading to 6.27 would help, but nope. I thought that 866/866 data rates would pickup backhaul traffic that pushes 250-300mb through AirFiber.

What's interesting, is when the link FIRST establishes connection after reboot or forced disable/renable of WLAN, the traffic spiked up to almost 250-300mb, then after a few seconds, maybe a minute, dropped to 80-90mb. It's obvious this is just something Mikrotik needs to tweak on.

Another implementation that should be addressed, you can ONLY chose 20/40/or 80mhz channel. I've seen with UBNT products on PtP, that 50 & 60mhz channel widths work MUCH better than 80mhz, especially if there's any noise. Really would be nice to be able to use 30/50/60 channel widths.

There are some SERIOUS issues with 802.11ac still, and I really wish Mikrotik would address these.

Data Rates: 866/866 (maxed out) but drop almost in 1/2 with NV2
NV2 throughput: 80-90mb
Nstreme throughput: 180-200mb
802.11 throughput: 120-150mb

We have a bunch of NetMetal radios in place as a "backup link" for our AirFiber24 which drops out during rain. We had the first heavy rain since I upgraded the backup links to Mikrotik AC, and it performed horrible. I thought maybe upgrading to 6.27 would help, but nope. I thought that 866/866 data rates would pickup backhaul traffic that pushes 250-300mb through AirFiber.

What's interesting, is when the link FIRST establishes connection after reboot or forced disable/renable of WLAN, the traffic spiked up to almost 250-300mb, then after a few seconds, maybe a minute, dropped to 80-90mb. It's obvious this is just something Mikrotik needs to tweak on.

Another implementation that should be addressed, you can ONLY chose 20/40/or 80mhz channel. I've seen with UBNT products on PtP, that 50 & 60mhz channel widths work MUCH better than 80mhz, especially if there's any noise. Really would be nice to be able to use 30/50/60 channel widths.

There are some SERIOUS issues with 802.11ac still, and I really wish Mikrotik would address these.

Data Rates: 866/866 (maxed out) but drop almost in 1/2 with NV2
NV2 throughput: 80-90mb
Nstreme throughput: 180-200mb
802.11 throughput: 120-150mb

+1000.....

We have a bunch of NetMetal radios in place as a "backup link" for our AirFiber24 which drops out during rain. We had the first heavy rain since I upgraded the backup links to Mikrotik AC, and it performed horrible. I thought maybe upgrading to 6.27 would help, but nope. I thought that 866/866 data rates would pickup backhaul traffic that pushes 250-300mb through AirFiber.

What's interesting, is when the link FIRST establishes connection after reboot or forced disable/renable of WLAN, the traffic spiked up to almost 250-300mb, then after a few seconds, maybe a minute, dropped to 80-90mb. It's obvious this is just something Mikrotik needs to tweak on.

Another implementation that should be addressed, you can ONLY chose 20/40/or 80mhz channel. I've seen with UBNT products on PtP, that 50 & 60mhz channel widths work MUCH better than 80mhz, especially if there's any noise. Really would be nice to be able to use 30/50/60 channel widths.

There are some SERIOUS issues with 802.11ac still, and I really wish Mikrotik would address these.

Data Rates: 866/866 (maxed out) but drop almost in 1/2 with NV2
NV2 throughput: 80-90mb
Nstreme throughput: 180-200mb
802.11 throughput: 120-150mb

+1000.....

+10000

pppoe - fixed crash when big ppp packets with were sent over EOIP;

Could explain the symptoms of this issue?

pppoe - fixed crash when big ppp packets with were sent over EOIP;

Could explain the symptoms of this issue?

Your router could either have a high memory usage or reboot itself.

Sending e-mail is still broken for me. The issue is described here:
System Error sending email timeout occurred

Any chance to get that fixed?

I´m downloading the changelog, but since RC16 everytime is the same outdated "routeros_devnote.txt"... someone have the latest changes? Thanks guys

hi i need help, one port on my ccr router, it gives me an error fcs, which makes it not work and still disconnected still been running.



in this pictures the port is disconnected, but the state is still running.
the actual version is 6.28rc17, firmware 3.22.
I'm try to force, put the link spee to 100 mbps, but in the port 1gps is set ¿why?

The changelog is updated to the v6.28rc20
The version is going into the final testing phase - we hope to make a full v6.28 release next week. Please report to support@mikrotik.com if you see any problem in the latest RC version.

10:40:23 script,error script error: action timed out - try again, if error continues contact MikroTik support and send a supout file (13)
10:44:01 script,error script error: action timed out - try again, if error continues contact MikroTik support and send a supout file (13)

Switches mikrotik without igms snooping and DHCP snooping is cheap toys ! Why these toys you produce?

Switches mikrotik without igms snooping and DHCP snooping is cheap toys ! Why these toys you produce?

Why are you testing different using versions of ROS? Just check if "V6.28rc20 -> Server V6.28rc20" is OK.

Yes, I agree that this is BAD, unfortunately this is not the first time . But I know what answer will give you the Support team. Upgrade both ends and then make a test.

CRS125 ingress-port-policer is not working in v6.28rc20. Cannot do more than 1-5Mbps when set.

Code: Select all

/interface ethernet switch ingress-port-policer add burst=100k port=ether24-slave-local rate=60M

iperf does 1-5Mbps. Not 60M, 1-5M.
If I delete ingress-port-policer, goes back to normal and iperf does 900Mbps.

Why are you testing different using versions of ROS? Just check if "V6.28rc20 -> Server V6.28rc20" is OK.

How can I upgrade geographicali dispersed routers at once ? If there will be no other solution I'll be forced to do that, but breaking compatiblity betwen versions is very BAD.

Fixing the fetch ssl bug would be fantastic since it makes /tool fetch unusable for me:

http://forum.mikrotik.com/viewtopic.php?f=1&t=95576

Re: [Ticket#2015040666000483] Bug with /tool fetch and https.
Hello,

Its due to bug in ssl library. Next release will have the fix.

Regards,
Maris B.

Shouldn't that burst value be higher? The moment it goes in burst mode, it will send at 100k, than back to 60M, again burst mode at 100k and so on. Maybe burst = 100M?

Sending e-mail is still broken for me. The issue is described here:
System Error sending email timeout occurred

Any chance to get that fixed?

This is fixed in version 6.28rc20. Thanks a lot MikroTik!

I agree. I would rather time spent and get a quality release, instead of rushing and releasing garbage.

That said, I would like some more communication as to how the fixes are proceeding.

IE - We now have SSTP fixed, working on BGP this week, and we want to make sure OSPF is good before we release this one.
(Just an example)

I agree. I would rather time spent and get a quality release, instead of rushing and releasing garbage.

That said, I would like some more communication as to how the fixes are proceeding.

IE - We now have SSTP fixed, working on BGP this week, and we want to make sure OSPF is good before we release this one.
(Just an example)

It would definitely be helpful to have some kind of release timeline. I certainly don't want the releases rushed or buggy, but it's very beneficial to know roughly when the new code will come out for testing and maintenance window planning.

Who said anything about upgrading actual in-production SSTP servers? Pull a router out of stock and configure it as a temporary/test SSTP server. If you have no spare RouterBoards sitting around, fire up a copy of x86 RouterOS on a spare PC, or heck, even as a VM inside of VMware or something. There are TONS of options open to you that wouldn't require you to install a beta version of the OS on production routers!

-- Nathan

Who said anything about upgrading actual in-production SSTP servers? Pull a router out of stock and configure it as a temporary/test SSTP server. If you have no spare RouterBoards sitting around, fire up a copy of x86 RouterOS on a spare PC, or heck, even as a VM inside of VMware or something. There are TONS of options open to you that wouldn't require you to install a beta version of the OS on production routers!

-- Nathan

Well said Nathan. I have similar thoughts on tons of complaints here. Use stable versions that work for you, test the hell out of newer versions of ROS on some backup or spare router...simple as that.

So I have two devices that I just upgraded to 6.28 because of superior ethernet performance... One is an RB911G-HPnD the other is a RB912UAG-HPnD. They are about 1.4 miles apart with signals in the low 50/high 40's. I noticed that they were see a 20 mhz channel negotiation with channel set to 20/40 eC Figured there was interference so I tried Ce. Still couldn't get better than 144mb negotiation... On a whim, I changed one side to eC and left the other at Ce... Now running at 300/400mb/s and a 40mhz channel. What is up with that?

So I have two devices that I just upgraded to 6.28 because of superior ethernet performance... One is an RB911G-HPnD the other is a RB912UAG-HPnD. They are about 1.4 miles apart with signals in the low 50/high 40's. I noticed that they were see a 20 mhz channel negotiation with channel set to 20/40 eC Figured there was interference so I tried Ce. Still couldn't get better than 144mb negotiation... On a whim, I changed one side to eC and left the other at Ce... Now running at 300/400mb/s and a 40mhz channel. What is up with that?

Could you please tell us what center frequencies you were using on both ends? Could you provide support output files to support@mikrotik.com?

Updated a rb2011.

[admin@rb2011-despa] /interface> set 5 l2mtu=1600 mtu=1540
action timed out - try again, if error continues contact MikroTik support and send a supout file (13)
[admin@rb2011-despa] /interface>
[admin@rb2011-despa] /interface>
[admin@rb2011-despa] /interface>
[admin@rb2011-despa] /interface>
[admin@rb2011-despa] /interface> print


(And after the print it seems to be hanging).

I had to change the MTU manually because it lost the original MTU after the update.


And the router has crashed. I can no longer access it.

Latest version grabbed 5 minutes ago.