We have fixed most important issues and the version will be released this week, if possible, please test this version and let us know of any remaining issues, so we can address them. Thanks!
*) 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.
The change log is STILL very broken, in that it says things from 6.27. Compare
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;
with
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.
Could you provide a list of ticket numbers you believe that were corrected in this release? We should know if testing worths because you do not provide change lists in full.
@jarda: As usual, download, install and hope for the best, sometimes you get lucky. I did today. A little. But yeah, some kind of notification would be nice.
“Good news, dear user! We think that we fixed your ticket. Sincerely, your support.”
Just updated to .27 from .23 and immediately adopted an Ethernet negotiating issue on my ccr1036…
After two hours it just went off line. Has some FCS errors on my Cooper sfp. No asking of reboots or unplugging recovered it until it randomly decided to come up.
Not good… .23 was very stable but hey, it’s good to update right?
RB951G running 6.28rc15 poor performance with ipad mini 2 running 8.1 web pages fail to load but no issues with windows computers on the same wireless network
me too. i upgraded to 6.27 last night, and 2 hrs later had FCS errors on the uplink/wan port connecting to upstream isp. This resulted in an outage that was devastating. rebooting did not help, reseating did not help. nothing helped. it randomly came back an hour later… Very concerned it was this ‘rare’ issue, but it happened within 2 hours so who knows.
from v23 to v27 did the driver become more sensitive to cabling, have a lower tolerance to cable issues? etc…
using CCR1026 16GB, uplink was sfp+ mikrotik copper module.
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?
Is this the x27 (introduced in .25) port flapping issue? Taken off upstream switch cisco me3600x, ethernet port, connected to mikrotik sfp+ port on ccr1036 16GB via mikrotik copper sfp
Also note: their port is set to no autonegotiation / 1000M Full
My port would not sync up on autonegotiation unchecked when we first installed it with r23, advertising at 10,100,100M Full only. 2 hours after upgrading to x27 we had the logs occur below. We also saw some FCS errors on the microtik log. We changed MT to only advertise at 1000M Full, still no fixed rate port support.
lasted exactly 1 hour, then came back up without much issue… Is this the bug that is fixed in r28? that was introduced in r25 where r23 was free from this flapping issue?
====
Mar 19 18:06:32.507 MDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to down
Mar 19 18:06:33.567 MDT: %LINK-3-UPDOWN: Interface GigabitEthernet0/3, changed state to down
Mar 19 18:06:39.707 MDT: %LINK-3-UPDOWN: Interface GigabitEthernet0/3, changed state to up
Mar 19 18:06:40.707 MDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to up
Mar 19 18:08:30.924 MDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to down
Mar 19 18:08:31.980 MDT: %LINK-3-UPDOWN: Interface GigabitEthernet0/3, changed state to down
Mar 19 18:23:00.743 MDT: %LINK-3-UPDOWN: Interface GigabitEthernet0/3, changed state to up
Mar 19 18:23:01.743 MDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to up
Mar 19 18:23:08.063 MDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to down
Mar 19 18:23:09.123 MDT: %LINK-3-UPDOWN: Interface GigabitEthernet0/3, changed state to down
Mar 19 19:01:52.168 MDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to up
Mar 19 19:01:55.112 MDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to down
Mar 19 19:06:07.153 MDT: %LINK-3-UPDOWN: Interface GigabitEthernet0/3, changed state to up
Mar 19 19:06:08.153 MDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to up
