Difference between revisions of "SwOS"

From MikroTik Wiki
Jump to navigation Jump to search
(corrected at least 11 grammar mistakes in one sentence :D)
 
(→‎VLANs Tab: RB260GS Vlans tab)
(44 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{...}}
==Summary==
==Summary==
<p>
<p>
Line 40: Line 38:
* <b>Reboot</b> - reboot the switch
* <b>Reboot</b> - reboot the switch
* <b>Reset Configuration</b> - reset configuration back to factory defaults
* <b>Reset Configuration</b> - reset configuration back to factory defaults
* <b>Choose File</b> - browse for upgrade file
* <b>Choose File</b> - browse for upgrade or backup file
* <b>Upgrade</b> - upgrade firmware of the Switch
* <b>Upgrade</b> - upgrade firmware of the Switch
* <b>Restore Backup</b> - restore Switch using selected backup file
* <b>Save Backup</b> - generate and download backup file from the Switch
</p>
</p>


Line 52: Line 52:
* Switch management
* Switch management
* Configuration reset
* Configuration reset
* Backup and restore configuration
* Firmware upgrade</p>
* Firmware upgrade</p>


Line 63: Line 64:
</tr>
</tr>
<tr>
<tr>
     <td><b>Identity</b></td><td>Name of the Switch (for MikroTik neighbor discovery protocol)</td>
     <td><b>Identity</b></td><td>Name of the Switch (for Mikrotik neighbor discovery protocol)</td>
</tr>
</tr>
<tr>
<tr>
     <td><b>Allow From</b></td><td>IP address from which the service is accessible. Default value is '0.0.0.0/0' - any address.
     <td><b>Allow From</b></td><td>IP address from which the service is accessible. Default value is '0.0.0.0/0' - any address
</td>
</td>
</tr>
<tr>
    <td><b>Allow From Ports</b></td><td>List of switch ports from which the service is accessible
</td>
</tr>
<tr>
    <td><b>Allow From VLAN</b></td><td>VLAN ID with which  the service is accessible (VLAN Mode on ingress port must be other than <code>'''disabled''' </code>in order to connect)
</td>
</tr>
<tr>
    <td><b>Mikrotik Discovery Protocol</b></td><td>Enable or disable Mikrotik neighbor discovery protocol</td>
</tr>
</tr>
<tr>
<tr>
Line 85: Line 97:


{{ Note | SwOS uses a simple algorithm to ensure TCP/IP communication - it just replies to the same IP and MAC address packet came from. This way there is no need for Default Gateway on the device itself.}}
{{ Note | SwOS uses a simple algorithm to ensure TCP/IP communication - it just replies to the same IP and MAC address packet came from. This way there is no need for Default Gateway on the device itself.}}
===Firmware Upgrade===
<p>Firmware can be upgraded/downgraded by selecting firmware file and pressing upgrade button. Switch will reboot automatically after successful upgrade.</p>
{{ Note | Manual power cycle is necessary 5 seconds after upgrade button is pressed if you are upgrading from SwOS v1.0}}


==Link Tab==
==Link Tab==
<div>
 
<div style="float: left">
[[File:swos_link.png|345px|thumb]]
 
<p>Link Tab allows you to:
<p>Link Tab allows you to:
* Configure Ethernet ports
* Configure Ethernet ports
* Monitor status of Ethernet ports</p>
* Monitor status of Ethernet ports</p>
</div>
<div style="float: right;">
[[File:swos_link.png|345px|]]
</div>
</div>


<table class="styled_table" >
<table class="styled_table" >
Line 117: Line 131:
<tr>
<tr>
     <td><b>Full Duplex</b></td><td>Specify duplex mode of the port (requires auto negotiation to be disabled to specify)</td>
     <td><b>Full Duplex</b></td><td>Specify duplex mode of the port (requires auto negotiation to be disabled to specify)</td>
</tr>
<tr>
    <td><b>Crossover</b></td><td>Detect crossover cable (Read-only)</td>
