Hi,
will be added the STP and or RSTP to RB260GS switch ?
If so, what standard will be used for STP ? the IEEE 802.1D or a proprietary STP ?
I trust in you mikrotik!
They have simply said "sometime in the future"... but that was a couple of years ago! It may never be addedHi,
will be added the STP and or RSTP to RB260GS switch ?
If so, what standard will be used for STP ? the IEEE 802.1D or a proprietary STP ?
I trust in you mikrotik!
The hardware can probably handle it fine... but this feature is not longer planned for the near future (this means at least a few years away, maybe longer), see the post above.Unfortunately. STP, resp. RSTP is definitely important feature.
Can you generally estimate if RB250/260 hardware is capable to handle it or isn't?
SWOS is what it is. If it isn't there, it won't be added anytime soon. You should look at using the regular Miktorik router if you want ospf or stp.(R)STP is not a protocol I would like to depend on for redundancy. Is there no way to implement OSPF?
True, that's what I meant Maybe TS can solve his 'redundancy problems' using OSPF on a router instead of STP on a switch.SWOS is what it is. If it isn't there, it won't be added anytime soon. You should look at using the regular Miktorik router if you want ospf or stp.(R)STP is not a protocol I would like to depend on for redundancy. Is there no way to implement OSPF?
"who" is planning to adopt "what" ???Currently they are planning to adapot it.
It's not a chip limitation, maybe the chip isn't good at RSTP and thats why it's not implemented.at the market its very rare a switch under 8-10 gigabit ports to support stp or rstp, looks like there is no economically viable to implement strong features on 5 port switch, many features are only seen on 10+ ports switches.
not only on mikrotik, other brands are the same, looks like chipset limitation
It's not a chip limitation, maybe the chip isn't good at RSTP and thats why it's not implemented.at the market its very rare a switch under 8-10 gigabit ports to support stp or rstp, looks like there is no economically viable to implement strong features on 5 port switch, many features are only seen on 10+ ports switches.
not only on mikrotik, other brands are the same, looks like chipset limitation
Here is the feature list for the chip: (it's a lot of goodies ie QinQ)
AR8327/AR8327N Features
- Supports 802.3az Power Management
- The AR8327N chip includes the Hardware NAT (Network Address Translation) function
- The AR8327 chip (without the ‘N’ designation) does not contain the Hardware NAT function
- ACL Mask Rule from Layer1~4. Port No, DA, SA, Ethernet Type, VLAN, IP Protocol, IPv4/v6 Source/Destination Address, TCP/UDP Source/Destination port
- 96 ACL Mask Rule for Pass/Drop, VLAN/Q.O.S./DSCP Mapping/Translation
- User define ACL up to 48 bytes depth in Layer 4/3/2
- Q.O.S mechanisms include Weight Round Robin, Strict, Hybrid Up Queue
- Port Base VLAN & 4K 802.1Q VLAN Group
- IVL & SVL
- IGMP Snooping V1, V2 & V3. IPv6 MLD V1/V2 forwarded to CPU
- Supports Light Hardware IGMP snooping v1/v2/v3, MLDv1/v2 and Smart Leave
- Hardware Looping Detection
- QinQ function for SVLAN & CVLAN Translation
- IP Packet/PPPoE bypass to reduce CPU loading on Video packet
- 16 PPPoE session support/PPP Session Header Removal/Addition
- Scalable Ingress/Egress Bandwidth Control
- 40 MIBs Counter/Port & Port Status.
- 1M Bit Packet Buffer
- Supports 9K Jumbo Frame
- Port Mirror, 802.1X Security, Rapid Spanning Tree
- Rule-based Bandwidth Control
- Programmable Wake on LAN
- Half Power Mode for Cable length less than 30m (for home installations)
- Supports Internal/External Loopback
- Supports Reduced AFE circuit
- 2K MAC Table. Edit, Search, Add & Delete.
- MAC Limit by Port/Chip/VLAN
- Trunking Function
- Supports Trunking and auto-failover
- Power Saving on Cable no Link, short Cable & 10BASE-Te Idle
- Supports 1K NAPT entries and 128 hardware based host routing (ARP) entries
- Supports hardware-based IP source guard, ARP inspection, routing/L3 switching
- Supports VLAN translation and mapping with 64 Translation entries
What's new in 6.38rc7 (2016-Sep-30 07:33):
!) switch - added hardware stp functionality for CRS devices (http://wiki.mikrotik.com/wiki/Manual:CR ... e_Protocol);
I wondered about the performance impacts as well, but optimistically suspect they are just using that as a location in the interface rather than actually putting the master port in a bridge behind the scenes. I partially think this because just adding it to a bridge wouldn't provide the information necessary to make port blocking decisions. I have yet to install it in a lab environment and do any benchmarking or testing though. My post was more to notify those interested that they are finally working on this and get everyone involved in influencing the development.Well, that's promising, but I'm not going to run RC firmware on my production network. Since it appears to require adding your master ports to a bridge to enable the switch-chip functionality, I wonder what the performance impact will be on the CRS CPU as a result of implementing STP.