Proxmox destroyed my eno1 interface. Help!

K

ksten

Active Member
Jan 16, 2018
13
0
41
55
I tried to create a bridge under the proxmox web interface, and when I rebooted, I had no internet access. When I took a look at /etc/network/interfaces, the entry for eno1 was gone.

Now I'm not up to speed on how to configure networking, so I've been scouring the net trying to figure out how to fix /etc/network/interfaces, but so far nothing has worked (auto, manual, static... I've been brute forcing my way around to no effect).

I just want to get eno1 back to connecting to the local network as 192.168.178.20 like it did before, and then hopefully set up a bridged network for a guest OS so that it can have its own IP address 192.168.178.200. This is a fresh install, so it doesn't matter what configuration I have to trash; I just don't want to have to reinstall the whole thing from scratch and then worry that it'll trash my networking sometime in the future...
 
A default config looks like this, it doesn't remove the interface, it binds it as a bridge port to the created bridge.
Code: 
iface enp5s0 inet manual

auto vmbr0
iface vmbr0 inet static
    address 192.168.178.20
    netmask 255.255.2255.0
    gateway 192.168.178.1
    bridge_ports enp5s0
    bridge_stp off
    bridge_fd 0
 
OK, adding an entry like that got me back online, but DNS is broken. For some reason, /etc/resolv.conf is now a bad symlink:

root@linux:/etc# ls -l resolv.conf
lrwxrwxrwx 1 root root 35 Jan 16 13:43 resolv.conf -> /var/run/NetworkManager/resolv.conf
root@linux:/etc# ls /var/run/NetworkManager/
devices
root@linux:/etc#
 
Alright, I just removed the symlink resolv.conf and manually created it with nameservers 8.8.8.8 and 8.8.8.9.

Hopefully this is the end of the troubles, but I'm a bit worried now that changing anything in proxmox is going to destroy my network again :/
 
Oh wait no, it doesn't work. This is so weird... the network config is all messed up now...

From outside:

$ nslookup linux
Server: 192.168.178.1
Address: 192.168.178.1#53

Name: linux.fritz.box
Address: 192.168.178.20
Name: linux.fritz.box
Address: 192.168.178.10
Name: linux.fritz.box
Address: 192.168.178.200

From inside:

# ifconfig
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether f4:4d:30:6d:58:84 txqueuelen 1000 (Ethernet)
RX packets 393 bytes 73164 (71.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 201 bytes 28951 (28.2 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0xdc300000-dc320000

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 6 bytes 314 (314.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 6 bytes 314 (314.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vmbr200: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.178.200 netmask 255.255.255.0 broadcast 192.168.178.255
inet6 2001:16b8:45fd:4f00:f64d:30ff:fe6d:5884 prefixlen 64 scopeid 0x0<global>
inet6 fe80::f64d:30ff:fe6d:5884 prefixlen 64 scopeid 0x20<link>
ether f4:4d:30:6d:58:84 txqueuelen 1000 (Ethernet)
RX packets 393 bytes 66090 (64.5 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 201 bytes 28099 (27.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

So it looks like the host is now using the bridge for all communications...
 
PVE doesn't use the NetworkManager. Uninstall the NetworkManager, as it will always try to auto configure your network and this is not what you want on a server.
 
OK, uninstalled that. Now I have:

# cat /etc/resolv.conf
nameserver 8.8.8.8
nameserver 8.8.8.9

root@linux:# cat /etc/network/interfaces
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage part of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

iface eno1 inet manual

auto vmbr200
iface vmbr200 inet static
address 192.168.178.200
netmask 255.255.255.0
gateway 192.168.178.1
bridge_ports none
bridge_stp off
bridge_fd 0​

root@linux:# cat /etc/hosts
127.0.0.1 localhost
#127.0.0.1 linux
192.168.178.20 linux.fritz.box linux pvelocalhost​

# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters​


What I'm trying for is:

  • Host machine: 192.168.178.20
  • Guest machine: 192.168.178.200

Such that both host and guest machine has its own IP address.
 
Hmm... that's strange. There's an extra bridge vmbr20 that Proxmox doesn't see:

# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr20 state UP mode DEFAULT group default qlen 1000
link/ether f4:4d:30:6d:58:84 brd ff:ff:ff:ff:ff:ff
4: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
link/ether 02:42:6d:df:ff:66 brd ff:ff:ff:ff:ff:ff
5: vmbr20: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether f4:4d:30:6d:58:84 brd ff:ff:ff:ff:ff:ff
6: vmbr200: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether 66:90:7b:c6:32:e5 brd ff:ff:ff:ff:ff:ff
8: vethf0fa359@if7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP mode DEFAULT group default
link/ether 02:41:39:0e:f9:35 brd ff:ff:ff:ff:ff:ff link-netnsid 0
9: tap100i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr200 state UNKNOWN mode DEFAULT group default qlen 1000
link/ether 66:90:7b:c6:32:e5 brd ff:ff:ff:ff:ff:ff
 
You must log in or register to reply here.
Top Bottom