netdev - more findings/questions on vlans/bonds

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Tue, 7 Apr 2009 12:14:46 +0300 (IDT)
From:	Or Gerlitz <ogerlitz@...taire.com>
To:	Jay Vosburgh <fubar@...ibm.com>
cc:	netdev@...r.kernel.org
Subject: more findings/questions on vlans/bonds

Hi Jay,

I hope that you can help clarify what's the correct/supported method
to work with vlans and bonds, with 2.6.29 I see that one can either

	- vlan a bond (bond0.4001 over bond0 over eth0/1.4001)
	- bond vlans (e.g bond0 over eth0/1.4001)

I played a bit with bonding vlans (2.6.29 active-backup mode) and it
doesn't seem to work - specifically, I noted that bonding doesn't issue
fail-over after I changed the current slave link status to down ("ifconfig
eth0.4001 down"). I suspect that the carrier based link monitoring scheme
is broken wrt to vlan devices - e.g I found that at least from sysfs
perspective the vlan device carrier isn't available:

$ cat /sys/class/net/eth0.4001/carrier
cat: /sys/class/net/eth0.4001/carrier: Invalid argument

I also played with a post 2.6.29 cut of Linus tree, and I couldn't bond vlans.
I thought that the reason may be that a vlan device has already master -
but I found out that its wrong and vlans don't have the IFF_SLAVE bit set
in their flags bit mask. So this may be either something wrong on my side
or a bug introduced after 2.6.29 or just something which isn't supported,
e.g following my findings with 2.6.29 above...

Or.
--
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