No network connectivity/interface down on fresh install

M

marble nature

New Member
Feb 26, 2024
11
0
1
Hi all,

absolute first time installing any type of server for me, so apologies for noob questions. I have seen various threads with similar problems but haven't been able to fix it by myself.

I fresh installed 8.1, ran through the config accepting default values and forgot to set up a proper IP address.

So I successfully set a static IP of 192.168.1.101 with nano /etc/network/interfaces and also edited the hosts file with nano /etc/hosts

Then tried to make a DHCP reservation on my router, but I cannot find my server on the list of connected devices on my router's page.

This led me to investigate using ip link command and it seems that my interface is down. This used to be a Win 10 machine and the NIC was working fine before install. What can I do to fix/investigate further?

Please see screenshots of the CLI here (files were too big to upload): https://imgur.com/a/bW0cCGQ

Thank you very much in advance.
 
Last edited:
bbgeek17 said:
Notice the interface name on your second image on the line that starts with "2: ".
Its not "enp3s0", so edit your config file and replace "enp3s0" with correct interface name that matches your physical configuration


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Click to expand...
Thanks, that makes sense.

However I changed "enp3s0" to "enp0s31f6" in nano /etc/network/interfaces and it still shows line 2 as DOWN in ip link

What do you mean by "config file", and also how can I find the physical configuration of my interface?
 
marble nature said:
What do you mean by "config file", and also how can I find the physical configuration of my interface?
Click to expand...
Config file is etc/network/interfaces
Physical configuration meant enp0s31f6

Editing file does not change running configuration. Now you need to either reboot or restart network services, ie : systemctl restart networking

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
  • Like
Reactions: Kingneutron
bbgeek17 said:
Config file is etc/network/interfaces
Physical configuration meant enp0s31f6

Editing file does not change running configuration. Now you need to either reboot or restart network services, ie : systemctl restart networking

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Click to expand...
Unfortunately it is still showing DOWN (after running the command + rebooting). Does that mean the NIC is broken?

Pinging default gateway 192.168.1.1 says destination host unreachable.
Pinging loopback 127.0.0.1 works
Pinging self 192.168.1.101 also works

So I think the NIC is still working?
 
Last edited:
There could be a number of things:
- you can have a typo in your configuration file
- cable could have fallen out of the jack
- you might have a bad cable
- it could be a realtek based NIC which are know to be problematic, the first command in this thread should tell you:
https://forum.proxmox.com/threads/r...eze-performance-with-promox-7-4-and-8.134212/

Pinging the host from itself locally does not utilize the NIC in any way. The OS is using an internal loopback software-only "adapter".

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
bbgeek17 said:
There could be a number of things:
- you can have a typo in your configuration file
- cable could have fallen out of the jack
- you might have a bad cable
- it could be a realtek based NIC which are know to be problematic, the first command in this thread should tell you:
https://forum.proxmox.com/threads/r...eze-performance-with-promox-7-4-and-8.134212/

Pinging the host from itself locally does not utilize the NIC in any way. The OS is using an internal loopback software-only "adapter".

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Click to expand...
I think we can rule out hardware issues because the cable is properly connected and the same cable works on my other PC. The ethernet controller is Intel Corporation Ethernet Connection (5) 1219-V, so we can also rule out the realtek NIC problem.

I think there is probably a typo in the config file (as usual), but I have 0 clue where to start.
 
Last edited:
marble nature said:
I think there is probably a typo in the config file (as usual), but I have 0 clue where to start.
Click to expand...
First step would be to provide new outputs to the forum, so members can review:
cat /etc/network/interfaces
ip a

If you can, put them into a file, store on USB and transfer to your workstation, for easier addition.
I.e.: ip a > ip_a.txt
You can then copy/paste the text into post with CODE tags.

If you are able to do above, then also add "dmesg > dmesg.txt" as an attachment.

Other things to try :
different port on your switch
direct connect PVE to another workstation - check for UP/light

It could be a bad NIC or incompatibility between the NIC/firmware and Linux Kernel, or some weird BIOS issue.

Good luck

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
gfngfn256 said:
Is it 192.168.1.101 or 192.168.2.101,

What's your gateway on your router 192.168.1.XXX or 192.168.2.XXX?
Click to expand...
Good point on correctness. That said, the "2" was probably a typo, judging from screenshots. Also IP subnet would not be affecting "DOWN" state of the interface.
All the more reason to provide new set of information!


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
  • Like
Reactions: marble nature
bbgeek17 said:
judging from screenshots
Click to expand...
Just checked screenshot. You're probably right.

Why does he have/need the line at the bottom "source /etc/network/interfaces.d/*", is he using some sort of SDN as per https://pve.proxmox.com/wiki/Software-Defined_Network ? Or maybe he installed on top of Debian? Maybe the current installer includes it by default? I don't have one on my relatively new (couple of months) recent (latest) install?
 
bbgeek17 said:
First step would be to provide new outputs to the forum, so members can review:
cat /etc/network/interfaces
ip a

If you can, put them into a file, store on USB and transfer to your workstation, for easier addition.
I.e.: ip a > ip_a.txt
You can then copy/paste the text into post with CODE tags.

If you are able to do above, then also add "dmesg > dmesg.txt" as an attachment.

Other things to try :
different port on your switch
direct connect PVE to another workstation - check for UP/light

It could be a bad NIC or incompatibility between the NIC/firmware and Linux Kernel, or some weird BIOS issue.

Good luck

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Click to expand...
I have never felt dumber, I cannot figure out how to save to USB. I've been at it for hours and I basically don't have mountpoints on any of my USB drives and I keep getting the following error when i try to mount:

Code: 
mount: wrong fs type, bad option, bad superblock on /dev/sda, missing codepage or helper program, or other error

The best I can do is take pictures. I would write code manually but its going to be prone to errors and typos.

Please see pictures here: https://imgur.com/a/SR4y7sc
 
1. In your "ip a" image output,
The link/ether mac of vmbr0 does not match that of enp0s31f6.
This is never going to work, you've messed up some config.



2. In your "nano /etc/hosts" output, I notice (second line) you have:
Code: 
192.168.1.101 host1.leo.local host1
I would change it to:
Code: 
192.168.1.101 host1.local host1
 
  • Like
Reactions: marble nature
gfngfn256 said:
1. In your "ip a" image output,
The link/ether mac of vmbr0 does not match that of enp0s31f6.
This is never going to work, you've messed up some config.



2. In your "nano /etc/hosts" output, I notice (second line) you have:
Code: 
192.168.1.101 host1.leo.local host1
I would change it to:
Code: 
192.168.1.101 host1.local host1
Click to expand...
I will try this when I get back home, then I will just re-install if it doesn't work. I will update the thread. Thank you.
 
marble nature said:
Thanks, I think I will re-install and start from scratch, I just don't have enough experience to get around this.
Click to expand...
hmm, you literally need to edit a file and change "enp3s0" to "enp0s31f6. But if you feel like reinstalling, go for it

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
  • Like
Reactions: marble nature
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back