Hello Mikrotikonians!
Need some help understanding management access to both ends of a Wireless-Wire 60ghz bridge. I have traffic passing thru but am unable to access one end (master) with winbox or ssh. I used to be able to manage to both ends.
The setup is: Main Office in first Bldg with WirelessWire-Slave (RBwAPG-60ad) ↔ Office in 2nd Building with WirelessWire Master (RBwAPG-60ad)<–> and Access Point (RBwAPG-5HacT2HnD) connected directly.
I can access the slave unit via winbox and ssh (that unit is closest to me in main office) from a system in a server room. I cannot access the master from here. I was able to upgrade the master by telnetting from the slave New terminal window and using the fetch command to copy the 6.47.1 package across. I can access the access point in 2nd building that is connected to the master, and users can also connect and use it and get online. I have attached both configs. Internet is connected at the Main Office.
I cannot ping or Traceroute from the master out to the internet.
TIA!
Jerry
WW-master.rsc (1.84 KB)
WW-slave.rsc (1.43 KB)
the issue is related to the config.
you assigned address to ether1.
/ip address
add address=192.168.2.16/24 interface=ether1 network=192.168.2.0
but the same interface is also a bridge port:
/interface bridge port
add bridge=bridge comment=defconf hw=no interface=ether1
add bridge=bridge comment=defconf interface=wlan60-1
this will not work properly. depending where the packet enters it will be processed by the CPU or not.
remember, L3 config (such as ip address, dhcp server/client) shall always be attached to the bridge interface, never to its ports.
on master you can fix it with this command:
/ip address
set [find where address=192.168.2.16/24] interface=bridge
and your slave also needs to be fixed in a similar way.
The IP used to be assigned to the bridge and I could not manage so I moved to ether1. I have moved it back to the bridge interface and still same issue. Any other Ideas?
WW-slave.rsc (1.42 KB)
WW-master.rsc (1.84 KB)
there is no default route configured in one of the configs - which makes sense as you have a dhcp-client active on bridge.
but the master has a default route configured which will always take precedence over the DHCP assigned one:
/ip route
add distance=1 gateway=192.168.2.3
what is the actual IP address of the router on your subnet?
if it’s not 192.168.2.3, then you should remove/disable the static route entry on ww-master
ip dhcp-client never gets an address on the bridge or ether1 interface. I added a static IP and route and still no access. I can only get to it via the IP>Neighbor from the slave unit with telnet or mac-telnet.
ok. small details add a great deal of information.
i have to emphasise: don’t (actually you can’t) run L3 components on bridge ports. dhcp client cannot even be active if configured on bridge ports (ether1 in your case).
one of your devices doesn’t have but a single connected route in its routing table as far i can judge from the configuration. this can be also a reason why it is not reachable from a ‘distance’ but only from the connected devices (from the same IP subnet) and mac-telnet.
can you please post the output of
/ip route print
below?