Hi,

I'm new to the RouterOS and i was testing a setup, but i seem to need some help

I've been able to set up untagged vlan's through bridges
but I seem to fail to trunk (tagged) the vlan's to a 2nd Mikrotik device.
adding interface vlan to the ethernet interface which is connected to the other device

Also, i seem to be able to set vlan's in 2 places, and i'm not sure why the
/interface ethernet switch vlan
is there?
should i use that also?
(i have Atheros8316 btw http://wiki.mikrotik.com/wiki/Switch_Chip_Features)

i had some reference on http://forum.mikrotik.com/viewtopic.php ... 20#p130220

It seems i need to enable service tags, but i don't know why..
Now i have been able to link my vlan's over one interface

Still i would like to know why there is a vlan setting under switch

Thanks

VLAN setting under switch section is to manage VLANs going through switch chip, while standard VLAN interface manages VLANs going through CPU.

VLAN setting under switch section is to manage VLANs going through switch chip, while standard VLAN interface manages VLANs going through CPU.

That is what i thought at first, but i don't seem to setup it like i want.
it looks like it is for tagged only?
or do i need to setup the rules?

I need tagged vlan traffic on 1 interface and untagged on the other interfaces.
I have been able to make it work like this:
-Make a bridge per vlan,
-Assign ports to the bridge to which i wanted to have untagged traffic.
-Create vlans, assigned to the port where i want the tagged traffic over (for some reason ,I do not know, I need to enable the service tag, else it doesn't work), (also in my case i needed to have the vlan's an mtu of 1496 to work over powerline adaptors)
-on the bridge add the vlan's device to the right bridge (to have the untagged traffic)

While doing some tests (making it work)
i think i stumbled upon a bug (which made testing harder)

When i tried to make a bridge, just for the vlan, assigned the tagged port, and made a vlan interface on that bridge.
Then removed the bridged from the interface list (not from the bridge menu) the vlan traffic kept going over the bridge interface.
I needed to remove the bridge from the bridge menu.
Also when i removed a vlan via the interfacelist, it removed the vlan from the vlan list, but not from the bridge ports, there it remained named as 'unknown'

I think this are minor bugs, but they slowed my testing way down, cause i could send vlan traffic over my trunk, but i didn't seem to get any traffic back, until i saw in bridge menu, the vlan bridge i made before had the traffic, but wasn't assigned.
I know this wasn't the way to work, but i was trying to make it work with the little documentation i found about this subject.

I hope i made this clear enough to reproduce, else i'll try to put together the commandline commands to reproduce.
HW is Routerboard 560G, using 5.0rc4 software

Not to bash on your guys great work, but i don't really understand why i need to make bridge interfaces
While on other brands, i just need to create vlan's, assign them to and interface, define if it is tagged or not and that's it.
I even can combine on them, so when there is untagged traffic on the interface, automaticly assigned to a vlan i defined as untagged traffic.
for example
on ether1 i can have tagged traffic of vlan 10 and 20, and the untagged traffic is for vlan 50 (for example)

in this case i this i caught this with the "interface ethernet switch", i added a rule that defined, if there is no vlan header, add one with a certain tag.

(my last posts i was pretty tired, so that was why i was so brief)

Thanks

Not to bash on your guys great work, but i don't really understand why i need to make bridge interfaces

Because RouterOS is, at the heart of things, a Linux router. And not a switch.

Not to bash on your guys great work, but i don't really understand why i need to make bridge interfaces

Because RouterOS is, at the heart of things, a Linux router. And not a switch.

Oh, ok didn't think about it in that way, was distracted from that cause of the "ethernet switch" capabilities, thanks

also subquestion:
When i add vlan interfaces to a certain ethernet interface, can i add that ethernet interface also to a bridge, to have an untagged part?
I tried it, but it seemed not to work :/

unfortunately, for now you cannot add to the same bridge both VLAN and ethernet interface of that VLAN

Add the Ethernet interface to a bridge.
Create the VLAN interfaces with the bridge as the parent interface.
Add those VLAN interfaces to another bridge. You cannot add them to the same bridge as the Ethernet interface.

Add the Ethernet interface to a bridge.
Create the VLAN interfaces with the bridge as the parent interface.
Add those VLAN interfaces to another bridge. You cannot add them to the same bridge as the Ethernet interface.

Oh damn, didn't think about it in that way

thanks for the hint! i'll try it as soon as posible

i didn't add the trunk interface to a bridge.. didn't seem needed, but now i get it

about

While doing some tests (making it work)
i think i stumbled upon a bug (which made testing harder)

When i tried to make a bridge, just for the vlan, assigned the tagged port, and made a vlan interface on that bridge.
Then removed the bridged from the interface list (not from the bridge menu) the vlan traffic kept going over the bridge interface.
I needed to remove the bridge from the bridge menu.
Also when i removed a vlan via the interfacelist, it removed the vlan from the vlan list, but not from the bridge ports, there it remained named as 'unknown'

I think this are minor bugs, but they slowed my testing way down, cause i could send vlan traffic over my trunk, but i didn't seem to get any traffic back, until i saw in bridge menu, the vlan bridge i made before had the traffic, but wasn't assigned.

Do i need to post a ticket about this somewhere?
or is this already known?

I have noticed that happens on just about anything. If you remove a setting that another is dependent on it goes red and appears not to work. In relation to VLANs still passing traffic it may be a bug but I can't really say.