</tr>
</tr>
<tr>
<tr>
Line 127: Line 138:


==Forwarding Tab==
==Forwarding Tab==
<div>
 
<div style="float: left;width: 385px">
[[File:swos_forwarding.png|345px|thumb]]
 
<p>Forwarding Tab provides advanced forwarding options among switch ports, port locking, port mirroring, bandwidth limit and broadcast storm control features. </p>
<p>Forwarding Tab provides advanced forwarding options among switch ports, port locking, port mirroring, bandwidth limit and broadcast storm control features. </p>
</div>
<div style="float: right">
[[File:swos_forwarding.png|345px|]]
</div>
</div>


<table class="styled_table" >
<table class="styled_table" >
Line 152: Line 159:
     <td><b>Port Mirroring</b></td><td>
     <td><b>Port Mirroring</b></td><td>
* <code><b>Mirror Ingress</b></code> - Whether traffic entering this port must be copied and forwarded to mirroring target port
* <code><b>Mirror Ingress</b></code> - Whether traffic entering this port must be copied and forwarded to mirroring target port
* <code><b>Mirror Outgress</b></code> - Whether traffic leaving this port must be copied and forwarded to mirroring target port
* <code><b>Mirror Egress</b></code> - Whether traffic leaving this port must be copied and forwarded to mirroring target port
* <code><b>Mirror To</b></code> - Mirroring target port</td>
* <code><b>Mirror To</b></code> - Mirroring target port</td>
</tr>
</tr>
Line 158: Line 165:
     <td><b>Bandwidth Limit</b></td><td>
     <td><b>Bandwidth Limit</b></td><td>
* <code><b>Ingres Rate</b></code> -  Limit traffic entering this port (bps)
* <code><b>Ingres Rate</b></code> -  Limit traffic entering this port (bps)
* <code><b>Outgres Rate</b></code> - Limit traffic leaving this port (bps)</td>
* <code><b>Egress Rate</b></code> - Limit traffic leaving this port (bps)</td>
</tr>
</tr>
<tr>
<tr>
     <td><b>Broadcast Storm Control</b></td><td>
     <td><b>Broadcast Storm Control</b></td><td>
* <code><b>Storm Rate</b></code> -  Limit the number of broadcast packets sent by an interface
* <code><b>Storm Rate</b></code> -  Limit the number of broadcast packets transmitted by an interface


* <code><b>Include Unicast</b></code> - Include unicast packets without an entry in host table in <code>Storm Rate</code> limitation</td>
* <code><b>Include Unicast</b></code> - Include unicast packets without an entry in host table in <code>Storm Rate</code> limitation</td>
Line 169: Line 176:


==Statistics Tab==
==Statistics Tab==
<div>
 
<div style="float: left;width:385px">
[[File:swos_statistics.png|345px|thumb]]
 
<p>Provides detailed information about received and transmitted packets.</p>
<p>Provides detailed information about received and transmitted packets.</p>
</div>
 
<div style="float: right;">
<div style="clear:both;"></div>
[[File:swos_statistics.png|345px|]]
 
</div>
==Packet Flow==
</div>
 
