lo-Interface loopback

RouterOS General
1

Hey There!
Im new in this forum,I would like to share my “issue” on my home mikrotik routerOS v7.14.1 (hAP ax2).
After reboot on interfaces appear a loopback interface with lo name,and when i remove it manualy it appears again on next start automaticaly.
Well- it hasn’t giving me any trouble/issue of working out the connection etc. but seems like it looking annoying and it loks weird since it appear again even if I remove it manualy.
Maybe someone has this “technical issue too” or intuite is leading me something is missing from routerOS.
my bridge conf as below:

**0 R ;;; TRUNK-20,200
name=“BR_LAN” mtu=auto actual-mtu=1500 l2mtu=1568 arp=enabled arp-timeout=auto mac-address=4C:XX:8A:XX:XX:DC
protocol-mode=rstp fast-forward=yes igmp-snooping=no auto-mac=yes ageing-time=5m priority=0x8000
max-message-age=20s forward-delay=15s transmit-hold-count=6 vlan-filtering=no dhcp-snooping=no
port-cost-mode=short

1 R name=“BR_VLAN200” mtu=auto actual-mtu=1500 l2mtu=1564 arp=enabled arp-timeout=auto mac-address=4C:XX:8A:XX:XX:DX
protocol-mode=rstp fast-forward=yes igmp-snooping=yes multicast-router=temporary-query multicast-querier=no
startup-query-count=2 last-member-query-count=2 last-member-interval=1s membership-interval=4m20s
querier-interval=4m15s query-interval=2m5s query-response-interval=10s startup-query-interval=31s250ms
igmp-version=2 mld-version=1 auto-mac=yes ageing-time=5m priority=0x8000 max-message-age=20s forward-delay=15s
transmit-hold-count=6 vlan-filtering=no dhcp-snooping=no port-cost-mode=short**
Thanks in ADVANCE!

2

Standard loopback interface.
It has always been there but was hidden in the past.

Recent versions of ROS made it visible.

Don’t worry too much about it and just let it be :sunglasses:

3

you’re not the first one to complain about this recently exposed loopback Interface. Accept it. It does no harm. If people would care as much about their bloated config…

4

some kind of loopback-o-phobia

5

Can you create a second proper “type=loopback” interface or do you need to still do it the old school way of creating a bridge interface with no ports?

6

type=loopback from where?
It is not an option for /interface/bridge

I am also confused as to why I am suddenly seeing this. Its not under veth, bridge or anything. I see nowhere I can create another interface with “type=loopback”

7

This is also my question, should I move my IPs from the loopback bridge to the lo interface or leave the loopback bridge? Is there any advantage to getting rid of the bridge?

8

The advantage is you have one less interface in your configuration, which is already something :stuck_out_tongue:

9

You can leave your IPs on the loopback bridge if it’s working for your setup. However, moving them to the “lo” interface can simplify your configuration by reducing unnecessary layers. The main advantage of removing the bridge is less complexity, but if Apple’s network stack relies on it, keeping the bridge may be the better option. It depends on your specific system needs.

CredibleBH