Recently I get a hEX, I am trying to use it as switch as my current room switch (TP-LINK TL-ST5008Fv1) does not have ethernet port.
When I am trying to set the hEX following the wiki, I find a strange problem
I have to set the Frame Type to admit-all, otherwise, the CRS305 will be disconnected and the logging show
17:44:31 bridge,stp sfp-sfpplus2 (Room) discarding
17:44:31 route,debug,event Interface change
17:44:31 route,debug,event interface=sfp-sfpplus2 (Room)
17:44:31 route,debug,event status=UP,RUNNING
17:44:31 route,debug,event mtu=9000
17:44:31 route,debug,calc Begin calculation
17:44:31 route,debug,calc End calculation
17:44:32 bridge,stp sfp-sfpplus2 (Room) learning
17:44:33 bridge,stp sfp-sfpplus2 (Room) discarding
The interface bridge,stp sfp-sfpplus2 (Room) is in [learning discarding] loop
In my understanding, I should set the Frame Type to admit-only-vlan-tagged
What is the problem?
99.99% of the time its you.
I can confirm its the config.
On the hex your vlans are a mess.
The /interface bridge ports and bridge vlans dont line up.
You need to decide what the format is based on what is attached to each port.
ex.
ETHER1 - smart device - trunk port ( all vlans coming in tagged )
ETHER2-dumb device - access port one vlan untagged
ETHER3- smart device but needs untagged port into it but can carry vlans as well - hybrid port one vlan untagged, other vlans tagged
Since your diagram also failed to indicate what devices were attached to which port, impossible to make heads or tails of the misconfiguration.
Pass on that and it can be fixed up.
In retrospect I may need to adjust some of my settings, because I HAVE NO CLUE as to why you insist on bizarro networking setup…
It may be perfectly legit but getting cute with stuff doesnt help ignorant me.
Thank you for the reply and explanation of the concept, anav. I am sorry for my late reply as I am busy these days.
First, thank you for your explanation of VLAN port, I understand the concept when I setup my CRS305, maybe I deleted too many useful information for identify the Port usage.
For the Bridge’s VLAN setting, I follow the Basic VLAN Switching Guide so I think I should set frame-types=admit-only-vlan-tagged in the bridge.
However, I am still new to RouterOS. I would like to know if it is important to add interface list for the Manage VLAN.
For the neighbor discovery-settings, since I want to hide the device, so I disable it. Is it normal to expose the device in the network?
Besides, I would like to know more about the DNS function in a Switch. My target is to use the hEX as a VLAN switch, is it necessary to set DNS on a Intranet only Switch?
I also see you add some setting which I never touch. May I know the function of mac-server?
Finally, I follow your solution but no luck. After some digging, I find that I misconfig the TPLINK switch, the Trunk Port on the TP’s switch include VLAN 1 by default.
After I untag the VLAN 1 on the TP’s Switch Truck Port, both the frame-types=admit-only-vlan-tagged or frame-types=admit-all work on the Bridge (hEX) / Trunk Port (Port 1 on hEX).
Super glad you got it resolved.
The management interface list is to allow you to manage the trusted subnet and reach all MT devices via winbox.
So thats why its in neighbors discovery and why all smart devices get IPs on the trusted subnet etc…
