What’s new in 1.4:
*) added ability to limit access by VLAN;
*) added ability to disable Mikrotik Discovery Protocol;
*) fixed problem - connecting to SwOS over VLAN did not work;
*) fixed problem - switch sometimes stopped responding;
tried but still could not get remote access to SWos
my update to 1.4
my config as kirshteins posted had post on Tue Oct 19, 2010 9:14 am
still unable to ping to 88.1
need your assistance please… to be able to remotely access the SWos
I can confirm that I had no access to the switch web interface on the “trunk” port of this configuration: http://wiki.mikrotik.com/wiki/SwOS/Router-On-A-Stick with versions 1.3 and 1.4. On the access ports, I had access to the web config (v1.3) when I added a static arp entry on the PC. The PC was sending vlan0 (no tags) frames.
Which port are you trying to access through? Make sure IP address you are trying to connect from is in Allow From range.
vlan access port4 vlanID 16
hm… the “Allow From” range were blank(nothing there), I assume “0.0.0.0”, is it right… I will give a try… thank you for the response… will be back to you soonest
Port4 removes VLAN header on egress. That is why you cannot connect with VLAN tagged frames.
Thank you kirshteins.
This makes perfect sense.
Is it possible for SwOS to be easily modified for the next release so that we would access the web interface regardless of vlan tags and vlan settings? 
ouch… nothing that work to remote access… play with IP in the “Allow From” also changing Egress VLAN Header “add if missing” or “always strip” or “leave as is”
btw its already ticked(port 1,2,3,4,5) on “allow from ports” and “allow from vlan”:“16”
need your guidance… for easy setup…
If you specify Allow From VLAN make sure VLAN Mode is not disabled on ingress port. Then you should be able to connect to port2 or port3 using VLAN 16 tag.
We will check what can be done about it. I agree than it can be very confusing when VLAN Header “add if missing” or “always strip” modes are used.
pls show screen capture for these “remote access setup”… thank you very much
Can anyone confirm if an upgrade from 1.2 to 1.4 is possible to do remotely? (No VLANing, just simple switch)
I have sites that I would like to upgrade, but I have no access to them for a few months. If I do the upgrade I can not power cycle the switch if needed.
If I had this choice, I would not upgrade until I have a person on sight to help power-cycle or even replace hardware if the power stops in the middle of upgrade procedure.
Remote upgrade from 1.2 to 1.4 is impossible.
For me its a bug, its look like switch after “reboot” doesnt make power cycle (1.4 has that same problem).
I can confirm the same.
Reboot button does not work after upgrade. Need to manually power cycle the units.
Dammit MT why are errors as simple and stupid as these being allowed through the firmware cycle?
This is the last chance and I’m buying other boards. It’s not worth the headaches of waiting a year just for you guys to make it work.
I hear HP is having a sale on good switches that aren’t broken
This is v1.2 problem not v1.4 problem. Try upgrading from different PC/OS/browser.
Like I said - 1.4 has the same problem.
What exactly happens when you try to reboot switch? What is your network topology between switch and management device? Reboot is working perfectly fine for me.
Switch is on my table, connected directly to pc. I tried IE and FF and I cant downgrade 1.4 to 1.2 remotly.
When I “click” reboot there is info “rebooting”, then “receiving”, webpage reloads and FW is still that same.
Switch doesnt make power cycle because my PC should say “network cable unplugged” (I mean link should be down for a moment).
One more thing - after reboot uptime is still that same.
To clarify you need to select FW file and press upgrade to downgrade. Have you tested with another PC?