Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== LXC - Profiles - Create a macvlan profile ======

===== Create the macvlan manually =====

<code bash>
lxc profile create macvlan
</code>

returns:

<code bash>
Profile macvlan created
</code>

----

===== List the profiles =====

<code bash>
lxc profile list
</code>

returns:

<code bash>
+------------+---------+
| NAME       | USED BY |
+------------+---------+
| default    | 3       |
+------------+---------+
| macvlan    | 0       |
+------------+---------+
</code>

<WRAP info>
**NOTE:**  This now shows the newly created **macvlan** profile as well.
</WRAP>


----

===== Show default settings of the new profile =====

<code bash>
lxc profile show macvlan
</code>

returns:

<code bash>
config: {}
description: ""
devices: {}
name: macvlan
used_by: []
</code>

----

===== Determine Default Network Route =====

Determine the default IP network on the host.

<code bash>
ip route show default 0.0.0.0/0
</code>

returns:

<code bash>
default via 192.168.1.1 dev br0 proto static
</code>

<WRAP info>
**NOTE:**  This shows the default Network Device is **br0**.
</WRAP>


----

===== Add the Network Device to the macvlan LXD profile =====

<code bash>
lxc profile device add macvlan eth0 nic nictype=macvlan parent=br0
</code>

returns:

<code bash>
Device eth0 added to macvlan
</code>

<WRAP info>
**NOTE**:  The changes are:

  * **eth0** is added as the network interface for LXC.
  * **nictype** is set to macvlan
  * **parent** is set to br0.

</WRAP>

----

===== Display details of the new macvlan profile =====

<code bash>
lxc profile show macvlan
</code>

returns:

<code bash>
config: {}
description: ""
devices:
  eth0:
    nictype: macvlan
    parent: br0
    type: nic
name: macvlan
used_by: []
</code>

----

All Done!

Any containers created using this new profile will get an IP address from the DHCP server of the LAN.

<WRAP important>
**WARNING**:  By using macvlan, your computer’s network interface will appear on the network to have more than one MAC address.

This is fine for Ethernet networks.

However, if your interface is a Wireless interface (with security like WPA/WPA2), then the access point will reject any other MAC addresses coming from your computer.

Therefore, all these will not work in that specific case.

</WRAP>

<WRAP info>
**NOTE**:  If your host is in a virtual machine, then it is likely that the VM software will block the DHCP requests of the containers.

To overcome this, configure the host virtual machine to allow **Promiscuous mode**, usually found in Network settings.

Alternatively, try to use a **bridgeprofile**.

</WRAP>

----