RouterOS v6.26!

RouterOS General
1

What’s new in 6.26 (2015-Feb-03 15:18):

*) ovpn - allow to add VLANs to ovpn server bindings;
*) sstp - added pfs option which enables DHE;
*) pppoe client - increased timeout when searching for servers;
*) sstp - fixed problem were Windows 8 clients couldn’t connect;
*) console - fixed some missing export entries;
*) smb - improved stability, fixed some crashes and problems causing disconnects;
*) api - fixed system check-installation;
*) cerm - fix scep client ca caps parsing;
*) RouterBOARD - included new RouterBOOT 3.22 to enable protected-routerboot setting (see wiki);
*) webfig - fixed various design skin issues;
*) NTP client - accepts ipv6 as a server address;
*) known issue - system check-installation incorrectly reports error on PPC;

Simply click “Check for updates” in QuickSet, Webfig or Winbox packages menu. It should also work from v5

v6.26 will be released on 6th week of 2015, check the latest
RouterOS v6.25
2

If you run the Check for update of Winbox, seems release notes are garbled.

3

kometchtech, thank you for the report.
Changelog should be correct within few minutes.

4

There is still the IPSEC Problem as I just wrote here

http://forum.mikrotik.com/t/solved-l2tp-ipsec-stoped-working-after-upgrade-to-6-18/79942/10

5

Michel, please make sure you are using the latest Winbox,
http://download2.mikrotik.com/routeros/winbox/3.0rc2/winbox.exe

We are not able to repeat your described problem.

6

Just upgraded an x86 VM and RB2011UiAS-RM to 6.26 with no issues…will put it onto several different platforms and see how it goes.

Thanks MT! :smiley:

7

Same problem, If I create a new Peer over the GUI or just change anything inside the existing Peer than IPSEC L2TP is broken. I start from scratch with 6.26 on a brand new RB2011UiAS-2HnD

The only way to fix is to delte the Peer and add a new one with the Syntax

add address=0.0.0.0/0 local-address=0.0.0.0 passive=no port=500 auth-method=pre-shared-key secret="test" generate-policy=port-override policy-template-group=*FFFFFFFF exchange-mode=main-l2tp\ send-initial-contact=yes nat-traversal=yes proposal-check=obey hash-algorithm=sha1 enc-algorithm=3des dh-group=modp1024 lifetime=1d lifebytes=0 dpd-interval=disable-dpd dpd-maximum-failures=5

If the policy-template-group does not have *FFFFFFFF set, than there is no chance and you see all the time in the error log “failed to pre-process ph2 packet”

8

Michel,
policy-template should be default not *FFFFF, perhaps you upgraded from the version, where was issuse with it.
Add new peer, it should has correct settings.

9

What happened with “HEALTH”?

10

RB2011UAS-2HnD
After upgrade from 6.25 to 6.26 DHCP doesn’t work.

11

That is the curios part, with default it is not working only with *FFFFFFFF … and no, I start from scratch without default configuration of the router ( /system reset-configuration no-defaults=yes )

Even if I copy the working Peer over the GUI to a new one, disable the old one than the new Peer is not working.

On my old 493AH Router I see also under V6.25 the *FFFFFFF - if I copy the Peer to a new one than the *FFFFFF is gone and IPSEC is no longer working.

Totaly crazy… sorry that I can give no more information.

model: 2011UiAS-2HnD
serial-number: 5695043D3xxx
current-firmware: 3.22
upgrade-firmware: 3.22

12

Ljubo

Any more information on that? Doesn’t tell us much.

13

jdog

upgrade metod by selected package
Package.JPG
full function router on 6.25 working firmware 3.19
upgrade to 6.26 and firmware 3.22 doesn’t working
downgrade to 6.25 all woks

14 
[admin@MikroTik] > /tool e-mail send subject="stest" body="btest" to="mymail@yahoo.com"

