A random MAC address will be generated in this case. ipv6 address add address=2003::1/64 advertise=no interface=lobridgeĪlternative solution is to use a fake EoIP tunnel interface instead of bridge. interface bridge add name=lobridge auto-mac=no admin-mac=01:00:00:00:01:00 Since IPv6 link-local address is needed for IPv6 to function properly on an interface, this means that by default the empty bridge interface cannot be used as IPv6 loopback interface.Īdd an empty bridge, and specify bridge MAC address manually: MT RouterOS does not generate IPv6 link-local addresses on interfaces with zero MAC address (because of high address collision probability). ip address add address=10.0.0.1/24 interface=lobridgeĮmpty bridge interface has zero MAC byte default. In MT RouterOS the recommended way to add a loopback interface for IPv4 is to create a new empty bridge interface: In the end I essentially decided to use /128 on loopback interfaces using globally unique IPv6 space out of a /64 reserved for loopback numbering across our entire network. Such addresses are useful, for example, as source addresses for TCP connections between two routers that have more that one physical interfaces between them. I have been doing some reading on IPv6 and have read a few different best practices guides and all of them seem to have conflicting information on the best way to assign loopback addresses. It can be used to hold addresses that belong to the "router itself" and not to any particular outgoing interface. The above table shows the reserved multicast addresses used by interior routing protocol.
Reserved Multicast Address for Routing Protocols. After loopback address, it can be represented as ::1/128. But in IPv6, only 0:0:0:0:0:0:0:1/128 represents the Loopback address. In some cases it is necessary to have a kind of loopback interface. Loopback addresses in IPv4 are represented by 127.0.0.1 to 127.255.255.255 series.