Fresh Install 1.9 Netowrking not working. No route to host.

  • Thread starter Thread starter vegas
  • Start date Start date
V

vegas

Guest
Searched all over the place and cant find anyone having the same issue as me.
This is a fresh install of 1.9 from the ISO.

Server has 3 NICs installed.
During the install the DHCP ip address was pulled from the DHCP server just fine. (10.80.0.165)
After install, I am unable to browse to the server.
At the console of the proxmox, I have tried ping 10.80.0.1 and I get: Destination Host unreachable.
Route shows default gateway is correct.

I have tried setting a static IP and I have tried installing with only one NIC plugged into Ethernet. Everything I have tried shows no results.
This is a default out of the box install.

I now have the proxmox server installed with only 1 NIC active and it seems to work fine. How should I add the other two correctly to gain added speed while still resulting in a working network?
 
vegas said:
Searched all over the place and cant find anyone having the same issue as me.
This is a fresh install of 1.9 from the ISO.

Server has 3 NICs installed.
During the install the DHCP ip address was pulled from the DHCP server just fine. (10.80.0.165)
After install, I am unable to browse to the server.
At the console of the proxmox, I have tried ping 10.80.0.1 and I get: Destination Host unreachable.
Route shows default gateway is correct.

I have tried setting a static IP and I have tried installing with only one NIC plugged into Ethernet. Everything I have tried shows no results.
This is a default out of the box install.

I now have the proxmox server installed with only 1 NIC active and it seems to work fine. How should I add the other two correctly to gain added speed while still resulting in a working network?
Click to expand...
Hi,
you can defined a bond (search for bond in the forum), or define the other nics as a seperate network.
Depends on your usage (how many network do you use/need). With more networks, the host need only one ip one the vmbr0-network, so you can define the other networks without ip-address (the VM use than ips ot that network).
The config is debian-like in /etc/network/interfaces.

If you use an bond, you must also define the bond on the switch-side.

Udo
 
vegas said:
During the install the DHCP ip address was pulled from the DHCP server just fine. (10.80.0.165)
After install, I am unable to browse to the server.?
Click to expand...

Please tried to plug the cable into one of the other slots - maybe the slot assignments changed after the reboot.
 
Thanks for the reply.
The problem was that the NIC's MAC addresses were reassigning in the BIOS. I had to change a setting in the BIOS for NON-PNP Ethernets. Intel based.
Thanks you for the help. it is now working with one NIC bridged to the eth0
What I would like is to use one network: 10.80.0.0/24
I have a switch that as capable of LACP so I would like to use LAGG for the eth0,eth1,eth2 for speed.
Is the bonding what I need to search for if I want to do LACP?
Thank you.
 
vegas said:
Thanks for the reply.
The problem was that the NIC's MAC addresses were reassigning in the BIOS. I had to change a setting in the BIOS for NON-PNP Ethernets. Intel based.
Click to expand...
sure? take a look at /etc/udev/rules.d/70-persistent-net.rules
Thanks you for the help. it is now working with one NIC bridged to the eth0
What I would like is to use one network: 10.80.0.0/24
I have a switch that as capable of LACP so I would like to use LAGG for the eth0,eth1,eth2 for speed.
Is the bonding what I need to search for if I want to do LACP?
Thank you.
Click to expand...
right.
 
You must log in or register to reply here.
Top Bottom