I concur about Sob's posts.

As for the vrf* interfaces: when you program it via terminal the vrf* interface gets autocompleted with "tab" when as an in-interface option. Thus ROS knows it - not sure why - and should consider it. With that rule, it wasn't working.

Best.

Thanks for the reply, but I think I found the solution. This is my working configuration: /ip vrf add interfaces=ether4 name=vrf50 add interfaces=ether2 name=vrf30 add interfaces=ether3 name=vrf40 /ip address add address=10.2.4.1/24 interface=ether1 network=10.2.4.0 add address=192.168.1.1/24 interf...

Thanks for the reply. vrf30 and vrf40 put in the ip/route are indeed the vrf created in ip/vrf/add Adding vrfXX instead of the interface like ether2 or 3 is a practice mentioned in Mikrotik manual for "[url https://help.mikrotik.com/docs/pages/viewpage.action?pageId=328206]Static VRF-Lite Conne...

Dear members, I need help with a particular setup where one MT router CCR2004 needs to be connected with multiple switches where a local lan is present with a fix subnet. In specific there are many identical subnet (each in a dedicate VLAN) with same overlapping IP subnet 192.168.1.0/24 - let's call...

Hi there,

It might be because you are missing the VLAN definition as interface (vlan99). I haven't had time to look at the config in details, but here is a great tutorial that helped me set things up.

Let me know if that helps.

A

Hi there, I'm currently researching a very similar solution for a setup where I have: - a single CCR acting as main and unique router for a whole plant (ROS 7.14.2) configured with VLANs under bridge - one CRS switch connected to the CCR (via trunk port) and also to other (18) "dev" subnet...