Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
L
lxc
Project
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Chen Yisong
lxc
Commits
3e5c2e69
Commit
3e5c2e69
authored
Apr 03, 2019
by
tomponline
Committed by
Thomas Parrott
Jul 11, 2019
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
doc: Documents the lxc.net.[i].veth.mode option
Signed-off-by:
Thomas Parrott
<
thomas.parrott@canonical.com
>
parent
6dfa9581
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
21 additions
and
2 deletions
+21
-2
api-extensions.md
doc/api-extensions.md
+9
-0
lxc.container.conf.sgml.in
doc/lxc.container.conf.sgml.in
+11
-2
api_extensions.h
src/lxc/api_extensions.h
+1
-0
No files found.
doc/api-extensions.md
View file @
3e5c2e69
...
...
@@ -96,3 +96,12 @@ This is primarily intended for use with layer 3 networking devices, such as IPVL
This introduces the ability to specify a custom MTU for
`phys`
and
`macvlan`
devices using the
`lxc.net.[i].mtu`
property.
# network\_veth\_router
This introduces the ability to specify a
`lxc.net.[i].veth.mode`
setting, which takes a value of
"bridge" or "router". This defaults to "bridge".
In "router" mode static routes are created on the host for the container's IP addresses pointing to
the host side veth interface. In addition to the routes, a static IP neighbour proxy is added to
the host side veth interface for the IPv4 and IPv6 gateway IPs.
doc/lxc.container.conf.sgml.in
View file @
3e5c2e69
...
...
@@ -443,14 +443,23 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
<para>
<option>veth:</option> a virtual ethernet pair
device is created with one side assigned to the container
and the other side attached to a bridge specified by
and the other side on the host.
<option>lxc.net.[i].veth.mode</option> specifies the
mode the veth parent will use on the host.
The accepted modes are <option>bridge</option> and <option>router</option>.
The mode defaults to bridge if not specified.
In <option>bridge</option> mode the host side is attached to a bridge specified by
the <option>lxc.net.[i].link</option> option.
If the bridge is not specified, then the veth pair device
If the bridge
link
is not specified, then the veth pair device
will be created but not attached to any bridge.
Otherwise, the bridge has to be created on the system
before starting the container.
<command>lxc</command> won't handle any
configuration outside of the container.
In <option>router</option> mode static routes are created on the host for the
container's IP addresses pointing to the host side veth interface.
Additionally Proxy ARP and Proxy NDP entries are added on the host side veth interface
for the gateway IPs defined in the container to allow the container to reach the host.
By default, <command>lxc</command> chooses a name for the
network device belonging to the outside of the
container, but if you wish to handle
...
...
src/lxc/api_extensions.h
View file @
3e5c2e69
...
...
@@ -49,6 +49,7 @@ static char *api_extensions[] = {
"network_l2proxy"
,
"network_gateway_device_route"
,
"network_phys_macvlan_mtu"
,
"network_veth_router"
,
};
static
size_t
nr_api_extensions
=
sizeof
(
api_extensions
)
/
sizeof
(
*
api_extensions
);
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment