Is this all new or are they bug fixes?What's new in 6.32.3 (2015-Oct-19 11:13):
*) switch - fixed CRS settings set back to defaults after a reboot;
*) netinstall - include missing RB1200 drivers;
*) firewall - fixed connection-rate matcher;
*) ppp, pptp, l2tp, pppoe: fixed router dead locked if compression was enabled on link;
*) quickset - create proper firewall rules when PPPoE is used for address acquisition;
*) sstp - fixed kernel crash when other party started to fragment ppp packets in the middle;
*) ippool6 - optimize same prefix acquisition;
*) winbox - Shift+Ins & Shift+Del did not work in multi entry fields;
*) winbox - allow to specify ipv6 address in traffic flow target;
*) winbox - allow to specify eap-radius-accounting in CAPsMAN;
*) winbox - allow to enter dns name in email server;
*) ups - fix console oid print;
*) tunnel - fix loopback keepalives on gre and ipip;
*) pptp,l 2tp, sstp, pppoe: do not send data packets before we have negotiated connection with other
side (happens on dial-on-demand interfaces), this brakes when connecting to other party servers;
*) pptp, l2tp, sstp - make it work when add-default-route & dial-on-demand both are enabled;
*) pptp, l2tp, sstp, pppoe clients - fixed problem where they failed to connect
at startup and only reboot helped;
*) nv2 - fixed kernel failure with frame size accounting;
*) ovpn client - fixed crash when ovpn didn't receive it's ip address;
*) lcd - fix slideshow for CCR1072, and possible sign issues for temperatures;
*) winbox - make console notice correct screen size;
*) ssh - allow to specify pass as argument for private key import;
*) winbox - refetch hotspot walled garden hit counter;
*) winbox - added client-connections & server-connections to web proxy status;
*) cerm - fix scep server certificate-reply degenerate PKCS#7 signed-data content;
*) bgp - specific BGP networks were changed to different ones;
*) cerm - allow export for all types except templates;
*) wlan - update brazil-anatel country;
*) winbox - fixed context menu actions to apply to all selected items;
*) nv2 - fixed kernel failure with frame size accounting;
What problem was this? Did it happen on each nv2 running radio? I had some backhauls stalling after weeks of running, could this have to do with it?
Same story happens again: 6.32.2 [current] was pretty stable after being around for some weeks without too many new comments or disasters.
This morning found a client that still wasn't upgraded to 6.32.2 so started the auto upgrade script and AGAIN to my surprise a new 'current' version (6.32.3) is installed. Do you guys never learn? DON'T call it "Current" and DON'T make it default download option.
Now I can only hope its a good one, not a new disaster in the make...... (and its only a single client... pff)
