Network resets a lot and looped packet message after upgraded to 7.14(and .1)

RouterOS General
1

Hi All,

Not sure if this is a known issue, but after I’ve upgraded to 7.14, my CCR2004 becomes intermittently connecting and generating below error messages:

 03-12 23:58:24 interface,warning ether10: bridge RX looped packet - MAC 18:fd:74:e9:9c:04 -> 00:0d:5d:10:12:a6 VID 1 ETHERTYPE 0x0806
...
 03-12 23:58:29 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC 18:fd:74:e9:9c:04 -> 78:7e:61:d1:e3:65 VID 1 ETHERTYPE 0x0800 IP UDP 192.168.24.24:53 -> 192.168.24.150:56812
...
 03-12 23:59:58 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC 18:fd:74:e9:9c:04 -> 00:0d:5d:10:12:a6 VID 1 ETHERTYPE 0x0806
...
 00:00:03 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC 18:fd:74:e9:9c:04 -> 26:ce:61:31:72:b4 VID 1 ETHERTYPE 0x0800 IP PROTO 1 192.168.24.24 -> 192.168.24.154
...
 00:00:09 interface,warning ether10: bridge RX looped packet - MAC 18:fd:74:e9:9c:04 -> 26:ce:61:31:72:b4 VID 1 ETHERTYPE 0x0806
 00:00:14 interface,warning ether10: bridge RX looped packet - MAC 18:fd:74:e9:9c:04 -> 52:54:00:04:81:72 VID 1 ETHERTYPE 0x0800 IP UDP 192.168.24.24:1900 -> 192.168.24.31:51567
...
 00:11:03 dhcp,info dhcp-client on brg2-wan lost IP address 50.46.252.170 - lease stopped locally
 00:11:03 bridge,info "brg2-wan" mac address changed to 48:A9:8A:85:C1:F6
 00:11:03 interface,info sit1 link down
 00:11:03 interface,warning ether10: bridge RX looped packet - MAC 18:fd:74:e9:9c:04 -> 4c:56:df:39:86:3b VID 1 ETHERTYPE 0x0800 IP TCP 192.168.219.161:8009 -> 192.168.24.173:58385

I am very puzzled by these messages. All these ports are connected to RSTP enabled switches, while these ports themselves are under a bridge which has RSTP enabled. And, there’s no loop on my network at all. I don’t understand why there could be looped packet, especially there’s no such issue with 7.13.5 and many versions before. It causes severe connection issue on my network, that as you can see somehow the WAN port will change its MAC address and get reset, while my winbox connection to the router will stutter too.

Also confirmed 7.14.1 has this issue too.

I’ve tried to remove some of the physical links, it did not help. It seems that for any switches with RSTP connected to the router, it will generate this message. I can eventually remove all switches from the router, only connecting my laptop and the WAN, it would still reset on the WAN and causes stuttering.

Please help me understand what’s the situation here and how to make 7.14 work with the router. Thanks!

2

Did you maybe load a backup file from a different device?
Otherwise, show the config of your bridges. Did you set the admin MAC address and is it the same as the ethernet MAC address of a port (of the CCR2004 itself) in the bridge?

3

Hi pe1chl, thanks for reply! Yes this device is restored using backup from another device. Is this something bad? And how to fix?

Nonetheless, here’s the bridge config:

/interface bridge
add igmp-snooping=yes multicast-querier=yes name=brg1-lan port-cost-mode=\
    short priority=0x1000 protocol-mode=mstp querier-interval=2m5s \
    query-interval=1m vlan-filtering=yes
add name=brg2-wan port-cost-mode=short
add igmp-snooping=yes name=v-brg3-lan-utilities port-cost-mode=short \
    protocol-mode=none
add igmp-snooping=yes name=v-brg4-lan-guest port-cost-mode=short \
    protocol-mode=none
add disabled=yes igmp-snooping=yes name=v-brg5-lan-untagged port-cost-mode=\
    short protocol-mode=none
