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:
Here's the state of everything during / immediately after a fresh install.
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
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
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
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: