this is the desired setup
eth1 -> br0 -> (vlans split out here) net.br1
eth1 is external physical interface
br0 is the bridged trunk (so I can attach tap devices and connect them to VMs as the trunk)
br0.2 is the bridge for vlan2 (which I can attach VMs to via tap interfaces)
I've noticed that I can't use this config (notice the vconfig_br0 line is commented out in this one, meaning the interface created by vconfig should be named br0.1).
This config also does not work because vconfig creates interfaces with a '.' meaning that 'config_br0.1' will not work.
brctl_br0="setfd 0 sethello 0 stp off"
This config (the line is uncommented meaning vconfig should create an interface named vlan1, this does not happen)
This config will not work because even with the vconfig line uncomented (the interface created should be named vlan1) the interface is still named br0.1
brctl_br0="setfd 0 sethello 0 stp off"
the best solution to this would be to allow interface names with dots in them (as vconfig is set up to do by default). A stopgap is to figure out why config2 does not work (why doesn't it create the vlan1 interface instead of br0.1)
here is the output of trying to start net.br0.1, just to be clear about the variable assignment error.
/etc/init.d/../conf.d/net: line 23: config_br0.1=null: command not found
broken in stable as well btw :D
I spoke with Matthew about this bug. He sited the handbook  as why he
thought this configuration should work. This is definitely out of date,
and we keep the information up to date in
What do you think we should do wrt this handbook section since we update
this ourselves in the OpenRC distribution? Should we write a man page
which we install for oldnet?
Created attachment 327642 [details]
config that works
The handbook explicitly covers that '.' in an interface name must be converted to an underscore.
"Important: For using some bridge setups, you may need to consult the variable name documentation."
And that's a link to this: http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4&chap=2#variable_name
So, you didn't read the handbook enough.
That said, I think we need to get the manpages online, and link to them from the handbook, instead of maintaining two separate copies of the documentation.
I've CC'd the docs team for their input on handling this best.
read the page, but missed this line.
The downside of all this is that Gentoo uses bash variables for networking - and bash cannot use anything outside of English alpha-numerics. To get around this limitation we change every character that is not an English alpha-numeric into a _ character.
was searching for '.' my fault :D
(In reply to comment #5)
> That said, I think we need to get the manpages online, and link to them from
> the handbook, instead of maintaining two separate copies of the
> I've CC'd the docs team for their input on handling this best.
That still seems to be maintaining two separate copies of the documentation (the local man pages and the online ones).
What do people think about having the handbook refer people to the appropriate man pages on their systems?
(In reply to comment #7)
> What do people think about having the handbook refer people to the
> appropriate man pages on their systems?
I want an online copy of the manpage, built from the source tree, to be linked from the handbook, so it can be linked to directly online, and easily viewed from other systems.
Whats the primary source of the manual page (assuming you don't write nroff directly)? Docbook?
It's not manpage yet.
It's just this file
(In reply to comment #10)
> It's not manpage yet.
> It's just this file
Shouldn't we also include net.example.BSD.in and find the differences between them etc if we are going to come up with an oldnet guide?
The BSD one was mostly a subset last I checked.
*** Bug 441990 has been marked as a duplicate of this bug. ***
nothing to do with the docs-team, as it's about upstream changes for an obsolete version; removing us from CC.
I think this is fixed, aka config works?