add igmp-snooping=yes name=v-brg6-lan-datacenter port-cost-mode=short \
    protocol-mode=none

/interface bridge port
add bridge=v-brg4-lan-guest ingress-filtering=no interface=brg1-lan-vlan0029 \
    internal-path-cost=10 path-cost=10
add bridge=v-brg3-lan-utilities ingress-filtering=no interface=\
    brg1-lan-vlan0019 internal-path-cost=10 path-cost=10
add bridge=v-brg5-lan-untagged ingress-filtering=no interface=\
    brg1-lan-vlan0013 internal-path-cost=10 path-cost=10
add bridge=v-brg6-lan-datacenter ingress-filtering=no interface=\
    brg1-lan-vlan0059 internal-path-cost=10 path-cost=10
add bridge=brg2-wan ingress-filtering=no interface=sfp-sfpplus2 \
    internal-path-cost=1280 path-cost=128
add bridge=brg1-lan ingress-filtering=no interface=sfp-sfpplus1 \
    internal-path-cost=128 path-cost=128
add bridge=brg1-lan ingress-filtering=no interface=ether10 \
    internal-path-cost=1280 path-cost=1280
add bridge=brg1-lan ingress-filtering=no interface=ether11 \
    internal-path-cost=1280 path-cost=1280
add bridge=brg1-lan ingress-filtering=no interface=ether12 \
    internal-path-cost=1280 path-cost=1280
add bridge=brg1-lan ingress-filtering=no interface=ether13 \
    internal-path-cost=1280 path-cost=1280
add bridge=brg1-lan ingress-filtering=no interface=ether14 \
    internal-path-cost=1280 path-cost=1280
add bridge=brg1-lan ingress-filtering=no interface=ether15 \
    internal-path-cost=1280 path-cost=1280
add bridge=brg1-lan ingress-filtering=no interface=ether16 \
    internal-path-cost=1280 path-cost=1280
add bridge=brg1-lan ingress-filtering=no interface=ether01 \
    internal-path-cost=1280 path-cost=1280
add bridge=brg1-lan ingress-filtering=no interface=ether02 \
    internal-path-cost=1280 path-cost=1280
add bridge=brg1-lan ingress-filtering=no interface=ether09 \
    internal-path-cost=1280 path-cost=1280
add bridge=brg1-lan interface="aggregate[3,4]" internal-path-cost=640 \
    path-cost=640
add bridge=brg1-lan interface="aggregate[5,6]" internal-path-cost=640 \
    path-cost=640
add bridge=brg1-lan interface="aggregate[7,8]" internal-path-cost=640 \
    path-cost=640
4

Yes, that is bad!
Reset the device to defaults and configure it again.
You can use /export and paste it to the router, but you can NOT restore a backup from another device!

5

Sadly that could be a bit hard because it will require me to interrupt internet. What’s bad about this, except interface MAC addresses? Because the WAN is set to that MAC due to the interface must use this MAC to work with WAN.

6

You will always have such surprises as you have now, until you reset the device…

7

It’s possible a backup file from another device was loaded. Review bridge configurations, ensuring the admin MAC address matches the Ethernet MAC.

8

Hi all, @pe1chl, I have reset the router and manually reapplied all configuration, then upgraded to 7.14 now. However the issue is exactly the same, that there’s message about looped packets, and WAN resets frequently.

9

Did you set (or have set by the defaults) the admin-mac of the bridge to the MAC of the first ethernet port in that bridge?
Can you send the entire /export for interface, bridge and bridge ports?
There must be some dup MAC
Is there no other router in the network running from a backup of a different device?

10

Actually I found that when I set the admin-mac on the bridge, the resetting stops, and only getting looped packet messages at boot up. Although still puzzled and this is not optimal, at least the network works now.

Here’s the full export on interface, bridge, and bridge ports:

/interface bridge
add admin-mac=52:39:26:13:00:01 auto-mac=no igmp-snooping=yes \
    multicast-querier=yes name=brg1-lan port-cost-mode=short priority=0x1000 \
    protocol-mode=mstp querier-interval=2m5s query-interval=1m \
    vlan-filtering=yes
add admin-mac=48:A9:8A:85:C1:F6 auto-mac=no comment=\
    "Cannot change MAC, or Internet traffic will be gone." name=brg2-wan \
    port-cost-mode=short
add admin-mac=52:39:26:13:00:03 auto-mac=no igmp-snooping=yes name=\
    v-brg3-lan-utilities port-cost-mode=short protocol-mode=none
add admin-mac=52:39:26:13:00:04 auto-mac=no igmp-snooping=yes name=\
    v-brg4-lan-guest port-cost-mode=short protocol-mode=none
add admin-mac=52:39:26:13:00:05 auto-mac=no disabled=yes igmp-snooping=yes \
    name=v-brg5-lan-untagged port-cost-mode=short protocol-mode=none
add admin-mac=52:39:26:13:00:06 auto-mac=no igmp-snooping=yes name=\
    v-brg6-lan-datacenter port-cost-mode=short protocol-mode=none
/interface ethernet
set [ find default-name=ether1 ] loop-protect-disable-time=2m \
    loop-protect-send-interval=10s name=ether01
set [ find default-name=ether2 ] loop-protect-disable-time=2m \
    loop-protect-send-interval=10s name=ether02
set [ find default-name=ether3 ] loop-protect-disable-time=2m \
    loop-protect-send-interval=10s name=ether03
set [ find default-name=ether4 ] loop-protect-disable-time=2m \
    loop-protect-send-interval=10s name=ether04
set [ find default-name=ether5 ] loop-protect-disable-time=2m \
    loop-protect-send-interval=10s name=ether05
set [ find default-name=ether6 ] loop-protect-disable-time=2m \
    loop-protect-send-interval=10s name=ether06
set [ find default-name=ether7 ] loop-protect-disable-time=2m \
    loop-protect-send-interval=10s name=ether07
set [ find default-name=ether8 ] loop-protect-disable-time=2m \
    loop-protect-send-interval=10s name=ether08
set [ find default-name=ether9 ] loop-protect-disable-time=2m \
    loop-protect-send-interval=10s name=ether09
set [ find default-name=ether10 ] loop-protect-disable-time=2m \
    loop-protect-send-interval=10s
set [ find default-name=ether11 ] loop-protect-disable-time=2m \
    loop-protect-send-interval=10s
set [ find default-name=ether12 ] loop-protect-disable-time=2m \
    loop-protect-send-interval=10s
set [ find default-name=ether13 ] loop-protect-disable-time=2m \
    loop-protect-send-interval=10s
set [ find default-name=ether14 ] loop-protect-disable-time=2m \
    loop-protect-send-interval=10s
set [ find default-name=ether15 ] loop-protect-disable-time=2m \
    loop-protect-send-interval=10s
set [ find default-name=ether16 ] loop-protect-disable-time=2m \
    loop-protect-send-interval=10s
set [ find default-name=sfp-sfpplus1 ] loop-protect-disable-time=2m \
    loop-protect-send-interval=10s sfp-rate-select=low
set [ find default-name=sfp-sfpplus2 ] comment=WAN loop-protect-disable-time=\
    2m loop-protect-send-interval=10s sfp-rate-select=low
/interface 6to4
add comment="Hurricane Electric IPv6 Tunnel Broker" !keepalive local-address=\
    50.35.75.10 mtu=1280 name=sit1 remote-address=216.218.226.238
/interface vlan
add disabled=yes interface=brg1-lan name=brg1-lan-vlan0013 vlan-id=13
add interface=brg1-lan name=brg1-lan-vlan0019 vlan-id=19
add interface=brg1-lan name=brg1-lan-vlan0029 vlan-id=29
add interface=brg1-lan name=brg1-lan-vlan0059 vlan-id=59
/interface bonding
add down-delay=100ms mode=802.3ad name="aggregate[3,4]" slaves=\
    ether03,ether04 up-delay=100ms
