Bridge vlan solution without adding interface vlan

RouterOS General
1

Is it possible to bridge all incoming vlans from a port without creating a vlan interface?
DHCP and ip block 10.0.0.1/16 should be assigned for this bridge on Mikrotik.

The vlan range of 1201-1248 comes over the Ether2 connected switch.

/interface bridge
add name=bridge2 vlan-filtering=yes
/interface bridge port
add bridge=bridge2 interface=ether2
/interface bridge settings
set use-ip-firewall=yes use-ip-firewall-for-pppoe=yes use-ip-firewall-for-vlan=yes
/interface bridge vlan
add bridge=bridge2 tagged=ether2 vlan-ids=1201-1248
/ip address
add address=10.0.0.1/16 interface=bridge2 network=10.0.0.0

In short, I want a solution on the bridge without adding interface vlans for each vlan. Is it possible?

2

No.

IP layer (L3) in mikrotik can only work with untagged frames. If frames are tagged, then you absolutely need VLAN interface to do the tagging/untagging, one for each VLAN ID.

If you use bridge only to pass frames between member ports, then VLAN interfaces aren’t needed.

BTW, if router is supposed to interact with those VLANs, you’ll have to add bridge interface as tagged member of all those VLANs (just the same way as ether2).

3

Dont think so.
YOu have to add each vlan interface to the bridge as in a basic definition requirement
If the router is not involved with DHCP for the vlan subnets then there are some savings there because normally each vlan
would also need an IP pool, DHCP server, DHCP server network and IP address.

Also typically each VLAN would have a separate interface bridge vlan setting entry
but in this case you could enter multiple vlan #s, dont think a range is allowed.
add bridge=bridge tagged=bridge,ether2 vlan=ids=a,b,c,d,e,f,g,h.i,j,k,l,m,n etc…

4

Yoncu, are you trying to bridge together different vlans?

5

Yes. I want to merge all vLan and assign IP.
Creating interfaces reduces performance because there are hundreds of vLans. I’m looking for a solution on Bridge without creating Interfaces.

6 



add bridge=bridge2 tagged=ether2,bridge2 vlan-ids=1201-2048

The solution is unsuccessful. No IP assignment.
“/ip address add address=10.0.0.1/16 interface=bridge2 network=10.0.0.0” not working.

7

So you want to bridge a network of many VLANs and give your router an IP on all of these VLANs?
That can only be done by putting a VLAN interface for each tag and setting an IP on each of these interfaces.

For merely bridging the VLANs from one port to another this is not required.

8

I need to give 10.0.0.0/16 ip from common pool for all vLans. how can I do that.
Could you please consider solving it without creating interfaces. Too many interfaces create high cpu problem.

9

yoncu, you are asking to put a square peg into a round hole. In other words you need to step back and provide the requirements of how you got yourself into this corner.
What are the requirements of the network that created a whole bunch of vlans. A design is best evolved when you know the back story or the history…

10

What Mikrotik hardware are you using in that 48 VLANs is putting extra load on the device?

The reasoning behind not using VLANs and routing seems odd.

11

There are more than 1500 vlans available, even the CCR1072 has a CPU problem. If I can’t find a solution, I won’t be able to use Mikrotik.

12

As I stated, without an appreciation of the situation, how did you end up with 1000s of vlans etc… What does the total network(s) look like, too much information you are leaving out.

13

Do you think simply bridging your network would work anyway? 1500 networks into one collision domain?

14

You cannot solve that. Not with MikroTik routers, at least.
Maybe with a high-end L3 routing switch it is possible, but even there you could hit some limitation.

15

This remark is of course nonsense, a bridge or switch does not create a collision domain.

16

I was referring from the OP where he wanted to create a 10.0.0.0/16 network with these vlans- onto one bridge - thus creating a huge collision domain.

17

No, that would “only” create a huge broadcast domain, not a collision domain.
My question is more like: Why bother with so many VLANs if the whole network construct is going in one huge broadcast domain anyway?

The desire to implement a huge number of VLANs only to bridge them together could point to

  • a specialized application


  • a possible indicator for a misunderstanding of commonly accepted networking concepts

I think the OP should not be surprised that - for lack of more background information - most readers tend to spot a misunderstanding.

18

I think I was having a flashback to the days of coax, BNC and terminators. :smiley:

19

Until the op reveals some truths about the infrastructure involved you are wasting your time…
Either that or it was a homework assignment he was trying to get others to solve LOL

20

Consider a datacenter.
It has 10 Gbit/s Fiber Uplink.
36 cabinets available.
48 port switches are available for each cabinet.
All ports and server systems should use ip address from common pool.
Active bridge traffic averages 1 Gbit/s.
My goal is to monitor and control each switch port via Mikrotik. (For security purposes)