You can select an uplink port on the "Forwarding" page. This selected port can talk to the other two ports, while two non-uplink ports are isolated from each other.*) GPEN21: allow to select up-link port;
What does that mean? Can we now use all 3 ports independently?
Can confirm, autonegotiated 10G link seems to work fine with Intel's X520 (82599ES). Only tried it for about an hour, but it seems to be stable.Can anybody confirm if this fixes the link issues with Intel SFP NIC's? Currently on 2.13 release candidate for that to work as 2.13 final could not link.
~# snmpwalk -v2c -c public 192.168.88.1 220.127.116.11.4.1.14918.104.22.168 iso.22.214.171.124.1.149126.96.36.199.188.8.131.52 = STRING: "SFP1" iso.184.108.40.206.1.149220.127.116.11.18.104.22.168 = Gauge32: 0 iso.22.214.171.124.1.149126.96.36.199.188.8.131.52 = Gauge32: 65408 iso.184.108.40.206.1.149220.127.116.11.18.104.22.168 = Gauge32: 0 iso.22.214.171.124.1.149126.96.36.199.188.8.131.52 = Gauge32: 0 iso.184.108.40.206.1.149220.127.116.11.18.104.22.168 = No more variables left in this MIB View (It is past the end of the MIB tree)
+1some confirmation on "Reset Configuration" button can help...
Is near to "Save Backup" and do not ask for confirmation...
There is no option to configure the IGMP querier version, we will see if this option can be added in the next release. Also, there is no option to disable the querier, but the switch will stop sending queries in case another querier is detected. As for the 0.0.0.0 querier address, this is a special case querier address that should not affect the querier election, the multicast routers and IGMP proxy should ignore such packets.SwOS Lite 2.14 acts as igmp querier using IGMPv3 when igmp-snooping is turned on. You can't change the igmp version being used nor can you turn off the querier function.
What makes things worse, it sends out these igmp reports using 0.0.0.0, since it has no IP Address other than on the management vlan.
Because of the low ip address, it wins every querier election and ultimately breaks multicast, where a L3 device needs to be the querier for PIM / igmp-proxy to work correctly.
Please add the option to enable igmp-snooping together with no-querier and let users select on which vlans they want to use this feature including the igmp version.
Thanks for sharing this, hope to include the Tx/Rx power values for SNMP in the next release.The values for SFP RX Power and SFP TX Power are not given (even though listed in Mikrotiks MIB), but shown on the Web Interface.
Thanks for reporting, please share the details about used SFP modules to support if not already.As of release 2.14 GPEN21 and maybe others won't auto negotiate correctly with certain generic lasers in them.
As for the 0.0.0.0 querier address, this is a special case querier address that should not affect the querier election, the multicast routers and IGMP proxy should ignore such packets.
I'm having the same issue with my CSS610's, IGMP Snooping is basically broken.Nice work, osc86! I got the same results in our lab, will try to find some solution. No need for a support ticket.
We need a fix for SFP negotiation now.
As of release 2.14 GPEN21 and maybe others won't auto negotiate correctly with certain generic lasers in them.
Using a very old 20km Mikrotik branded laser works.
Using 2.13 version works with any laser.
Using 2.14 does NOT work with just about any laser we have tried.
We've had to resort to setting it all to static 1Gbps FDX link on BOTH the switch port on the other side and the GPEN21.
Please fix asap!
This would be awesome, especially on the configuration side like a Netonix in the aspectAny update about SFP(+) compatibility fixes?
Running 2.13 and it works, afraid to upgrade to 2.14 especially if remote access is over fiber connection that might break.
The devices really should have a dual firmware feature - upgrade, reboot and login to confirm (within a timeout) the new firmware is working properly, if timeout (like 10 minutes or so) passes without anyone login and confirm, then reboot back to the old version. The same should also apply to any configuration changes that might result in loss of remote access.
/ipv6 neighbor print
/interface bridge set 0 igmp-snooping=yes multicast-router=permanent multicast-querier=no