add down-delay=100ms mode=802.3ad name="aggregate[5,6]" slaves=\
    ether05,ether06 up-delay=100ms
add down-delay=100ms mode=802.3ad name="aggregate[7,8]" slaves=\
    ether07,ether08 up-delay=100ms
/interface list
add comment=defconf name=WAN
add comment=defconf name=LAN
add comment="Specific IPv6 only WAN interface, like IPv6 Tunnel Broker" \
    include=WAN name=WANv6
    
/interface bridge port
add bridge=v-brg4-lan-guest ingress-filtering=no interface=brg1-lan-vlan0029 \
    internal-path-cost=10 path-cost=10
add bridge=v-brg3-lan-utilities ingress-filtering=no interface=\
    brg1-lan-vlan0019 internal-path-cost=10 path-cost=10
add bridge=v-brg5-lan-untagged ingress-filtering=no interface=\
    brg1-lan-vlan0013 internal-path-cost=10 path-cost=10
add bridge=v-brg6-lan-datacenter ingress-filtering=no interface=\
    brg1-lan-vlan0059 internal-path-cost=10 path-cost=10
add bridge=brg2-wan ingress-filtering=no interface=sfp-sfpplus2 \
    internal-path-cost=1280 path-cost=128
add bridge=brg1-lan ingress-filtering=no interface=sfp-sfpplus1 \
    internal-path-cost=128 path-cost=128
add bridge=brg1-lan ingress-filtering=no interface=ether10 \
    internal-path-cost=1280 path-cost=1280
add bridge=brg1-lan ingress-filtering=no interface=ether11 \
    internal-path-cost=1280 path-cost=1280
add bridge=brg1-lan ingress-filtering=no interface=ether12 \
    internal-path-cost=1280 path-cost=1280
add bridge=brg1-lan ingress-filtering=no interface=ether13 \
    internal-path-cost=1280 path-cost=1280
add bridge=brg1-lan ingress-filtering=no interface=ether14 \
    internal-path-cost=1280 path-cost=1280
add bridge=brg1-lan ingress-filtering=no interface=ether15 \
    internal-path-cost=1280 path-cost=1280
add bridge=brg1-lan ingress-filtering=no interface=ether16 \
    internal-path-cost=1280 path-cost=1280
add bridge=brg1-lan ingress-filtering=no interface=ether01 \
    internal-path-cost=1280 path-cost=1280
add bridge=brg1-lan ingress-filtering=no interface=ether02 \
    internal-path-cost=1280 path-cost=1280
add bridge=brg1-lan ingress-filtering=no interface=ether09 \
    internal-path-cost=1280 path-cost=1280
add bridge=brg1-lan interface="aggregate[3,4]" internal-path-cost=640 \
    path-cost=640
add bridge=brg1-lan interface="aggregate[5,6]" internal-path-cost=640 \
    path-cost=640
add bridge=brg1-lan interface="aggregate[7,8]" internal-path-cost=640 \
    path-cost=640
/interface bridge vlan
# ether03,ether04,ether05,ether06,ether07,ether08 not a bridge port
add bridge=brg1-lan tagged="brg1-lan,ether01,ether02,ether03,ether04,ether05,e\
    ther06,ether07,ether08,ether09,ether10,ether11,ether12,ether13,ether14,eth\
    er15,ether16,sfp-sfpplus1,aggregate[3,4],aggregate[5,6],aggregate[7,8]" \
    vlan-ids=19
# ether03,ether04,ether05,ether06,ether07,ether08 not a bridge port
add bridge=brg1-lan tagged="brg1-lan,ether01,ether02,ether03,ether04,ether05,e\
    ther06,ether07,ether08,ether09,ether10,ether11,ether12,ether13,ether14,eth\
    er15,ether16,sfp-sfpplus1,aggregate[3,4],aggregate[5,6],aggregate[7,8]" \
    vlan-ids=29
# ether03,ether04,ether05,ether06,ether07,ether08 not a bridge port
add bridge=brg1-lan tagged="brg1-lan,ether01,ether02,ether03,ether04,ether05,e\
    ther06,ether07,ether08,ether09,ether10,ether11,ether12,ether13,ether14,eth\
    er15,ether16,sfp-sfpplus1,aggregate[3,4],aggregate[5,6],aggregate[7,8]" \
    vlan-ids=59
# ether03,ether04,ether05,ether06,ether07,ether08 not a bridge port
add bridge=brg1-lan tagged="brg1-lan,ether01,ether02,ether03,ether04,ether05,e\
    ther06,ether07,ether08,ether09,ether10,ether11,ether12,ether13,ether14,eth\
    er15,ether16,sfp-sfpplus1,aggregate[3,4],aggregate[5,6],aggregate[7,8]" \
    vlan-ids=13
# ether03,ether04,ether05,ether06,ether07,ether08 not a bridge port
add bridge=brg1-lan untagged="brg1-lan,ether01,ether02,ether03,ether04,ether05\
    ,ether06,ether07,ether08,ether09,ether10,ether11,ether12,ether13,ether14,e\
    ther15,ether16,sfp-sfpplus1,aggregate[3,4],aggregate[5,6],aggregate[7,8]" \
    vlan-ids=1
/interface detect-internet
set internet-interface-list=WAN lan-interface-list=LAN wan-interface-list=WAN
/interface list member
add interface=brg2-wan list=WAN
add interface=brg1-lan list=LAN
add interface=v-brg3-lan-utilities list=LAN
add interface=v-brg4-lan-guest list=LAN
add interface=v-brg5-lan-untagged list=LAN
add interface=v-brg6-lan-datacenter list=LAN
add interface=sit1 list=WANv6
11

So to update on this, I am inclining to believe there’s something wrong with the 7.14’s RSTP implementation. Once I have switch connection events, I see a lot of log items regarding looped packets and conflict ARP, and causes switches to be blocked for a long period of time. Again, none of these makes sense, as that although I do have RSTP enabled on the network, there’s no loop to begin with.

2024-03-17 18:26:06 by RouterOS 7.14.1

