What's new

[How-To] Link Aggregation/LACP on RT-AC68U/W/R/P

  • Thread starter Deleted member 28123
  • Start date
  • 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!

not trying to hijack this thread, but, has anyone been able to confirm or deny that the AC-3200 is capable link aggregation using this LinkAgg script? I have tried without success to get it working, script says bonding complete using either ports 1 2 or 3 4 but when set the switch appears to crash as it is no longer visible in gui's network map (none of the wired connections show regardless of port).
 
Hello! I've read through the thread but am confused on what set of commands I should use for my AC-87U.

My ISP sends both IPTV and Internet traffic over a single RJ45 port from the Fibre Terminal. This is currently configured on the AC87U as the ISP profile, Singtel-Others. (IPTV = VLAN 20, Prio 4 ; Internet = VLAN 10, Prio 0). IPTV on LAN4.

I bought a Netgear JGS524Ev2 switch which has support for 802.3ad link aggregation and am looking to have ports 1 and 2 on the AC87U teamed to ports 1 and 2 on the JGS524Ev2. How should I go about this?
 
Hello! I've read through the thread but am confused on what set of commands I should use for my AC-87U.

My ISP sends both IPTV and Internet traffic over a single RJ45 port from the Fibre Terminal. This is currently configured on the AC87U as the ISP profile, Singtel-Others. (IPTV = VLAN 20, Prio 4 ; Internet = VLAN 10, Prio 0). IPTV on LAN4.

I bought a Netgear JGS524Ev2 switch which has support for 802.3ad link aggregation and am looking to have ports 1 and 2 on the AC87U teamed to ports 1 and 2 on the JGS524Ev2. How should I go about this?

I also want to know.
 
not trying to hijack this thread, but, has anyone been able to confirm or deny that the AC-3200 is capable link aggregation using this LinkAgg script? I have tried without success to get it working, script says bonding complete using either ports 1 2 or 3 4 but when set the switch appears to crash as it is no longer visible in gui's network map (none of the wired connections show regardless of port).

I'd also like to know if anyone has got the LACP/LAG to work on 3200 too!
 
I can't seem to get this working between my Asus RT-AC68U and my Cisco SG300 switch. According to the Web UI of the SG300 Link Aggregation (LACP) should be active with one port as active and the other as standby.

But I get no communication between the router and the switch and running cat /proc/net/bonding/bond0 gives me this;

Ethernet Channel Bonding Driver: v3.7.0 (June 2, 2010)

Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer3+4 (1)
MII Status: down
MII Polling Interval (ms): 50
Up Delay (ms): 0
Down Delay (ms): 0

802.3ad info
LACP rate: fast
Aggregator selection policy (ad_select): stable
bond bond0 has no active aggregator
 
Hello; I would like to connect the AC68 to a switch that has 4 upload lines. (TP-LINK TL-SG3424)
Reading through this thread I've not seen someone post a configuration for all 4 lines have LAG for a 4GB connection. I do understand that a 4GB LAG is overkill for anything I'm doing now, however is it possible with this AC68?

The new house I bought has been pre wired with every room have x2 Coax and x2 Ethernet. I plan to wire the Ethernet connects (16) into the TP Link Managed Switch. From this thread getting 2 LAG ports up and running would be just fine. Our area will be moving to 1gigabit internet soon. I would like to have the full internet speed coming in, along with full wireless speed, going to multiple clients.

Thoughts?
 
I am having similar problems with LACP my ASUS on merlin's newest 380.67_beta2 and my Synology DS1513+. At some point in the past, it was working but I, unfortunately, do not know when it stopped. It could have been months due to recent work travel. Hopefully, you guys can offer similar assistance if possible.

MY SETUP
ASUS RT-AC5300 - Teaming is built in on ports LAN1 and LAN2
Firmware - Merlin 380.67 Beta 2
Synology DiskStation 1513+ - Also using ports LAN1 and LAN2
All cables are cat6 and tested working

