6.20 is being prepared to release, we will release the newest version shortly.
We will be happy to receive feedback about 6.20rc from you.

What's new in 6.20rc15 (2014-Sep-25 13:28):

*) fetch - fixed problem where files fetched over https were trimmed in size;
*) fixed problem - it was not possible to see & uninstall dude package;
*) stores are replaced with folders and disks are now managed under /disk menu;
*) added support for SMSC750x USB Gigabit Ethernet on x86;
*) ups - support selftest for smart and hid UPS;
*) pppoe client - increase connection timeout to make connection establishment
possible on busy pppoe server;
*) dhcp server - change default lease time from 3 days to 10 minutes
to avoid running out of IPs;
*) ipsec - allow binding modeconf address to username;
*) eoip/eoipv6/gre/gre6/ipip/ipipv6/6to4 tunnels have new features:
auto mtu (enabled by default for new tunnels);
dscp (inherit/specific value, inherit by default for new tunnels);
clamp-tcp-mss (yes by default for new tunnels);
*) eoip/gre/ipip/6to4 tunnels have dont-fragment option (inherit/no, no by default for new tunnels);
*) bridge has auto mtu feature (enabled by default for new bridges);
*) pppoe-server has auto mtu feature (enabled by default for new pppoe servers);

NOTE1: In v6.20rc all non-ppp tunnel interfaces got optimized and common set of features,
this is important step in direction to add fast path support to those interfaces.
Please, test non-ppp tunnels and report back with results.

NOTE2: 6.20rc15 is going through final testing, it will be the release as version 6.20.
Please, test and report back any persisting issues, so that we can fix that till final release.


http://www.mikrotik.com/download/share/ ... latest.zip
http://www.mikrotik.com/download/share/ ... evnote.txt

No one sentence about wireless improvenments, so it means - no improvenments in this package?

No one sentence about wireless improvenments, so it means - no improvenments in this package?

Yeah I'm disappointed with that too because my problem lodged under ticket number 2014080266000118 is still unresolved :

http://forum.mikrotik.com/viewtopic.php?f=7&t=88808

Ticket#2014091366000293
What about my problem?
I am not able to install 500 devices by netinsall

This version didn't recognize my LTE modem Huawei E5372S.
No lte in interface menu

[admin@MikroTik] > system resource usb print
# DEVICE VENDOR NAME SPEED
0 1:1 Linux 3.3.5 ehci_hcd RB400 EHCI 480 Mbps
1 1:2 HUAWEI Technology HUAWEI Mobile 480 Mbps
[admin@MikroTik] > interface print
Flags: D - dynamic, X - disabled, R - running, S - slave
# NAME TYPE ACTUAL-MTU L2MTU
0 ether1-gateway ether 1500 1598
1 RS ether2-master-local ether 1500 1598
2 S ether3-slave-local ether 1500
3 S ether4-slave-local ether 1500
4 S ether5-slave-local ether 1500
5 S wlan1 wlan 1500
6 R bridge-local bridge 1500
[admin@MikroTik] > system resource print
uptime: 6m6s
version: 6.20rc15
build-time: Sep/25/2014 13:28:37
free-memory: 107.9MiB
total-memory: 128.0MiB
cpu: MIPS 74Kc V4.12
cpu-count: 1
cpu-frequency: 600MHz
cpu-load: 3%
free-hdd-space: 111.9MiB
total-hdd-space: 128.0MiB
write-sect-since-reboot: 81
write-sect-total: 21363
bad-blocks: 0%
architecture-name: mipsbe
board-name: RB951Ui-2HnD
platform: MikroTik

I was feeling adventurous tonight and upgraded my 751G-2HnD from 5.26. I can't login to webfig with firefox now, I get an "ERROR: Internal Server Error". Chromium works, winbox works, telnet/ssh works... tried another reboot and resetting the password, no luck.

My GRE tunnel (to a C6500) seems to be working alright, though!

NM my firefox problem, clearing the cache fixed it! (duh!)

*) dhcp server - change default lease time from 3 days to 10 minutes
to avoid running out of IPs;

