# Forward LACP in bridge?

**URL:** <https://forum.mikrotik.com/t/forward-lacp-in-bridge/122451>\
**Category:** General\
**Created:** [August 17, 2018, 7:20am UTC](https://forum.mikrotik.com/t/forward-lacp-in-bridge/122451 "2018-08-17T07:20:41Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![mhugo](https://forum.mikrotik.com/letter_avatar/mhugo/32/6_449c533f586939b6e5f246632a46421f.png) [@mhugo](https://forum.mikrotik.com/u/mhugo)\
**Post date:** [August 17, 2018, 7:20am UTC](https://forum.mikrotik.com/t/forward-lacp-in-bridge/122451/1 "2018-08-17T07:20:41Z")

</div>

Hi,

We are trying to use a CRS317 to repeat a wave that required more than 80 km laser. The customer wants us to forward LACP, but it seems the CRS is not doing it.

Is there any way I can bridge two interfaces so seamlessly that LACP is forwarded?

/M

---

<div class="post-metadata">

**Author:** ![dadaniel](https://forum.mikrotik.com/letter_avatar/dadaniel/32/6_449c533f586939b6e5f246632a46421f.png) [@dadaniel](https://forum.mikrotik.com/u/dadaniel)\
**Post date:** [August 17, 2018, 7:44am UTC](https://forum.mikrotik.com/t/forward-lacp-in-bridge/122451/2 "2018-08-17T07:44:55Z")

</div>

It seems that this is still not working after 10 years:  
[http://forum.mikrotik.com/t/redundancy-with-2-bridge-and-lacp-switchs/19196/1](http://forum.mikrotik.com/t/redundancy-with-2-bridge-and-lacp-switchs/19196/1)

---

<div class="post-metadata">

**Author:** ![artz](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/artz/32/2003_2.png) [@artz](https://forum.mikrotik.com/u/artz)\
**Post date:** [August 17, 2018, 8:03am UTC](https://forum.mikrotik.com/t/forward-lacp-in-bridge/122451/3 "2018-08-17T08:03:48Z")

</div>

This is possible by using the latest RC and protocol-mode=none.

Are you sure you want to use LACP on links that are bridged? There can be some throughput issues since LACP requires both links to be with the same speed.  
I would guess that you are trying to use Wireless links, which can change the Wireless rate at any time, you should consider using other bonding modes.

You can read about an issue that you are going to have when using Wireless links in a bond here:  
[https://wiki.mikrotik.com/wiki/Manual:Layer2\_misconfiguration#Bonding\_between\_Wireless\_links](https://wiki.mikrotik.com/wiki/Manual:Layer2_misconfiguration#Bonding_between_Wireless_links)

If you are using CRS317, which is capable of offloading to the switch chip LACP interfaces, then you will have to give up hardware support for the bonding interface because of the protocol limitations described in the link.

LACPDUs are not meant to be forwarded for a reason, take precaution when forwarding them.

---

<div class="post-metadata">

**Author:** ![mhugo](https://forum.mikrotik.com/letter_avatar/mhugo/32/6_449c533f586939b6e5f246632a46421f.png) [@mhugo](https://forum.mikrotik.com/u/mhugo)\
**Post date:** [August 17, 2018, 9:13am UTC](https://forum.mikrotik.com/t/forward-lacp-in-bridge/122451/4 "2018-08-17T09:13:20Z")

</div>

Hi,

The reason is that the optical link was too long, so im using a CRS317 to repeat the signal. It should not do anything but forward packets to the other port. I dont know if a port mirror could be used?

/M

---

<div class="post-metadata">

**Author:** ![artz](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/artz/32/2003_2.png) [@artz](https://forum.mikrotik.com/u/artz)\
**Post date:** [August 17, 2018, 11:12am UTC](https://forum.mikrotik.com/t/forward-lacp-in-bridge/122451/5 "2018-08-17T11:12:59Z")

</div>

In such case it is possible, here is an example:

```plaintext
/interface ethernet switch rule
add new-dst-ports=ether2 ports=ether1 switch=switch1

```

---

<div class="post-metadata">

**Author:** ![sindy](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/sindy/32/55716_2.png) [@sindy](https://forum.mikrotik.com/u/sindy)\
**Post date:** [August 17, 2018, 11:19am UTC](https://forum.mikrotik.com/t/forward-lacp-in-bridge/122451/6 "2018-08-17T11:19:44Z")

</div>

It couldn’t because mirroring copies both traffic directions from the source port to the destination port, but what is received on the mirror destination port gets nowhere. So yes, you need a bridge between two ports.

Assuming that you are going to use two CRS with two SFPs each to avoid a SPOF represented by a single CRS with two bonds, one looking in each direction.

---

<div class="post-metadata">

**Author:** ![anuser](https://forum.mikrotik.com/letter_avatar/anuser/32/6_449c533f586939b6e5f246632a46421f.png) [@anuser](https://forum.mikrotik.com/u/anuser)\
**Post date:** [October 8, 2018, 7:57am UTC](https://forum.mikrotik.com/t/forward-lacp-in-bridge/122451/7 "2018-10-08T07:57:31Z")

</div>

Hello,

I´m in the same situation. I updated my CRS317-1G-16S+ to 6.44beta17 and LACPPDUS are traveling through the bridge which is configured on the CRS317.  
When I login on the switches and show lldp neighbor the switches actually see the CRS317:

* * *

> **dis lldp neighbor-information list  
> System Name Local Interface Chassis ID Port ID  
> swch-047 XGE1/0/25 d894-03fc-a9a6 Ten-GigabitEthernet1/0/25 \<= LACP link1.1  
> swch-047 XGE1/0/26 d894-03fc-a9a6 Ten-GigabitEthernet1/0/26 \<= LACP link1.2  
> MikroTik XGE1/0/26 64d1-54ea-c305 bridge1**

* * *

> **/interface bridge port  
> add bridge=bridge1 comment=defconf hw=no interface=sfp-sfpplus1  
> add bridge=bridge1 comment=defconf hw=no interface=sfp-sfpplus2**

So how can I make the CRS317 truly transparent such that the switches don´t see him?

UPDATE:  
CRS317 configuration with “ARP disabled” on bridge1" and “ip neighbors” disabled for all ports helped

---

<div class="post-metadata">

**Author:** ![sindy](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/sindy/32/55716_2.png) [@sindy](https://forum.mikrotik.com/u/sindy)\
**Post date:** [October 8, 2018, 8:19am UTC](https://forum.mikrotik.com/t/forward-lacp-in-bridge/122451/8 "2018-10-08T08:19:24Z")

</div>

The way @artz has suggested in [post #5 above](http://forum.mikrotik.com/t/forward-lacp-in-bridge/122451/7) - you must use _/interface ethernet switch rule_ to forward ingress frames from port A to port B and vice versa without local processing. So also the LLDP frames, BPDU frames etc. won’t make it to the CPU but will be forwarded to the other port in the A\<-\>B pair.

---

<div class="post-metadata">

**Author:** ![anuser](https://forum.mikrotik.com/letter_avatar/anuser/32/6_449c533f586939b6e5f246632a46421f.png) [@anuser](https://forum.mikrotik.com/u/anuser)\
**Post date:** [October 8, 2018, 9:43am UTC](https://forum.mikrotik.com/t/forward-lacp-in-bridge/122451/9 "2018-10-08T09:43:11Z")

</div>

Thanks!

---

<div class="post-metadata">

**Author:** ![xtornado](https://forum.mikrotik.com/letter_avatar/xtornado/32/6_449c533f586939b6e5f246632a46421f.png) [@xtornado](https://forum.mikrotik.com/u/xtornado)\
**Post date:** [December 5, 2019, 1:53pm UTC](https://forum.mikrotik.com/t/forward-lacp-in-bridge/122451/10 "2019-12-05T13:53:11Z")

</div>

Hello

I use a crs305-1G-4S+ ,

I tried to use crs305-1G-4s+ as regeneration device , for 80+ km long fiber.

For test i have setup two crs305 on my desk.. Sfp1+Sfp2 works as pair1, Sfp3+Sfp4 work as second pair I it configured on the same way…  
On test CRS1 and CRS2 are connected over SFP1… ping beeween devices over MVlan100 (192.168.1.0/24) work fine until i get turn on switch rule:

> /interface ethernet switch rule  
> add disabled=no new-dst-ports=sfp-sfpplus1 ports=sfp-sfpplus2 switch=switch1  
> add disabled=no new-dst-ports=sfp-sfpplus2 ports=sfp-sfpplus1 switch=switch1  
> add disabled=no new-dst-ports=sfp-sfpplus3 ports=sfp-sfpplus4 switch=switch1  
> add disabled=no new-dst-ports=sfp-sfpplus4 ports=sfp-sfpplus3 switch=switch1

Its stops IP connectivity beetween ports and devices.. it not allow passing any ip traffic… not eaven beetween two CRS305… and not eaven on devices that are connected to SFP2 on both devices (two routers) , cannot ping anything..

> /interface bridge  
> add arp=disabled igmp-snooping=yes name=bridge1 protocol-mode=none vlan-filtering=yes  
> /interface ethernet  
> set [find default-name=ether1] speed=100Mbps  
> set [find default-name=sfp-sfpplus1] speed=10Gbps  
> set [find default-name=sfp-sfpplus2] speed=10Gbps  
> set [find default-name=sfp-sfpplus3] speed=10Gbps  
> set [find default-name=sfp-sfpplus4] speed=10Gbps  
> /interface vlan  
> add interface=bridge1 name=Mvlan110 vlan-id=110  
> add interface=bridge1 name=Mvlan120 vlan-id=120  
> add interface=bridge1 mtu=10200 name=vlan10 vlan-id=10  
> add interface=bridge1 mtu=10200 name=vlan20 vlan-id=20  
> /interface bridge port  
> add bridge=bridge1 interface=sfp-sfpplus1 pvid=10  
> add bridge=bridge1 interface=sfp-sfpplus2 pvid=10  
> add bridge=bridge1 interface=sfp-sfpplus3 pvid=20  
> add bridge=bridge1 interface=sfp-sfpplus4 pvid=20  
> /interface bridge vlan  
> add bridge=bridge1 tagged=bridge1 untagged=sfp-sfpplus1,sfp-sfpplus2 vlan-ids=10  
> add bridge=bridge1 tagged=bridge1 untagged=sfp-sfpplus3,sfp-sfpplus4 vlan-ids=20  
> add bridge=bridge1 tagged=bridge1,sfp-sfpplus1,sfp-sfpplus2 vlan-ids=110  
> add bridge=bridge1 tagged=bridge1,sfp-sfpplus1,sfp-sfpplus2 vlan-ids=120  
> /interface ethernet switch rule  
> add disabled=yes new-dst-ports=sfp-sfpplus1 ports=sfp-sfpplus2 switch=switch1  
> add disabled=yes new-dst-ports=sfp-sfpplus2 ports=sfp-sfpplus1 switch=switch1  
> add disabled=yes new-dst-ports=sfp-sfpplus3 ports=sfp-sfpplus4 switch=switch1  
> add disabled=yes new-dst-ports=sfp-sfpplus4 ports=sfp-sfpplus3 switch=switch1  
> /ip address  
> add address=192.168.88.1/24 interface=ether1 network=192.168.88.0  
> add address=192.168.1.2/24 interface=Mvlan110 network=192.168.1.0  
> /ip ssh  
> set allow-none-crypto=yes forwarding-enabled=remote  
> /system clock  
> set time-zone-name=Europe/Zagreb  
> /system identity  
> set name=test2  
> /system routerboard settings  
> set boot-os=router-os

Can someone knows what is the problem in this config?  
I need a LACP forwarding beetween ports and i need that l3 traffic works over the same ports..

Thx  
Best regards

---

<div class="post-metadata">

**Author:** ![anuser](https://forum.mikrotik.com/letter_avatar/anuser/32/6_449c533f586939b6e5f246632a46421f.png) [@anuser](https://forum.mikrotik.com/u/anuser)\
**Post date:** [April 2, 2025, 2:47pm UTC](https://forum.mikrotik.com/t/forward-lacp-in-bridge/122451/11 "2025-04-02T14:47:11Z")

</div>

I was still on 7.10 on my CRS317 switches and upgraded to 7.18.2. Well, traffic doesn´t pass the bridge any longer with old config. All counters stay at “0”.

Is there any parameter I have to additionally change in order to get it working again?

(In the meantime I downgraded to 7.11.x where traffic passes the bridge without any problems)

---

<div class="post-metadata">

**Author:** ![EdPa](https://forum.mikrotik.com/letter_avatar/edpa/32/6_449c533f586939b6e5f246632a46421f.png) [@EdPa](https://forum.mikrotik.com/u/EdPa)\
**Post date:** [April 3, 2025, 2:53pm UTC](https://forum.mikrotik.com/t/forward-lacp-in-bridge/122451/12 "2025-04-03T14:53:46Z")

</div>

It will be related to this change in 7.16:

\*) bridge - added forward-reserved-addresses property which controls forwarding of MAC 01:80:C2:00:00:0x range (separated from “protocol-mode=none” functionality, disabled by default after upgrade);

See the docs  
[https://help.mikrotik.com/docs/spaces/ROS/pages/328068/Bridging+and+Switching#BridgingandSwitching-BridgeInterfaceSetup](https://help.mikrotik.com/docs/spaces/ROS/pages/328068/Bridging+and+Switching#BridgingandSwitching-BridgeInterfaceSetup)

---

<div class="post-metadata">

**Author:** ![anuser](https://forum.mikrotik.com/letter_avatar/anuser/32/6_449c533f586939b6e5f246632a46421f.png) [@anuser](https://forum.mikrotik.com/u/anuser)\
**Post date:** [April 4, 2025, 9:02am UTC](https://forum.mikrotik.com/t/forward-lacp-in-bridge/122451/13 "2025-04-04T09:02:21Z")

</div>

> [@](#):
>
> It will be related to this change in 7.16:
> 
> \*) bridge - added forward-reserved-addresses property which controls forwarding of MAC 01:80:C2:00:00:0x range (separated from “protocol-mode=none” functionality, disabled by default after upgrade);
> 
> See the docs  
> [https://help.mikrotik.com/docs/spaces/ROS/pages/328068/Bridging+and+Switching#BridgingandSwitching-BridgeInterfaceSetup](https://help.mikrotik.com/docs/spaces/ROS/pages/328068/Bridging+and+Switching#BridgingandSwitching-BridgeInterfaceSetup)

That did it. It works again. Thank you.

---

<div class="post-metadata">

**Author:** ![anuser](https://forum.mikrotik.com/letter_avatar/anuser/32/6_449c533f586939b6e5f246632a46421f.png) [@anuser](https://forum.mikrotik.com/u/anuser)\
**Post date:** [November 20, 2026, 11:31am UTC](https://forum.mikrotik.com/t/forward-lacp-in-bridge/122451/14 "2026-11-20T11:31:16Z")

</div>

I recently discovered that offloading does not work at all for the bridge traffic. I upgraded to CRS510 and use SFP25 ports

I see traffic going through

- sfp28-7
- sfp28-8
- switch1-cpu =\> Counter "Drop Packet" goes up

With ~ 500 Mbit/s of throughput CPU shows values up to 100%.

What am I missing currently?

> /interface ethernet switch port  
> set sfp28-7 !egress-rate !ingress-rate l3-hw-offloading=yes limit-broadcasts=yes limit-unknown-multicasts=no limit-unknown-unicasts=no mirror-egress=no mirror-ingress=no storm-rate=100  
> set sfp28-8 !egress-rate !ingress-rate l3-hw-offloading=yes limit-broadcasts=yes limit-unknown-multicasts=no limit-unknown-unicasts=no mirror-egress=no mirror-ingress=no storm-rate=100

> /interface bridge settings  
> set allow-fast-path=yes use-ip-firewall=no use-ip-firewall-for-pppoe=no use-ip-firewall-for-vlan=no

> /interface ethernet switch l3hw-settings  
> set autorestart=yes fasttrack-hw=yes icmp-reply-on-error=yes ipv6-hw=yes  
> /interface ethernet switch l3hw-settings advanced  
> set neigh-discovery-burst-delay=300ms neigh-discovery-burst-limit=64 neigh-discovery-interval=1m37s neigh-dump-retries=3 neigh-keepalive-interval=15s partial-offload-chunk=1024 route-index-delay-max=10s route-index-delay-min=1s  
> route-queue-limit-high=256 route-queue-limit-low=0 shwp-reset-counter=128

> /ip neighbor discovery-settings  
> set add-dns-entries=no add-dns-entries-suffix=lan discover-interface-list=!none discover-interval=30s dying-gasp=no lldp-dcbx=yes lldp-mac-phy-config=no lldp-max-frame-size=no lldp-med=yes lldp-med-net-policy-vlan=disabled lldp-poe-in-power=  
> yes lldp-vlan-info=no mode=tx-and-rx protocol=cdp,lldp,mndp

> set [find default-name=sfp28-7] advertise=10M-baseT-half,10M-baseT-full,100M-baseT-half,100M-baseT-full,1G-baseT-half,1G-baseT-full,1G-baseX,2.5G-baseT,2.5G-baseX,5G-baseT,10G-baseT,10G-baseSR-LR,10G-baseCR,25G-baseSR-LR,25G-baseCR arp=  
> enabled arp-accept=no arp-timeout=auto auto-negotiation=yes bandwidth=unlimited/unlimited disabled=no fec-mode=auto l2mtu=10218 loop-protect=default loop-protect-disable-time=5m loop-protect-send-interval=5s mac-address=04:F4:1C:15:26:39  
> mtu=10218 name=sfp28-7 orig-mac-address=04:F4:1C:15:26:39 rx-flow-control=off sfp-ignore-rx-los=no sfp-rate-select=high sfp-shutdown-temperature=95C tx-flow-control=off  
> set [find default-name=sfp28-8] advertise=10M-baseT-half,10M-baseT-full,100M-baseT-half,100M-baseT-full,1G-baseT-half,1G-baseT-full,1G-baseX,2.5G-baseT,2.5G-baseX,5G-baseT,10G-baseT,10G-baseSR-LR,10G-baseCR,25G-baseSR-LR,25G-baseCR arp=  
> enabled arp-accept=no arp-timeout=auto auto-negotiation=yes bandwidth=unlimited/unlimited disabled=no fec-mode=auto l2mtu=10218 loop-protect=default loop-protect-disable-time=5m loop-protect-send-interval=5s mac-address=04:F4:1C:15:26:3A  
> mtu=10218 name=sfp28-8 orig-mac-address=04:F4:1C:15:26:3A rx-flow-control=off sfp-ignore-rx-los=no sfp-rate-select=high sfp-shutdown-temperature=95C tx-flow-control=off

> /queue interface  
> set sfp28-7 queue=only-hardware-queue  
> set sfp28-8 queue=only-hardware-queue  
> /interface ethernet switch  
> set switch1 l3-hw-offloading=yes mirror-target=none name=switch1 qos-hw-offloading=yes rspan=no rspan-egress-vlan-id=1 rspan-ingress-vlan-id=1

> /interface bridge  
> add ageing-time=5m arp=disabled arp-timeout=auto auto-mac=yes !dhcp-agent-circuit-id !dhcp-agent-remote-id dhcp-snooping=no !dhcpv6-agent-circuit-id !dhcpv6-agent-remote-id dhcpv6-snooping=no disabled=yes fast-forward=yes  
> forward-reserved-addresses=yes igmp-snooping=no max-learned-entries=auto mlag-heartbeat=5s mlag-init-delay=1m mlag-lacp-fallback=yes mlag-peer-port=none mlag-priority=128 mtu=auto name=bridge-2 port-cost-mode=long  
> protocol-mode=none ra-guard=no vlan-filtering=no  
> /queue interface  
> set bridge1 queue=no-queue  
> set lo queue=no-queue  
> set bridge-2 queue=no-queue  
> /interface bridge port  
> add auto-isolate=no bpdu-guard=no bridge=bridge1 broadcast-flood=yes disabled=no edge=auto fast-leave=no frame-types=admit-all horizon=none hw=yes ingress-filtering=no interface=sfp28-7 !internal-path-cost learn=auto multicast-router=  
> disabled mvrp-applicant-state=normal-participant mvrp-registrar-state=normal !path-cost point-to-point=auto priority=0x80 pvid=1 restricted-role=no restricted-tcn=no tag-stacking=no trusted=no trusted-arp=no trusted-dhcpv6=no trusted-ra=  
> no unknown-multicast-flood=yes unknown-unicast-flood=yes  
> add auto-isolate=no bpdu-guard=no bridge=bridge1 broadcast-flood=yes disabled=no edge=auto fast-leave=no frame-types=admit-all horizon=none hw=yes ingress-filtering=no interface=sfp28-8 !internal-path-cost learn=auto multicast-router=  
> disabled mvrp-applicant-state=normal-participant mvrp-registrar-state=normal !path-cost point-to-point=auto priority=0x80 pvid=1 restricted-role=no restricted-tcn=no tag-stacking=no trusted=no trusted-arp=no trusted-dhcpv6=no trusted-ra=  
> no unknown-multicast-flood=yes unknown-unicast-flood=yes  
> /interface ethernet switch rule  
> add copy-to-cpu=no disabled=no !dscp !dst-address !dst-address6 !dst-mac-address !dst-port !flow-label !mac-protocol mirror=yes !new-dst-ports !new-qos-profile !new-vlan-id !new-vlan-priority !new-vrf ports=sfp28-7,sfp28-8 !protocol !rate  
> redirect-to-cpu=no !src-address !src-address6 !src-mac-address !src-port switch=switch1 !traffic-class !vlan-header !vlan-id !vlan-priority  
> add copy-to-cpu=no disabled=no !dscp !dst-address !dst-address6 !dst-mac-address !dst-port !flow-label !mac-protocol mirror=yes !new-dst-ports !new-qos-profile !new-vlan-id !new-vlan-priority !new-vrf ports=sfp28-8,sfp28-7 !protocol !rate  
> redirect-to-cpu=no !src-address !src-address6 !src-mac-address !src-port switch=switch1 !traffic-class !vlan-header !vlan-id !vlan-priority  
> /ip traffic-flow  
> set active-flow-timeout=30m cache-entries=32k enabled=no inactive-flow-timeout=15s interfaces=all packet-sampling=no sampling-interval=0 sampling-space=0
> 
> ![grafik](https://data-discourse.cdn.mikrotik.com/original/3X/1/3/13d879c614121fcc61bce0e41cced641dff925d9.png)

 ![grafik](https://data-discourse.cdn.mikrotik.com/original/3X/e/c/ec736fa9678abe8afe4ccb9656653241d89b5821.png)

 ![grafik](https://data-discourse.cdn.mikrotik.com/original/3X/e/c/ec3daaa2cf57e935714cc5004a509258e122ea8d.png)

"H" for offloading

 ![grafik](https://data-discourse.cdn.mikrotik.com/original/3X/9/6/966238ad3bbcd25f12ca3eb630c776a9c04c892c.png)
