What's new in 6.20 (2014-Oct-01 10:06):
*) cert scep - use fingerprints for transaction ids;
*) ipsec - support fqdn as my id;
*) fetch - allow fetching files larger than 4G;
*) fetch - fixed problem where files fetched over https were trimmed in size;
*) fixed problem - it was not possible to see %26 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);
If you already run some RouterOS v6.x version, simply click “Check for updates” in QuickSet, Webfig or Winbox packages menu.
Others: http://www.mikrotik.com/download
/me waits for people to upgrade their access point 100km away and have it fail then complain on the forums
[admin@xxxx] /ppp active> print Flags: R - radius # NAME SERVICE CALLER-ID ADDRESS UPTIME ENCODING 0 probe sstp x 0.0.0.0 57s AES256-CBC 1 probe sstp x 0.0.0.0 43s AES256-CBC 2 probe sstp x 0.0.0.0 42s AES256-CBC 3 probe sstp x 0.0.0.0 39s AES256-CBC 4 probe sstp x 0.0.0.0 38s AES256-CBCThe address is not 0.0.0.0 but a valid adres. It all works, this is a cosmetic bug only.
Sergejs,zyzelis, what exact changes do you want to see for wireless?
happens when i check the package aswllwhere is wireless-fp ??all the above files are from all-packages-mipsbe-6.20.zip
P
More stability for ac Nv2zyzelis, what exact changes do you want to see for wireless?
More stability for ac Nv2zyzelis, what exact changes do you want to see for wireless?
More tuning of the ac protocol
Maybe now I can see dude on package list, but it is not possible to login to dude.What's new in 6.20 (2014-Oct-01 10:06):
*) fixed problem - it was not possible to see %26 uninstall dude package;
k0st3k,
make sure you have used the same wireless package before and after upgrade (for example wireless-fp was installed and now wireless is installed).
Yes, Winbox 2.2.18 still works.Winbox v2.x still works?
what exactly happened? Can you see in the Winbox by Layer2 connection?when upgrading from 6.1 to 6.20 tik ccr1036 went in down .
Current-tx-power reading isn't made yet for the AC radios.RB922UAGS-5HPacD hanged after upgrade, needed power cycle to restore access.
minimum tx-power 6dBm, seriously guys? Current Tx power still shows 0dBm. Automatic Tx power based on antenna gain still not working. No manual noise floor threshold... No spectral scan... I guess I am holding the AC products until the wireless-fp will be ready for production. Its a shame I have already upgraded one PTP link with SXTacs which at the current state has lower performance and shitty CCQ (with R52n-M was perfect).
Would like to know as well. Have held at 6.7 because I need to maintain SSTP compatibility with Windows clients.has all the sstp and pptp issues been resolved from the 6.8 debacle?
Does this mean we soon now will se a new version of The Dude to ?Hello,
after 6.19 -> 6.20 the monitor service disk for the dude doesn't work anymore...
p.s. *) stores are replaced with folders and disks are now managed under /disk menu;
I can create folders from winbox or i need to create via console?
18:31:36 system,info verified ntp-6.20-mipsbe.npk
18:31:36 system,info verified ppp-6.20-mipsbe.npk
18:31:36 system,info verified security-6.20-mipsbe.npk
18:31:36 system,info verified advanced-tools-6.20-mipsbe.npk
18:31:36 system,info verified system-6.20-mipsbe.npk
18:31:36 system,info installed system-6.20
18:31:36 system,info installed advanced-tools-6.20
18:31:36 system,info installed security-6.20
18:31:36 system,info installed ppp-6.20
18:31:36 system,info installed ntp-6.20
18:31:36 system,info installed dhcp-6.20
18:31:55 interface,info ether1-gateway link up (speed 100M, full duplex)
18:31:55 interface,info ether2-master-local link up (speed 100M, full duplex)
18:32:05 l2tp,info first L2TP UDP packet received from AAA.BBB.CCC.DDD
18:32:06 l2tp,ppp,info,account NewYork logged in, 172.16.2.2
18:32:07 l2tp,ppp,info l2tp-NewYork: authenticated
18:32:07 l2tp,ppp,info l2tp-NewYork: connected
18:33:29 l2tp,info first L2TP UDP packet received from EEE.FFF.GGG.HHH
18:33:30 l2tp,ppp,info,account AmsTerDam logged in, 172.16.0.2
18:33:30 l2tp,ppp,info l2tp-AmsTerDam: authenticated
18:33:30 l2tp,ppp,info l2tp-AmsTerDam: connected
18:34:24 ipsec,error phase1 negotiation failed due to time up XXX.YYY.ZZZ.XYZ[500]<=>172.16.0.2[500] d3315d1866b8c332:0000000000000000
18:34:25 ipsec,error phase1 negotiation failed due to time up XXX.YYY.ZZZ.XYZ[500]<=>172.16.3.2[500] 16586dd9987fdd61:0000000000000000
18:34:25 ipsec,error phase1 negotiation failed due to time up XXX.YYY.ZZZ.XYZ[500]<=>172.16.2.2[500] eb7dcfc791c0bee6:0000000000000000
18:35:20 system,info,account user poi logged in from xx.xx.xx.xx via winbox
18:35:25 ipsec,error phase1 negotiation failed due to time up XXX.YYY.ZZZ.XYZ[500]<=>172.16.3.2[500] 093864a77ece5743:0000000000000000
18:36:25 ipsec,error phase1 negotiation failed due to time up XXX.YYY.ZZZ.XYZ[500]<=>172.16.3.2[500] 4c4becbcae12daaf:0000000000000000
18:37:25 ipsec,error phase1 negotiation failed due to time up XXX.YYY.ZZZ.XYZ[500]<=>172.16.3.2[500] 4f9ce96e1d5c59fc:0000000000000000
18:38:35 ipsec,error phase1 negotiation failed due to time up XXX.YYY.ZZZ.XYZ[500]<=>172.16.3.2[500] deb801af0ba9d6c9:0000000000000000
18:39:45 ipsec,error phase1 negotiation failed due to time up XXX.YYY.ZZZ.XYZ[500]<=>172.16.3.2[500] 1dcfedef4e117603:0000000000000000
18:40:45 ipsec,error phase1 negotiation failed due to time up XXX.YYY.ZZZ.XYZ[500]<=>172.16.3.2[500] cd73a72de5a4bac4:0000000000000000
18:41:55 ipsec,error phase1 negotiation failed due to time up XXX.YYY.ZZZ.XYZ[500]<=>172.16.3.2[500] 283e9d748f979c57:0000000000000000
18:43:05 ipsec,error phase1 negotiation failed due to time up XXX.YYY.ZZZ.XYZ[500]<=>172.16.3.2[500] 1ec10de96c1e35d1:0000000000000000
18:44:05 ipsec,error phase1 negotiation failed due to time up XXX.YYY.ZZZ.XYZ[500]<=>172.16.3.2[500] 5242da5b92f02b49:0000000000000000
18:45:15 ipsec,error phase1 negotiation failed due to time up XXX.YYY.ZZZ.XYZ[500]<=>172.16.3.2[500] af1788a953e26d08:0000000000000000
18:46:15 ipsec,error phase1 negotiation failed due to time up XXX.YYY.ZZZ.XYZ[500]<=>172.16.3.2[500] ff0ccd07cae83c2e:0000000000000000
18:47:15 ipsec,error phase1 negotiation failed due to time up XXX.YYY.ZZZ.XYZ[500]<=>172.16.3.2[500] 808e73705a1348d8:0000000000000000
18:48:25 ipsec,error phase1 negotiation failed due to time up XXX.YYY.ZZZ.XYZ[500]<=>172.16.3.2[500] 6035bc208336ee44:0000000000000000
18:49:35 ipsec,error phase1 negotiation failed due to time up XXX.YYY.ZZZ.XYZ[500]<=>172.16.3.2[500] 01b1c837e087c94c:0000000000000000
18:50:35 ipsec,error phase1 negotiation failed due to time up XXX.YYY.ZZZ.XYZ[500]<=>172.16.3.2[500] 981177407414de2b:0000000000000000
18:51:45 ipsec,error phase1 negotiation failed due to time up XXX.YYY.ZZZ.XYZ[500]<=>172.16.3.2[500] 0dc357f7303910f6:0000000000000000
18:52:55 ipsec,error phase1 negotiation failed due to time up XXX.YYY.ZZZ.XYZ[500]<=>172.16.3.2[500] 5f75d3969bcac9a1:0000000000000000
18:53:55 ipsec,error phase1 negotiation failed due to time up XXX.YYY.ZZZ.XYZ[500]<=>172.16.3.2[500] f788b880bcbb35af:0000000000000000
18:55:05 ipsec,error phase1 negotiation failed due to time up XXX.YYY.ZZZ.XYZ[500]<=>172.16.3.2[500] a70224a893e2dd19:0000000000000000
18:56:15 ipsec,error phase1 negotiation failed due to time up XXX.YYY.ZZZ.XYZ[500]<=>172.16.3.2[500] a18784aafea7ce3e:0000000000000000
18:57:15 ipsec,error phase1 negotiation failed due to time up XXX.YYY.ZZZ.XYZ[500]<=>172.16.3.2[500] 600e0d1fcba18246:0000000000000000
18:58:25 ipsec,error phase1 negotiation failed due to time up XXX.YYY.ZZZ.XYZ[500]<=>172.16.3.2[500] aee578115f534004:0000000000000000
18:59:35 ipsec,error phase1 negotiation failed due to time up XXX.YYY.ZZZ.XYZ[500]<=>172.16.3.2[500] 89f6b5acc9731f3a:0000000000000000
19:00:35 ipsec,error phase1 negotiation failed due to time up XXX.YYY.ZZZ.XYZ[500]<=>172.16.3.2[500] 83cea2c786936e7c:0000000000000000
19:01:45 ipsec,error phase1 negotiation failed due to time up XXX.YYY.ZZZ.XYZ[500]<=>172.16.3.2[500] 58f4bf218c569a07:0000000000000000
19:02:55 ipsec,error phase1 negotiation failed due to time up XXX.YYY.ZZZ.XYZ[500]<=>172.16.3.2[500] acd4b68e28f0a7ff:0000000000000000
same case here, and already sent support output file to support@mikrotik.com).RB433UAH
6.20 (6.21rc3) no micro-sd disk ( microSDHC Kingston 4GB) > downgrade 6.19 disk view
I already wrote here, but it was deleted. (20 days ago)
Thanks for the heads up.My 6to4 tunnel to tunnelbroker.net broke with 6.20. Can't even get them working again if I redo the configuration completely.
In 6.19 I could set manual tx-power to 0 but starting 6.20 the driver wont let me go below 6dBm (on Netmetal 5).... So apparently there is a change in wireless but its not in the changelog. Yes, manual tx-power works but not the automatic based on the antenna gain... at least it did not work the way I am used to from previous versions.Current-tx-power reading isn't made yet for the AC radios.RB922UAGS-5HPacD hanged after upgrade, needed power cycle to restore access.
minimum tx-power 6dBm, seriously guys? Current Tx power still shows 0dBm. Automatic Tx power based on antenna gain still not working. No manual noise floor threshold... No spectral scan... I guess I am holding the AC products until the wireless-fp will be ready for production. Its a shame I have already upgraded one PTP link with SXTacs which at the current state has lower performance and shitty CCQ (with R52n-M was perfect).
TX-power changing is working on the AC.
What signal you have on your SXT AC link?
If you set the band to the A/N on both sides do you get the same CCQ and performance like with the R52nM cards?
Try to reset the wireless interface configuration and check if the situation gets bettwe with default values.
My 6to4 tunnel to tunnelbroker.net works as expected after upgrade to 6.20.pitr wrote:
My 6to4 tunnel to tunnelbroker.net broke with 6.20. Can't even get them working again if I redo the configuration completely.
Thanks for the heads up.
I was too busy the past few days to upgrade mine to 6.20 (they're currently on 6.19). Guess I'll leave them at 6.19 till the problem is fixed.
[admin@kattegat] > /interface 6to4 add mtu=1280 name=ipng-tunnel local-address=86.26.1.97 remote-address=192.88.99.1 disabled=no
[admin@kattegat] > /ipv6 address add address=2002:561a:0161::1/3 interface=ipng-tunnel
[admin@kattegat] > /ipv6 route add dst-address=2000::/3 gateway=::192.88.99.1%ipng-tunnel
[admin@kattegat] > /ipv6 route print detail
Flags: X - disabled, A - active, D - dynamic,
C - connect, S - static, r - rip, o - ospf, b - bgp, U - unreachable
0 ADC dst-address=2000::/3 gateway=ipng-tunnel
gateway-status=ipng-tunnel unreachable distance=0 scope=10
1 S dst-address=2000::/3 gateway=::192.88.99.1%ipng-tunnel
gateway-status=::192.88.99.1%ipng-tunnel unreachable distance=1
scope=30 target-scope=10
2 ADC dst-address=2002:561a:161:1::/64 gateway=ether2-master-local
gateway-status=ether2-master-local reachable distance=0 scope=10
3 ADC dst-address=2002:561a:161:2::/64 gateway=wlan1
gateway-status=wlan1 reachable distance=0 scope=10
This is not a probably OK. A maybe better:[admin@kattegat] > /ipv6 address add address=2002:561a:0161::1/3 interface=ipng-tunnel
[admin@kattegat] > /ipv6 route add dst-address=2000::/3 gateway=::192.88.99.1%ipng-tunnel
Check how you have defined IPv6 address and default gateway on the tunnel. It looks that 6.20 is more strictly that previous version. The definition like this works with 6.20 OK:My 6to4 tunnel to tunnelbroker.net broke with 6.20. Can't even get them working again if I redo the configuration completely.
Conclusion: Wait for a stable release.Conclusion: be careful on remote installs in case similar issues come through for you, as it did on my RB2011UAS-2HnD, in our case we had someone on the other end before we did the upgrade. (upgrade rollout planning is key )
Ok, that fixed it. ThanksThis is not a probably OK. A maybe better:[admin@kattegat] > /ipv6 address add address=2002:561a:0161::1/3 interface=ipng-tunnel
[admin@kattegat] > /ipv6 route add dst-address=2000::/3 gateway=::192.88.99.1%ipng-tunnel
/ipv6 address add address=2002:561a:0161::1/16 interface=ipng-tunnel
/ipv6 route add dst-address=::/0 gateway=::192.88.99.1%ipng-tunnel
Check how you have defined IPv6 address and default gateway on the tunnel. It looks that 6.20 is more strictly that previous version. The definition like this works with 6.20 OK:My 6to4 tunnel to tunnelbroker.net broke with 6.20. Can't even get them working again if I redo the configuration completely.
/ipv6 address add address=2001:db85678::2/64 advertise=no interface=wan6he
/ipv6 route add check-gateway=ping distance=1 gateway=2001:db85678::1
The default gateway in this way do not (older ROS version probably accepts this):
/ipv6 route add distance=1 gateway=wan6he
We also managed to reproduce this issue which appears after upgrade. Please follow our changelog on download page and wait for version which will include fix for it.Ok, that fixed it. ThanksThis is not a probably OK. A maybe better:[admin@kattegat] > /ipv6 address add address=2002:561a:0161::1/3 interface=ipng-tunnel
[admin@kattegat] > /ipv6 route add dst-address=2000::/3 gateway=::192.88.99.1%ipng-tunnel
/ipv6 address add address=2002:561a:0161::1/16 interface=ipng-tunnel
/ipv6 route add dst-address=::/0 gateway=::192.88.99.1%ipng-tunnel
Check how you have defined IPv6 address and default gateway on the tunnel. It looks that 6.20 is more strictly that previous version. The definition like this works with 6.20 OK:My 6to4 tunnel to tunnelbroker.net broke with 6.20. Can't even get them working again if I redo the configuration completely.
/ipv6 address add address=2001:db85678::2/64 advertise=no interface=wan6he
/ipv6 route add check-gateway=ping distance=1 gateway=2001:db85678::1
The default gateway in this way do not (older ROS version probably accepts this):
/ipv6 route add distance=1 gateway=wan6he
Somebody make firmware update from 3.18 to 3.19 ?
where can i find change log to this firmware?
Thanks for the suggestion. That's actually the configuration I was using before the upgrade, and it has precisely the same problem:This is not a probably OK. A maybe better:[admin@kattegat] > /ipv6 address add address=2002:561a:0161::1/3 interface=ipng-tunnel
[admin@kattegat] > /ipv6 route add dst-address=2000::/3 gateway=::192.88.99.1%ipng-tunnel
/ipv6 address add address=2002:561a:0161::1/16 interface=ipng-tunnel
/ipv6 route add dst-address=::/0 gateway=::192.88.99.1%ipng-tunnel
[admin@kattegat] /ipv6 route> print detail
Flags: X - disabled, A - active, D - dynamic,
C - connect, S - static, r - rip, o - ospf, b - bgp, U - unreachable
0 S dst-address=::/0 gateway=::192.88.99.1%ipng-tunnel
gateway-status=::192.88.99.1%ipng-tunnel unreachable distance=1
scope=30 target-scope=10
1 ADC dst-address=2002::/16 gateway=ipng-tunnel
gateway-status=ipng-tunnel unreachable distance=0 scope=10
2 ADC dst-address=2002:561a:161:1::/64 gateway=ether2-master-local
gateway-status=ether2-master-local reachable distance=0 scope=10
3 ADC dst-address=2002:561a:161:2::/64 gateway=wlan1
gateway-status=wlan1 reachable distance=0 scope=10
0 items in Tools-->Profile on some upgraded devices
I can't realize what this issue depends of...
Dear developers, please see the attached screenshots. Can You explain, where are my disks? Before update to 6.20 i have two disks - internal and sd-card. After - nothing.
Same here plus:In 6.19 I could set manual tx-power to 0 but starting 6.20 the driver wont let me go below 6dBm (on Netmetal 5).... So apparently there is a change in wireless but its not in the changelog. Yes, manual tx-power works but not the automatic based on the antenna gain... at least it did not work the way I am used to from previous versions.Current-tx-power reading isn't made yet for the AC radios.RB922UAGS-5HPacD hanged after upgrade, needed power cycle to restore access.
minimum tx-power 6dBm, seriously guys? Current Tx power still shows 0dBm. Automatic Tx power based on antenna gain still not working. No manual noise floor threshold... No spectral scan... I guess I am holding the AC products until the wireless-fp will be ready for production. Its a shame I have already upgraded one PTP link with SXTacs which at the current state has lower performance and shitty CCQ (with R52n-M was perfect).
TX-power changing is working on the AC.
What signal you have on your SXT AC link?
If you set the band to the A/N on both sides do you get the same CCQ and performance like with the R52nM cards?
Try to reset the wireless interface configuration and check if the situation gets bettwe with default values.
I have -57/-54 signal on the link with 0 tx-power (its 50m link across the road), I cannot get close to my previous setup with R52n-M and standard wireless package with 5.26... Even if I switch the SXTs to A/N its similar to AC.. lower CCQ, lower throughput (40MHz jumping between 100 and 170Mbps).
When I tried wireless-fp with R52n-M on another link some time ago (I guess it was 6.15) I have seen similar issues - lower CCQ and performance, so switched back to default wireless package = stable 99-100% CCQ and throughput
I am using SSTP with 6.20 (and 6.19) with Windows clients and I didn't experienced troubles. What kind of issues should I check?Would like to know as well. Have held at 6.7 because I need to maintain SSTP compatibility with Windows clients.has all the sstp and pptp issues been resolved from the 6.8 debacle?
For a while there people were complaining about the inability to establish SSTP tunnels from Windows as well as stability issues with them from MT to MT.I am using SSTP with 6.20 (and 6.19) with Windows clients and I didn't experienced troubles. What kind of issues should I check?Would like to know as well. Have held at 6.7 because I need to maintain SSTP compatibility with Windows clients.has all the sstp and pptp issues been resolved from the 6.8 debacle?
SSTP to win7 clients is fine for me on 6.19Would like to know as well. Have held at 6.7 because I need to maintain SSTP compatibility with Windows clients.has all the sstp and pptp issues been resolved from the 6.8 debacle?
SIP Direct Media appeared only in 6.20, You need more accurate read my question ...This 'new' option exists even in ROS 5.x and is described here:
http://wiki.mikrotik.com/wiki/Manual:IP ... vice_Ports
Regards,
[grzegorz@Some_Gateway] /ip firewall service-port> export # oct/09/2014 13:38:06 by RouterOS 5.26 # /ip firewall service-port set ftp disabled=no ports=21 set tftp disabled=no ports=69 set irc disabled=no ports=6667 set h323 disabled=no set sip disabled=no ports=5060,5061 sip-direct-media=no set pptp disabled=noAll I wanted to say, is that 'sip-direct-media' option is not new feature introduced in ROS 6.20.
Just Google it...And I interesting in how it work
> /export compact # oct/09/2014 08:18:04 by RouterOS 6.20 #error exporting /ip ipsec mode-config #error exporting /ip ipsec policy group #error exporting /ip ipsec proposal #error exporting /snmp community #error exporting /certificate scep-server #error exporting /certificate scep-server ra #error exporting /ip ipsec peer #error exporting /ip ipsec policy #error exporting /ip ssh #error exporting /routing bfd interface #error exporting /snmp #error exporting /tool e-mail #error exporting /tool mac-server mac-winbox > /snmp print error - contact MikroTik support and send a supout file (2)I downgraded to 6.19 and everything worked again.... anyone else experience something like this?
Same issue with CCR1009. I created a ticket to mt.same case here, and already sent support output file to support@mikrotik.com).RB433UAH
6.20 (6.21rc3) no micro-sd disk ( microSDHC Kingston 4GB) > downgrade 6.19 disk view
I already wrote here, but it was deleted. (20 days ago)
You can find more about this in iptables documentation. It's a helper that rewrite SIP Header if you using NAT.What is this "SIP Direct Media" ?
Where information about this new feature ?
We had an issue going from 6.15 to 6.20 on a CCR1009:
ros code
> /export compact # oct/09/2014 08:18:04 by RouterOS 6.20 #error exporting /ip ipsec mode-config #error exporting /ip ipsec policy group #error exporting /ip ipsec proposal #error exporting /snmp community #error exporting /certificate scep-server #error exporting /certificate scep-server ra #error exporting /ip ipsec peer #error exporting /ip ipsec policy #error exporting /ip ssh #error exporting /routing bfd interface #error exporting /snmp #error exporting /tool e-mail #error exporting /tool mac-server mac-winbox > /snmp print error - contact MikroTik support and send a supout file (2)I downgraded to 6.19 and everything worked again.... anyone else experience something like this?
[admin@MikroTik] /ip dhcp-server network> export
# oct/12/2014 00:20:22 by RouterOS 6.20
# software id = 6GM9-Z8QY
#
/ip dhcp-server network
add address=192.168.33.0/24
Facing the same problem with Webfig on the RB850Gx2 too (ROS 6.20).I upgraded an RB2011 from 6.12 to 6.20. Now the configuration of networks for DHCP Server in webfig does not work anymore.
Upgraded NetMetal firmware to 3.18.1 and the device crashes every time that I use wireless scanner. Totally inaccessible, and it needs power cycle.
We are also seeing an issue with UM and WG500MP printers interfaced via API. Ticket for 1 Hour or 4 Hour print as 1 or 4 seconds. Printing was correct on RoS 6.17. Avccount still works for 1 or 4 hours though so only a "cosmetic" bug we hope.......Again problems with user-manager.
6.18 on x86 with user manager, upgraded to 6.20 and user-manager stop working, not see the files of the database.
Revert back to 6.18 solve the problem.
I have the same problemthis "router was rebooted without proper shutdown by watchdog timer" problem solved?
I still have this issue from 6.7 to 6.19 mostly on all RB2011/ RB750G / RB911 / SXT Lite5 devices approx 70 pieces of our devices affected by this error.
Mostly all devices reboot between 1am to 3am. Devices that are affacted are not on the same location, (20-40km) all of them are running through uninterruptible power supply, so it could not be a power problem. At the same time, and on the same tower other devices which are not running Mikrotik 6.x version are still running.
+1I have the same problemthis "router was rebooted without proper shutdown by watchdog timer" problem solved?
I still have this issue from 6.7 to 6.19 mostly on all RB2011/ RB750G / RB911 / SXT Lite5 devices approx 70 pieces of our devices affected by this error.
Mostly all devices reboot between 1am to 3am. Devices that are affacted are not on the same location, (20-40km) all of them are running through uninterruptible power supply, so it could not be a power problem. At the same time, and on the same tower other devices which are not running Mikrotik 6.x version are still running.
even sometimes when you try to generate or export supout.rif configure itself can perform a watchdog-reboot
This is simply fucking hate.
RB2011 has 60MIt happens on 6.x when running on 32mb devices for me. Have you seen it also on other devices?
yes, mikrotik suggested execution netinsall, so I made for test on RB2011iL.Have you tried netinstall? I wasn't able to solve this problem only when there was not enough free memory.
I would like to see some effective memory management optimisation in the next ros release as 32mb devices really need it.
Any news on supporting LACP/802.3ad for trunking on CRS (without taxing the CPU)? We have just activated our 10GE link from our Data Center and the point where our radio trunk arrives in a 6+0 configuration. We're now obligated to keep a V1910 on site just for the aggregation of the radio links. On the remote site we have a similar situation, since our V1910 doesn't support 10GE.
What's new in 6.20 (2014-Oct-01 10:06):
*) cert scep - use fingerprints for transaction ids;
*) ipsec - support fqdn as my id;
*) fetch - allow fetching files larger than 4G;
*) fetch - fixed problem where files fetched over https were trimmed in size;
*) fixed problem - it was not possible to see %26 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);
If you already run some RouterOS v6.x version, simply click “Check for updates” in QuickSet, Webfig or Winbox packages menu.
Others: http://www.mikrotik.com/download
We have a similar OSPF problem. E.g. one system 6.19 the other one 6.20; OSPF does not work! (Doesnt find the OSPF router).Upgraded a link to 6.20 with both sides doing OSPF/MPLS. After 2 days a IP subnet on one side of the link was no longer reachable.
Routes are there but packets do not pass. Reboot resolved the issue.
Check my reply here will solve it: http://forum.mikrotik.com/viewtopic.php ... 21#p452421Again problems with user-manager.
6.18 on x86 with user manager, upgraded to 6.20 and user-manager stop working, not see the files of the database.
Revert back to 6.18 solve the problem.
ThanksCheck my reply here will solve it: http://forum.mikrotik.com/viewtopic.php ... 21#p452421Again problems with user-manager.
6.18 on x86 with user manager, upgraded to 6.20 and user-manager stop working, not see the files of the database.
Revert back to 6.18 solve the problem.
Hello,We have upgraded several RB951 series routers in a class situation. 2 or 3 of these have all exhibited odd firewall behavior when rules are disabled.
It shows a rule disabled in Winbox yet the rule continues to work, e.g a rule that logs traffic keeps logging even when disabled. We did not test this in CLI as time was tight.
A reboot fixes the issue.
Not all devices have shown this so perhaps user error - has anyone else seen this ?
That confirms that oneHello,We have upgraded several RB951 series routers in a class situation. 2 or 3 of these have all exhibited odd firewall behavior when rules are disabled.
It shows a rule disabled in Winbox yet the rule continues to work, e.g a rule that logs traffic keeps logging even when disabled. We did not test this in CLI as time was tight.
A reboot fixes the issue.
Not all devices have shown this so perhaps user error - has anyone else seen this ?
I am experience the same problem. I made a video that shows the bug: http://www.youtube.com/watch?v=2umo6Kvd ... e=youtu.be
Best regards.
I've run into something similar.I found this:
in 6.20 does not show the correct values for the data rates and current transmit power
Attention:
Mikrotik 6.21 bricked 3 rb951-G after upgrade.
Beep and lights looping.
Mikrotik upgrade failed rb951-G 6.21: http://youtu.be/O0kJacEIdh0
How to fix? RMA?!
Ticket#2014103066001015
Thanks
I manage after a few tens of tries with netinstall to roll back to 6.20, but only in 1 951G.tenta com netinstall.... se nao der... deita ao lixo
Attention:
Mikrotik 6.21 bricked 3 rb951-G after upgrade.
Beep and lights looping.
Mikrotik upgrade failed rb951-G 6.21: http://youtu.be/O0kJacEIdh0
How to fix? RMA?!
Ticket#2014103066001015
Thanks