[Bug 305333] New: Bridge and bridge port ifup order
https://bugzilla.novell.com/show_bug.cgi?id=305333 Summary: Bridge and bridge port ifup order Product: openSUSE 10.3 Version: Beta 2 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jfunk@funktronics.ca QAContact: qa@suse.de Found By: --- I have a rather complex network setup, so I will just list the relevant parts: eth - Physical ethernet interface, connected to a vlan trunk vlan4 - VLAN 4, on eth dot23 - A bridge containing vlan4 and my default route It appears that the network init script brings up non-physical interfaces alphabetically, so it will bring these devices in the following order: eth dot23 vlan4 Since vlan4 doesn't exist when dot23 is brought up, it is never added to the bridge, and I have to manually add it or restart the bridge. One way to solve this, of course, is to make the init script bring up any interfaces listed in BRIDGE_PORTS before bringing up the bridge. Another way is to also define port membership in the port ifcfg files. This is actually something I have been doing for a long while now with a custom {ifup,ifdown}-bridgeport script in /etc/sysconfig/network/scripts, which I will attach. Basically, I use Qemu and OpenVPN quite a bit, and I usually want them bridged to one place to another automatically. I configure them to create tap devices, with descriptive names (when you have 16 or more active interfaces at any one time, descriptive helps :-). I then create an ifcfg file like so: BOOTPROTO='none' NAME='Some Qemu Instance External Interface' STARTMODE='auto' USERCONTROL='yes' POST_UP_SCRIPT='ifup-bridgeport' PRE_DOWN_SCRIPT='ifdown-bridgeport' BRIDGENAME='dot23' If I called it ifcfg-foo and had Qemu create a tap device called foo, It would automatically be bridged to vlan4 on creation. This setup has been working quite well for me, and it would be nice if similar functionality were available in openSUSE by default. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=305333#c1 --- Comment #1 from James Oakley <jfunk@funktronics.ca> 2007-08-28 08:23:24 MST --- Created an attachment (id=160316) --> (https://bugzilla.novell.com/attachment.cgi?id=160316) ifup-bridgeport -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=305333 Cyril Hrubis <chrubis@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |zoz@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=305333#c2 Christian Zoz <zoz@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mt@novell.com --- Comment #2 from Christian Zoz <zoz@novell.com> 2007-08-31 05:04:52 MST --- First, as a workaround, name your bridge interface 'xdot23' that comes after vlan in alphabet. Yes, this all might be improved. Currently you cannot set up a bridge with hot-plugged bridge ports. Beeing able to do that, would solve your problem as well. I wont change anything regarding this in 10.3, because i have no time left to implement and test that properly. After 10.3 we could think about that. But that is not up to me, because the network scripts will then have a new maintainer. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=305333 User mt@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=305333#c5 Marius Tomaschewski <mt@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #5 from Marius Tomaschewski <mt@novell.com> 2008-01-18 00:50:52 MST --- The start/stop order should be fixed in sysconfig-0.70.4 in openSUSE_Factory: http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/suse/i5... The support for tun/tap interfaces follows. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=305333 User mt@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=305333#c6 Marius Tomaschewski <mt@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |jfunk@funktronics.ca --- Comment #6 from Marius Tomaschewski <mt@novell.com> 2008-01-18 01:15:28 MST --- In attachment 190961 you can find the /etc/init.d/network script extracted from sysconfig-0.70.4, can you test if it works for you please? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=305333 User jfunk@funktronics.ca added comment https://bugzilla.novell.com/show_bug.cgi?id=305333#c7 James Oakley <jfunk@funktronics.ca> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|jfunk@funktronics.ca | --- Comment #7 from James Oakley <jfunk@funktronics.ca> 2008-01-18 08:56:53 MST --- Yes, this new network script works great. I renamed both of my vlan bridges (s/^x//) and everything comes up in the proper order. What about automatic addition of dynamic interfaces to bridges? This is very useful for tap devices created by OpenVPN and Qemu. I can continue using my custom if{up,down}-bridgeport script, but it would be nice to see the functionality in stock openSUSE. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=305333 User mt@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=305333#c8 --- Comment #8 from Marius Tomaschewski <mt@novell.com> 2008-01-18 09:14:30 MST --- (In reply to comment #7 from James Oakley)
Yes, this new network script works great. I renamed both of my vlan bridges (s/^x//) and everything comes up in the proper order.
What about automatic addition of dynamic interfaces to bridges?
It is already on my TODO for 11.0, together with the tun/tap support (I _need_ it too ;-) Previews will be available in home:mtomaschewski:sysconfig project in the build service (build.opensuse.org). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=305333 User ast@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=305333#c9 --- Comment #9 from Anja Stock <ast@novell.com> 2008-04-11 04:00:11 MST --- released -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=305333 User mt@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=305333#c13 Marius Tomaschewski <mt@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #13 from Marius Tomaschewski <mt@novell.com> 2009-02-13 10:11:08 MST --- see comment #9, fixed & released. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com