From: Jonathan Thibault <jonathan@navigue.com>
To: netdev@vger.kernel.org
Cc: Francois Romieu <romieu@fr.zoreil.com>
Subject: Bonding/LACP on RTL8169sc/8110sc (R1869)
Date: Tue, 12 Apr 2011 09:35:20 -0400 [thread overview]
Message-ID: <4DA45518.60407@navigue.com> (raw)
Greetings all,
I have a a pair of Jetway motherboards with an add-on 3Gbit LAN modules
and have been doing some testing for a linux router project. I found
that I while I can get LACP working properly using eth0 and eth1, using
the exact same setup with any of the other three lan fails. Is this a
known issue?
This is on Linux 2.6.32.10. Here is a blurb of dmesg showing the NICs
detected.
eth0: RTL8168b/8111b at 0xf8adc000, 00:30:18:ac:a6:80, XID 0c200000 IRQ 24
eth1: RTL8168b/8111b at 0xf8ae0000, 00:30:18:ac:a6:81, XID 0c200000 IRQ 25
eth2: RTL8169sc/8110sc at 0xf8ae4c00, 00:30:18:ae:34:3a, XID 18000000 IRQ 18
eth3: RTL8169sc/8110sc at 0xf8ae8800, 00:30:18:ae:34:3b, XID 18000000 IRQ 19
eth4: RTL8169sc/8110sc at 0xf8aec400, 00:30:18:ae:34:3c, XID 18000000 IRQ 16
I can probably manage this project using only eth0 and eth1 in LACP
configuration but I figured I'd give a heads up.
The interfaces seem able to detect when the link is up or down, bonding
removes and adds them to the LACP trunk but I can't get traffic through
them.
Kind regards,
Jonathan
next reply other threads:[~2011-04-12 13:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 13:35 Jonathan Thibault [this message]
2011-04-12 22:47 ` Bonding/LACP on RTL8169sc/8110sc (R1869) Jay Vosburgh
2011-04-13 17:49 ` François Romieu
2011-04-13 18:28 ` Ben Hutchings
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DA45518.60407@navigue.com \
--to=jonathan@navigue.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).