netdev - Re: [Sk-drivers] sky2 bonding problem, 802.3ad

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 16 Feb 2007 12:34:10 -0800
From:	Jay Vosburgh <fubar@...ibm.com>
To:	Holger Eitzenberger <holger@...eitzenberger.de>
cc:	netdev@...r.kernel.org, sk-drivers@...ts.linux-foundation.org
Subject: Re: [Sk-drivers] sky2 bonding problem, 802.3ad 

Holger Eitzenberger <holger@...eitzenberger.de> wrote:

>Holger Eitzenberger <holger@...eitzenberger.de> writes:
>
>>  bonding: ad_tx_machine() 1210: Sent LACPDU on port 1
>>  bonding: bond_3ad_rx_indication() 2175: Received LACPDU on port 1
>>  bonding: ad_rx_machine() 1123: Rx Machine: Port=1, Last State=6, Curr
>>    State=6
>
>One important point I forgot about in my previous post: the host
>receives LACPDUs, but still the bond does not work.
>
>Also note that the other e1000 bond works happily: it is in fact the
>link which I use to configure it currently (via telnet).

	Can you send me (off list, I'm thinking) the full bonding debug
dmesg log as well as a tcpdump trace of the LACP exchange (i.e., the
case that LACPDUs are both sent and received)?  The raw tcpdump
("tcpdump -w somefile") is better than the formatted text output.

	I don't have either of the pieces of hardware you're using (the
switch or the sky2 card), so I'm hoping there will be some gleaming
nuggets of evidence in the logs.

	-J

---
	-Jay Vosburgh, IBM Linux Technology Center, fubar@...ibm.com
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html