6.23 released!

What’s new in 6.23 (2014-Dec-04 14:46):

*) pptp - fixed problem where tunnel stopped transmitting packets under heavy load;
*) web proxy - caching in RAM for boards with 32MB or less RAM will not cache any content;
*) leds - removed ‘led’ command and added support for ‘on’, ‘off’ types under ‘system leds’;
*) files - allow to move files between different disks in winbox;
*) dhcpv4 server - fix adding address lists from radius;
*) dhcpv4 server - make radius classless static route tag as dhcp vendor specific;
*) smb - fixed HDD used/free space reporting
*) made powerpc metarouters work again (were broken in v6.22);
*) disks - fixed fat32 formatting where some bogus files with strange names were created
(to delete existing files reformatting is needed);
*) disks - fixed problem where some of USB disks were not recognized;
*) fetch - allow checking certificate trust without crl checking;
*) userman - fix more web session problems when user uses
customer and administrator interfaces at the same time;
*) snmp - fix external storage info reporting;
*) snmp - fix bulk walk problem introduced in v6.20;
*) fix tunnels - keep keepalive disabled for existing tunnels when upgrading;
*) fix tunnels - mtu for eoip tunnels was not allowed
to be set less than 1280 since 6.20;
*) using routing-marks could lead to tunnel loop detection to turn off tunnels;

Click “Check for updates” in QuickSet or Packages menu to get the new version. It should also work for v5 routers, please report if your device found the new release and how the update went.

Upgraded 3 lab routers. RB 493G, X86 and RB411AR. Have RIP, OSPF, EOIP, PPPOE, PPTP services running. NO problems so far. I upgraded 411AR with autoupgrade feature, rest with manual file transfer. Sadly I don’t have a spare micro SD card here to test whether the filesystem (pxe boot on it) on RB493G now recognizes it.

Bug with SNMP not enabling without a reboot from ticket [Ticket#2014112666000541] is also fixed.

Why is it not in the change-log? :frowning:

I have used command

/led user-led=yes

in netwatch. Now it is not working. What is the new syntax?

EDIT: It seems like

/system leds set numbers=[find leds=user-led] type=on

should work, right?

I think there is a small bug here - that command is working only if user-led is defined. So I must use

 /system leds add leds=user-led type=off

first. This is missing in WinBox.

RB433UAH

6.23 (2014-Dec-03 14:50) one disk
6.23 (2014-Dec-04 14:46) dual disk :smiley: bonus?
double disk.jpg

It will be fixed in Winbox, but from now on such preset has to be added first.

uptime 11 min crash :confused:

downgrade 6.23 (2014-Dec-03 14:50) crash :frowning: before updating to 6.23 (2014-Dec-04 14:46) works !
crash.jpg

Ah-h-h, 6to4 tunnel’s routes to he.net work again :slight_smile: And again - it’s not in changelog =)

continuation

downgrade 6.19
upgrade 6.23 (2014-Dec-03 14:50)
winbox delete fake disk (disk1,disk3) ; rename disk4 > disk1; proxy disable, enable
reboot

6.23 (2014-Dec-04 14:46) bad build
6.23 (2014-Dec-03).jpg

cosmetic ..

If you experience any crash at 6.23. Please make support output file after the crash and send it to support (support@mikrotik.com).
It will help us very much!

Hello MikroTik support team,

thank you for starting more active communication between releasing new version and after releasing it. I would like to ask you about one old topic (from 08/2012) - setting variable via SMS - what is the chance that this bug will be fixed? Is there any ETA for fixing of this bug, please?

Tickets opened for this issue:
Ticket#2012083066000462
Ticket#2013010766000731

Issue is discussed here:
http://forum.mikrotik.com/t/how-initialized-a-variable-by-sms/53857/1

Thank you

There is something strange about SSTP client in this version:

  • if there is just one SSTP connection from router, no problem;
  • if there is one SSTP and one PPTP connection from router, no problem;
  • if I manually connect router to two SSTP connections, no problem;
  • if there are two SSTP connections, after reboot there is an error state.

As an error state I mean this:

  • IP addresses of all SSTP and PPTP connections are marked as invalid;
  • I can disable both SSTP connections, but after enabling back, still none is working, neither PPTP, I have to reboot.

Is somebody experiencing this problem too? It started in 6.21, I think. When I revert to 6.20, no problem…

I’m facing the same issue - two sstp-clients, and after some random time the connections are up, but the IP addresses on client’s side are marked as invalid, no communication is going through the tunnels. Only one solution is to disable both sstp-clients, reboot the router and then enable the sstp-client interfaces. Reboot without disabling interfaces is not working. I’m facing this issue in versions 6.13 - 6.19 (maybe also in earlier 6.x).

@MikroTik support team: Will be support.out files taken once there will be invalid IP addresses visible usefull in investigation, please?

Please run following command on your device “/system logging add topics=sstp,debug,packet”. Then reconnect all your sstp tunnels and generate supout file. Send this file to our support e-mail.
http://www.mikrotik.com/support.html

Well, I have just done it - [Ticket#2014120566000721]. Thanks for taking care.

6to4 tunnels working for me again (SixXS), finally able to upgrade from 6.19. :slight_smile:

Hi,

ipv6 not working - [Ticket#2014120566000801]

I have downgrade all RB.

Thanks.

Virtual APs in CAPsMAN v2 re not working, discussed in thread http://forum.mikrotik.com/t/capsman-v2-ready-for-testing/82662/1 It was also in 6.22.