[SOLVED] No network connectivity on fresh install

brokndremes

New Member
Aug 13, 2016
2
0
1
30
Hello,

I've got a rather frustrating problem, and haven't had much luck finding a solution to it. In short, I can't seem to get any sort of network connection on Proxmox.

First off, hardware - installing on an RS140 with the following specs, collected by ThinkServer EasyStartup:
Processor: 1x Intel Xeon E3-1246 v3 @ 3.5GHz
Memory: 4G ECC
Storage: AHCI Storage Controller
Network:
--Intel Gigabit Network Connection (i217)
--Intel Ethernet Server Adapter i350-T2
--Intel Gigabit i210 PCIE NIC
Chipset:
--Intel USB 3.0 eXtensible Host Controller
--Intel Management Engine Interface
--Intel Active Management Technology-SOL
--Intel 8 Series/C220 Series / USB Enhanced Host Controller
--Intel 8 Series/C220 Series / USB Enhanced Host Controller
--Intel C226 Series Chipset

Here's the state of everything during / immediately after a fresh install.
Hostname : host.proxmox.local
IP Address : 192.168.1.220
Netmask : 255.255.255.0
Gateway : 192.168.1.2
DNS Server : 8.8.8.8

Code:
eth0      Link encap:Ethernet  HWaddr a0:36:9f:68:6b:28
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:183 errors:0 dropped:0 overruns:0 frame:0
          TX packets:54 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

eth1      Link encap:Ethernet  HWaddr 6c:0b:84:42:59:8e
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:20 Memory:f7d00000-f7d20000

eth2      Link encap:Ethernet  HWaddr a0:36:9f:68:6b:29
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

eth3      Link encap:Ethernet  HWaddr 44:39:c4:e9:4f:40
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

eth4      Link encap:Ethernet  HWaddr 44:39:c4:e9:4f:41
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:10 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:1006 (1006.0 B)  TX bytes:1006 (1006.0 B)

vmbr0     Link encap:Ethernet  HWaddr a0:36:9f:68:6b:28
          inet addr:192.168.1.220  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

Code:
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.2     0.0.0.0         UG    0      0        0 vmbr0
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 vmbr0

Code:
auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
         address 192.168.1.220
         netmask 255.255.255.0
         gateway 192.168.1.2
         bridge_ports eth0
         bridge_stp off
         bridge_fd 0

First things first, I had to make sure that I was plugged into the correct port. I downloaded ethtools using https://packages.debian.org/ and installed it using dpkg to be certain. And yes, I am definitely plugged into the correct port.

Well, my next idea was that it's a driver issue. Fortunately for me, I have an RS140 disk with everything I should need. Unfortunately for me, it needs make and kernel headers to install. After gaining a great appreciation for the wonderful work that apt-get does, it was time to try building. Even worse, when compiling I got the in igbmake_1.txt

I get similar errors when trying to compile the drivers provided on the disk for different Linux operating systems. I only now decided to compare the version of the installed drivers with the provided ones, and discovered that the disk one's are even less up to date than the one's initially installed. So much for that. Looking at the output of dmesg (Attatched) it appears that I'm using igb 5.3.4.4 and e100e 3.3.3. Looking at Intel, the newest versions appear to be 5.3.5.3 and 3.3.4. I tried installing those and encountered an error on the igb (Also attatched). The e1000e installed successfully, but I was still unable to connect to the network. It seems as though there was a bug report for this problem back in 2013, fixed in 3.13.7-1.

I'm spending more time writing this post than I'd intended, so I'll be rather less verbose describing the other things I've tried.

Installing other OS:
This had mixed results. I was able to connect straight off on Windows 8.1, and 10, Ubuntu 14.04, and 16.04.1. but not on CentOS 6 or 7 or RHEL 6.5 which presented similarly to Proxmox.
Messing with interface settings:
I've tried changing which port is used by disabling other NIC's, or by changing which interface vmbr0 bridges. I've tried removing vmbr0 and assigning IP's to ethx, and have not had any luck with those results. I've also tried using dhcp. Unfortunately I didn't document all of this very well, so I can't say exactly what I've tried.


At this point, I'm hoping another set of eyes on this can help fix the problem. I'm really hoping this is just some stupid mistake I made.


Thanks for any help
 

Attachments

Last edited:
Update bios and firmware to latest version. Replace patch cord.
Try to use another ethernet port on different network card, for example eth1 (e1000e driver). To do this, set "bridge_ports eth1" in /etc/network/interfaces or try all cards, set "bridge_ports eth0 eth1 eth2 eth3 eth4".
Manually download latest pve kernel (pve-kernel-4.4.15) and install it on server.
 
is this line
bridge _ports eth0

a typo, or is there really a space between "bridge" and "_ports"
there definitely should be no space, so the line should be:
Code:
bridge_ports eth0
 
Update bios and firmware to latest version. Replace patch cord.
Try to use another ethernet port on different network card, for example eth1 (e1000e driver). To do this, set "bridge_ports eth1" in /etc/network/interfaces or try all cards, set "bridge_ports eth0 eth1 eth2 eth3 eth4".
Manually download latest pve kernel (pve-kernel-4.4.15) and install it on server.

Attempting to update BIOS gives the following error:
Code:
/media/usb/BIOSLinux64/.temp/amifldrv.c:42:1: warning: data definition has no type or storage class
module_init(amifldrv_init_module);
^
/media/usb/BIOSLinux64/.temp/amifldrv.c:42:1: error: type defaults to ‘int’ in declaration of ‘module_init’ [-Werror=implicit-int]
/media/usb/BIOSLinux64/.temp/amifldrv.c:42:1: warning: parameter names (without types) in function declaration
/media/usb/BIOSLinux64/.temp/amifldrv.c:43:1: warning: data definition has no type or storage class
module_exit(amifldrv_cleanup_module);
^
/media/usb/BIOSLinux64/.temp/amifldrv.c:43:1: error: type defaults to ‘int’ in declaration of ‘module_exit’ [-Werror=implicit-int]
/media/usb/BIOSLinux64/.temp/amifldrv.c:43:1: warning: parameter names (without types) in function declaration
/media/usb/BIOSLinux64/.temp/amifldrv.c:14:12: warning: ‘amifldrv_init_module’ defined but not used [-Wunused-function]
static int amifldrv_init_module(void)
            ^
/media/usb/BIOSLinux64/.temp/amifldrv.c:22:13: warning: ‘amifldrv_cleanup_module’ defined but not used [-Wunused-function]
static void amifldrv_cleanup_module(void)
             ^
cc1: some warnings being treated as errors
make[2]: *** [/media/usb/BIOSLinux64/.temp/amifldrv.o] Error 1
make[1]: *** [_module_/media/usb/BIOSLinux64/.temp] Error 2
make: *** [default] Error 2
10 - Error: Unable to load driver.

No change when bridging any other port / bridging all of them, or changing cables. Installed newest kernel but no change.

is this line
Code:
bridge _ports eth0
a typo, or is there really a space between "bridge" and "_ports"
there definitely should be no space, so the line should be:
Code:
bridge_ports eth0

Typo, there is no space between bridge and _ports in the actual file. Not sure why it showed up there.

--------------------------------------------------------------------------------------------------------------------------------------

Edit: Solved the issue by installing the latest debian, was able to then update drivers for my NIC and then install proxmox on top of debian. Took some additional fiddling to get right, but I think I managed to get things running now.
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, 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 yours easily in our online shop.

Buy now!