Assign IP to Secondary Network Card Issue in Proxmox VE 8.0

kelvinlo171084

New Member
Apr 24, 2025
3
0
1
I have a problem about assigning IP to secondary network card in Proxmox VE 8.0

i read the proxmox technical document to assign IP to secondary network card and follow the document to configure it. And i perform the ping testing with other device in the same network and the ping test result tell me is 'Destination Host Unreachable'

As this result, May i know if there are any configuration need to perform ???

Kelvin Lo
 

Attachments

  • Capture1.jpg
    Capture1.jpg
    49.7 KB · Views: 10
  • Capture2.jpg
    Capture2.jpg
    103.6 KB · Views: 10
Gabriel

I cannot ping the other device in 10.10.0.0/24 network even i assign the IP (10.10.0.26/24) to the secondary network card. Please refer two screen-capture for the reference.
 

Attachments

  • Capture3.jpg
    Capture3.jpg
    85.3 KB · Views: 8
  • Capture4.jpg
    Capture4.jpg
    65.1 KB · Views: 8
Hi @kelvinlo171084 , welcome to the forum.

It is much easier to examine the configuration data when it is provided as text (copy/paste) output in CODE tags, as @_gabriel requested.

That said, the configuration looks ok. However, only you know if the physical interface you are trying to use is actually connected to the right network, or that you are using the right subnet.

I also noticed that you have VLAN attribute set, are you actually using VLANs? Is your switch configured properly?
Is there a reason why you've added a virtual bridge to "storage" interface? Are you expecting VMs to have direct access to storage?

My recommendation, is to start with the basics:
- remove the virtual bridge
- initiate a network trace on the interface, confirm that you see some (i.e. ARP broadcast) traffic from other hosts in expected network
- assign the IP to physical interface, ensure you can achieve the connectivity
- add complexity as needed

Good luck


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Thanks your advice.

I have tried your recommendation and the following is my result.

1. The virtual bridge have removed and assign IP to the physical interface.

2. Performed the arp testing for the expected network and please take the screen-capture in the details.

3. Please take the simple network diagram for my idea.

4. No Vlan configuration in the network switch.

5. I expected the VM have to access the storage via ISCSI so i dedicated another network adapter to connect the storage(10.10.0.10/24). but the ping test is still fail to the storage.
 

Attachments

  • Capture5.jpg
    Capture5.jpg
    79.8 KB · Views: 6
  • Capture6.jpg
    Capture6.jpg
    132.2 KB · Views: 6
  • Simple-Network-Diagram.jpg
    Simple-Network-Diagram.jpg
    51.1 KB · Views: 6
2. Performed the arp testing for the expected network and please take the screen-capture in the details.
What you posted is not ARP "testing". Its an output of the existing system state that we already indirectly knew.
You may want to review this: https://www.lixu.ca/2014/10/linux-arp-and-how-to-tcpdump-arp.html or similar posts.

3. Please take the simple network diagram for my idea.
Your idea looks fine. The problem likely lies in your network configuration _outside_ of the PVE.

What does your storage device network configuration look like? What other IPs do you have on storage network? Do they function properly?

You have 5 ports with active link connection, 2 are used as part of the Bond. Are you sure you picked the correct remaining port for storage setup? Or that you did not use wrong port in the bond?

Again, running tcpdump on each interface consecutively _may_ give you some guiding information.

Cheers

PS if you are able to initiate a continuous ping from your storage system or another system on 10.x network, that will assist in your tcpdump analyses.


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Last edited: