Hello
I would like to have assigned the IP address of PVE Host by the DHCP server.
This is the configuration of /etc/network/interfaces:
When I launch my container, I get this messages in the logs:
Aug 16 21:24:35 pve3 systemd[1]: Created slice system-lxc.slice.
Aug 16 21:24:35 pve3 systemd[1]: Starting LXC Container: 100...
Aug 16 21:24:36 pve3 kernel: [ 112.136640] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null)
Aug 16 21:24:36 pve3 systemd-udevd[1389]: Could not generate persistent MAC address for vethI3L0F5: No such file or directory
Aug 16 21:24:36 pve3 kernel: [ 112.177930] IPv6: ADDRCONF(NETDEV_UP): veth100i0: link is not ready
Aug 16 21:24:36 pve3 kernel: [ 112.528805] vmbr0: port 1(veth100i0) entered blocking state
Aug 16 21:24:36 pve3 kernel: [ 112.528807] vmbr0: port 1(veth100i0) entered disabled state
Aug 16 21:24:36 pve3 kernel: [ 112.528862] device veth100i0 entered promiscuous mode
Aug 16 21:24:36 pve3 kernel: [ 112.592601] eth0: renamed from vethI3L0F5
Aug 16 21:24:36 pve3 systemd[1]: Started LXC Container: 100.
Aug 16 21:24:36 pve3 pvedaemon[1174]: <root@pam> end task UPID
ve3:0000053C:00002BB0:59951A83:vzstart:100:root@pam: OK
Aug 16 21:24:37 pve3 kernel: [ 113.140955] vmbr0: port 1(veth100i0) entered blocking state
Aug 16 21:24:37 pve3 kernel: [ 113.140956] vmbr0: port 1(veth100i0) entered forwarding state
The container starts but has not IPV4 network.
I do not have a preference between the default configuration suggested in the docs or one with routed IPs.
What modifications does the network configuration needs to work? I want the IP address of the be assigned by the DHCP server.
I would like to have assigned the IP address of PVE Host by the DHCP server.
This is the configuration of /etc/network/interfaces:
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eno1
iface eno1 inet dhcp
post-up echo 1 > /proc/sys/net/ipv4/conf/eno1/proxy_arp
# For virtual machines and containers
auto vmbr0
iface vmbr0 inet manual
gateway 172.17.0.1
bridge_ports none
bridge_stp off
bridge_fd 0
iface lo inet loopback
# The primary network interface
allow-hotplug eno1
iface eno1 inet dhcp
post-up echo 1 > /proc/sys/net/ipv4/conf/eno1/proxy_arp
# For virtual machines and containers
auto vmbr0
iface vmbr0 inet manual
gateway 172.17.0.1
bridge_ports none
bridge_stp off
bridge_fd 0
When I launch my container, I get this messages in the logs:
Aug 16 21:24:35 pve3 systemd[1]: Created slice system-lxc.slice.
Aug 16 21:24:35 pve3 systemd[1]: Starting LXC Container: 100...
Aug 16 21:24:36 pve3 kernel: [ 112.136640] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null)
Aug 16 21:24:36 pve3 systemd-udevd[1389]: Could not generate persistent MAC address for vethI3L0F5: No such file or directory
Aug 16 21:24:36 pve3 kernel: [ 112.177930] IPv6: ADDRCONF(NETDEV_UP): veth100i0: link is not ready
Aug 16 21:24:36 pve3 kernel: [ 112.528805] vmbr0: port 1(veth100i0) entered blocking state
Aug 16 21:24:36 pve3 kernel: [ 112.528807] vmbr0: port 1(veth100i0) entered disabled state
Aug 16 21:24:36 pve3 kernel: [ 112.528862] device veth100i0 entered promiscuous mode
Aug 16 21:24:36 pve3 kernel: [ 112.592601] eth0: renamed from vethI3L0F5
Aug 16 21:24:36 pve3 systemd[1]: Started LXC Container: 100.
Aug 16 21:24:36 pve3 pvedaemon[1174]: <root@pam> end task UPID
ve3:0000053C:00002BB0:59951A83:vzstart:100:root@pam: OKAug 16 21:24:37 pve3 kernel: [ 113.140955] vmbr0: port 1(veth100i0) entered blocking state
Aug 16 21:24:37 pve3 kernel: [ 113.140956] vmbr0: port 1(veth100i0) entered forwarding state
The container starts but has not IPV4 network.
I do not have a preference between the default configuration suggested in the docs or one with routed IPs.
What modifications does the network configuration needs to work? I want the IP address of the be assigned by the DHCP server.