This property only has an effect when dhcp-snooping is set to yes. Can be used together with Option-82 capable DHCP server to assign IP addresses and implement policies. Whether to add DHCP Option-82 information (Agent Remote ID and Agent Circuit ID) to DHCP packets.
To avoid unwanted MAC address changes, it is recommended to disable "auto-mac", and to manually specify MAC by using "admin-mac".Īdd-dhcp-option82 ( yes | no Default: no) One MAC address from slave (secondary) ports will be assigned to the bridge interface, the MAC address will be chosen automatically, depending on "port-number", and it can change after a reboot. To combine a number of networks into one bridge, a bridge interface should be created (later, all the desired interfaces should be set up as its ports). The root bridge is the bridge with the lowest bridge ID.
(R/M)STP selects a root bridge which is responsible for network reconfiguration, such as blocking and opening ports on other bridges. This algorithm exchanges configuration messages (BPDU - Bridge Protocol Data Unit) periodically, so that all bridges are updated with the newest information about changes in a network topology. All other alternative connections that would otherwise form loops are put on standby, so that should the main connection fail, another connection could take its place. (R/M)STP allows bridges to communicate with each other, so they can negotiate a loop-free topology. Each bridge runs an algorithm that calculates how the loop can be prevented. Without any special treatment, loops would prevent the network from functioning normally, as they would lead to avalanche-like packet multiplication.
Network loops may emerge (intentionally or not) in complex topologies.
As bridges are transparent, they do not appear in the traceroute list, and no utility can make a distinction between a host working in one LAN and a host working in another LAN if these LANs are bridged (depending on the way the LANs are interconnected, latency and data rate between hosts may vary). The bridge feature allows the interconnection of hosts connected to separate LANs (using EoIP, geographically distributed networks can be bridged as well if any kind of IP network interconnection exists between them) as if they were attached to a single LAN. We did secure the Cat5 to form a drip loop.Ethernet-like networks (Ethernet, Ethernet over IP, IEEE 802.11 in ap-bridge or bridge mode, WDS, VLAN) can be connected together using MAC bridges.
They were last rebooted only 45 days ago (probably an upgrade to 5.22), which means they are still holding their configuration.įWIW, we did not seal any holes, or treat or modify the board or enclosure in any way just mounted it in the proper orientation. The SXTs themselves have been sitting out in the sun, rain, snow and wind for over a year with zero maintenance. The only issue we had was last Summer when a sweating irrigation pipe inside a utility shed dripped on a PoE box and fried the RJ45 plug. We mounted them just like in the Mikrotik video.Have you done a visual inspection, or power cycled them? If they have rusted up its likely the reset button will be rooted and it wont hold configuration.Our experience has been the same as nz_monkey's: More than a year ago, we installed 3 SXTs (and an OmniTik) in a multi-building campus, which sits on a windy hill directly overlooking the ocean <1km away. They have survived several tropical cyclones now. We have a bunch from the first production run, 100m from the ocean with high wind going about 2km and they have been rock solid. I dont understand how so many people have issues with SXT.