Thu Aug 05, 2021 10:22 pm
Ok I think I have it figured out!!!!
MGT PC---------------------Bridged----------MikroTik Ether1
:
Router------192.18.10.0/24------------------MikroTik Ether2
Using the GUI
Ether1 connected as Bridged Adapter 1 within Oracle Virtual Box (The intent is to change this interface to the up streams router where Ether2 is currently sitting)
Ether2 is sitting on the upstream routers subnet
Ether3 is down
Ether4 is down
Reset config via GUI
System, Reset Configuration, check box: No Default Configuration, check box: Do Not Backup, Click on: Reset Configuration button
Reset config via CLI
/system reset-configuration no-defaults=yes skip-backup=yes
Setup IP Management of bridge (switch)
Bridge, Bridge tab, +, Enter bridge name (I used SW-1)
Bridge, Ports tab, +, Select interface ether1, bridge SW-1
IP, Addresses, +, 192.168.10.252/24 interface SW-1
IP, Routes, +, Dst. Address 192.168.2.0/24, Gateway 192.168.10.1, ok button
Ok here is where things go wrong.
Because RouterOS is able to communicate with the upstream router on Ether2 and not on Ether1, RouterOS dynamically modifies the configuration and as I pointed out before, NO NOTICE and NO GUI UP DATES. RouterOS sets the gateway address to Ether2. This change can be seen in the CLI output only- ip address print or also with the export command. The Changes are not updated within the GUI.
ip address print
Flags: X - disable, I - invalid, D - dynamic
# ADDRESS NETWORK INTERFACE
0 192.168.10.252 192.168.10.0 ether2
--or--
export
....
/ip address
add address=192.168.10.252/24 interface=ether2 network=192.168.10.0
Once Ether2 is able to communicate with the up stream router you cannot change this route unless you create an alternate interface that can communicate with the up stream router. After you add the new interface and the new interface is able to communicate with the up stream router, you can remove Ether2 from your configuration. You can successfully ping this MikroTik CHR bridge from the up stream router. However, the MikroTik cannot ping anything nor can you connect to it.
I setup a 2nd MikroTik CHR with my new CLI commands (shown below) and it worked as expected. I compared both configurations (working and broken) and the only differences were IP addresses of the management IP. Once I reset the configuration on the broken box and reset via CLI, all worked as expected but I spent most of today figuring this out. Keep in mind this is only to allow you to connect to the remote MikroTik bridge and start configurations which I have sadly not figured out yet. Hope this help you!!
And ol yea, I did reboot and power off multiple times, but to no avail.
#######################################
# Name your MikroTik bridge
#######################################
/system identity set name=SW-2
#######################################
# Bridge, create bridge and assign interface
#######################################
/interface bridge add name=SW-2
/interface bridge port add bridge=SW-2 interface=ether3
#######################################
# IP Addressing & Routing
#######################################
/ip address add address=192.168.10.252/24 interface=SW-2
# Up stream router IP address
/ip route add distance=1 gateway=192.168.10.1
Hope you have a great day!!
Frank