Community discussions

 
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1278
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

v6.40.8 [bugfix] is released!

Tue Apr 24, 2018 12:30 pm

RouterOS version 6.40.8 has been released in public "bugfix" channel!

Before an upgrade:
1) Remember to make backup/export files before an upgrade and save them on another storage device;
2) Make sure the device will not lose power during upgrade process;
3) Device has enough free storage space for all RouterOS packages to be downloaded.

What''s new in 6.40.8 (2018-Apr-23 11:34):

!) winbox - fixed vulnerability that allowed to gain access to an unsecured router;
*) certificate - fixed incorrect SCEP URL after an upgrade;
*) health - fixed empty measurements on CRS328-24P-4S+RM;
*) ike2 - use "policy-template-group" parameter when picking proposal as initiator;
*) ipv6 - fixed IPv6 behaviour when bridge port leaves bridge;
*) routerboard - fixed "mode-button" support on hAP lite r2 devices;
*) ssh - fixed SSH service becoming unavailable;
*) traffic-flow - fixed IPv6 destination address value when IPFIX protocol is used;
*) winbox - show "Switch" menu on cAP ac devices;
*) wireless - improved compatibility with BCM chipset devices;

To upgrade, click "Check for updates" at /system package in your RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after some problem has appeared on device

Please keep this forum topic strictly related to this concrete RouterOS release.
 
skullzaflare
just joined
Posts: 17
Joined: Tue Apr 12, 2016 12:01 am

Re: v6.40.8 [bugfix] is released!

Tue Apr 24, 2018 5:38 pm

Related/unrelated?
Downgraded a customers router from 6.42.1 to 6.40.8, the bridge interface got deleted, resulting in no ports/dhcp on a bridge.
 
Pea
Frequent Visitor
Frequent Visitor
Posts: 77
Joined: Fri Jul 17, 2015 11:07 pm
Location: Czech

Re: v6.40.8 [bugfix] is released!

Tue Apr 24, 2018 5:43 pm

skullzaflare: see viewtopic.php?f=21&t=128915
Please, note that downgrading to previous RouterOS versions (below 6.41) will not restore "master-port" configuration, so use backups to restore configuration on downgrade.
 
User avatar
BartoszP
Forum Guru
Forum Guru
Posts: 1478
Joined: Mon Jun 16, 2014 1:13 pm
Location: Poland

Re: v6.40.8 [bugfix] is released!

Wed Apr 25, 2018 10:59 am

M33 (mmips) as CAPSMAN, mix of mipsbe devices as CAPS.
Upgrade of M33 from 6.40.7 to 6.40.8 with no problems but CAPS have not connected to CAPSMAN.
They have not been upgraded automatically to "current" version as CAPSMAN configuration is set to.
After manual upgrade and restart they have connected imediatelly. All CAPS have access to Internet.

EDIT:
maybe it's not verion related problem of CAPSMAN configuration with mixed archs.
Real admins use real keyboards.
 
Beone
Member Candidate
Member Candidate
Posts: 232
Joined: Fri Feb 11, 2011 1:11 pm

Re: v6.40.8 [bugfix] is released!

Wed Apr 25, 2018 6:43 pm

Please release v6.40.9 including following fixes:

*) tile - improved system performance and stability ("/system routerboard upgrade" required);
*) capsman - improved CAPsMAN responsiveness with large amount of CAP interfaces (confirmed fix for our issue);

There are still to many changes with the new bridge implementation that we want to hold of going to v6.41+
 
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1278
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.40.8 [bugfix] is released!

Wed Apr 25, 2018 7:40 pm

Unfortunately we can not backport any fixes to older versions. In order to get these updates you will need to upgrade above 6.40.x. All the fixes which are backportable and are tested - are included in bugfix versions. You simply will need at some point upgrade to the new bridge implementation and learn how to use it.
 
djdrastic
Member Candidate
Member Candidate
Posts: 267
Joined: Wed Aug 01, 2012 2:14 pm

Re: v6.40.8 [bugfix] is released!

Wed Apr 25, 2018 9:20 pm

Thanks,will report any findings we find migrating from v6.40.7-8 though a couple of customers were unimpressed when we told them we'd have to sit and patch all the equipment again.
Have started testing for the inevitable new bridge implementation , but have found some things a bit hard to find.

Will probably take a bit of time to get accustomed to the "new" way of doing things.
Last edited by djdrastic on Wed Apr 25, 2018 9:28 pm, edited 1 time in total.
 
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1278
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.40.8 [bugfix] is released!

Wed Apr 25, 2018 9:24 pm

You are always welcome to ask questions through support@mikrotik.com e-mail. If you find out something that seems to be a bug, then report it through the same e-mail. Same rules apply to any version and any other process besides bridge. If something is working on version X and is not working on version Y, then report such problem to us.
 
Beone
Member Candidate
Member Candidate
Posts: 232
Joined: Fri Feb 11, 2011 1:11 pm

Re: v6.40.8 [bugfix] is released!

Fri Apr 27, 2018 1:29 am

all v6.4x.y releases have 'broken' reachability information output for

/ip route get number=$interface value-name=gateway-status

OUTPUT up until v6.39.3 = consistent PPPoE-client & DHCP-client
dhcp-client "1.1.1.1 reachable via ether1"
pppoe-client "1.1.1.1 reachable via pppoe1"

OUTPUT starting v6.4x.y != consistent behavior
dhcp-client "1.1.1.1 reachable via ether1"
pppoe-client "pppoe1 reachable"

Changing the output as inconsistent results in broken scripts and maybe other broken things

[Ticket#2018042722000332]
 
User avatar
macsrwe
Long time Member
Long time Member
Posts: 605
Joined: Mon Apr 02, 2007 5:43 am
Location: Arizona, USA
Contact:

Re: v6.40.8 [bugfix] is released!

Fri Apr 27, 2018 9:06 am

[deleted]
 
User avatar
chechito
Forum Guru
Forum Guru
Posts: 1455
Joined: Sun Aug 24, 2014 3:14 am
Location: Bogota Colombia
Contact:

Re: v6.40.8 [bugfix] is released!

Sun Apr 29, 2018 3:22 pm

thanks a lot mikrotik for this

*) wireless - improved compatibility with BCM chipset devices;

improved too much wifi performance on all my clients

im very happy with this :D
 
mblfone
just joined
Posts: 8
Joined: Sun Feb 02, 2014 2:22 am

Re: v6.40.8 [bugfix] is released!

Mon Apr 30, 2018 5:25 am

Hello,

I updated to v6.40.8 this morning. I was working in Winbox this evening and kept getting disconnected. I have updated to the newest Winbox release and am still getting disconnected. There is no log entry as to why.

This seems to be since my v6.40.8 upgrade.

Any thoughts?
 
User avatar
chechito
Forum Guru
Forum Guru
Posts: 1455
Joined: Sun Aug 24, 2014 3:14 am
Location: Bogota Colombia
Contact:

Re: v6.40.8 [bugfix] is released!

Mon Apr 30, 2018 5:49 am

Hello,

I updated to v6.40.8 this morning. I was working in Winbox this evening and kept getting disconnected. I have updated to the newest Winbox release and am still getting disconnected. There is no log entry as to why.

This seems to be since my v6.40.8 upgrade.

Any thoughts?
im still on winbox 3.11
 
User avatar
Ocean
just joined
Posts: 3
Joined: Mon Sep 03, 2012 11:10 am
Location: Russia/Moscow
Contact:

Re: v6.40.8 [bugfix] is released!

Tue May 01, 2018 2:17 pm

If used in l2tp client "add-default-route=yes", then the routing table is not correctly created and VPN does not work (on ROS 39.3 everything ok).

Example:

ROS 6.40.8

