Container dont start eth1 (second interface)

warn1ng

New Member
Mar 19, 2019
7
1
3
39
Hi, i setup a second IP on a container, but when i start the container, only shows the eth0 with a IP and UP :

DeepinScreenshot_Seleccionar área_20200218210205.png

If i run "ifup eth1" it takes too long that i have to press CTRL+C, then i run "ip a" again and the interface shows UP and with IP :

DeepinScreenshot_Seleccionar área_20200218210420.png

How i can fix this, why is not going up when the container is starting up?.


Saludos
 

warn1ng

New Member
Mar 19, 2019
7
1
3
39
arch: amd64
cores: 1
hostname: ocs-dbcom
memory: 2048
nameserver: 172.16.2.1
net0: name=eth0,bridge=vmbr0,gw=172.16.2.1,hwaddr=5A:28:13:82:EA:E6,ip=172.16.2.22/24,ip6=dhcp,type=veth
net1: name=eth1,bridge=vmbr1,hwaddr=1E:81:E4:71:81:82,ip=172.16.1.22/24,ip6=dhcp,type=veth
ostype: debian
rootfs: local-LVM:vm-118-disk-0,size=25G
searchdomain: xxx.com
swap: 2048
unprivileged: 1
 

warn1ng

New Member
Mar 19, 2019
7
1
3
39
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 172.16.2.22
netmask 255.255.255.0
gateway 172.16.2.1

iface eth0 inet6 dhcp

auto eth1
iface eth1 inet static
address 172.16.1.22
netmask 255.255.255.0

iface eth1 inet6 dhcp
 

warn1ng

New Member
Mar 19, 2019
7
1
3
39
proxmox-ve: 5.3-1 (running kernel: 4.15.18-10-pve)
pve-manager: 5.3-8 (running version: 5.3-8/2929af8e)
pve-kernel-4.15: 5.3-1
pve-kernel-4.15.18-10-pve: 4.15.18-32
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-3
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-44
libpve-guest-common-perl: 2.0-19
libpve-http-server-perl: 2.0-11
libpve-storage-perl: 5.0-36
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-2
lxcfs: 3.0.2-2
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-22
pve-cluster: 5.0-33
pve-container: 2.0-33
pve-docs: 5.3-1
pve-edk2-firmware: 1.20181023-1
pve-firewall: 3.0-17
pve-firmware: 2.0-6
pve-ha-manager: 2.0-6
pve-i18n: 1.0-9
pve-libspice-server1: 0.14.1-1
pve-qemu-kvm: 2.12.1-1
pve-xtermjs: 3.10.1-1
qemu-server: 5.0-45
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.12-pve1~bpo1
 

Stoiko Ivanov

Proxmox Staff Member
Staff member
May 2, 2018
3,039
330
83
If i run "ifup eth1" it takes too long that i have to press CTRL+C,
do you indeed have a dhcp6 server running on the network where eth1 is connected to? (Otherwise this would explain the long wait for a dhcp-timeout)
if you don't have a dhcp6 server - chose static in the GUI (both for configuring a static ip, and configuring an interface without ipv6)

I hope this helps!
 

warn1ng

New Member
Mar 19, 2019
7
1
3
39
do you indeed have a dhcp6 server running on the network where eth1 is connected to? (Otherwise this would explain the long wait for a dhcp-timeout)
if you don't have a dhcp6 server - chose static in the GUI (both for configuring a static ip, and configuring an interface without ipv6)

I hope this helps!
Yep, that works ;), thanks !!
 
  • Like
Reactions: Stoiko Ivanov

Stoiko Ivanov

Proxmox Staff Member
Staff member
May 2, 2018
3,039
330
83
Glad that helped! please mark the thread as 'SOLVED' (this helps others who also search for this kind of problems)

Thanks!
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!