Hell yes, from one ditch, straight over the road into another.
If sysadmins were too clumsy to change them default lease times, now you make router to refresh them IPs every couple of minutes. From what I have noticed is this - when DHCP is refreshing them lease, users are without internets for small moment. Then there are those whiners who have online gaming or online chat or online whatever. They start calling you in and whining - why is my internets lagging every 10 mins or so. And just as Yoda said - "skrewed, my friend, you are".

Is there any chance for new ethernet drivers, especially very popular new intel chipsets Intel i217LM & Intel i210AT ?

noyo,
try to reset the wireless configuration to default values and configure the settings you only need, like, ssid, band, frequency, security, power and then check if the problem is still there.
Enable the rstp protocol mode for your bridge interfaces.
Also check if you disable the SNMP monitoring do you still see this problem

Does the reboot happens only on the links with Nv2 wireless protocol?

nbctcp,
please write to support@mikrotik.com and attach a support output file from the board with the modem plugged in so we could check if we could add support for it or not.

*) dhcp server - change default lease time from 3 days to 10 minutes
to avoid running out of IPs;

Hell yes, from one ditch, straight over the road into another.
If sysadmins were too clumsy to change them default lease times, now you make router to refresh them IPs every couple of minutes. From what I have noticed is this - when DHCP is refreshing them lease, users are without internets for small moment. Then there are those whiners who have online gaming or online chat or online whatever. They start calling you in and whining - why is my internets lagging every 10 mins or so. And just as Yoda said - "skrewed, my friend, you are".

Have you actually tested that??? Or you just assuming...
Lets read:
https://www.ietf.org/rfc/rfc2131.txt 4.4.5 Reacquisition and expiration

So in short, if client is present, and active, it will never loose lease, even for a moment, lease time will be extended.
Only thing that changes is that instead of 2 DHCP packets every 1,5 days, now you will have 2 packets every 5min

so stop panic!!

Have you actually tested that??? Or you just assuming...
Lets read:
https://www.ietf.org/rfc/rfc2131.txt 4.4.5 Reacquisition and expiration

So in short, if client is present, and active, it will never loose lease, even for a moment, lease time will be extended.
Only thing that changes is that instead of 2 DHCP packets every 1,5 days, now you will have 2 packets every 5min

so stop panic!!

There is no panic here, is there panic in your office ? Im just saying !
It was damn true back in 3.x times, then still true in v6.5, I dont see how it wont be true now. Then again, I did not do any hard tests on latest RC, so might be my bad, maybe they fixed something now. I am just pointing this out so that people test their networks for service continuity while they setup DHCP lease refresh this small. I had this back at the time, 10+ calls per hour just because this issue.

I am just pointing this out so that people test their networks for service continuity while they setup DHCP lease refresh this small. I had this back at the time, 10+ calls per hour just because this issue.

there is absolutely no point in assuming anything if that can be tested.

If they got this problem the problem is somewhere else. - it is easy to test it yourself - set minimal lease time for your own PC and see what happens. I've been on 10sec lease time since my previous post. VOIP, ping, and even some online games - no problems.

Anything changed that addresses my SXT-AC Problem ?