l2tp client config:
[admin@Dom-3G-Router] >  /interface l2tp-client print 
Flags: X - disabled, R - running 
 0  R name="l2tp-vpn.site.local" max-mtu=1450 max-mru=1450 mrru=disabled connect-to=vpn.site.local user="derevna" password="fwefwe" profile=default-encryption 
      keepalive-timeout=10 use-ipsec=no ipsec-secret="" allow-fast-path=no add-default-route=yes default-route-distance=1 dial-on-demand=no allow=pap,chap,mschap1,mschap2 
Routing table:
[admin@Dom-3G-Router] > /ip route print detail 
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibit 
 0 ADS  dst-address=0.0.0.0/0 gateway=l2tp-vpn.site.local gateway-status=l2tp-vpn.site.local reachable distance=1 scope=30 target-scope=10 
 1  DS  dst-address=0.0.0.0/0 gateway=ppp-out1 gateway-status=ppp-out1 reachable distance=2 scope=30 target-scope=10 
...
 3 A S  dst-address=10.10.10.0/27 gateway=172.16.2.1 gateway-status=172.16.2.1 reachable via  l2tp-vpn.site.local distance=1 scope=30 target-scope=10 
...
 5 ADC  dst-address=10.112.112.173/32 pref-src=100.91.5.55 gateway=ppp-out1 gateway-status=ppp-out1 reachable distance=0 scope=10 
 6  DS  dst-address=92.45.172.192/32 gateway=92.45.172.192 gateway-status=92.45.172.192 unreachable distance=0 scope=30 target-scope=10 
...
10 ADC  dst-address=172.16.2.1/32 pref-src=172.16.2.2 gateway=l2tp-vpn.site.local gateway-status=l2tp-vpn.site.local reachable distance=0 scope=10 
...
Watch entry 6:
DS  dst-address=92.45.172.192/32 gateway=92.45.172.192 gateway-status=92.45.172.192 unreachable
Wrong gateway is specified! IP - 92.45.172.192 is remote public IP address VPN (connect-to).

On ROS 6.39.3 correct gateway is specified:
[admin@Dom-3G-Router] > /ip route print detail 
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibit 
 0 ADS  dst-address=0.0.0.0/0 gateway=172.16.2.1 gateway-status=172.16.2.1 reachable via  l2tp-vpn.site.local distance=1 scope=30 target-scope=10 
 1  DS  dst-address=0.0.0.0/0 gateway=10.112.112.196 gateway-status=10.112.112.196 reachable via  ppp-out1 distance=2 scope=30 target-scope=10 
...
 3 A S  dst-address=10.10.10.0/27 gateway=172.16.2.1 gateway-status=172.16.2.1 reachable via  l2tp-vpn.site.local distance=1 scope=30 target-scope=10 
...
 5 ADC  dst-address=10.112.112.196/32 pref-src=100.64.84.86 gateway=ppp-out1 gateway-status=ppp-out1 reachable distance=0 scope=10 
 6 ADS  dst-address=92.45.172.192/32 gateway=10.112.112.196 gateway-status=10.112.112.196 reachable via  ppp-out1 distance=0 scope=30 target-scope=10 
...
 9 ADC  dst-address=172.16.2.1/32 pref-src=172.16.2.2 gateway=l2tp-vpn.site.local gateway-status=l2tp-vpn.site.local reachable distance=0 scope=10 
...
Watch entry 6:
ADS  dst-address=92.45.172.192/32 gateway=10.112.112.196 gateway-status=10.112.112.196 reachable via  ppp-out1 distance=0 scope=30 target-scope=10
dst-address=92.45.172.192/32 is accessible via ppp-out1 connection!
Andrey
 
dickyhk
just joined
Posts: 1
Joined: Sat May 05, 2018 4:18 pm

Re: v6.40.8 [bugfix] is released!

Sat May 05, 2018 4:32 pm

