The 1-Wire protocol is a proprietary protocol (Maxim/Dallas) single-wire interface, half-duplex, bidirectional, low-speed and power, long-distance serial-data communication protocol. It operates over a single data line, without clock signal. But, at least two wires are required for 1-wire bus: Data, GND. An additional wire might be necessary (Vcc), depending on powering mode. The powering modes are: parasitic (no vcc), and conventional (with vcc), as seen on figures below.
This is meant to be a somewhat-easier-to-digest recap of the discussion that can be found on the MikroTik forum at this URL: https://forum.mikrotik.com/viewtopic.php?f=23&t=157048&p=836497&hilit=failover#p836497 Note that the forum discussion not only addresses failover, but also load balancing at the same time (without explicitly saying so in the beginning).
For the sake of this document, we'll make some assumptions:
| /interface bridge add name=bridge | |
| /interface bridge port | |
| add bridge=bridge interface=ether3 | |
| add bridge=bridge interface=ether2 | |
| add bridge=bridge interface=ether1 | |
| /interface list | |
| add comment=defconf name=WAN | |
| add comment=defconf name=LAN |
| # This is an example from a work in progress, so final versions might | |
| # be slightly different. Don't use as a guide after release! | |
| # Define rule set macros | |
| # Whitelist a TCP destination port on the network. Use this as a template to | |
| # make your own rule sets for more advanced criteria like tag matches, etc. | |
| # This works for both IPv4 and IPv6. Add an ethertype match to restrict it to | |
| # one or the other. | |
| macro tcp_whitelist_dest_port($port) |