Discard Changes - removes unsaved configuration.Apply All - applies current configuration changes.Append - add new item to the end of the list.Currently LLDP is not supported.ĬSS326-24G-2S+ SwOS interface menu consists of multiple tabs: Link, SFP, SFP Status, Port Isolation, LAG, Forwarding, Stats, Errors, Histogram, VLAN, VLANs, Static Hosts, Hosts, SNMP, ACL, System and Upgrade.ĭescription of buttons in SwOS configuration tool: Note: MikroTik Neighbor Discovery protocol tools can be used to discover IP address of Mikrotik switch. Open your web browser and enter IP address of your Switch (192.168.88.1 by default) and login screen will appear. ACL actions include filtering, forwarding and modifying of the protocol header fields.Classification based on ports, L2, 元, L4 protocol header fields.Up to 250 VLAN entries (limited by SwOS).Hardware automatic failover and load balancing.Supports static link aggregation groups.Forwarding Database works based on SVL or IVL.Untagged is wanted, that's how it is configured now.Warning: Each RouterBOARD switch series device has its own firmware which cannot be installed on other series models! CSS326-24G-2S+ supports SwOS v2.0 and newer. Played with the VLAN settings on both sides. I'm missing that a number in "trunk" shows up (which should happen, according to Youtube videos explaning SwOS). Set the mode to "active", since pfSense speaks passive. tik-switchĬould someone verify my SwOS config and tell me if something is missing? User traffic sadly doesn't go through this link. As soon as I attach my pfSense to a Switchport, I can see that a neighbor is seen and the link gets up (Partner MAC of the correct pfSense interface is shown). On the pfSense side, everything was configured to get LACP working. For testing purposed, I'm trying to get this up and running with one port only (Port 16, see screenshots below).
The uplink to the pfSense should remain untagged without any VLANs being tagged. I'm using a pfSense firewall which I want to connect to my CRS326 Switch (running SwOS) via LACP. If this is not the case, your LAGG did not form. Important: The LAGG only formed as soon as you see a trunk member number. An exception might be a static configured LAGG where a trunk is entered manually (Not tested). Dynamic LACP needs at least two physical links to form a LAGG via SwOS.
0 kommentar(er)