Feb/04/2015 17:22:34 system,e-mail,error Error sending e-mail : invalid TO address
?!
Also after reboot something must happened since my main internet pppoe connection was connected but without internet access, disabled/enabled the pppoe interface solved the problem

15

System Health is not working anymore on RB711UA-2HND.

16

*) RouterBOARD - included new RouterBOOT 3.22 to enable protected-routerboot setting (see wiki);

from wiki:

Backup RouterBOOT version can not be older than v3.22 version. A special package is provided to upgrade backup RouterBOOT (DANGEROUS). Newer devices will have this new backup loader already installed in factory.

Please: where download the special package?

Thanks.

17



Thank you for noticing it will be fixed in next release.


Ljubo
Could you please send supout.rif with 6.26 and nonworking dhcp send to support@mikrotik.com ?

18

download mikrotik pack for linux
run: sh ./downloadMT.sh 6.26 /path/save

#!/bin/bash
if [ -z $1 ]; then
 echo $0" 0.00 '/path/save'";
elif [ -z $2 ]; then
 echo $0" 0.00 '/path/save'";
else
 ONE=`echo $1 | cut -d'.' -f1`
 LINK="http://download2.mikrotik.com/routeros/$1"

 mkdir $2/routeros-$1
 wget -c -P $2/routeros-$1 http://www.mikrotik.com/download/CHANGELOG_$ONE
 wget -c -P $2/routeros-$1 $LINK/netinstall-$1.zip

 wget -c -P $2/routeros-$1 $LINK/routeros-mipsbe-$1.npk
 wget -c -P $2/routeros-$1 $LINK/routeros-powerpc-$1.npk
 wget -c -P $2/routeros-$1 $LINK/routeros-mipsle-$1.npk
 wget -c -P $2/routeros-$1 $LINK/routeros-x86-$1.npk
 wget -c -P $2/routeros-$1 $LINK/routeros-tile-$1.npk
 wget -c -P $2/routeros-$1 $LINK/mikrotik-$1.iso

 wget -c -P $2/routeros-$1 $LINK/all_packages-mipsbe-$1.zip
 wget -c -P $2/routeros-$1 $LINK/all_packages-ppc-$1.zip
 wget -c -P $2/routeros-$1 $LINK/all_packages-mipsle-$1.zip
 wget -c -P $2/routeros-$1 $LINK/all_packages-x86-$1.zip
 wget -c -P $2/routeros-$1 $LINK/all_packages-tile-$1.zip

 wget -c -P $2/routeros-$1 $LINK/wireless-fp-$1-mipsbe.npk
 wget -c -P $2/routeros-$1 $LINK/wireless-fp-$1-ppc.npk
 wget -c -P $2/routeros-$1 $LINK/wireless-fp-$1-mipsle.npk
 wget -c -P $2/routeros-$1 $LINK/wireless-fp-$1-x86.npk
 wget -c -P $2/routeros-$1 $LINK/wireless-fp-$1-tile.npk

 wget -c -P $2/routeros-$1 $LINK/wireless-cm2-$1-mipsbe.npk
 wget -c -P $2/routeros-$1 $LINK/wireless-cm2-$1-powerpc.npk
 wget -c -P $2/routeros-$1 $LINK/wireless-cm2-$1-mipsle.npk
 wget -c -P $2/routeros-$1 $LINK/wireless-cm2-$1-x86.npk
 wget -c -P $2/routeros-$1 $LINK/wireless-cm2-$1-tile.npk
fi
19

In v6.26, AutoMTU is still not working for EoIP.

-tp

20

You have an ac-capable device. That’s all that matters. ac-capable devices at this time cannot do spectral-history scan, period. It doesn’t matter what settings you choose. The issue is not the settings, the issue is the WiFi chip on your RouterBoard. Setting an ac-capable radio chip to “n-only” mode does not magically allow you to do a spectral-history scan with it.

– Nathan