Hi, I have a problem on my wireless after update from 6.40.7 to 6.40.8 few days ago on my hAP ac device.
Sometimes all the wireless devices will be disconnected few seconds and then reconnect to the router and this problem happen quite frequently.
Sometimes it could happen few times per hour.
I see in the router log showing 00:00:00:00:00:00@wlan1: disconnected, unicast key exchange timeout and wlan1 00:00:00:00:00:00 was WDS master every time the disconnect happen.
Should I downgrade it to 6.40.7 or need some config changes?
Thank you.
20:48:07 wireless,info 00:00:00:00:00:00@wlan1: connected
20:48:12 wireless,info 00:00:00:00:00:00@wlan1: disconnected, unicast key exchange timeout
20:48:12 wireless,info wlan1 00:00:00:00:00:00 was WDS master
20:48:12 wireless,info Device A MAC address@wlan1: disconnected, disabling
20:48:12 wireless,info Device B MAC address@wlan3: disconnected, disabling
20:48:16 wireless,info Device B MAC address@wlan3: connected
20:48:19 wireless,info Device C MAC address@wlan1: connected
20:48:24 wireless,info 00:00:00:00:00:00@wlan1: connected
20:48:29 wireless,info 00:00:00:00:00:00@wlan1: disconnected, unicast key exchange timeout
20:48:29 wireless,info wlan1 00:00:00:00:00:00 was WDS master
20:48:29 wireless,info Device C MAC address@wlan1: disconnected, disabling
20:48:29 wireless,info Device B MAC address@wlan3: disconnected, disabling
20:48:31 wireless,info Device C MAC address@wlan1: connected
20:48:35 wireless,info 00:00:00:00:00:00@wlan1: connected
20:48:36 wireless,info Device D MAC address@wlan1: connected
20:48:40 wireless,info 00:00:00:00:00:00@wlan1: disconnected, unicast key exchange timeout
20:48:40 wireless,info wlan1 00:00:00:00:00:00 was WDS master
20:48:40 wireless,info Device D MAC address@wlan1: disconnected, disabling
20:48:40 wireless,info Device C MAC address@wlan1: disconnected, disabling
20:48:42 wireless,info Device C MAC address@wlan1: connected
20:48:44 wireless,info Device D MAC address@wlan1: connected
20:48:45 wireless,info Device B MAC address@wlan3: connected
20:48:54 wireless,info Device A MAC address@wlan1: connected
 
chubbs596
newbie
Posts: 34
Joined: Fri Dec 06, 2013 6:07 pm

Re: v6.40.8 [bugfix] is released!

Fri May 11, 2018 8:08 am

Hi Guys

I have upgraded on of my x86 edge bgp peering routers from 6.37.4 to 6.40.8,

I have noticed the the following issues on ipv6 bgp sessions that sessions with MD5 Keys do not establish a connection but the ipv4 sessions do.

I then upgraded the same router to 6.42.1 and the ipv6 bgp sessions with md5 keys work again.

has someone else seen these issues?
 
OlegTrufanov
just joined
Posts: 2
Joined: Thu May 30, 2013 6:26 pm

Re: v6.40.8 [bugfix] is released!

Fri May 11, 2018 10:32 am

Hi. I would like to inform you from Russia. After installation of Dr. web anti-virusWeb Security Space there is no possibility to pass authorization on mikrotik router . In my case, I use the product rbm33g.
After the installation of the antivirus when you try to enter the address of the router 192.168.88.1 after entering username and password I get infinite loading of the page.
Dr.web said this is due to a non-project code page in the router mikrotik version ROS 6.40.8 .Engineer-drweb said that they that the make to correct this situation.
I thought you might be interested in this information . If you decide it will be faster.
Thanks for understanding
 
kos
just joined
Posts: 4
Joined: Mon Oct 31, 2016 11:51 am

Re: v6.40.8 [bugfix] is released!

Fri May 11, 2018 10:46 am

If used in l2tp client "add-default-route=yes", then the routing table is not correctly created and VPN does not work (on ROS 39.3 everything ok).

