Hello friends, I have a problem. I want to expand the coverage by putting another OMNITIK
Currently I have an Omnitik and it works fine, it has on port 3 with a vlan123, connected to a ptp to the central node.
It has a bridge, with all the ports and the vlan except the ehter3
clients connect by ppoe
The ip is 100.40.100.134/30 and gateway 100.40.100.133/30
ip route 0.0.0.0/0 with gateway 100.40.100.133 ether3
I have connected another omnitik to port 2, with ip 100.40.101.40/30 and gateway 100.400.101.39/30
but I don’t have access only by mac-telnet
the latter has ip route 0.0.0.0/0 at 100.40.101.39 interface ether1
I have managed to access through winbox if I add the ethernet port to the old omnitik and disable the vlan but then the clients do not connect to the pppoe
Many people can help you if you post the export of the current configuration of the two Omnitiks. See my automatic signature just below regarding anyonymisation.
You are right I have uploaded the current configuration, it is possible that some IP do not match the previous graph since I continue to carry out tests.
What I had in mind was the configuration file export from the devices. The drawing, even though updated, says nothing about what you have actually set up in the devices themselves. Do not post screenshots from Winbox/WebGui. Press the [Terminal] button, type /export hide-sensitive file=my-config, then download the file and sanitize it before posting if there are any public IPs.
I don’t understand your idea regarding the IP addressing.
The IP address of omnitik_old_.00 is attached to ether3 itself, so no VLAN tag.
The IP address of Omnitik.01 is in the VLAN 1132, because the whole bridge1 on omnitik_old_.00 is connected to the tagless end of the /interface vlan attached to ether3, ether2 of omnitik_old_.00 is a tagless port of the bridge1, and so is ether1 of new Omnitik.01.
So at the other end of the PtP link, 100.40.4.25/30 has to be attached to VLAN 1132 in order that you could reach Omnitik.01.
If you wanted something else, describe what you actually wanted.
Before digging any further, there is a typo in Omnitik.01’s configuration - in the default route setting, there is gateway=10.40… instead of gateway=100.40….
Also, 100.40.0.0/16 is a public IP address range assigned to Verizon. The “shared” IP address range is 100.64.0.0/12 if you intended to use that one for your internal purposes.
The idea is to be able to access from the central router Mikrotik CCRxxx at 2 ominitik, right now I only access the first omnitik.01 or called .old, and the second omnitik I have not managed to access.
Well, that high level design is clear, my question was regarding the implementation details
So confirm that the PtP link is in bridge mode, and post the export of the configuration of the box named Router. But before doing that, fix the typo in the default route’s gateway on the new Omnitik - have you done that already?
Hello, I have already made the change of ip, both in the old omnitik and in the new one.
This is the configuration.
Right now I only have access to the old omnitik, I can’t access the new one by winbox, The ping not found omnitik_old (2).txt (2.57 KB) omnitik_new.txt (2.46 KB)
One more time. The way you have added the IP address 100.40.101.40/30 to the new omnitik, it is visible inside VLAN 1123 on the PtP link. So unless you have added 100.40.101.39/30 to vlan 1123 on the central node’s router, the 100.40.101.39 and 100.40.101.40 cannot see each other.
I’ve asked you to post the configuration of the central node’s router but you haven’t done that, so I cannot help you more.
Just notice that you had one typo in IP address in the configuration and another typo in the IP address in your original post, so the problem may be simply yet anothed typo in the configuration of the central node’s router.
