My ISP give me to VLAN 100 and 200 on two servers location, this able to connect this location for making backup and connection with the same IP.
On first location i have:
Router CCR1072
CRS317-1G-16S+
On second:
The same
First location:
On Router:
On port eth2 i created vlan frm ISP 100 and 200
On port eth3 i eth4 i created bridge LAN (100) and BACKUP(200)
On switch:
I created 2 vlan 100 and 200
Ports 1-8 i set to Strict Untagged 100
Ports 9-16 i set to Strict Untagged 200
Second Location:
The same configuration
I cannot ping this two diffrent location, you know what i make bad?
As always there are “many ways to skin the cat” when it comes to dealing with VLANs in RouterOS. Your vague description what you tried to do is one of them (but we can only guess if you did it right), but the recommended way is to use single VLAN-enabled bridge. @pcunite wrote a nice tutorial about it.
If you decide to pursue the way you went with, post configuration of all devices (at least part under /interface) for review.
SFP1-WAN
SFP2- ISP Provider VLAN to other location
SFP3- Connected to SWITCH 1-12 Port Untagged 100
SFP4- Connected 13-16 port untagged 200
The same configuration on second location but on second location have two switch. On the second switch i make the same vlan untagged, the same configuration what on switch one.
If you have CCR1072 port sfp-sfpplus3 connected to one of CRS317 ports 1-12 (that’s what I can read from screenshots, too heavily cropped to be sure), then the rest of CRS ports 1-12 should be able to talk via VLAN 100 with peer devices on the other location.
Similarly, if you have CCR1072 port sfp-sfpplus4 connected to one of CRS317 ports 13-16 (again that’s what I can read from screenshots), then the rest of CRS ports 13-16 should be able to talk via VLAN 200 with peer devices on the other location.
If physical connections between CCR and CRS are not as written above, then CCR and CRS configuration is not in par with physical setup.
As I aleady noted: VLAN setup can ve done in different ways, yours is a bit odd (mildly put). E.g. single connection between CCR and CRS carrying both VLANs would be more common. If you want to use two links, you could use them in bond (again carriying both VLANs), providing increased capacity and fault tolerance.
SFP1 - WAN
SFP3 - ISP PROVIDER VLAN 100/200 Connetion to other location
SFP2 - LINK TO SWITCH PROD PORT UNTAGGED 100 VLAN
SFP4 - LINK TO SWITCH BACKUP PORT UNTAGGED 200 VLAN
SWITCH1: https://ibb.co/169sdgH https://ibb.co/f2NQXNK
LINK1 on SWITCH CONNETED TO SFP2
LINK15 on SWITCH Conneted to SFP4
LINK16 on SWITCH conneted to second switch on this location
By using single VLAN-aware bridge … as per tutorial linked in my post #2 above. It works on all ROS devices versions 6.42 and above. Recent SwOS will handle trunk (tagged-only) ports fine as well.
But essentially it’ll be the same as your inter-location fibre carrying two tagged VLANs.
I don’t have any idea about why you can’t use devices in different locations which belong to same IP subnet … other than it’s something else on router(s) which is in the way. Since both locations use same VLANs, but yet you have two routers (assumingly to break out local traffic to internet) … it may be down to IP addressing (and routing and firewalling). How do you configure L3?
The last post did not really answer to my question
How do you configure L3?
And that means all of it … addresses, routes, whatnot. I’m getting tired of pulling bits of information out of you. And I can not help you without seeing the full picture.
It could be that you’re seeing effects of routing triangle. But I can’t say if that’s so because I can’t get a grasp on the network layout you’ve got.
Traffic between device on 192.168.0.0/24 subnet on site 1 and device in the same subnet on site 2 should flow undisturbed. Similarly for 10.0.0/24. The only thing that might get into the way is proxy arp setting on bridges. Any good reason to have it enabled?
Traffic between different subnets will take different paths in each direction, local router will route it to the other VLAN. And this upsets connection tracking machinery. Similar could happen even for intra VLAN traffic if proxy arp “pulls” traffic to router’s L3 where it becomes subject to firewalling.
I’m sure there are multiple ways out but as I wrote: since I can’t get a grip on how your networks are like, I don’t know which way out would be appropriate.