[Ticket#2014082966000498] Kernel failure V6.19

No news about the glitch on IPv6 routing over VLAN on PPC? (Ticket#2014032466000943)
I think that issues on IPv6 should be addressed due to the IPv4 exhaustion.

Carlos Strauch

+1

I think IPv6 needs more priority..... IPv4 exhaustion remember ???

No news about the glitch on IPv6 routing over VLAN on PPC? (Ticket#2014032466000943)
I think that issues on IPv6 should be addressed due to the IPv4 exhaustion.

Carlos Strauch

Hi, is possible add too support for ( Broadcom NetXtreme BCM5720 Gigabit Ethernet PCIe ) on x86 ?
I have a Dell PowerEdge r220 that no work with RouterOS.

Thanks,
Lailton

Hi,

I would like to inquire if anything has changed for IPSec between 6.20rc7 and 6.20rc16?
It seems that when I upgrade to 6.20rc16 from 6.20rc7, using the same config. None of my IPSec sessions are establishing

Well, DHCP Leases Address List bug seems to be fixed now.

But I can't find any Stores in Winbox - they were moved from System -> Stores to System -> Disks, but it is completely empty - no disk, no storage. I can just see folders in Files windows. Is it OK?

I see on changelog for version 6.20rc16 that you add: *) ipsec - support fqdn as my id;


Can we have it also for EOIP?

I see on changelog for version 6.20rc16 that you add: *) ipsec - support fqdn as my id;


Can we have it also for EOIP?

6.20 supports FQDN as ipsec local identifier.

It's not actually used to resolve an IP at any point, it's just another match condition for Phase1.

Any changes on CAPsMAN?

No one sentence about wireless improvenments, so it means - no improvenments in this package?

How possible the 【Metal 5SHPn】 can like the microwave, most of the microwave with low cpu speed but can achieve 360Mbps?

Such speed is impossible with one chain in a/n band.

CCR1016, RouterOS 6.20rc16.
Trying to modify any filed of existing /ip ipsec peer using winbox -got an error "Couldn't change IPsec Peer <address here> - address ID must be used in main mode! (6)", tying to save new peer - the same error.
Doing the same things in console - got no error, everyrhing is OK.
Peer config is

SNMP still broken on high speeds
we tested switch(10G)---(10G)mikrotik ang get statistic from this ports.
on speed traffic higher then 3.2 G statisctic for traffic is wrong.
statisctik for packet is seems to right.

Well, DHCP Leases Address List bug seems to be fixed now.

But I can't find any Stores in Winbox - they were moved from System -> Stores to System -> Disks, but it is completely empty - no disk, no storage. I can just see folders in Files windows. Is it OK?

Please redownload the latest test release - this problem is fixed in RouterOS v6.20rc17 - you should be able to see all the disks.

Any changes on CAPsMAN?

compared to v6.19 there are few configuration crash fixed, added eap-tls certificate options for the security, and some minor changes in winbox.

hm... I have kind of déjà vu...

What's new in 6.8 (2014-Jan-29 15:52):
*) default configuration - changed dhcp server lease time to 10 minutes;

What's new in 6.20rc15 (2014-Sep-25 13:28):
*) dhcp server - change default lease time from 3 days to 10 minutes
to avoid running out of IPs;

slow and steady

Can someone direct me to the details for the new features within EoIP such as "Don't Fragment" and "Clamp TCP MSS"
As well, why does the term "Slave" show greyed out on the lower right hand corner of the EoIP interface window?

Thanks in advance,

-tp

SNMP still broken on high speeds
we tested switch(10G)---(10G)mikrotik ang get statistic from this ports.
on speed traffic higher then 3.2 G statisctic for traffic is wrong.
statisctik for packet is seems to right.

Are you sure this is a problem with Mikrotik / routeros specifically? Debug the SNMP responses you should see the counters continue to go up - but how your graphing management tool handles these values may be causing you the issues - for instance the field in which it stores the counter difference from 1 poll to the next may only be able to fit a certain sized integer (int, bigint etc) before it has to 'loop around' so to speak.

I've come across similar issues using 'Cacti' in which most graphs would do this at 100mbit until you upgraded them to use '64 bit' counters so they field could actually store a bigger integer.

Hi, Any update regarding support of new intel ethernet cards like intel i210AT ?
Populer on many embedded board and firewall barebones ?

We're already send ticket id and autosuport file but not respond.