I have gone through a slew of attempts to get this working again with no success. I have tried stock firmware, the custom teaming scripts for merlins firmware, tried remapping ports for different LAN jacks, etc. Before I came here, I have completely reset the router with latest ASUS firmware and then moved to Merlins latest 380.67.

------------------------------------------------
ASUS SETTINGS/OUTPUT
------------------------------------------------
#
ASUSWRT-Merlin RT-AC5300
admin@ASUS:/# ifconfig -a
agg Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet6 addr: fe80::200:ff:fe00:0/128 Scope:Link
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

bond0 Link encap:Ethernet HWaddr 34:97:F6:6F:A6:40
inet6 addr: fe80::3697:f6ff:fe6f:a640/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:31415 errors:0 dropped:0 overruns:0 frame:0
TX packets:66431 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:19741168 (18.8 MiB) TX bytes:11681270 (11.1 MiB)

br0 Link encap:Ethernet HWaddr 34:97:F6:6F:A6:40
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::3697:f6ff:fe6f:a640/64 Scope:Link
inet6 addr: 2601:XXX:XXXX:XXXX::X/64 Scope:Global
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:203374 errors:0 dropped:0 overruns:0 frame:0
TX packets:199980 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:38622948 (36.8 MiB) TX bytes:134852394 (128.6 MiB)

dpsta Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet6 addr: fe80::200:ff:fe00:0/128 Scope:Link
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

eth0 Link encap:Ethernet HWaddr 34:97:F6:6F:A6:40
inet addr:XXX.XXX.XXX.XXX Bcast:XXX.XXX.XXX.XXX Mask:XXX.XXX.XXX.XXX
inet6 addr: XXXX:XXX:XXXX:XX:XXXX:XXXX:XXXX:XXXX/128 Scope:Global
inet6 addr: fe80::3697:f6ff:fe6f:a640/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1566454 errors:0 dropped:0 overruns:0 frame:0
TX packets:1587756 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1250603064 (1.1 GiB) TX bytes:1252601676 (1.1 GiB)
Interrupt:181 Base address:0x6000

eth1 Link encap:Ethernet HWaddr 34:97:F6:6F:A6:40
inet6 addr: fe80::3697:f6ff:fe6f:a640/64 Scope:Link
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6204 errors:0 dropped:2 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:1217638 (1.1 MiB)

eth2 Link encap:Ethernet HWaddr 34:97:F6:6F:A6:44
inet6 addr: fe80::3697:f6ff:fe6f:a644/64 Scope:Link
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6194 errors:0 dropped:2 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:1216876 (1.1 MiB)

eth3 Link encap:Ethernet HWaddr 34:97:F6:6F:A6:48
inet6 addr: fe80::3697:f6ff:fe6f:a648/64 Scope:Link
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6916 errors:0 dropped:1 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:1321869 (1.2 MiB)

fwd0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING PROMISC ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:7880 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:179 Base address:0x4000

fwd1 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING PROMISC ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:8500 errors:0 dropped:0 overruns:0 frame:0
TX packets:5005 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:1450002 (1.3 MiB)
Interrupt:180 Base address:0x5000

ifb0 Link encap:Ethernet HWaddr 9E:06:96:0D:9F:E1
inet6 addr: fe80::9c06:96ff:fe0d:9fe1/128 Scope:Link
BROADCAST NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

ifb1 Link encap:Ethernet HWaddr 56:F3:C7:2B:96:48
inet6 addr: fe80::54f3:c7ff:fe2b:9648/128 Scope:Link
BROADCAST NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MULTICAST MTU:16436 Metric:1
RX packets:10249 errors:0 dropped:0 overruns:0 frame:0
TX packets:10249 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2269771 (2.1 MiB) TX bytes:2269771 (2.1 MiB)

vlan1 Link encap:Ethernet HWaddr 34:97:F6:6F:A6:40
inet6 addr: fe80::3697:f6ff:fe6f:a640/64 Scope:Link
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:585607 errors:0 dropped:0 overruns:0 frame:0
TX packets:237047 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:80514372 (76.7 MiB) TX bytes:155531971 (148.3 MiB)

vlan2 Link encap:Ethernet HWaddr 34:97:F6:6F:A6:40
inet6 addr: fe80::3697:f6ff:fe6f:a640/128 Scope:Link
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

vlan3 Link encap:Ethernet HWaddr 34:97:F6:6F:A6:40
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:7940 errors:0 dropped:0 overruns:0 frame:0
TX packets:8923 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3697423 (3.5 MiB) TX bytes:1584075 (1.5 MiB)

vlan4 Link encap:Ethernet HWaddr 34:97:F6:6F:A6:40
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:23475 errors:0 dropped:0 overruns:0 frame:0
TX packets:57508 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:16043745 (15.2 MiB) TX bytes:10097195 (9.6 MiB)
 
....ASUS CONTINUED

admin@ASUS:/# robocfg show
Switch: enabled
Port 0: 1000FD enabled stp: none vlan: 2 jumbo: off mac: 00:01:5c:9e:72:46
Port 1: 1000FD enabled stp: none vlan: 3 jumbo: off mac: 00:11:32:1e:90:9b
Port 2: 1000FD enabled stp: none vlan: 4 jumbo: off mac: 00:11:32:1e:90:9b
Port 3: 1000FD enabled stp: none vlan: 1 jumbo: off mac: 70:4d:7b:28:63:e8
Port 4: 1000FD enabled stp: none vlan: 1 jumbo: off mac: 24:0a:64:77:8c:73
Port 8: 1000FD enabled stp: none vlan: 1 jumbo: off mac: 34:97:f6:6f:a6:40
VLANs: BCM5301x enabled mac_check mac_hash
1: vlan1: 3 4 8t
2: vlan2: 0 8u
3: vlan3: 1 8t
4: vlan4: 2 8t
#
#
#
admin@ASUS:/# brctl show
bridge name bridge id STP enabled interfaces
br0 8000.3497f66fa640 yes vlan1
bond0
#
#
#
admin@ASUS:/# cat /proc/net/vlan/config
VLAN Dev name | VLAN ID
Name-Type: VLAN_NAME_TYPE_PLUS_VID_NO_PAD
vlan1 | 1 | eth0
vlan2 | 2 | eth0
vlan3 | 3 | eth0
vlan4 | 4 | eth0
#
#
#
admin@ASUS:/# ifconfig | grep Link
bond0 Link encap:Ethernet HWaddr 34:97:F6:6F:A6:40
inet6 addr: fe80::3697:f6ff:fe6f:a640/64 Scope:Link
br0 Link encap:Ethernet HWaddr 34:97:F6:6F:A6:40
inet6 addr: fe80::3697:f6ff:fe6f:a640/64 Scope:Link
eth0 Link encap:Ethernet HWaddr 34:97:F6:6F:A6:40
inet6 addr: fe80::3697:f6ff:fe6f:a640/64 Scope:Link
eth1 Link encap:Ethernet HWaddr 34:97:F6:6F:A6:40
inet6 addr: fe80::3697:f6ff:fe6f:a640/64 Scope:Link
eth2 Link encap:Ethernet HWaddr 34:97:F6:6F:A6:44
inet6 addr: fe80::3697:f6ff:fe6f:a644/64 Scope:Link
eth3 Link encap:Ethernet HWaddr 34:97:F6:6F:A6:48
inet6 addr: fe80::3697:f6ff:fe6f:a648/64 Scope:Link
fwd0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
fwd1 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
lo Link encap:Local Loopback
vlan1 Link encap:Ethernet HWaddr 34:97:F6:6F:A6:40
inet6 addr: fe80::3697:f6ff:fe6f:a640/64 Scope:Link
vlan3 Link encap:Ethernet HWaddr 34:97:F6:6F:A6:40
vlan4 Link encap:Ethernet HWaddr 34:97:F6:6F:A6:40
#
#
#
admin@ASUS:/# nvram show | sort | grep vlan
size: 77330 bytes (53742 left)
lan_ifnames=vlan1 eth1 eth2 eth3
landevs=vlan1 wl0 wl1 wl2
vlan1hwname=et2
vlan1ports=1 2 3 4 5 7 8*
vlan2hwname=et2
vlan2ports=0 8u
wl0_vlan_prio_mode=off
wl1_vlan_prio_mode=off
wl2_vlan_prio_mode=off
wl_vlan_prio_mode=off
#
#
#
admin@ASUS:/# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.7.0 (June 2, 2010)

Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer2 (0)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

802.3ad info
LACP rate: fast
Aggregator selection policy (ad_select): stable
Active Aggregator Info:
Aggregator ID: 1
Number of ports: 1
Actor Key: 5
Partner Key: 1
Partner Mac Address: 00:00:00:00:00:00

Slave Interface: vlan3
MII Status: up
Link Failure Count: 0
Permanent HW addr: 34:97:f6:6f:a6:40
Aggregator ID: 2
Slave queue ID: 0

Slave Interface: vlan4
MII Status: up
Link Failure Count: 0
Permanent HW addr: 34:97:f6:6f:a6:40
Aggregator ID: 1
Slave queue ID: 0
 
-------------
DISKSTATION
-------------
#
COMMANDS
ifconfig -a
brctl show
ifconfig | grep Link
cat /proc/net/bonding/bond0
#
admin@DiskStation:~$ ifconfig -a
bond0 Link encap:Ethernet HWaddr 00:11:32:1E:90:9B
inet addr:192.168.0.170 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::211:32ff:fe1e:909b/64 Scope:Link
inet6 addr: 2601:XXX:XXXX:XXXX:XXX:XXXX:XXXX:XXXX/64 Scope:Global
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:2982281 errors:0 dropped:0 overruns:0 frame:0
TX packets:4632497 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3261936911 (3.0 GiB) TX bytes:6245636498 (5.8 GiB)

bond1 Link encap:Ethernet HWaddr 00:11:32:1E:90:9D
inet addr:192.168.0.171 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::211:32ff:fe1e:909d/64 Scope:Link
inet6 addr: 2601:XXX:XXXX:XXXX:XXX:XXXX:XXXX:XXXX/64 Scope:Global
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:6025089 errors:0 dropped:0 overruns:0 frame:0
TX packets:8958389 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6125519883 (5.7 GiB) TX bytes:10149734111 (9.4 GiB)

eth0 Link encap:Ethernet HWaddr 00:11:32:1E:90:9B
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:15807 errors:0 dropped:0 overruns:0 frame:0
TX packets:19121 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3006817 (2.8 MiB) TX bytes:11300676 (10.7 MiB)

eth1 Link encap:Ethernet HWaddr 00:11:32:1E:90:9B
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:2966474 errors:0 dropped:0 overruns:0 frame:0
TX packets:4613376 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3258930094 (3.0 GiB) TX bytes:6234335822 (5.8 GiB)

eth2 Link encap:Ethernet HWaddr 00:11:32:1E:90:9D
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:4457963 errors:0 dropped:0 overruns:0 frame:0
TX packets:4314720 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6002637183 (5.5 GiB) TX bytes:5521612643 (5.1 GiB)

eth3 Link encap:Ethernet HWaddr 00:11:32:1E:90:9E
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:1567127 errors:0 dropped:0 overruns:0 frame:0
TX packets:4643670 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:122884070 (117.1 MiB) TX bytes:4628121522 (4.3 GiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:10162 errors:0 dropped:0 overruns:0 frame:0
TX packets:10162 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1409245 (1.3 MiB) TX bytes:1409245 (1.3 MiB)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
#
#
#
admin@DiskStation:~$ brctl show
bridge name bridge id STP enabled interfaces
#
#
#
admin@DiskStation:~$ ifconfig | grep Link
bond0 Link encap:Ethernet HWaddr 00:11:32:1E:90:9B
inet6 addr: fe80::211:32ff:fe1e:909b/64 Scope:Link
bond1 Link encap:Ethernet HWaddr 00:11:32:1E:90:9D
inet6 addr: fe80::211:32ff:fe1e:909d/64 Scope:Link
eth0 Link encap:Ethernet HWaddr 00:11:32:1E:90:9B
eth1 Link encap:Ethernet HWaddr 00:11:32:1E:90:9B
eth2 Link encap:Ethernet HWaddr 00:11:32:1E:90:9D
eth3 Link encap:Ethernet HWaddr 00:11:32:1E:90:9E
lo Link encap:Local Loopback
 
...DiskStation Continued

admin@DiskStation:~$ cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer2 (0)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 100
Down Delay (ms): 0

802.3ad info
LACP rate: fast
Min links: 0
Aggregator selection policy (ad_select): stable
Active Aggregator Info:
Aggregator ID: 1
Number of ports: 1
Actor Key: 17
Partner Key: 1
Partner Mac Address: 00:00:00:00:00:00

Slave Interface: eth0
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:11:32:1e:90:9b
Aggregator ID: 1
Slave queue ID: 0

Slave Interface: eth1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:11:32:1e:90:9c
Aggregator ID: 2
Slave queue ID: 0

Thank you!!!!
 
Sorry everyone, I am beginner, I open putty & access,but how to edit the script?
"Step 2 - Create/Edit services-start script

Include the following code in services-start script located in /jffs/scripts/ (you will need to create this file from scratch, if you haven't done so already, with the right permissions)"

what is from scratch?is it a program?
after this use WinSCP copy to router?

thanks so much for everyone.
 
Hello,

Is there a way to create 2 aggregated connections? e.g. one on ports 1 & 2 and second on 3 & 4 so that I can have 2 NAS devices that could communicate with each other on 10GbE?
 
Is there a way to create 2 aggregated connections? e.g. one on ports 1 & 2 and second on 3 & 4 so that I can have 2 NAS devices that could communicate with each other on 10GbE?
I don't know. But if it were possible you'd only get 2Gbps for each aggregated link not 10Gbps.
 
I successfully setup a 2-port link aggregation between RT-AC68U (with the latest firmware 384.4) and QNAP NAS (firmware v4.3.4.0516) by following the method 2 of the asus merlin wiki (Ref 1).
QNAP recommends using Layer 2+3 (MAC+IP) hash. So, I change the services-start script as follows (no other modification is made).

Code:
echo 2 > /sys/class/net/bond0/bonding/xmit_hash_policy ip link set bond0 up

No performance impact on WAN speed is observed. All other functions appear normal.
In the process, I learn more about the inner working of my router ports (Ref 3, 4 & 5)!

Thx for making all this information available online!! Nice job!

References:
1. Merlin Wiki
https://github.com/RMerl/asuswrt-merlin/wiki/Link-Aggregation

2. QNAP Port Trunking
https://www.qnap.com/en/how-to/tuto...o-increase-the-bandwidth-via-802-3ad-protocol

3. VLAN & Bridging Concepts
http://aming-blog.blogspot.hk/2010/10/understanding-network-interfaces.html

4. Switched Ports
https://www.dd-wrt.com/wiki/index.php/Switched_Ports

5. User-scripts
https://github.com/RMerl/asuswrt-merlin/wiki/User-scripts
 
Thx for making all this information available online!! Nice job!

You're welcome.

@gekko44 I don't believe it would work without modifying /etc/modprobe.conf which requires changes to the source ie. add modprobe to postconf feature with the following appended to modprobe.conf

Code:
alias bond0 bonding
alias bond1 bonding

Reason: calling 'modprobe bonding' manually adds a single bond0 interface and you require 2 bond interfaces. Furthermore, firmware's modprobe command lacks -o option support which is used to load multiple bonds ie. modprobe bonding -obond1 .. So setting multiple bonds manually is out of the question without changes to the firmware's source.

Your best bet is to connect those 2 NASes via LACP enabled links to a LACP-capable switch and connect the switch via LACP enabled links to the router.
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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

Members online

Top