Summary: | sys-apps/openrc-0.11.2 does not allow vlans and bridges to be used together | ||
---|---|---|---|
Product: | Gentoo Hosted Projects | Reporter: | Matthew Thode ( prometheanfire ) <prometheanfire> |
Component: | netifrc | Assignee: | netifrc Team <netifrc> |
Status: | CONFIRMED --- | ||
Severity: | major | CC: | axiator, rwhite |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | netifrc:DOC | ||
Package list: | Runtime testing required: | --- | |
Attachments: | config that works |
Description
Matthew Thode ( prometheanfire )
2012-10-28 05:43:46 UTC
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 @robbat2: I spoke with Matthew about this bug. He sited the handbook [1] as why he thought this configuration should work. This is definitely out of date, and we keep the information up to date in /usr/share/doc/openrc*/net.example. 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? [1] http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4&chap=3 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 > documentation. > > 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 http://git.overlays.gentoo.org/gitweb/?p=proj/openrc.git;a=blob;f=doc/net.example.Linux.in;h=70ae4e92d432766aecaec1d037a881cb146ba4c9;hb=HEAD (In reply to comment #10) > It's not manpage yet. > It's just this file > http://git.overlays.gentoo.org/gitweb/?p=proj/openrc.git;a=blob;f=doc/net. > example.Linux.in;h=70ae4e92d432766aecaec1d037a881cb146ba4c9;hb=HEAD @robbat2: 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? |