03-17 13:49:38 dhcp,warning Detected conflict by ARP response for 192.168.XXX.XXX from XX:XX:XX:XX:24:74
03-17 14:49:36 dhcp,warning Detected conflict by ARP response for 192.168.XXX.XXX from XX:XX:XX:XX:24:74
03-17 15:49:37 dhcp,warning Detected conflict by ARP response for 192.168.XXX.XXX from XX:XX:XX:XX:24:74
03-17 17:49:38 dhcp,warning Detected conflict by ARP response for 192.168.XXX.XXX from XX:XX:XX:XX:24:74
03-17 17:59:12 interface,warning ether10: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:1c:82 VID 1 ETHERTYPE 0x0800 IP TCP 146.112.41.2:443 → 192.168.XXX.XXX:64969
03-17 17:59:18 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:05:6c VID 1 ETHERTYPE 0x0806
03-17 17:59:23 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:05:6c VID 1 ETHERTYPE 0x0806
03-17 17:59:28 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:09:2a VID 1 ETHERTYPE 0x0800 IP TCP 146.112.41.2:443 → 192.168.XXX.XXX:52400
03-17 17:59:33 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:05:6c VID 1 ETHERTYPE 0x0806
03-17 17:59:38 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:18:03 VID 1 ETHERTYPE 0x0800 IP PROTO 1 192.168.XXX.XXX → 192.168.XXX.XXX
03-17 17:59:45 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:09:2a VID 1 ETHERTYPE 0x0800 IP TCP 40.83.240.146:443 → 192.168.XXX.XXX:49411
03-17 18:00:59 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:34:d3 VID 1 ETHERTYPE 0x0800 IP TCP 23.20.71.198:443 → 192.168.XXX.XXX:43230
03-17 18:01:01 dhcp,warning dhcp-lan-default offering lease 192.168.XXX.XXX for XX:XX:XX:XX:34:D3 without success
03-17 18:01:01 dhcp,warning dhcp-lan-default offering lease 192.168.XXX.XXX for XX:XX:XX:XX:34:D3 without success
03-17 18:01:04 interface,warning ether10: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:e2:1a VID 1 ETHERTYPE 0x0800 IP TCP 52.96.164.210:443 → 192.168.XXX.XXX:62448
03-17 18:01:09 dhcp,warning dhcp-lan-default offering lease 192.168.XXX.XXX for XX:XX:XX:XX:1B:94 without success
03-17 18:01:09 interface,warning ether10: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:e2:1a VID 1 ETHERTYPE 0x0800 IP TCP 192.168.XXX.XXX:5357 → 192.168.XXX.XXX:62721
03-17 18:01:19 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:48:87 VID 1 ETHERTYPE 0x0800 IP TCP 44.239.134.176:443 → 192.168.XXX.XXX:41313
03-17 18:02:29 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:1c:82 VID 1 ETHERTYPE 0x0800 IP TCP 142.251.211.227:80 → 192.168.XXX.XXX:64863
03-17 18:02:30 dhcp,warning dhcp-lan-default offering lease 192.168.XXX.XXX for XX:XX:XX:XX:AB:B9 without success
03-17 18:02:35 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:09:2a VID 1 ETHERTYPE 0x0806
03-17 18:02:35 dhcp,warning dhcp-lan-default offering lease 192.168.XXX.XXX for XX:XX:XX:XX:AB:B9 without success
03-17 18:02:35 dhcp,warning dhcp-lan-default offering lease 192.168.XXX.XXX for XX:XX:XX:XX:AB:B9 without success
03-17 18:02:35 dhcp,warning dhcp-lan-default offering lease 192.168.XXX.XXX for XX:XX:XX:XX:AB:B9 without success
03-17 18:02:40 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:09:2a VID 1 ETHERTYPE 0x0800 IP TCP 146.112.41.2:443 → 192.168.XXX.XXX:55899
03-17 18:03:18 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:ff:ff VID 1 ETHERTYPE 0x0806
03-17 18:03:23 interface,warning ether10: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:90:28 VID 1 ETHERTYPE 0x0806
03-17 18:04:17 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:ff:ff VID 1 ETHERTYPE 0x0806
03-17 18:04:23 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:e2:1a VID 1 ETHERTYPE 0x0800 IP TCP 52.96.35.178:443 → 192.168.XXX.XXX:62742
03-17 18:04:48 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:00:01 VID 1 ETHERTYPE 0x86dd
03-17 18:05:56 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:ff:ff VID 1 ETHERTYPE 0x0806
03-17 18:06:02 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:48:87 VID 1 ETHERTYPE 0x0800 IP PROTO 1 1.1.1.1 → 192.168.XXX.XXX
03-17 18:06:08 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:1c:82 VID 1 ETHERTYPE 0x0800 IP UDP 192.168.XXX.XXX:67 → 192.168.XXX.XXX:68
03-17 18:06:19 interface,warning ether10: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:92:ba VID 1 ETHERTYPE 0x0806
03-17 18:07:35 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:05:6c VID 1 ETHERTYPE 0x0806
03-17 18:07:36 dhcp,warning dhcp-lan-default offering lease 192.168.XXX.XXX for XX:XX:XX:XX:2C:4C without success
03-17 18:07:36 dhcp,warning dhcp-lan-default offering lease 192.168.XXX.XXX for XX:XX:XX:XX:2C:4C without success
03-17 18:07:42 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:ff:ff VID 1 ETHERTYPE 0x0800 IP UDP 192.168.XXX.XXX:67 → 255.255.255.255:68
03-17 18:07:47 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:12:a6 VID 1 ETHERTYPE 0x0806
03-17 18:08:52 dhcp,warning dhcp-lan-default offering lease 192.168.XXX.XXX for XX:XX:XX:XX:34:D3 without success
03-17 18:08:52 dhcp,warning dhcp-lan-default offering lease 192.168.XXX.XXX for XX:XX:XX:XX:34:D3 without success
03-17 18:08:53 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:12:a6 VID 1 ETHERTYPE 0x0806
03-17 18:08:58 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:18:03 VID 1 ETHERTYPE 0x0806
03-17 18:09:03 interface,warning ether10: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:18:03 VID 1 ETHERTYPE 0x0800 IP PROTO 1 192.168.XXX.XXX → 192.168.XXX.XXX
03-17 18:09:41 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:90:28 VID 1 ETHERTYPE 0x0806
03-17 18:09:47 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:b2:21 VID 1 ETHERTYPE 0x0806
03-17 18:09:52 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:12:a6 VID 1 ETHERTYPE 0x0806
03-17 18:10:06 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:ff:ff VID 1 ETHERTYPE 0x0806
03-17 18:11:02 interface,warning ether10: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:00:01 VID 1 ETHERTYPE 0x86dd
03-17 18:11:07 interface,warning ether10: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:00:03 VID 1 ETHERTYPE 0x86dd
03-17 18:11:13 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:24:74 VID 1 ETHERTYPE 0x0800 IP TCP 3.83.206.183:443 → 192.168.XXX.XXX:53062
03-17 18:11:18 interface,warning ether10: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:0d:39 VID 1 ETHERTYPE 0x0800 IP TCP 162.159.134.234:443 → 192.168.XXX.XXX:55811
03-17 18:12:06 interface,warning ether10: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:58:a1 VID 1 ETHERTYPE 0x0800 IP UDP 192.168.XXX.XXX:28197 → 192.168.XXX.XXX:10926
03-17 18:12:56 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:1c:82 VID 1 ETHERTYPE 0x0800 IP TCP 172.64.149.13:443 → 192.168.XXX.XXX:65428
03-17 18:14:12 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:18:03 VID 1 ETHERTYPE 0x0806
03-17 18:14:17 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX:05:6c VID 1 ETHERTYPE 0x0806
03-17 18:14:25 interface,warning sfp-sfpplus1: bridge RX looped packet - MAC XX:XX:XX:XX:00:01 → XX:XX:XX:XX> :ab:> b9 VID 1 ETHERTYPE 0x0806
03-17 18:17:04 dhcp,warning dhcp-lan-default offering lease 192.168.XXX.XXX for XX:XX:XX:XX:58:A1 without success
03-17 18:17:36 dhcp,warning dhcp-lan-default offering lease 192.168.XXX.XXX for XX:XX:XX:XX:58:A1 without success
03-17 18:17:49 dhcp,warning dhcp-lan-default offering lease 192.168.XXX.XXX for XX:XX:XX:XX:2C:4C without success
03-17 18:23:08 dhcp,warning Detected conflict by ARP response for 192.168.XXX.XXX from XX:XX:XX:XX:2C:4C
03-17 18:23:08 dhcp,warning Detected conflict by ARP response for 192.168.XXX.XXX from XX:XX:XX:XX:D4:D5

12

I’m running several routers with RSTP, but for me the current “stable version” is 7.12.1
So I am not running 7.14 on any production device… only in test environments where there is no bridge.
So maybe try installing 7.12.1 and remain on that version for some time (until the many new bugs in 7.13 and 7.14 have been resolved)?

13

So it is a known issue? I have the router on 7.13.5 now which seems to be stable enough for me. I will wait for the situation to be fixed then. Thank you for the help!

14

I don’t know if it is a known issue, I only know that I do not experience it.
(and I have a similar config running under 7.12.1)