Example:

ROS 6.40.8

l2tp client config:
[admin@Dom-3G-Router] >  /interface l2tp-client print 
Flags: X - disabled, R - running 
 0  R name="l2tp-vpn.site.local" max-mtu=1450 max-mru=1450 mrru=disabled connect-to=vpn.site.local user="derevna" password="fwefwe" profile=default-encryption 
      keepalive-timeout=10 use-ipsec=no ipsec-secret="" allow-fast-path=no add-default-route=yes default-route-distance=1 dial-on-demand=no allow=pap,chap,mschap1,mschap2 
Routing table:
[admin@Dom-3G-Router] > /ip route print detail 
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibit 
 0 ADS  dst-address=0.0.0.0/0 gateway=l2tp-vpn.site.local gateway-status=l2tp-vpn.site.local reachable distance=1 scope=30 target-scope=10 
 1  DS  dst-address=0.0.0.0/0 gateway=ppp-out1 gateway-status=ppp-out1 reachable distance=2 scope=30 target-scope=10 
...
 3 A S  dst-address=10.10.10.0/27 gateway=172.16.2.1 gateway-status=172.16.2.1 reachable via  l2tp-vpn.site.local distance=1 scope=30 target-scope=10 
...
 5 ADC  dst-address=10.112.112.173/32 pref-src=100.91.5.55 gateway=ppp-out1 gateway-status=ppp-out1 reachable distance=0 scope=10 
 6  DS  dst-address=92.45.172.192/32 gateway=92.45.172.192 gateway-status=92.45.172.192 unreachable distance=0 scope=30 target-scope=10 
...
10 ADC  dst-address=172.16.2.1/32 pref-src=172.16.2.2 gateway=l2tp-vpn.site.local gateway-status=l2tp-vpn.site.local reachable distance=0 scope=10 
...
Watch entry 6:
DS  dst-address=92.45.172.192/32 gateway=92.45.172.192 gateway-status=92.45.172.192 unreachable
Wrong gateway is specified! IP - 92.45.172.192 is remote public IP address VPN (connect-to).

On ROS 6.39.3 correct gateway is specified:
[admin@Dom-3G-Router] > /ip route print detail 
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibit 
 0 ADS  dst-address=0.0.0.0/0 gateway=172.16.2.1 gateway-status=172.16.2.1 reachable via  l2tp-vpn.site.local distance=1 scope=30 target-scope=10 
 1  DS  dst-address=0.0.0.0/0 gateway=10.112.112.196 gateway-status=10.112.112.196 reachable via  ppp-out1 distance=2 scope=30 target-scope=10 
...
 3 A S  dst-address=10.10.10.0/27 gateway=172.16.2.1 gateway-status=172.16.2.1 reachable via  l2tp-vpn.site.local distance=1 scope=30 target-scope=10 
...
 5 ADC  dst-address=10.112.112.196/32 pref-src=100.64.84.86 gateway=ppp-out1 gateway-status=ppp-out1 reachable distance=0 scope=10 
 6 ADS  dst-address=92.45.172.192/32 gateway=10.112.112.196 gateway-status=10.112.112.196 reachable via  ppp-out1 distance=0 scope=30 target-scope=10 
...
 9 ADC  dst-address=172.16.2.1/32 pref-src=172.16.2.2 gateway=l2tp-vpn.site.local gateway-status=l2tp-vpn.site.local reachable distance=0 scope=10 
...
Watch entry 6:
ADS  dst-address=92.45.172.192/32 gateway=10.112.112.196 gateway-status=10.112.112.196 reachable via  ppp-out1 distance=0 scope=30 target-scope=10
dst-address=92.45.172.192/32 is accessible via ppp-out1 connection!
I can confirm this issue, when using dongle for WAN connection. Tested with OVPN and ROS 6.40.7, 6.40.8, 6.42.1 and 6.43rc11. Working fine with ROS 6.39.3.
 
OlegTrufanov
just joined
Posts: 2
Joined: Thu May 30, 2013 6:26 pm

Re: v6.40.8 [bugfix] is released!

Fri May 11, 2018 11:02 am

Do you respond to requests from the forum or bugfix create a new bug ?
 
andriys
Forum Guru
Forum Guru
Posts: 1025
Joined: Thu Nov 24, 2011 1:59 pm
Location: Kharkiv, Ukraine

Re: v6.40.8 [bugfix] is released!

Fri May 11, 2018 3:38 pm

Do you respond to requests from the forum or bugfix create a new bug ?
This is a user forum. Mikrotik staff responds on forum occasionally, but in general all (potential) bugs should be reported to support@ via email.
 
Kerbia
newbie
Posts: 41
Joined: Wed Nov 16, 2016 3:03 pm

Re: v6.40.8 [bugfix] is released!

Sat May 26, 2018 12:27 pm

edit:// nvm.
 
gotsprings
Member
Member
Posts: 454
Joined: Mon May 14, 2012 9:30 pm

Re: v6.40.8 [bugfix] is released!

Wed Jun 06, 2018 6:46 pm

Nevermind.

Romon in script and not schedule...

Scripts fire now.
 
jarda
Forum Guru
Forum Guru
Posts: 7333
Joined: Mon Oct 22, 2012 4:46 pm

Re: v6.40.8 [bugfix] is released!

Thu Jun 14, 2018 9:39 pm

I have just updated rb750GR3 with dude package installed from 6.40.5 to 6.40.8 which resulted into bootloop without any beep.
Netinstalled 6.40.8 and imported rsc file generated by 6.40.5 before.
Only about 1/3 of the config was imported on the first run, so the rest needed to be copy-pasted into terminal window afterwards. It was not signalized anyhow.
After that, first minutes of run looks good...

So be prepaired when you decide to do the same!

edit: not so good... the ntp client looks to be not working and the environment of the scripts (variables) are not created/populated.

edit2: ntp client works finally... dont know why...

edit3: finally even the variables started to work. Good.

Why the router tries to connect to ip 224.0.0.22?
 
andriys
Forum Guru
Forum Guru
Posts: 1025
Joined: Thu Nov 24, 2011 1:59 pm
Location: Kharkiv, Ukraine

Re: v6.40.8 [bugfix] is released!

Fri Jun 15, 2018 2:31 pm

Why the router tries to connect to ip 224.0.0.22?
This is a multicast address that has something to do with IGMPv3. May be related to IGMP proxy or UPnP.
 
jarda
Forum Guru
Forum Guru
Posts: 7333
Joined: Mon Oct 22, 2012 4:46 pm

Re: v6.40.8 [bugfix] is released!

Fri Jun 15, 2018 3:24 pm

Maybe the multicast option was selected at that time in ntp client when I tried to convince it to work. At the moment these tryouts vanished. I do not use upnp at all nor igmp.

 
jondavy
Member Candidate
Member Candidate
Posts: 112
Joined: Tue May 12, 2009 11:14 pm
Location: Brasil

Re: v6.40.8 [bugfix] is released!

Sun Jun 17, 2018 2:53 am

I was with my cloud core router restarting every day saying kernel failure,
I decided to update to last version and it did not solve, I decided to buy another cloud core and it continues with the same problem says:

system,error,critical router was rebooted without proper shutdown, probably kernel failure
system,error,critical kernel failure in previous boot
 
andriys
Forum Guru
Forum Guru
Posts: 1025
Joined: Thu Nov 24, 2011 1:59 pm
Location: Kharkiv, Ukraine

Re: v6.40.8 [bugfix] is released!

Sun Jun 17, 2018 1:41 pm

I decided to buy another cloud core and it continues with the same problem says:
Have you tried writing to support@ ? Just curious.

Who is online

Users browsing this forum: complexgeek, npero and 6 guests