What's new

LACP on AC87

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

initrd

Occasional Visitor
Hi,

Is anyone successful on getting LACP to work on AC87 ?

I am trying to run the script in

https://github.com/RMerl/asuswrt-merlin/wiki/Link-Aggregation

I am able to create bond successfully:

ASUSWRT-Merlin RT-AC87U_3.0.0.4 Sun Jul 27 01:36:11 UTC 2014
admin@RT-AC87R-22E0:/tmp/home/root# /jffs/scripts/LinkAgg 3 4

Bond Created Successfully

However, when I connect it to my switch, the router goes crazy and becomes unresponsive, the 5G is affected and goes to channel 0

Here is the dmesg output:


device vlan1 entered promiscuous mode
device eth0 entered promiscuous mode
device eth1 entered promiscuous mode
br0: topology change detected, propagating
br0: port 2(eth1) entering forwarding state
br0: port 2(eth1) entering forwarding state
br0: topology change detected, propagating
br0: port 1(vlan1) entering forwarding state
br0: port 1(vlan1) entering forwarding state

gro enabled with interval 2
nf_conntrack_rtsp v0.6.21 loading
nf_nat_rtsp v0.6.21 loading
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
ADDRCONF(NETDEV_UP): tun21: link is not ready
device tun21 entered promiscuous mode
ADDRCONF(NETDEV_CHANGE): tun21: link becomes ready
bonding: Ethernet Channel Bonding Driver: v3.7.0 (June 2, 2010)
bonding: Warning: either miimon or arp_interval and arp_ip_target module parameters must be specified, otherwise bonding will not detect link failures! see bonding.txt for details.
bonding: bond0: setting mode to 802.3ad (4).
bonding: bond0: Setting LACP rate to fast (1).
ADDRCONF(NETDEV_UP): bond0: link is not ready
8021q: adding VLAN 0 to HW filter on device bond0
bonding: bond0: Setting MII monitoring interval to 100.
bonding: bond0: Adding slave vlan3.
bonding: bond0: enslaving vlan3 as a backup interface with an up link.
bonding: bond0: Adding slave vlan4.
bonding: bond0: enslaving vlan4 as a backup interface with an up link.
device bond0 entered promiscuous mode
device vlan3 entered promiscuous mode
device vlan4 entered promiscuous mode
ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
br0: topology change detected, propagating
br0: port 3(bond0) entering forwarding state
br0: port 3(bond0) entering forwarding state
br0: port 2(eth1) entering forwarding state
device eth1 left promiscuous mode
br0: port 2(eth1) entering disabled state
wl_module_init: passivemode set to 0x0
wl_module_init: txworkq set to 0x1
eth1: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.86 (r456083)
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
device eth1 entered promiscuous mode
br0: topology change detected, propagating
br0: port 2(eth1) entering forwarding state
br0: port 2(eth1) entering forwarding state
net_ratelimit: 16387 callbacks suppressed
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
net_ratelimit: 29620 callbacks suppressed
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
net_ratelimit: 23805 callbacks suppressed
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
net_ratelimit: 23953 callbacks suppressed
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
net_ratelimit: 21095 callbacks suppressed
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
net_ratelimit: 20954 callbacks suppressed
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
net_ratelimit: 20153 callbacks suppressed
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
br0: received packet on vlan1 with own address as source address
......


:(:(:(

__initrd
 
that script was designed for the N66U afaik, it will need to be modified for your ac87

ie, the physical ports for your router are probably something like:

0 1 2 3 - 4 - 5, logically
1 2 3 4 - WAN - 5 (cpu), physical

whereas that script was designed for mips with

1 2 3 4 - 0 - 8, logically for
1 2 3 4 - WAN - 8, physical
 
Thanks Sinshiva.

Could you please do a little more hand holding ? :D Could you please let me know what changes i need to do ?

Thanks
__Initrd
 
Try using port 1 and 2. Port 4 is actually on a separate internal switch.
 
yeah, I created the script for AC66U mips

might be a good idea to reboot, and leave the ports untouched
then run
Code:
robocfg show

that way you can see how the router is set up to begin with
 
Try using port 1 and 2. Port 4 is actually on a separate internal switch.


Tried using 1 & 2, the router does not go bonkers but LACP does not work and 5G drops (Attached screenshot)
 

Attachments

  • 5G_Drop.pdf
    62.6 KB · Views: 228
Last edited:
yeah, I created the script for AC66U mips

might be a good idea to reboot, and leave the ports untouched
then run
Code:
robocfg show

that way you can see how the router is set up to begin with

ASUSWRT-Merlin RT-AC87U_3.0.0.4 Sun Jul 27 01:36:11 UTC 2014
admin@RT-AC87R-22E0:/tmp/home/root# robocfg show
Switch: enabled
Port 0: 1000FD enabled stp: none vlan: 2 jumbo: off mac: xx:xx:xx:xx:xx:xx
Port 1: DOWN enabled stp: none vlan: 1 jumbo: off mac: 00:00:00:00:00:00
Port 2: DOWN enabled stp: none vlan: 1 jumbo: off mac: 00:00:00:00:00:00
Port 3: DOWN enabled stp: none vlan: 1 jumbo: off mac: 00:00:00:00:00:00
Port 4: DOWN enabled stp: none vlan: 1 jumbo: off mac: 00:00:00:00:00:00
Port 8: 1000FD enabled stp: none vlan: 1 jumbo: off mac: xx:xx:xx:xx:xx:xx
VLANs: BCM5301x enabled mac_check mac_hash
1: vlan1: 1 2 3 5 8t
2: vlan2: 0 8t
1045: vlan1045: 0t 2 4 5t 7 8u
1046: vlan1046: 0 1 2t 3
1047: vlan1047: 0t 1 2 3 7t 8t
1099: vlan1099: 1t 7
1100: vlan1100: 1t 5t 7 8t
1101: vlan1101: 1 2t 4t 7t 8u
1102: vlan1102: 3 4 5 7t 8t
1103: vlan1103: 5t 8t


admin@RT-AC87R-22E0:/tmp/home/root# /jffs/scripts/LinkAgg 1 2

Bond Created Successfully

admin@RT-AC87R-22E0:/tmp/home/root# robocfg show
Switch: enabled
Port 0: 1000FD enabled stp: none vlan: 2 jumbo: off mac: XX:XX:XX:XX:XX
Port 1: DOWN enabled stp: none vlan: 3 jumbo: off mac: 00:00:00:00:00:00
Port 2: DOWN enabled stp: none vlan: 4 jumbo: off mac: 00:00:00:00:00:00
Port 3: DOWN enabled stp: none vlan: 1 jumbo: off mac: 00:00:00:00:00:00
Port 4: DOWN enabled stp: none vlan: 1 jumbo: off mac: 00:00:00:00:00:00
Port 8: 1000FD enabled stp: none vlan: 1 jumbo: off mac: XX:XX:XX:XX:XX
VLANs: BCM5301x enabled mac_check mac_hash
1: vlan1: 3 4 8t
2: vlan2: 0 8t
3: vlan3: 1 8t
4: vlan4: 2 8t
1045: vlan1045: 0t 2 4 5t 7 8u
1046: vlan1046: 0 1 2t 3
1047: vlan1047: 0t 1 2 3 7t 8t
1099: vlan1099: 1t 7
1100: vlan1100: 1t 5t 7 8t
1101: vlan1101: 1 2t 4t 7t 8u
1102: vlan1102: 3 4 5 7t 8t
1103: vlan1103: 5t 8t
 
Tried using 1 & 2, the router does not go bonkers but LACP does not work and 5G drops (Attached screenshot)

If 5G drops then it means port 3 and 4 are actually the correct ones to use.
 
yeah, I created the script for AC66U mips

might be a good idea to reboot, and leave the ports untouched
then run
Code:
robocfg show

that way you can see how the router is set up to begin with

The RT-AC87U is a special case. One of the four ports is actually from the Quantenna SoC, and won't be properly reported by either "et" or "robocfg".
 
it could be something to due with which ports are tagged, and which are not, etc ...

of with the Quantenna piece of the puzzle, this might not be easy

I'd still recommend running robocfg show
so at least you have part of the picture
then maybe RMerlin knows how to find the quantenna bits of info

the script makes some assumptions of tagged and untagged ports, vlan handling etc ...
 
it could be something to due with which ports are tagged, and which are not, etc ...

of with the Quantenna piece of the puzzle, this might not be easy

I'd still recommend running robocfg show
so at least you have part of the picture
then maybe RMerlin knows how to find the quantenna bits of info

the script makes some assumptions of tagged and untagged ports, vlan handling etc ...

ASUSWRT-Merlin RT-AC87U_3.0.0.4 Sun Jul 27 01:36:11 UTC 2014
admin@RT-AC87R-22E0:/tmp/home/root# robocfg show
Switch: enabled
Port 0: 1000FD enabled stp: none vlan: 2 jumbo: off mac: xx:xx:xx:xx:xx:xx
Port 1: DOWN enabled stp: none vlan: 1 jumbo: off mac: 00:00:00:00:00:00
Port 2: DOWN enabled stp: none vlan: 1 jumbo: off mac: 00:00:00:00:00:00
Port 3: DOWN enabled stp: none vlan: 1 jumbo: off mac: 00:00:00:00:00:00
Port 4: DOWN enabled stp: none vlan: 1 jumbo: off mac: 00:00:00:00:00:00
Port 8: 1000FD enabled stp: none vlan: 1 jumbo: off mac: xx:xx:xx:xx:xx:xx
VLANs: BCM5301x enabled mac_check mac_hash
1: vlan1: 1 2 3 5 8t
2: vlan2: 0 8t
1045: vlan1045: 0t 2 4 5t 7 8u
1046: vlan1046: 0 1 2t 3
1047: vlan1047: 0t 1 2 3 7t 8t
1099: vlan1099: 1t 7
1100: vlan1100: 1t 5t 7 8t
1101: vlan1101: 1 2t 4t 7t 8u
1102: vlan1102: 3 4 5 7t 8t
1103: vlan1103: 5t 8t


admin@RT-AC87R-22E0:/tmp/home/root# /jffs/scripts/LinkAgg 1 2

Bond Created Successfully

admin@RT-AC87R-22E0:/tmp/home/root# robocfg show
Switch: enabled
Port 0: 1000FD enabled stp: none vlan: 2 jumbo: off mac: XX:XX:XX:XX:XX
Port 1: DOWN enabled stp: none vlan: 3 jumbo: off mac: 00:00:00:00:00:00
Port 2: DOWN enabled stp: none vlan: 4 jumbo: off mac: 00:00:00:00:00:00
Port 3: DOWN enabled stp: none vlan: 1 jumbo: off mac: 00:00:00:00:00:00
Port 4: DOWN enabled stp: none vlan: 1 jumbo: off mac: 00:00:00:00:00:00
Port 8: 1000FD enabled stp: none vlan: 1 jumbo: off mac: XX:XX:XX:XX:XX
VLANs: BCM5301x enabled mac_check mac_hash
1: vlan1: 3 4 8t
2: vlan2: 0 8t
3: vlan3: 1 8t
4: vlan4: 2 8t
1045: vlan1045: 0t 2 4 5t 7 8u
1046: vlan1046: 0 1 2t 3
1047: vlan1047: 0t 1 2 3 7t 8t
1099: vlan1099: 1t 7
1100: vlan1100: 1t 5t 7 8t
1101: vlan1101: 1 2t 4t 7t 8u
1102: vlan1102: 3 4 5 7t 8t
1103: vlan1103: 5t 8t
 
First thing I notice, my god there's a lot of vlan's on this device

ok next
see normal
1: vlan1: 1 2 3 5 8t
2: vlan2: 0 8t

but after running script
1: vlan1: 3 4 8t
2: vlan2: 0 8t
3: vlan3: 1 8t
4: vlan4: 2 8t


But it probably should be
1: vlan1: 3 5 8t
2: vlan2: 0 8t
3: vlan3: 1 8t
4: vlan4: 2 8t

I also suspect something quantanna related is probably needed as well
I'm not going to be editing the script for this, but you can look through it and easily see what's happening

1. selected ports are removed from vlan1
2. create separate vlan for each port selected
3. create bond
4. set up permissions
 
Those bogus VLANs at the bottom don't exist. It's just that I don't know a way to properly validate if VLANs actually exist on the 5011x switch.
 
Thanks KAD, Merlin.

I tried various combinations to enable lacp and dint succeed :-( Dunno if I need to return this and go for an AC68. Before I do that could you guys please let me know iff its possible to have lacp on this routers ??? I can wait and try more if its possible.....

__init
 
is it possible on this device? I don't know. I don't have one to test with

I can tell you for sure, than unless you modify my script, the script will not work on this device

the script assumes the ports are 1 2 3 4 8t
but your device is 1 2 3 5 8t

I suspect LACP might work on ports 1 & 2
but to do it correctly, you'll have to do all the set up manually
 
Thanks KAD, Merlin.

I tried various combinations to enable lacp and dint succeed :-( Dunno if I need to return this and go for an AC68. Before I do that could you guys please let me know iff its possible to have lacp on this routers ??? I can wait and try more if its possible.....

If I were you I'd be patient. Look at what's written between the number 1 and 2 of the port numbers at the back of your RT-AC87U - that's probably something still in Asus's pipeline.
 
that's right, you mentioned that before

I'm interested to see if asus does anything with that
and if they choose to backport any of it to older devices
 
Update on LAG/LACP/802.3ad on RT-AC87U...

Hi everyone, any updates on 802.3ad on the RT-AC87U? I tried asking the local support office and those level 1 tools do not even know what 802.3ad is, much less know that their products do or don't support it... :(
 
Similar threads
Thread starter Title Forum Replies Date
D Solved Samba, LACP & WireGuard. Question. Asuswrt-Merlin 5
D Solved Lacp Asuswrt-Merlin 11

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top