<div style="clear: both;"></div>
Packet processing through RB250GS is described here: [http://wiki.mikrotik.com/wiki/Manual:Packet_flow_through_Atheros8316 Atheros8316 packet flow diagram]


==VLAN Tab==
==VLAN Tab==
<div>
 
<div style="float: left;width:385px;">
[[File:swos_vlan.png|345px|thumb]]
 
<p>VLAN configuration for Switch ports.</p>
<p>VLAN configuration for Switch ports.</p>
</div>
 
<div style="float: right;">
[[File:swos_vlan.png|345px|]]
</div>
</div>


<table class="styled_table" >
<table class="styled_table" >
Line 196: Line 201:
<tr>
<tr>
     <td><b>VLAN Mode</b></td><td>
     <td><b>VLAN Mode</b></td><td>
VLAN mode for certain port:
VLAN mode for ingress port:
* <code><b>disabled</b></code> - Ignore VLAN table,  treat packet with VLAN tags just as if they did not contain a VLAN tag
* <code><b>disabled</b></code> - VLAN table is not used. Switch ignores VLAN tag part of tagged packets
* <code><b>optional</b></code> - Handle packets with VLAN tag that is not present in VLAN table just like packets without VLAN tag
* <code><b>optional</b></code> - Handle packets with VLAN tag ID that is not present in VLAN table just like packets without VLAN tag
* <code><b>enabled</b></code> - Drop packets with VLAN tag that is not present in VLAN table. Packets without VLAN tag are treat as tagged packets with <code>Default VLAN ID</code>
* <code><b>enabled</b></code> - Drop packets with VLAN tag ID that is not present in VLAN table. Packets without VLAN tag are treat as tagged packets with <code>Default VLAN ID</code>
* <code><b>strict</b></code> - Same as <code>enable</code>, but also checks VLAN support for inbound interface (drop packets with VLAN tag and ingress port that are not present in VLAN table)
* <code><b>strict</b></code> - Same as <code>enable</code>, but also checks VLAN support for inbound interface (drop packets with VLAN tag ID and ingress port that are not present in VLAN table)
</td>
</td>
</tr>
</tr>
<tr>
<tr>
     <td><b>Default VLAN ID</b></td><td>VLAN ID for untagged packets when <code>VLAN Mode</code> "<code>enabled</code>" or "<code>strict</code>" is used</td>
     <td><b>Default VLAN ID</b></td><td>Switch will treat untagged ingress packets as they are tagged with this VLAN ID. VLAN tag itself will be added only if there is <code>VLAN Header = add if missing</code> specified on egress port</td>
</tr>
</tr>
<tr>
<tr>
Line 217: Line 222:
</tr>
</tr>
</table>
</table>
===Example===
*[http://wiki.mikrotik.com/wiki/SwOS/Router-On-A-Stick  802.1Q Trunk]
*[http://wiki.mikrotik.com/wiki/SwOS/SWOS-802.1Q-TrunkTwoSwitches 802.1Q Trunk with two switches]


==VLANs Tab==
==VLANs Tab==
<div>
 
<div style="float: left;width:385px;">
[[File:swos_vlans.png|345px|thumb]]
<p>VLAN tables specifies certain forwarding rules for packets that have specific 802.1q tag. Basically the table contains entries that map specific vlan tag ids to a group of one or more ports. Packets with vlan tags leave switch through one or more ports that are set in corresponding table entry</p>
 
</div>
<p>VLAN tables specifies certain forwarding rules for packets that have specific 802.1q tag. Basically the table contains entries that map specific VLAN tag IDs to a group of one or more ports. Packets with VLAN tags leave switch through one or more ports that are set in corresponding table entry. VLAN table works together with destination MAC lookup to determine egress ports. VLAN table supports up to 4096 entries.</p>
<div style="float: right;">
 
[[File:swos_vlans.png|345px|]]
<h4>RB250GS VLANs tab</h4>
</div>
</div>


<table class="styled_table" >
<table class="styled_table" >
Line 238: Line 246:
<tr>
<tr>
     <td><b>Ports</b></td><td>Ports the packet should be mapped to</td>
     <td><b>Ports</b></td><td>Ports the packet should be mapped to</td>
</tr>
</table>
<h4>RB260GS VLANs tab</h4>
<table class="styled_table" >
<tr>
  <th width="25%">Property</th>
  <th >Description</th>
</tr>
<tr>
    <td><b>VLAN ID</b></td><td>VLAN ID of the packet</td>
</tr>
<tr>
    <td><b>Ports</b></td><td>Each port has individual ''VLAN header'' options for each VLAN ID. Depending on ''VLAN mode'' if lookup is done in this table, egress action of packets is processed by this option. Egress option from '''VLAN tab''' is ignored.</td>
</tr>
</tr>
</table>
</table>


==Hosts Tab==
==Hosts Tab==
<div>
 
<div style="float: left;width:380px;">
[[File:swos_hosts.png|345px|thumb]]
 
<p>This table represents dynamically learnt MAC address to port mapping entries. When Switch receives a packet from certain port, it adds the packets source MAC address X and port it received the packet from to host table, so when a packet comes in with destination MAC address X it knows to which port it should forward the packet. If the destination MAC address is not present in host table then it forwards the packet to all ports in the group. Dynamic entries take about 5 minutes to time out.</p>
<p>This table represents dynamically learnt MAC address to port mapping entries. When Switch receives a packet from certain port, it adds the packets source MAC address X and port it received the packet from to host table, so when a packet comes in with destination MAC address X it knows to which port it should forward the packet. If the destination MAC address is not present in host table then it forwards the packet to all ports in the group. Dynamic entries take about 5 minutes to time out.</p>
</div>
 
<div style="float: right;">
<div style="clear:both;"></div>
[[File:swos_hosts.png|345px|]]
 
</div>
{{ Note | RB250GS supports 2k host table entries.  }}
</div>


<table class="styled_table" >
<table class="styled_table" >
Line 265: Line 288:


==Static Hosts Tab==
==Static Hosts Tab==
<div>
 
<div style="float: left;width:385px">
[[File:swos_static_hosts.png|345px|thumb]]
 
<p>Static host table entries. Static entries will take over dynamic if dynamic entry with same mac-address already exists. Also by adding a static entry you get access to some more functionality.</p>
<p>Static host table entries. Static entries will take over dynamic if dynamic entry with same mac-address already exists. Also by adding a static entry you get access to some more functionality.</p>
</div>
<div style="float: right;">
[[File:swos_static_hosts.png|345px|]]
</div>
</div>


<table class="styled_table" >
<table class="styled_table" >
Line 287: Line 305:
</tr>
</tr>
<tr>
<tr>
     <td><b>Drop</b></td><td>Packet can be cloned and sent to mirror-target port</td>
     <td><b>Mirror</b></td><td>Packet can be cloned and sent to mirror-target port</td>
</tr>
</tr>
<tr>
<tr>
     <td><b>Mirror</b></td><td>Packet with certain MAC address coming from certain ports can be dropped</td>
     <td><b>Drop</b></td><td>Packet with certain MAC address coming from certain ports can be dropped</td>
</tr>
</tr>
</table>
</table>


==ACL Tab==
==ACL Tab==
<div>
 
<div style="float: left;width:385px">
[[File:swos_acl.png|345px|thumb]]
<p>An access control list (ACL) rule table is very powerful tool allowing wire speed packet filtering, forwarding and vlan tagging based on L2,L3 protocol header field matchers.  SwOS allow you to implement limited number of access control list rules (32 simple rules (either L2 or L3 matchers are used) or 16 complex rules (both L2 and L3 matchers are used)).
 
<p>An access control list (ACL) rule table is very powerful tool allowing wire speed packet filtering, forwarding and VLAN tagging based on L2,L3 protocol header field conditions.  SwOS allow you to implement limited number of access control list rules (32 simple rules (only L2 conditions are used); 16 rules where both L2 and L3 conditions are used; or 8 advanced rules where all L2,L3 and L4 conditions are used).
</p>
</p>


<p>Each rule contains a matching part and an action part.</p>
<p>Each rule contains a conditions part and an action part.</p>
</div>
 
<div style="float: right;">
<div style="clear:both"></div>
[[File:swos_acl.png|345px|]]
</div>
</div>
<div style="clear:both;"></div>


<h3>Matching part parameters</h3>
<h3>Conditions part parameters</h3>


<table class="styled_table" >
<table class="styled_table" >
Line 316: Line 331:
</tr>
</tr>
<tr>
<tr>
     <td><b>From</b></td><td>Match port that packet came in from</td>
     <td><b>From</b></td><td>Port that packet came in from</td>
</tr>
</tr>
<tr>
<tr>
     <td><b>MAC Src</b></td><td>Match by source MAC address and mask</td>
     <td><b>MAC Src</b></td><td>Source MAC address and mask</td>
</tr>
</tr>
<tr>
<tr>
     <td><b>MAC Dst</b></td><td>Match by destination MAC address and mask</td>
     <td><b>MAC Dst</b></td><td>Destination MAC address and mask</td>
</tr>
</tr>
<tr>
<tr>
     <td><b>Ethertype</b></td><td>Match by protocol encapsulated in the payload of an Ethernet Frame</td>
     <td><b>Ethertype</b></td><td>Protocol encapsulated in the payload of an Ethernet Frame</td>
</tr>
</tr>
<tr>
<tr>
     <td><b>VLAN</b></td><td>
     <td><b>VLAN</b></td><td>
Match by VLAN header presence:
VLAN header presence:
* any
* any
* present
* present
Line 335: Line 350:
</tr>
</tr>
<tr>
<tr>
     <td><b>VLAN ID</b></td><td>Match by VLAN tag ID</td>
     <td><b>VLAN ID</b></td><td>VLAN tag ID</td>
</tr>
</tr>
<tr>
<tr>
     <td><b>Priority</b></td><td>Match by priority in VLAN tag</td>
     <td><b>Priority</b></td><td>Priority in VLAN tag</td>
</tr>
</tr>
<tr>
<tr>
     <td><b>IP Src</b></td><td>Match by source IP address and mask</td>
     <td><b>IP Src</b> (IP/netmask:port)</td><td>Source IP address, netmask and L4 port number</td>
</tr>
</tr>
<tr>
<tr>
     <td><b>IP Dst</b></td><td>Match by destination IP address and mask</td>
     <td><b>IP Dst</b> (IP/netmask:port)</td><td>Destination IP address, netmask and L4 port number</td>
</tr>
</tr>
<tr>
<tr>
     <td><b>Protocol</b></td><td>Match by IP protocol</td>
     <td><b>Protocol</b></td><td>IP protocol</td>
</tr>
</tr>
<tr>
<tr>
     <td><b>DSCP</b></td><td>Match by IP DSCP field</td>
     <td><b>DSCP</b></td><td>IP DSCP field</td>
</tr>
</tr>
</table>
</table>
Line 368: Line 383:
</tr>
</tr>
<tr>
<tr>
     <td><b>Mirror</b></td><td>Clones matching packets and send them to mirror-target port</td>
     <td><b>Mirror</b></td><td>Clones packet and sends it to mirror-target port</td>
</tr>
</tr>
<tr>
<tr>
     <td><b>Set VLAN ID</b></td><td>Changes the VLAN tag id, if VLAN tag is present</td>
     <td><b>Set VLAN ID</b></td><td>Changes the VLAN tag ID, if VLAN tag is present</td>
</tr>
</tr>
<tr>
<tr>
     <td><b>Priority</b></td><td>Changes the vlan tag priority bits, if VLAN tag is present</td>
     <td><b>Priority</b></td><td>Changes the VLAN tag priority bits, if VLAN tag is present</td>
</tr>
</tr>
</table>
</table>
<div style="clear:both"></div>


==SNMP Tab==
==SNMP Tab==


<div>
[[File:swos_snmp.png|345px|thumb]]
<div style="float: left">


<p>SNMP Tab consists of settings to monitor the Switch remotely.</p>
<p>SNMP Tab consists of settings to monitor the Switch remotely.</p>
</div>
<div style="float: right;">
[[File:swos_snmp.png|345px|]]
</div>
</div>


<table class="styled_table" >
<table class="styled_table" >
Line 409: Line 421:
</tr>
</tr>
</table>
</table>
==Reinstall SwOS firmware==
<p>It is possible to upload and install SwOS firmware on RB250GS using BOOTP. This example shows how to reinstall SwOS using RouterOS.</p>
* Configure IP address and DHCP server with BOOTP enabled on the installation router.
<pre>/ip address
add address=192.168.88.254/24 interface=ether1
</pre>
<pre>/ip pool
add name=dhcp_pool1 ranges=192.168.88.1
/ip dhcp-server
add address-pool=dhcp_pool1 bootp-support=dynamic interface=ether1 disabled=no
/ip dhcp-server network
add address=192.168.88.0/24 gateway=192.168.88.254
</pre>
*Upload new SwOS firmware file to the router filesystem.
<pre>[admin@MikroTik] /file> print
# NAME            TYPE            SIZE                CREATION-TIME     
0 swos-1.2.lzb    .lzb file        38142                sep/02/2010 08:40:17</pre>
* Configure TFTP server.
<pre>/ip tftp
add allow=yes disabled=no ip-addresses=192.168.88.1 read-only=yes \
    real-filename=swos-1.2.lzb</pre>
* Hold the RESET button of the switch when starting it.
* After few seconds ACT LED will start blinking. Wait till ACT LED blinks twice as fast and release RESET button.
* Make ethernet connection between the switch and ethernet port you configured DHCP server on. After few seconds new firmware should be successfully uploaded and installed.

Revision as of 07:48, 15 March 2013

Summary

SwOS is an operating system designed specifically for administration of MikroTik Switch products.

SwOS is configurable from your web browser. It gives you all the basic functionality for a managed switch, plus more: Allows to manage port-to-port forwarding, broadcast storm control, apply MAC filter, configure VLANs, mirror traffic, apply bandwidth limitation and even adjust some MAC and IP header fields.

Connecting to the Switch

Open your web browser and enter IP address of your Switch (192.168.88.1 by default) and login screen will appear.

Swos login.png

SwOS default IP address: 192.168.88.1, user name: admin and there is no password.

Icon-note.png

Note: MikroTik neighbor discovery protocol tools can be used to discover IP address of Mikrotik Switch. Manual:IP/Neighbor_discovery


Interface Overview

SwOS interface menu consists of 10 tabs: Link, Forwarding, Statistics, VLAN, VLANs, Static Hosts, Hosts, SNMP, ACL and System.

Description of buttons in SwOS configuration tool:

  • Append - add new item to the end of the list
  • Apply All - applies current configuration changes
  • Cut - removes item from the list
  • Clear - resets properties of the item
  • Discard Changes - removes unsaved configuration
  • Insert - add new item to the list (places it before current item)
  • Sort - sort VLAN table by VLAN-IDs; sort host table by MAC addresses


  • Change Password - changes password of the switch
  • Logout - logout from current Switch
  • Reboot - reboot the switch
  • Reset Configuration - reset configuration back to factory defaults
  • Choose File - browse for upgrade or backup file
  • Upgrade - upgrade firmware of the Switch
  • Restore Backup - restore Switch using selected backup file
  • Save Backup - generate and download backup file from the Switch

System Tab

System Tab performs the following functions:

  • General information about Switch
  • Switch management
  • Configuration reset
  • Backup and restore configuration
  • Firmware upgrade

Property Description
IP AddressIP address of the Switch
IdentityName of the Switch (for Mikrotik neighbor discovery protocol)
Allow FromIP address from which the service is accessible. Default value is '0.0.0.0/0' - any address
Allow From PortsList of switch ports from which the service is accessible
Allow From VLANVLAN ID with which the service is accessible (VLAN Mode on ingress port must be other than disabled in order to connect)
Mikrotik Discovery ProtocolEnable or disable Mikrotik neighbor discovery protocol
WatchdogEnable or disable system watchdog. It will reset CPU of the switch in case of fault condition
MAC AddressMAC address of the Switch (Read-only)
VersionFirmware version of the Switch
UptimeCurrent Switch uptime


Icon-note.png

Note: SwOS uses a simple algorithm to ensure TCP/IP communication - it just replies to the same IP and MAC address packet came from. This way there is no need for Default Gateway on the device itself.


Firmware Upgrade

Firmware can be upgraded/downgraded by selecting firmware file and pressing upgrade button. Switch will reboot automatically after successful upgrade.

Icon-note.png

Note: Manual power cycle is necessary 5 seconds after upgrade button is pressed if you are upgrading from SwOS v1.0


Link Tab

Link Tab allows you to:

  • Configure Ethernet ports
  • Monitor status of Ethernet ports

Property Description
EnabledEnable or disable port
Link StatusCurrent link status (Read-only)
Auto NegotiationEnable or disable auto negotiation
SpeedSpecify speed setting of the port (requires auto negotiation to be disabled to specify)
Full DuplexSpecify duplex mode of the port (requires auto negotiation to be disabled to specify)
Flow control Enable or disable flow control

Forwarding Tab

Forwarding Tab provides advanced forwarding options among switch ports, port locking, port mirroring, bandwidth limit and broadcast storm control features.

Property Description
ForwardingForwarding table - allows or restricts traffic flow between specific ports
Port Lock
  • Port Lock - Enable or disable MAC address learning on this port
  • Lock On First - Enable or disable MAC address learning on this port (MAC address from the first recieved packet will still be learnt)
Port Mirroring
  • Mirror Ingress - Whether traffic entering this port must be copied and forwarded to mirroring target port
  • Mirror Egress - Whether traffic leaving this port must be copied and forwarded to mirroring target port
  • Mirror To - Mirroring target port
Bandwidth Limit
  • Ingres Rate - Limit traffic entering this port (bps)
  • Egress Rate - Limit traffic leaving this port (bps)
Broadcast Storm Control
  • Storm Rate - Limit the number of broadcast packets transmitted by an interface
  • Include Unicast - Include unicast packets without an entry in host table in Storm Rate limitation

Statistics Tab

Provides detailed information about received and transmitted packets.

Packet Flow

Packet processing through RB250GS is described here: Atheros8316 packet flow diagram

VLAN Tab

VLAN configuration for Switch ports.


Property Description
VLAN Mode

VLAN mode for ingress port:

  • disabled - VLAN table is not used. Switch ignores VLAN tag part of tagged packets
  • optional - Handle packets with VLAN tag ID that is not present in VLAN table just like packets without VLAN tag
  • enabled - Drop packets with VLAN tag ID that is not present in VLAN table. Packets without VLAN tag are treat as tagged packets with Default VLAN ID
  • strict - Same as enable, but also checks VLAN support for inbound interface (drop packets with VLAN tag ID and ingress port that are not present in VLAN table)
Default VLAN IDSwitch will treat untagged ingress packets as they are tagged with this VLAN ID. VLAN tag itself will be added only if there is VLAN Header = add if missing specified on egress port
Force VLAN IDWhether to apply Default VLAN ID to incoming packets with VLAN tag
VLAN Header
  • leave as is - if VLAN header is present it remains unchanged
  • always strip - if VLAN header is present it is removed from the packet
  • add if missing - if VLAN header is not present it is added to the packet (VLAN ID will be Default VLAN ID of ingress port)

Example

VLANs Tab

VLAN tables specifies certain forwarding rules for packets that have specific 802.1q tag. Basically the table contains entries that map specific VLAN tag IDs to a group of one or more ports. Packets with VLAN tags leave switch through one or more ports that are set in corresponding table entry. VLAN table works together with destination MAC lookup to determine egress ports. VLAN table supports up to 4096 entries.

RB250GS VLANs tab

Property Description
VLAN IDVLAN ID of the packet
PortsPorts the packet should be mapped to

RB260GS VLANs tab

Property Description
VLAN IDVLAN ID of the packet
PortsEach port has individual VLAN header options for each VLAN ID. Depending on VLAN mode if lookup is done in this table, egress action of packets is processed by this option. Egress option from VLAN tab is ignored.

Hosts Tab

This table represents dynamically learnt MAC address to port mapping entries. When Switch receives a packet from certain port, it adds the packets source MAC address X and port it received the packet from to host table, so when a packet comes in with destination MAC address X it knows to which port it should forward the packet. If the destination MAC address is not present in host table then it forwards the packet to all ports in the group. Dynamic entries take about 5 minutes to time out.

Icon-note.png

Note: RB250GS supports 2k host table entries.


Property Description
MACMAC address (Read-only)
PortsPorts the packet should be forwarded to (Read-only)

Static Hosts Tab

Static host table entries. Static entries will take over dynamic if dynamic entry with same mac-address already exists. Also by adding a static entry you get access to some more functionality.

Property Description
MACMAC address
PortsPorts the packet should be forwarded to
MirrorPacket can be cloned and sent to mirror-target port
DropPacket with certain MAC address coming from certain ports can be dropped

ACL Tab

An access control list (ACL) rule table is very powerful tool allowing wire speed packet filtering, forwarding and VLAN tagging based on L2,L3 protocol header field conditions. SwOS allow you to implement limited number of access control list rules (32 simple rules (only L2 conditions are used); 16 rules where both L2 and L3 conditions are used; or 8 advanced rules where all L2,L3 and L4 conditions are used).

Each rule contains a conditions part and an action part.

Conditions part parameters

Property Description
FromPort that packet came in from
MAC SrcSource MAC address and mask
MAC DstDestination MAC address and mask
EthertypeProtocol encapsulated in the payload of an Ethernet Frame
VLAN

VLAN header presence:

  • any
  • present
  • not present
VLAN IDVLAN tag ID
PriorityPriority in VLAN tag
IP Src (IP/netmask:port)Source IP address, netmask and L4 port number
IP Dst (IP/netmask:port)Destination IP address, netmask and L4 port number
ProtocolIP protocol
DSCPIP DSCP field

Action part parameters

Property Description
Redirect ToWhether to force new destination ports (If Redirect To is enabled and no ports specified in Redirect To Ports, packet will be dropped )
Redirect To PortsDestination ports for
MirrorClones packet and sends it to mirror-target port
Set VLAN IDChanges the VLAN tag ID, if VLAN tag is present
PriorityChanges the VLAN tag priority bits, if VLAN tag is present


SNMP Tab

SNMP Tab consists of settings to monitor the Switch remotely.

Property Description
EnabledEnable or disable SNMP service
CommunitySNMP community name
Contact InfoContact information for the NMS
LocationLocation information for the NMS

Reinstall SwOS firmware

It is possible to upload and install SwOS firmware on RB250GS using BOOTP. This example shows how to reinstall SwOS using RouterOS.


  • Configure IP address and DHCP server with BOOTP enabled on the installation router.
/ip address
add address=192.168.88.254/24 interface=ether1
/ip pool
add name=dhcp_pool1 ranges=192.168.88.1
/ip dhcp-server
add address-pool=dhcp_pool1 bootp-support=dynamic interface=ether1 disabled=no
/ip dhcp-server network
add address=192.168.88.0/24 gateway=192.168.88.254
  • Upload new SwOS firmware file to the router filesystem.
[admin@MikroTik] /file> print 
 # NAME             TYPE             SIZE                 CREATION-TIME       
 0 swos-1.2.lzb     .lzb file        38142                sep/02/2010 08:40:17
  • Configure TFTP server.
/ip tftp
add allow=yes disabled=no ip-addresses=192.168.88.1 read-only=yes \
    real-filename=swos-1.2.lzb
  • Hold the RESET button of the switch when starting it.
  • After few seconds ACT LED will start blinking. Wait till ACT LED blinks twice as fast and release RESET button.
  • Make ethernet connection between the switch and ethernet port you configured DHCP server on. After few seconds new firmware should be successfully uploaded and installed.