We have released 6.33.3 version. Version includes only bug fixes compared with 6.33.2 and does not include new features. If you need new features, then test 6.34rc versions.
Version is released in current channel.
What’s new in 6.33.3 (2015-Dec-03 16:08):
*) ethernet - fixed 10/100Mbps autonegotiation fails on RB922UAGS ether1 (introduced in v6.33.2);
*) upnp - fixed memory leak;
*) ssh - avoid double session cleanup;
*) email - make password field sensitive in console.
it is even worse. SXT5 sa ac. upgrade but still fixed on 100mbit-fdx → i see it in the neighbor list, i can see the ip and some traffic (torch) but it is inaccessible. no ping, no mac-ping, no telnet/winbox/mac-telnet.
wireless connect is working for 5 seconds. “no beacons received”.. with a signal of -59.
on 6.33 it was stable and fast. sometimes a longer connect. but no mac-ping/telnet via wireless possible.
the device is on a 25m high mast and it is hard snowing today.. thanx.
it is the first time since i use mikrotik devices (and i use them for many years) where i have to change the production state to “unreliable”.
It is connected to a CRS125-24G and the included external GigE PoE Injector. All mounted in an upwarmed and dry container.
I drove to the mast, unplugged the PoE, plugged it back after a while and the device was working again.
But this should not be part of future update-scenarios. If the devices can´t be updated remote, they are useless.
I can not test out every possible variants and konstellations within the routerboard product line local before updating remote devices. This is YOUR job
Something™ is breaking sporadically my ssh communication to the router with this firmware.
I have a python script managing some interfaces and routes on my RB1100AHx2. It uses paramiko for the ssh access functions and runs hourly.
After update to 6.33.3 I had 4 connection failures in less than 24 hours:
Traceback (most recent call last):
File "/opt/ampr/updateros.py", line 167, in <module>
main()
File "/opt/ampr/updateros.py", line 154, in main
ssh.exec_command(command)
File "/usr/lib/python2.7/dist-packages/paramiko/client.py", line 363, in exec_command
chan = self._transport.open_session()
File "/usr/lib/python2.7/dist-packages/paramiko/transport.py", line 658, in open_session
return self.open_channel('session')
File "/usr/lib/python2.7/dist-packages/paramiko/transport.py", line 713, in open_channel
raise SSHException('SSH session not active')
paramiko.SSHException: SSH session not active
Unfortunately I have no logging. Back to 6.33.2 to check if it happens again…
This may be a sign to switch to the ROS API, but anyhow…
After update from 6.33.1 to 6.33.3 two of four my Mikrotik will not boot!!! This firmware is not compatible with all devices/configurations! Do not update your production routers…
2 RB951G-2HnD updated successfully
1 RB2011UiAS will not boot after update - stopped on “Starting Services” with all ethernet status LEDs off (no second beep).
1 RB751G-2HnD will not boot after update - stopped somewhere during boot.
I was able to reset both routers and after restoring config from backup - it was stopped again. After it I tested latest Beta - same result.
After downgrading to 6.33.1 and restoring config from backup - everything working again…
Now I’m afraid to do future upgrades… something wrong with this new firmwares… be aware!!!
I still have unsolved Ticket#2015113066000843. Since 6.33.1 my 4 devices are unusable, 2xGrooveA 52HPn, 1xSXTG2HnD and 1xRB2011UiAS-2HnD-IN. Problem is that they work ok unencrypted but are unable to establish WPA or WPA2. AP log says “unicast key exchange timeout”. After couple of days of correspondence with support they demanded SSH connection with 2 of my problematic devices. Support operator made new security profile with predefined WPA2 key and somehow established connection. Trying to replicate that thru winbox, I disconnected devices and not succeeded to connect them again. I have year long experience playing with these mikrotiks and remember these devices working straight from the box. Anyone familiar with this problem?
I found a routerboard 532 with 2.95 sitting in a drawer, so far I can’t upgrade it by dragging any v5 or 6 .npk file into the files directory and rebooting.
How can I upgrade this?
Hi,
It seems that after upgrade, routeros does not clear ssh session if client suddenly kills the connection without calling a close() function.
I use php ssh2 to backup my devices and there are many dead connections in /users/active
This can be reproduced easily with official ssh client (eg ubuntu):
ssh from a linux machine to the device
Open a new terminal in client and kill the ssh process
It seems that fix “ssh - avoid double session clean-up;” is not working as expected.
Downgrading to 6.33.2 fixes the problem.
Please write to support@mikrotik.com and send supout files which would be generated while there are “dead” SSH connections.
I am not being able to reproduce this issue. I make multiple SSH sessions and break them without close. After few seconds they are closed and I do not see them any more under active connections.
I’ve Problems with the OVPN - Server coming with RoS 6.33 not solved yet.
First of all, after any OVPN - Client, except a MKT - Router, connects, I get the Errormessages shown.
Also,
the Tunnels are very unstable or the Connection is established but there is no Traffic ( even Ping the other endpoint ) going through the Tunnel.
I tried different ( Linux and Windows ) Clients, but they all show the same.
No Problem with RoS 6.27 so far,
so any idea what to do ?