*) added ability to specify ethernet ports from
which it is allowed to connect to the switch;
*) fixed problem - reboot sometimes made switch unresponsive;
*) fixed problem - Hosts table were not shown sometimes;
*) fixed problem - sometimes it didn’t respond to ARP requests
or responded with big packets;
*) fixed problem - remote web interface didn’t work well over VLANs;
Nice but remote upgrade from 1.2 to 1.3 is impossible because switch need power cycle
EDIT
I have another issue. After upgrade i can’t manage switch, when i click some tab i.eg. system switch stops respond to ping and disconnect link (my PC says “cable unpluged”). Now my switch is useless because i cant do downgrade so im afraid to check another switch.
I turned off autonegotiation on my card but it doesnt work.
another EDIT
After few disconnects i made downgrade to 1.2 and switch is working.
I had that problem too, i have to press reset and hold, then power switch off still holding reset, then power on and release reset after few seconds.
Its something new because in fw 1.0 and 1.2 reset button worked normally.
What is status of ACL LED? It should start blinking few seconds after power up, if reset button is pressed. Configuration will be reset if you release reset at this point. Otherwise (after 10 seconds of ACT blinking) it will start to blink twice as frequent and switch will try to boot using BOOTP. http://wiki.mikrotik.com/wiki/SwOS#Reinstall_SwOS_firmware
kirshteins - I bought 3 new switches (i think is newer series than before because it has diffrent ac adaptor).
I upgraded to 1.3 and … that same trouble. I managed that when I “click” some tab switch is doing reboot.
1.3 really sucks
I click on tabs in 1.3 and they work just fine, the switch does not reboot itself.
Although I must say my VLAN trunk scenario is taking way too long to implement at first. One would dream configurations would get easier with new products. Good thing I am a stubborn donkey with a few hours to bash my head.