Hi there,
I want to design a simple network using two hAP ac switches as shown in the diagram. Both hAP ac will be connected to each other through a wired and wireless network. Whenever one network is unavailable (wired or wireless), I want all devices to automatically switch to the other network and communicate. If someone can provide a quick on this it would be very useful.
And I want to connect to soup cans by string from here to the moon.
Better diagram, I dont see any internet or routers in the mix
Description of requirements without any discussion of a config.
once we understand what the USERS need and the context a design/config can be developed that makes sense.
or it will be more clear that what is being asked is not possible etc…
There is no internet requirement at this stage. What I want is for two devices(device 1 and device 2) to be able to communicate with each other constantly as shown in the diagram. If one of the links (wired or wireless) goes down for any reason, the other link will automatically start communication and provide connectivity.
Dont understand, are you expecting the cable between the two devices to fail… lot of rodents in the walls?
What I want is for two devices(device 1 and device 2) to be able to communicate with each other constantly as shown in the diagram. If one of the links (wired or wireless) goes down for any reason, the other link will automatically start communication and provide connectivity.
Multiple ways to do this, either layer 3 (routes) or layer 2 (interface bonding).
L2 Like the CUBE 60 doing bonding between the 2 wireless links (60GHz and 5 GHz)
Following is an extract from the default config, when delivered as wireless-wire pair.
Communication is over interface “bond1” , which will use 60GHz link if available, and 5GHz link as instant backup.
Master CUBE:
/interface bonding
add comment=defconf mode=active-backup name=bond1 primary=wlan60-station-1 \
slaves=wlan60-station-1,wlan1
/interface bridge port
add bridge=bridge comment=defconf interface=ether1
add bridge=bridge comment=defconf interface=bond1
/ip address
add address=192.168.88.2/24 comment=defconf interface=bridge network=\
192.168.88.0
Slave CUBE:
/interface bonding
add comment=defconf mode=active-backup name=bond1 primary=wlan60-1 slaves=\
wlan60-1,wlan1
/interface bridge port
add bridge=bridge comment=defconf interface=ether1
add bridge=bridge comment=defconf interface=bond1
/ip address
add address=192.168.88.3/24 comment=defconf interface=bridge network=\
192.168.88.0
A Similar thing could be setup in your case with etherX and wlanY as slave interfaces.
Only bond1 is used as interface to the bridge, not the slaves. “ether1” stands above for the other ethernet interfaces, also on the bridge for a L2 bridged network.
For monitoring options see: https://wiki.mikrotik.com/wiki/Manual:Interface/Bonding