/system resource pci> print
# DEVICE VENDOR NAME IRQ
0 12:00.0 Intel Corporation unknown device (rev: 3) 11
1 11:00.0 Intel Corporation unknown device (rev: 3) 5
2 10:00.0 Intel Corporation unknown device (rev: 3) 10
3 0f:00.0 Intel Corporation unknown device (rev: 3) 11
4 0e:00.0 Intel Corporation unknown device (rev: 3) 11
5 0d:00.0 Intel Corporation unknown device (rev: 3) 5
6 0c:00.0 Intel Corporation unknown device (rev: 3) 10
7 0b:00.0 Intel Corporation unknown device (rev: 3) 11
8 0a:00.3 Intel Corporation 82580 Gigabit Network Co... 10
9 0a:00.2 Intel Corporation 82580 Gigabit Network Co... 11
10 0a:00.1 Intel Corporation 82580 Gigabit Network Co... 11
11 0a:00.0 Intel Corporation 82580 Gigabit Network Co... 5
12 08:00.3 Intel Corporation 82580 Gigabit Network Co... 10
13 08:00.2 Intel Corporation 82580 Gigabit Network Co... 11
14 08:00.1 Intel Corporation 82580 Gigabit Network Co... 11
15 08:00.0 Intel Corporation 82580 Gigabit Network Co... 5
16 07:05.0 PLX Technology, Inc. unknown device (rev: 187) 5
17 07:04.0 PLX Technology, Inc. unknown device (rev: 187) 10
18 07:01.0 PLX Technology, Inc. unknown device (rev: 187) 5
19 06:00.0 PLX Technology, Inc. unknown device (rev: 187) 10
20 05:00.3 Intel Corporation 82580 Gigabit Network Co... 11
21 05:00.2 Intel Corporation 82580 Gigabit Network Co... 11
22 05:00.1 Intel Corporation 82580 Gigabit Network Co... 5
23 05:00.0 Intel Corporation 82580 Gigabit Network Co... 10
24 03:00.3 Intel Corporation 82580 Gigabit Network Co... 11
25 03:00.2 Intel Corporation 82580 Gigabit Network Co... 11
26 03:00.1 Intel Corporation 82580 Gigabit Network Co... 5
27 03:00.0 Intel Corporation 82580 Gigabit Network Co... 10
28 02:05.0 PLX Technology, Inc. unknown device (rev: 187) 10
29 02:04.0 PLX Technology, Inc. unknown device (rev: 187) 11
30 02:01.0 PLX Technology, Inc. unknown device (rev: 187) 10
31 01:00.0 PLX Technology, Inc. unknown device (rev: 187) 11
32 00:1f.3 Intel Corporation unknown device (rev: 5) 5
33 00:1f.2 Intel Corporation unknown device (rev: 5) 11
34 00:1f.0 Intel Corporation unknown device (rev: 5) 0
35 00:1d.0 Intel Corporation unknown device (rev: 5) 10
36 00:1c.7 Intel Corporation unknown device (rev: 213) 11
37 00:1c.6 Intel Corporation unknown device (rev: 213) 5
38 00:1c.5 Intel Corporation unknown device (rev: 213) 10
39 00:1c.4 Intel Corporation unknown device (rev: 213) 11
40 00:1c.3 Intel Corporation unknown device (rev: 213) 11
41 00:1c.2 Intel Corporation unknown device (rev: 213) 5
42 00:1c.1 Intel Corporation unknown device (rev: 213) 10
43 00:1c.0 Intel Corporation unknown device (rev: 213) 11
44 00:1a.0 Intel Corporation unknown device (rev: 5) 11
45 00:16.3 Intel Corporation unknown device (rev: 4) 11
46 00:16.0 Intel Corporation unknown device (rev: 4) 11
47 00:14.0 Intel Corporation unknown device (rev: 5) 11
48 00:01.1 Intel Corporation unknown device (rev: 6) 11
49 00:01.0 Intel Corporation unknown device (rev: 6) 11
50 00:00.0 Intel Corporation unknown device (rev: 6) 0

Ticket id : Ticket#2014091866000882

any update mikrotik team ???

Thx
//Rudi

Hi,

Any changes to 802.11ac wireless. I`m still getting random kernel failures on new SXTac point to point kit.

Regards

Aidan

Anything changed that addresses my SXT-AC Problem ?

[Ticket#2014082966000498] Kernel failure V6.19

Hi Ste,

I get the same issue. SXT-AC point to Point = random kernel failures that's now upsetting my customer.

running ver 6.19

firmware 3.17

regards

Aidan

Anything changed that addresses my SXT-AC Problem ?

[Ticket#2014082966000498] Kernel failure V6.19

Hi Ste,

I get the same issue. SXT-AC point to Point = random kernel failures that's now upsetting my customer.

running ver 6.19

firmware 3.17

regards

Aidan

Make sure you can reset them remote. Sometimes they do not come back up after a kernel failure. Send supout to support. We have not seen this with 911/912 ac boards. So better use them with a good antenna. This will give better results anyway.

v6.20 released!
http://forum.mikrotik.com/viewtopic.php?f=2&t=89785