feature requests / bugs summary (RB250GS/ RB260GS)

Last UPDATED: 18 Dec 2013

!! WARNING, SWOS 1.7 has a BUG, which bricks RB250GS/RB260GS , do not use any ACL RULES with SwOS 1.7 !!
Version since 1.9 there is a new design of web ui, if you get weired output, powercycle switch (check: http://forum.mikrotik.com/viewtopic.php?f=17&t=72106)

latest: changelog: http://forum.mikrotik.com/viewtopic.php?f=17&t=80051
RB250GS: http://download.mikrotik.com/swos/swos-rb250-1.10.lzb
RB260GS: http://download.mikrotik.com/swos/swos-rb260-1.10.lzb



Hello,

i have summarized all feature requests and bugs, i have seen, to have a quick overview. Also, i added some bugs, i have found in my SwOS :slight_smile:

Could any guy from mikrotik give us some info on these bugs / feature requests, so that all customers can see, that there is developing going on ? :slight_smile:

Thanks Ronny


Bugfixes:
new:

fixed
Official Changelog for SwOS: http://download.mikrotik.com/swos/changelog.txt

  • fixed in 1.6 - Bugfix: SwOS SNMPv2-MIB::sysLocation. is 1. Cisco, Planet, Linksys, 3com all has sysLocation.0
  • fixed in 1.6 - Bugfix: SNMP: Values for “IF-MIB::ifSpeed.x” are wrong (Value: 100Mbits link=> 150 | 1000Mbit/s link => 152), needs to be 100000000 intead of 150 and 1000000000 instead of 152
  • fixed in 1.6 - Bugfix: SwOS Web Interface Error (http://forum.mikrotik.com/t/swos-web-interface-error/44351/1)
  • fixed in 1.6 - Bugfix: Problems with high latency or slow speed links and connecting to RB250G
  • fixed in 1.6 - Bugfix: Problems with passwords
  • fixed in 1.7 - Support for RB260GS
  • fixed in 1.7 - updated web look
  • fixed in 1.7 - setting link speed (without autoconfiguration) did not work (allways 10Mbits was used)
  • fixed in 1.8 - Bugfix: SFP Port information missing with SNMP on RB260GS - http://forum.mikrotik.com/viewtopic.php?f=17&t=70264
  • fixed in 1.8 - Bugfix: RB260GS: SFP LED diode (UD601) does not work - http://forum.mikrotik.com/viewtopic.php?f=17&t=70264&p=357749#p357749
  • fixed in 1.8 - Bugfix: RB260GS: Setup SFP port for tags (trunk) / Traffic from/to SFP port has no tags (striped) regardless of the setting. - http://forum.mikrotik.com/viewtopic.php?f=17&t=49646&p=252329#p357387
  • fixed in 1.8 - Bugfix: RB260GS: If i add 2 or more ACL rule - config file don’t make export with button “Save Backup” (not tried with RB250GS) - http://forum.mikrotik.com/viewtopic.php?f=17&t=70264&p=357749#p357749
  • fixed in 1.9 - fixed logout not working / power down port, when it is disabled / fixed problem - RB260G wasn’t reachable over VLAN
  • fixed in 1.10 - fixed problem - sometimes board did not reboot after upgrade
  • fixed in 1.10 - fixed problem - hosts tab stopped working if 0:0:0:0:0:0 was learned on RB250
  • fixed in 1.10 - fixed problem - broadcast correct uptime to it’s neighbors
  • fixed in 1.10 - allow to disable/enable auto negotiation on SFP port on RB260
  • fixed in 1.10 - enable transmit on SFP port only when module with signal is detected (RB260)
  • fixed in 1.10 - fixed problem - port lock & lock on first did not work on RB260
  • fixed in 1.10 - fixed problem - port full duplex setting was set for wrong port on RB260
  • fixed in 1.10 - fixed problem - port egress rate did not limit traffic properly on RB260
  • fixed in 1.10 - added vlan-id to static host table (RB260)


    acknowledged / being worked on
  • none yet

Features
new:

acknowledged / being worked on

not possible features (due to hardware limitations or inefficiency)

  • Feature: CLI through SSH / or telnet (http://forum.mikrotik.com/t/feature-request/42120/1)
  • Feature: SNMP: Version should be configurable(I prefer 2c or better 3 with simple user encryption for security)
  • Feature: LACP Channels possible
  • Feature: Remote Syslog

Hardware issues

+1 good job!

This is probably the place to add another request so here goes:

Make the user login name configurable. I’d like to change it from “admin” to something more suitable as per my username/password policy.

Thank you for the bug reports and feature requests.

We are working to fix the following bugs:

  • SwOS SNMPv2-MIB::sysLocation. is 1. Cisco, Planet, Linksys, 3com all has sysLocation.0
  • SNMP: Values for “IF-MIB::ifSpeed.x” are wrong (Value: 100Mbits link=> 150 | 1000Mbit/s link => 152), needs to be 100000000 intead of 150 and 1000000000 instead of 152

Feature list to be implemented in future releases:

  • SNMP: There should be 64-bit counter available
  • IGMP Snooping
  • Sort hosts by port
  • Add description/name for ports
  • Spanning-tree support (long development process)

Features that cannot be implemented due to hardware limitations or inefficiency:

  • CLI through SSH / or telnet
  • 802.1q Tunneling
  • SNMP: Version should be configurable (2c or better 3 with simple user encryption for security)
  • LACP Channels
  • Remote Syslog (there is no local syslog neither)

How about fixing the discovery protocol while you guys are at it? Take a look here http://forum.mikrotik.com/t/mikrotik-discovery-protocol-on-swos/45986/1

Also will we be able to change the username? Last question, what is 802.1q Tunneling?

Thanks,
Jeroen

@kirshteins Thanks for your feedback, good support from mikrotik :slight_smile:

I have updated my 1st post to reflect your feedback and what issues are not answered yet.
I hope this will help new customers.

Ronny

How about possibility to obtain IP via DHCP?
I use lot’s of those switches for untagging few vlan’s at the cable end, and get very soon very boring to assign IP for each of them manually.

Damn, I was kind of still hoping on LACP Channels and to a lesser extent remote syslog. The first feature does make more sense on a 8 or 24 port switch anyway:).

+1 to bugfixes pls:
SwOS ‘Hosts’ tab Web interface error (http://forum.mikrotik.com/t/swos-web-interface-error/40705/1)

updated 1st post to reflect resolved issues in version 1.6

If there is a bug missing or a feature, please give me a hint to the thread ,so that i can add this.
I think this summary is very good to have a short summary, without searching this entire forum :slight_smile:

Ronny

Still a very valuable topic. I find myself checking it too often :smiley:

Thanks :slight_smile:

I have updated my 1st post to reflect new Feature Requests. If i miss something, please let me know.

Any Mikrotik guy here, that can give us some updates on the mentioned issues / requests in the 1st post ?
More customer communication ist better :slight_smile:

Ronny

  • Bugs/Issues:
  • It is unclear what “LINK Enabled” does. Unchecking “Enabled” still shows a link even with reboot
    Is this a forwarding function and not an actual link function? If so, perhaps move it to Forwarding tab.
  • Sort vlan appears to sort by string value, not integer value; i.e. vlan 200 precedes vlan 5.
  • Web Interface errors persist, albeit vastly improved in 1.6; Reboot helps this and it gets worse over time.


  • Requests:
  • Forwarding database via snmp (with port/vlan)
  • ROS version via snmp
  • Forwarding database expiration (macs never expire currently)
    What happens when you get 2k entries? Is it fifo?
  • Select/Deselect all buttons on vlan page
    If you have 20 vlans, you don’t want to have to click 100 boxes.
  • Simple config file or publish the existing format
    I just installed ~100 of these and although “click-click” works, I now have carpal tunnel in my mouse hand.
    I could have written a php script to spit out the configs with ip, hostname, etc. if the format was published.
    I would reverse engineer except it is subject to change.
  • Move the LED’s to the front so that from front or top you can see the LED’s. Applies to 750 family as well.
    These zip tie perfectly in the RB450 rack mount bracket but the LED’s can’t be seen from the front.
    It seems silly to have the pwr and act on the front and link status on the top.
    A cheap light pipe can do this.

EDIT: Added ROS version via snmp
EDIT2: Added select-alls

What about these features? When will the new version come? There is a multicasting HD video streaming available here on academic networks, so IGMP Snooping is necessary.

Probably the best place for a feature request.

I love my little rb250GS. But it would be nice to have a per-vlan fdb table, this would likely mean a per-vlan hosts table too.

Currently If I send the same mac out of 2 different port on 2 separate vlans the fdb flaps between them. A table per vlan would resolve this.

For example, if I have a router with 2 upstream cable modems (both have the same gateway mac) It wont work through the rb250gs.

Not sure if its feasible.

Hello,

ok, i have updated my first post and it should now reflect all answers, so the 1st post has the most overview so far, hopefully there will be a feedback from mikrotik, when we can expect a new firmware and whats in detail is worked on.

Any information will be honored, so please mikrotik, give us a sign on the process here :wink:

Thanks,
Ronny

Good to see you’ve updated :smiley: . Although this part of the forum is kind of dead. I do also wonder whether SWOS is still being maintained…

Updated the thread title to reflect, that mostly this is RB250GS affected :slight_smile:

I also contacted mikrotik support to get some information, whats up with SWOS and the new RB260GS and hope, i will soon be able to let you all know, what i have get back from the guys :slight_smile:

Ronny

Hello,

got a response from janis:

Hello,

The development of SwOS is not cancelled but currently it is progressing very
slowly due to higher priority projects like RouterOS version 6 and Cloud Core Router.

There are no major software improvements in SwOS v1.7, it was released because of
hardware support for RB260GS. Besides SFP slot RB260GS has the same functionality
as RB250GS.

The differences between RB250GS and 260GS:

  • RB250GS has Atheros AR8316 switch chip
  • RB260GS has Atheros AR8327 switch chip and SFP slot

Ronny

Does the AR8327 in the new RB260GS finally address the VLAN limitations? As we know, the RB250GS doesn’t support mixed tagged and untagged VLANs on the same port, supported as so called General or Hybrid mode in better switches - must be all untagged (Access) or all tagged (Trunk). It would be a shame to do a new HW design and not include this often requested feature.