netdev - Re: [Bridge] [RFC 0/5] bridge - introduce via_phys

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090512172136.GC12820@lenovo>
Date:	Tue, 12 May 2009 21:21:36 +0400
From:	Cyrill Gorcunov <gorcunov@...il.com>
To:	Daniel Robbins <drobbins@...too.org>
Cc:	Stephen Hemminger <shemminger@...ux-foundation.org>,
	netdev@...r.kernel.org, bridge@...ts.linux-foundation.org,
	davem@...emloft.net, xemul@...nvz.org
Subject: Re: [Bridge] [RFC 0/5] bridge - introduce via_phys_dev feature

[Daniel Robbins - Tue, May 12, 2009 at 11:07:14AM -0600]
| On Tue, May 12, 2009 at 10:24 AM, Cyrill Gorcunov <gorcunov@...il.com> wrote:
| > So, Daniel, i think the right question is -- do I ever need to
| > configure/setup bridge remotely? I suppose yes, it happens.
| > (at least I had a machine with lack of input device except a few
| >  NICs :-)
| 
| Aha, yes it would be useful in that case :)
| 
| So is the idea that you use via_phys_dev *temporarily* when
| configuring the bridge, then you get it set up the way you want, and
| then maybe you reboot the machine, and this time leave via_phys_dev
| off? Or are there certain cases you can envision where you might want
| this enabled permanently?

You could turn this feature on while configuring bridge, then as only
you have done all you need you just turn it off and bridge back to its
regular behaviour (and remote connection lost of course). So no need
for reboot. At moment sysfs entry is added and ioctls as well (though
bridge utils need some change to support new ioctls).

Permanently... it could be usefull if you initially planned to have remote
access to bridge-master machine. Ie instead to set up IP for bridge
device you remain with master device IP (say eth0).

| 
| > This feature already was in OpenVZ 2.6.24 kernel. I'm more intiresting in
| > usefulness of this feature for the mainline. (in short -- we use it for bridging
| > VEs with eth0 as a master device so all works without needing to
| > reconfigure routing table). Moreover, since bridge already support
| > namespacing the feature could be usefull for lxc as well (though
| > didn't check to be fair).
| 
| But not in the OpenVZ 2.6.27-briullov kernel yet, at least the one I'm
| running :)

it's just a quiestion of time :)

| 
| > That is why it's RFC so people could decide should it be included
| > into mainline or not. Worth it so or not.
| 
| If it is accepted into mainline, be sure to send Stephen some
| documentation on this feature so he can add it to the net:bridge docs.
| When features like this aren't documented, no one knows how to use
| them. I just ran into this issue with the 2.6.27+ "sticky" bridge MAC
| feature. I'd also be willing to help keeping the bridge docs
| up-to-date. Please let me know if you or Stephen want me to do this.
| Bridging is really important for OpenVZ and other
| container/paravirtualization technologies so keeping docs up-to-date
| is becoming more important. It can be useful to have a
| non-kernel-developer like me document the functionality.

Of course, though with my english better to not touch docs :)

But again -- this series requires _strong_ review and testing
(since I'm not a netdevel expert)

| 
| Best Regards,
| 
| Daniel
| 
	-- Cyrill
--
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