Ubiquiti UDM PRO with native “default” vlan on port 3. (also made networks for vlan 500 and 1000)
Port 3 goes to Cube60-SA (Ap Bridge)
in the other end I have Cube60 Pro as Station bridge, put in bridge.
Have set static ip to those, and I can get in to them without problems, and the links fully OK.
On station side i have connected to EdgeSwitch on port 1 with Tagged vlan 1,500 and 1000.
On port 7 on EdgeSwith I have an access point connected that will send out vlan 500,1000 untagged.
When i connect an unifi ap to a port direct on UDM with default vlan 1 it gets IP I set on vlan 1. But how can I get that ip on port 7 on EdgeSwitch? (untagging vlan1?! that can’t be right?) I can’t get it to work. Or do I have to activate WDS on links to have the vlans pass?
Ok, that is true. Don’t know how Ubiquiti handles it when you can use there own stuff with vlan 1, but not the 3rd party stuff. When I untag ports in edgemax to vlan 2 it snaps up the ip from that vlan.
Do you know if the mikrotik 60ghz link passes vlans without any special config? Or do I have to use Vlan filtering?
if I use vlan 1 native as trunk on edgemax. or do I have to change to other native vlan because of the udm?
When (almost) any vendor says it’s “native” VLAN … this means that frames on wire side of port are untagged, but get tagged on ingress and untagged on egress, so on internal bridge those frames are tagged. It’s identical to MT setup of a “hybrid” port with PVID set (and port set as untagged on same VLAN ID).
Which means that edgeswitch port 1 should be set as untagged member of VLAN 1.
And yes, Cube60, if set as default, will be transparent for VLAN tags … untagged frames will be passed on as untagged, tagged frames will keep their VLAN headers unaltered. But this can be changed/broken if one starts to play with unfamiliar toys (of course, it’s a ROS device ).
No, I’m not sure about that, I’d be sure if I’d ever have to deal with edgeswitch myself. But based on my (limited) experience, I’d definitely try that first. As I wrote: when vendors talk about native VLANs, that in 99.9% cases means it’s untagged on the wire/fiber side (if it was tagged on wire/fiber side, then it’d be normal VLAN … even if used as management VLAN for that device).
Untagged VLAN1 on edgeswitch and everything works as expected .
Problem nr 2…
I have from router native vlan 1(untagged) to Cube 60 SA( cube 60 no vlan config, just edited static ip on same subnet as vlan 1, 192.168.1.10)
The traffic passes to the other side cube 60 pro with ip 192.168.1.11 and on to the untagged port 1 on edgeswitch. Works flawless…BUT I can’t ping or get in to the cube60’s from network? Why? do I have to make some vlan config on the cube’s to get this working?
i connect remotely over Wireguard. But probably I have to make a vlan with tag on wireless bridge and lay it in the bridge where Wlan60 and eth1 is…then I can do a tag of that vlan on downlink port from router? maybe?
I have made test from switch and other devices to ping to the 60g link devices but no ping answer…
Router is Unifi UDM Pro
Mikrotik Cube60 SA to Cube60 PRO links
Wireguard default config no limits. Can ping everything on this picture , but not the 2 Cube60s…No special config, just static ip set, but can’t reach them.
If this statement is about cube devices … then they need at least default route set with UDM’s address as gateway. Without this setting (and probably DNS settings as well) it’s not possible to use built-in package upgrader …
).
hmmm…. Untagged vlan 1 on edgeswitch port 1? Really sure about that? This is the trunk that goes through The cube 60 from downlink vlan 1 on udm….
.
