Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


Categories

In this Discussion

› › $100 if you fix this Proxmox VM issue - Page 2
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

$100 if you fix this Proxmox VM issue

245

Comments

  • ilikebeansilikebeans Member

    @mw said:

    @ilikebeans said:

    @mw said:
    $100 to the first person with a working fix

    I have a server running Proxmox that refuses to give me networking on a VM. The vendor confirmed the VM's IP shows up in the ARP table but it cannot ping anything, not even the gateway

    0-access-r02b08-drt-ams5.royalehosting.net(config)#show arp vrf internet <IP removed>

Address         Age (sec)  Hardware Addr   Interface
<IP removed>      0:00:51  bc24.116f.970e  Vlan100, Ethernet1/1

    It's a brand new Proxmox install, all I did was create the VM and configure it the way all our other VMs are configured

    Host:

    root@host:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
        address 45.94.x.2/24
        gateway 45.94.x.1
        bridge-ports enp1s0f0np0
        bridge-stp off
        bridge-fd 0

iface enp1s0f0np0 inet manual

iface enp1s0f1np1 inet manual


source /etc/network/interfaces.d/*

    VM:

    • ens18 is bridged to vmbr0

      root@vm:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto ens18
iface ens18 inet static
        address 45.94.x.3/24
        gateway 45.94.x.1

    It's a 9950X on a Supermicro board with 2x 40G NICs, nothing exotic.

    I've tried:

    • Using the vendors provided prefix
    • Using our prefix
    • With and without LACP on the host
    • Reinstalling the host and VM
    • Swapping IPs between the host and VM
    • Bridging the 2nd 40G interface to vmbr1 and giving that to the VM
    • Praying
    • A CT container
    • virtio and Intel E1000 NICs
    • Changing MTU
    • Spoofing the host MAC's unused interface for the VMs NIC

    Other boxes in this rack have VMs running fine. What could I be missing?

    I HAD THIS EXACT ISSUE WITH THE EXACT SPEC YOUR HAVING, WITH THE EXACT SAME HOST!!!!

    (although i had a 200G port & connectx6 mellanox NIC)

    good luck fixing it, because i couldnt even after a reinstall. Royale wont be able to help...

    GOOD LUCK!!!

    is this by any chance the 45.94.221.0/24 range?

    fr?

    I swear on everything.

  • mwmw Member

    @ilikebeans said:

    @mw said:

    @ilikebeans said:

    @mw said:
    $100 to the first person with a working fix

    I have a server running Proxmox that refuses to give me networking on a VM. The vendor confirmed the VM's IP shows up in the ARP table but it cannot ping anything, not even the gateway

    0-access-r02b08-drt-ams5.royalehosting.net(config)#show arp vrf internet <IP removed>

Address         Age (sec)  Hardware Addr   Interface
<IP removed>      0:00:51  bc24.116f.970e  Vlan100, Ethernet1/1

    It's a brand new Proxmox install, all I did was create the VM and configure it the way all our other VMs are configured

    Host:

    root@host:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
        address 45.94.x.2/24
        gateway 45.94.x.1
        bridge-ports enp1s0f0np0
        bridge-stp off
        bridge-fd 0

iface enp1s0f0np0 inet manual

iface enp1s0f1np1 inet manual


source /etc/network/interfaces.d/*

    VM:

    • ens18 is bridged to vmbr0

      root@vm:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto ens18
iface ens18 inet static
        address 45.94.x.3/24
        gateway 45.94.x.1

    It's a 9950X on a Supermicro board with 2x 40G NICs, nothing exotic.

    I've tried:

    • Using the vendors provided prefix
    • Using our prefix
    • With and without LACP on the host
    • Reinstalling the host and VM
    • Swapping IPs between the host and VM
    • Bridging the 2nd 40G interface to vmbr1 and giving that to the VM
    • Praying
    • A CT container
    • virtio and Intel E1000 NICs
    • Changing MTU
    • Spoofing the host MAC's unused interface for the VMs NIC

    Other boxes in this rack have VMs running fine. What could I be missing?

    I HAD THIS EXACT ISSUE WITH THE EXACT SPEC YOUR HAVING, WITH THE EXACT SAME HOST!!!!

    (although i had a 200G port & connectx6 mellanox NIC)

    good luck fixing it, because i couldnt even after a reinstall. Royale wont be able to help...

    GOOD LUCK!!!

    is this by any chance the 45.94.221.0/24 range?

    fr?

    I swear on everything.

    i guess im cooked.

  • ilikebeansilikebeans Member

    @mw said:

    @ilikebeans said:

    @mw said:

    @ilikebeans said:

    @mw said:
    $100 to the first person with a working fix

    I have a server running Proxmox that refuses to give me networking on a VM. The vendor confirmed the VM's IP shows up in the ARP table but it cannot ping anything, not even the gateway

    0-access-r02b08-drt-ams5.royalehosting.net(config)#show arp vrf internet <IP removed>

Address         Age (sec)  Hardware Addr   Interface
<IP removed>      0:00:51  bc24.116f.970e  Vlan100, Ethernet1/1

    It's a brand new Proxmox install, all I did was create the VM and configure it the way all our other VMs are configured

    Host:

    root@host:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
        address 45.94.x.2/24
        gateway 45.94.x.1
        bridge-ports enp1s0f0np0
        bridge-stp off
        bridge-fd 0

iface enp1s0f0np0 inet manual

iface enp1s0f1np1 inet manual


source /etc/network/interfaces.d/*

    VM:

    • ens18 is bridged to vmbr0

      root@vm:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto ens18
iface ens18 inet static
        address 45.94.x.3/24
        gateway 45.94.x.1

    It's a 9950X on a Supermicro board with 2x 40G NICs, nothing exotic.

    I've tried:

    • Using the vendors provided prefix
    • Using our prefix
    • With and without LACP on the host
    • Reinstalling the host and VM
    • Swapping IPs between the host and VM
    • Bridging the 2nd 40G interface to vmbr1 and giving that to the VM
    • Praying
    • A CT container
    • virtio and Intel E1000 NICs
    • Changing MTU
    • Spoofing the host MAC's unused interface for the VMs NIC

    Other boxes in this rack have VMs running fine. What could I be missing?

    I HAD THIS EXACT ISSUE WITH THE EXACT SPEC YOUR HAVING, WITH THE EXACT SAME HOST!!!!

    (although i had a 200G port & connectx6 mellanox NIC)

    good luck fixing it, because i couldnt even after a reinstall. Royale wont be able to help...

    GOOD LUCK!!!

    is this by any chance the 45.94.221.0/24 range?

    fr?

    I swear on everything.

    i guess im cooked.

    Thats one way to put it.

  • wamywamy Member

    :'(

  • mwmw Member

    @ilikebeans said:

    @mw said:

    @ilikebeans said:

    @mw said:

    @ilikebeans said:

    @mw said:
    $100 to the first person with a working fix

    I have a server running Proxmox that refuses to give me networking on a VM. The vendor confirmed the VM's IP shows up in the ARP table but it cannot ping anything, not even the gateway

    0-access-r02b08-drt-ams5.royalehosting.net(config)#show arp vrf internet <IP removed>

Address         Age (sec)  Hardware Addr   Interface
<IP removed>      0:00:51  bc24.116f.970e  Vlan100, Ethernet1/1

    It's a brand new Proxmox install, all I did was create the VM and configure it the way all our other VMs are configured

    Host:

    root@host:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
        address 45.94.x.2/24
        gateway 45.94.x.1
        bridge-ports enp1s0f0np0
        bridge-stp off
        bridge-fd 0

iface enp1s0f0np0 inet manual

iface enp1s0f1np1 inet manual


source /etc/network/interfaces.d/*

    VM:

    • ens18 is bridged to vmbr0

      root@vm:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto ens18
iface ens18 inet static
        address 45.94.x.3/24
        gateway 45.94.x.1

    It's a 9950X on a Supermicro board with 2x 40G NICs, nothing exotic.

    I've tried:

    • Using the vendors provided prefix
    • Using our prefix
    • With and without LACP on the host
    • Reinstalling the host and VM
    • Swapping IPs between the host and VM
    • Bridging the 2nd 40G interface to vmbr1 and giving that to the VM
    • Praying
    • A CT container
    • virtio and Intel E1000 NICs
    • Changing MTU
    • Spoofing the host MAC's unused interface for the VMs NIC

    Other boxes in this rack have VMs running fine. What could I be missing?

    I HAD THIS EXACT ISSUE WITH THE EXACT SPEC YOUR HAVING, WITH THE EXACT SAME HOST!!!!

    (although i had a 200G port & connectx6 mellanox NIC)

    good luck fixing it, because i couldnt even after a reinstall. Royale wont be able to help...

    GOOD LUCK!!!

    is this by any chance the 45.94.221.0/24 range?

    fr?

    I swear on everything.

    i guess im cooked.

    Thats one way to put it.

    i saw your thread where you passed on them. Was this the reason?

  • mwmw Member

    @wamy said:
    :'(

    we're so cooked

  • RoyaleHostingRoyaleHosting Member, Patron Provider

    @ilikebeans said:

    @mw said:
    $100 to the first person with a working fix

    I have a server running Proxmox that refuses to give me networking on a VM. The vendor confirmed the VM's IP shows up in the ARP table but it cannot ping anything, not even the gateway

    0-access-r02b08-drt-ams5.royalehosting.net(config)#show arp vrf internet <IP removed>

Address         Age (sec)  Hardware Addr   Interface
<IP removed>      0:00:51  bc24.116f.970e  Vlan100, Ethernet1/1

    It's a brand new Proxmox install, all I did was create the VM and configure it the way all our other VMs are configured

    Host:

    root@host:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
        address 45.94.x.2/24
        gateway 45.94.x.1
        bridge-ports enp1s0f0np0
        bridge-stp off
        bridge-fd 0

iface enp1s0f0np0 inet manual

iface enp1s0f1np1 inet manual


source /etc/network/interfaces.d/*

    VM:

    • ens18 is bridged to vmbr0

      root@vm:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto ens18
iface ens18 inet static
        address 45.94.x.3/24
        gateway 45.94.x.1

    It's a 9950X on a Supermicro board with 2x 40G NICs, nothing exotic.

    I've tried:

    • Using the vendors provided prefix
    • Using our prefix
    • With and without LACP on the host
    • Reinstalling the host and VM
    • Swapping IPs between the host and VM
    • Bridging the 2nd 40G interface to vmbr1 and giving that to the VM
    • Praying
    • A CT container
    • virtio and Intel E1000 NICs
    • Changing MTU
    • Spoofing the host MAC's unused interface for the VMs NIC

    Other boxes in this rack have VMs running fine. What could I be missing?

    I HAD THIS EXACT ISSUE WITH THE EXACT SPEC YOUR HAVING, WITH THE EXACT SAME HOST!!!!

    (although i had a 200G port & connectx6 mellanox NIC)

    good luck fixing it, because i couldnt even after a reinstall. Royale wont be able to help...

    GOOD LUCK!!!

    is this by any chance the 45.94.221.0/24 range?

    This is simply not the case. Additionally, we have been constantly assisting the customer to the best of our ability, and it is not at all related to any hardware or network-level issue. We have already carefully factored out these possibilities, even going as far as replacing the complete system just to make sure. We still have an active ticket with this customer, assisting them with any questions or configuration changes.

  • ilikebeansilikebeans Member

    @RoyaleHosting said:

    @ilikebeans said:

    @mw said:
    $100 to the first person with a working fix

    I have a server running Proxmox that refuses to give me networking on a VM. The vendor confirmed the VM's IP shows up in the ARP table but it cannot ping anything, not even the gateway

    0-access-r02b08-drt-ams5.royalehosting.net(config)#show arp vrf internet <IP removed>

Address         Age (sec)  Hardware Addr   Interface
<IP removed>      0:00:51  bc24.116f.970e  Vlan100, Ethernet1/1

    It's a brand new Proxmox install, all I did was create the VM and configure it the way all our other VMs are configured

    Host:

    root@host:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
        address 45.94.x.2/24
        gateway 45.94.x.1
        bridge-ports enp1s0f0np0
        bridge-stp off
        bridge-fd 0

iface enp1s0f0np0 inet manual

iface enp1s0f1np1 inet manual


source /etc/network/interfaces.d/*

    VM:

    • ens18 is bridged to vmbr0

      root@vm:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto ens18
iface ens18 inet static
        address 45.94.x.3/24
        gateway 45.94.x.1

    It's a 9950X on a Supermicro board with 2x 40G NICs, nothing exotic.

    I've tried:

    • Using the vendors provided prefix
    • Using our prefix
    • With and without LACP on the host
    • Reinstalling the host and VM
    • Swapping IPs between the host and VM
    • Bridging the 2nd 40G interface to vmbr1 and giving that to the VM
    • Praying
    • A CT container
    • virtio and Intel E1000 NICs
    • Changing MTU
    • Spoofing the host MAC's unused interface for the VMs NIC

    Other boxes in this rack have VMs running fine. What could I be missing?

    I HAD THIS EXACT ISSUE WITH THE EXACT SPEC YOUR HAVING, WITH THE EXACT SAME HOST!!!!

    (although i had a 200G port & connectx6 mellanox NIC)

    good luck fixing it, because i couldnt even after a reinstall. Royale wont be able to help...

    GOOD LUCK!!!

    is this by any chance the 45.94.221.0/24 range?

    This is simply not the case. Additionally, we have been constantly assisting the customer to the best of our ability, and it is not at all related to any hardware or network-level issue. We have already carefully factored out these possibilities, even going as far as replacing the complete system just to make sure. We still have an active ticket with this customer, assisting them with any questions or configuration changes.

    well if they're on the range i mentioned & they're having the exact same issue im having... this isnt a coincidence.

    Your support was good to me aswell, just to be clear. its just we physically couldnt find a fix for this issue.

  • RoyaleHostingRoyaleHosting Member, Patron Provider

    @ilikebeans said:

    @RoyaleHosting said:

    @ilikebeans said:

    @mw said:
    $100 to the first person with a working fix

    I have a server running Proxmox that refuses to give me networking on a VM. The vendor confirmed the VM's IP shows up in the ARP table but it cannot ping anything, not even the gateway

    0-access-r02b08-drt-ams5.royalehosting.net(config)#show arp vrf internet <IP removed>

Address         Age (sec)  Hardware Addr   Interface
<IP removed>      0:00:51  bc24.116f.970e  Vlan100, Ethernet1/1

    It's a brand new Proxmox install, all I did was create the VM and configure it the way all our other VMs are configured

    Host:

    root@host:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
        address 45.94.x.2/24
        gateway 45.94.x.1
        bridge-ports enp1s0f0np0
        bridge-stp off
        bridge-fd 0

iface enp1s0f0np0 inet manual

iface enp1s0f1np1 inet manual


source /etc/network/interfaces.d/*

    VM:

    • ens18 is bridged to vmbr0

      root@vm:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto ens18
iface ens18 inet static
        address 45.94.x.3/24
        gateway 45.94.x.1

    It's a 9950X on a Supermicro board with 2x 40G NICs, nothing exotic.

    I've tried:

    • Using the vendors provided prefix
    • Using our prefix
    • With and without LACP on the host
    • Reinstalling the host and VM
    • Swapping IPs between the host and VM
    • Bridging the 2nd 40G interface to vmbr1 and giving that to the VM
    • Praying
    • A CT container
    • virtio and Intel E1000 NICs
    • Changing MTU
    • Spoofing the host MAC's unused interface for the VMs NIC

    Other boxes in this rack have VMs running fine. What could I be missing?

    I HAD THIS EXACT ISSUE WITH THE EXACT SPEC YOUR HAVING, WITH THE EXACT SAME HOST!!!!

    (although i had a 200G port & connectx6 mellanox NIC)

    good luck fixing it, because i couldnt even after a reinstall. Royale wont be able to help...

    GOOD LUCK!!!

    is this by any chance the 45.94.221.0/24 range?

    This is simply not the case. Additionally, we have been constantly assisting the customer to the best of our ability, and it is not at all related to any hardware or network-level issue. We have already carefully factored out these possibilities, even going as far as replacing the complete system just to make sure. We still have an active ticket with this customer, assisting them with any questions or configuration changes.

    well if they're on the range i mentioned & they're having the exact same issue im having... this isnt a coincidence.

    Your support was good to me aswell, just to be clear. its just we physically couldnt find a fix for this issue.

    The issue is not identical at all, I appreciate you commenting and trying to share your experience to see if the issues could be related, but they are not related in any way, there is a completely different network, hardware and configuration stack, we also managed to find the issue of what you experienced a while back and it turned out to be some sort of firmware issue between the NIC and the other parts in your custom system, which we resolved in our test lab after re-diagnosting your ticket, for our internal documentation so that we can resolve it quicker if ever experienced again :)

    I am glad you appreciated our support, we always try to help as best as we can.

  • sixsix Member

    Likely already enabled, but is net.ipv4.ip_forward=1?

  • mwmw Member

    Thanks everyone who tried to help so far, I'm super shocked it's still not working despite everyone trying

    Theres a few more people that have offered to help via PM, so i'm gonna give everyone some time one by one to log in and try stuff

  • mwmw Member

    @six said:
    Likely already enabled, but is net.ipv4.ip_forward=1?

    Yes already enabled

  • ilikebeansilikebeans Member
    edited April 6

    l> @RoyaleHosting said:

    @ilikebeans said:

    @RoyaleHosting said:

    @ilikebeans said:

    @mw said:
    $100 to the first person with a working fix

    I have a server running Proxmox that refuses to give me networking on a VM. The vendor confirmed the VM's IP shows up in the ARP table but it cannot ping anything, not even the gateway

    0-access-r02b08-drt-ams5.royalehosting.net(config)#show arp vrf internet <IP removed>

Address         Age (sec)  Hardware Addr   Interface
<IP removed>      0:00:51  bc24.116f.970e  Vlan100, Ethernet1/1

    It's a brand new Proxmox install, all I did was create the VM and configure it the way all our other VMs are configured

    Host:

    root@host:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
        address 45.94.x.2/24
        gateway 45.94.x.1
        bridge-ports enp1s0f0np0
        bridge-stp off
        bridge-fd 0

iface enp1s0f0np0 inet manual

iface enp1s0f1np1 inet manual


source /etc/network/interfaces.d/*

    VM:

    • ens18 is bridged to vmbr0

      root@vm:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto ens18
iface ens18 inet static
        address 45.94.x.3/24
        gateway 45.94.x.1

    It's a 9950X on a Supermicro board with 2x 40G NICs, nothing exotic.

    I've tried:

    • Using the vendors provided prefix
    • Using our prefix
    • With and without LACP on the host
    • Reinstalling the host and VM
    • Swapping IPs between the host and VM
    • Bridging the 2nd 40G interface to vmbr1 and giving that to the VM
    • Praying
    • A CT container
    • virtio and Intel E1000 NICs
    • Changing MTU
    • Spoofing the host MAC's unused interface for the VMs NIC

    Other boxes in this rack have VMs running fine. What could I be missing?

    I HAD THIS EXACT ISSUE WITH THE EXACT SPEC YOUR HAVING, WITH THE EXACT SAME HOST!!!!

    (although i had a 200G port & connectx6 mellanox NIC)

    good luck fixing it, because i couldnt even after a reinstall. Royale wont be able to help...

    GOOD LUCK!!!

    is this by any chance the 45.94.221.0/24 range?

    This is simply not the case. Additionally, we have been constantly assisting the customer to the best of our ability, and it is not at all related to any hardware or network-level issue. We have already carefully factored out these possibilities, even going as far as replacing the complete system just to make sure. We still have an active ticket with this customer, assisting them with any questions or configuration changes.

    well if they're on the range i mentioned & they're having the exact same issue im having... this isnt a coincidence.

    Your support was good to me aswell, just to be clear. its just we physically couldnt find a fix for this issue.

    The issue is not identical at all, I appreciate you commenting and trying to share your experience to see if the issues could be related, but they are not related in any way, there is a completely different network, hardware and configuration stack, we also managed to find the issue of what you experienced a while back and it turned out to be some sort of firmware issue between the NIC and the other parts in your custom system, which we resolved in our test lab after re-diagnosting your ticket, for our internal documentation so that we can resolve it quicker if ever experienced again :)

    I am glad you appreciated our support, we always try to help as best as we can.

    I see... well, as long as its not the same issue :D

  • RoyaleHostingRoyaleHosting Member, Patron Provider
    edited April 6

    @ilikebeans said:
    l> @RoyaleHosting said:

    @ilikebeans said:

    @RoyaleHosting said:

    @ilikebeans said:

    @mw said:
    $100 to the first person with a working fix

    I have a server running Proxmox that refuses to give me networking on a VM. The vendor confirmed the VM's IP shows up in the ARP table but it cannot ping anything, not even the gateway

    0-access-r02b08-drt-ams5.royalehosting.net(config)#show arp vrf internet <IP removed>

Address         Age (sec)  Hardware Addr   Interface
<IP removed>      0:00:51  bc24.116f.970e  Vlan100, Ethernet1/1

    It's a brand new Proxmox install, all I did was create the VM and configure it the way all our other VMs are configured

    Host:

    root@host:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
        address 45.94.x.2/24
        gateway 45.94.x.1
        bridge-ports enp1s0f0np0
        bridge-stp off
        bridge-fd 0

iface enp1s0f0np0 inet manual

iface enp1s0f1np1 inet manual


source /etc/network/interfaces.d/*

    VM:

    • ens18 is bridged to vmbr0

      root@vm:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto ens18
iface ens18 inet static
        address 45.94.x.3/24
        gateway 45.94.x.1

    It's a 9950X on a Supermicro board with 2x 40G NICs, nothing exotic.

    I've tried:

    • Using the vendors provided prefix
    • Using our prefix
    • With and without LACP on the host
    • Reinstalling the host and VM
    • Swapping IPs between the host and VM
    • Bridging the 2nd 40G interface to vmbr1 and giving that to the VM
    • Praying
    • A CT container
    • virtio and Intel E1000 NICs
    • Changing MTU
    • Spoofing the host MAC's unused interface for the VMs NIC

    Other boxes in this rack have VMs running fine. What could I be missing?

    I HAD THIS EXACT ISSUE WITH THE EXACT SPEC YOUR HAVING, WITH THE EXACT SAME HOST!!!!

    (although i had a 200G port & connectx6 mellanox NIC)

    good luck fixing it, because i couldnt even after a reinstall. Royale wont be able to help...

    GOOD LUCK!!!

    is this by any chance the 45.94.221.0/24 range?

    This is simply not the case. Additionally, we have been constantly assisting the customer to the best of our ability, and it is not at all related to any hardware or network-level issue. We have already carefully factored out these possibilities, even going as far as replacing the complete system just to make sure. We still have an active ticket with this customer, assisting them with any questions or configuration changes.

    well if they're on the range i mentioned & they're having the exact same issue im having... this isnt a coincidence.

    Your support was good to me aswell, just to be clear. its just we physically couldnt find a fix for this issue.

    The issue is not identical at all, I appreciate you commenting and trying to share your experience to see if the issues could be related, but they are not related in any way, there is a completely different network, hardware and configuration stack, we also managed to find the issue of what you experienced a while back and it turned out to be some sort of firmware issue between the NIC and the other parts in your custom system, which we resolved in our test lab after re-diagnosting your ticket, for our internal documentation so that we can resolve it quicker if ever experienced again :)

    I am glad you appreciated our support, we always try to help as best as we can.

    I see... well, as long as its not the same issue :D

    It unfortunately isn't, otherwise it would already have been resolved (since we have the entire test-lab case documented) :)

  • ilikebeansilikebeans Member

    @RoyaleHosting said:

    @ilikebeans said:
    l> @RoyaleHosting said:

    @ilikebeans said:

    @RoyaleHosting said:

    @ilikebeans said:

    @mw said:
    $100 to the first person with a working fix

    I have a server running Proxmox that refuses to give me networking on a VM. The vendor confirmed the VM's IP shows up in the ARP table but it cannot ping anything, not even the gateway

    0-access-r02b08-drt-ams5.royalehosting.net(config)#show arp vrf internet <IP removed>

Address         Age (sec)  Hardware Addr   Interface
<IP removed>      0:00:51  bc24.116f.970e  Vlan100, Ethernet1/1

    It's a brand new Proxmox install, all I did was create the VM and configure it the way all our other VMs are configured

    Host:

    root@host:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
        address 45.94.x.2/24
        gateway 45.94.x.1
        bridge-ports enp1s0f0np0
        bridge-stp off
        bridge-fd 0

iface enp1s0f0np0 inet manual

iface enp1s0f1np1 inet manual


source /etc/network/interfaces.d/*

    VM:

    • ens18 is bridged to vmbr0

      root@vm:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto ens18
iface ens18 inet static
        address 45.94.x.3/24
        gateway 45.94.x.1

    It's a 9950X on a Supermicro board with 2x 40G NICs, nothing exotic.

    I've tried:

    • Using the vendors provided prefix
    • Using our prefix
    • With and without LACP on the host
    • Reinstalling the host and VM
    • Swapping IPs between the host and VM
    • Bridging the 2nd 40G interface to vmbr1 and giving that to the VM
    • Praying
    • A CT container
    • virtio and Intel E1000 NICs
    • Changing MTU
    • Spoofing the host MAC's unused interface for the VMs NIC

    Other boxes in this rack have VMs running fine. What could I be missing?

    I HAD THIS EXACT ISSUE WITH THE EXACT SPEC YOUR HAVING, WITH THE EXACT SAME HOST!!!!

    (although i had a 200G port & connectx6 mellanox NIC)

    good luck fixing it, because i couldnt even after a reinstall. Royale wont be able to help...

    GOOD LUCK!!!

    is this by any chance the 45.94.221.0/24 range?

    This is simply not the case. Additionally, we have been constantly assisting the customer to the best of our ability, and it is not at all related to any hardware or network-level issue. We have already carefully factored out these possibilities, even going as far as replacing the complete system just to make sure. We still have an active ticket with this customer, assisting them with any questions or configuration changes.

    well if they're on the range i mentioned & they're having the exact same issue im having... this isnt a coincidence.

    Your support was good to me aswell, just to be clear. its just we physically couldnt find a fix for this issue.

    The issue is not identical at all, I appreciate you commenting and trying to share your experience to see if the issues could be related, but they are not related in any way, there is a completely different network, hardware and configuration stack, we also managed to find the issue of what you experienced a while back and it turned out to be some sort of firmware issue between the NIC and the other parts in your custom system, which we resolved in our test lab after re-diagnosting your ticket, for our internal documentation so that we can resolve it quicker if ever experienced again :)

    I am glad you appreciated our support, we always try to help as best as we can.

    I see... well, as long as its not the same issue :D

    It unfortunately isn't, otherwise it would already have been resolved :)

    Would've loved to keep that dedi (If not upgrade it!) haha!

    oh well, it is what it is.

    Can I ask what firmware was running on the NIC? I'm certain it was compatible... I believe I chose a specific version because only an older version of the firmware was supported & worked on the OS?

    unsure, oh well!

  • RoyaleHostingRoyaleHosting Member, Patron Provider
    edited April 6

    @ilikebeans said:

    @RoyaleHosting said:

    @ilikebeans said:
    l> @RoyaleHosting said:

    @ilikebeans said:

    @RoyaleHosting said:

    @ilikebeans said:

    @mw said:
    $100 to the first person with a working fix

    I have a server running Proxmox that refuses to give me networking on a VM. The vendor confirmed the VM's IP shows up in the ARP table but it cannot ping anything, not even the gateway

    0-access-r02b08-drt-ams5.royalehosting.net(config)#show arp vrf internet <IP removed>

Address         Age (sec)  Hardware Addr   Interface
<IP removed>      0:00:51  bc24.116f.970e  Vlan100, Ethernet1/1

    It's a brand new Proxmox install, all I did was create the VM and configure it the way all our other VMs are configured

    Host:

    root@host:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
        address 45.94.x.2/24
        gateway 45.94.x.1
        bridge-ports enp1s0f0np0
        bridge-stp off
        bridge-fd 0

iface enp1s0f0np0 inet manual

iface enp1s0f1np1 inet manual


source /etc/network/interfaces.d/*

    VM:

    • ens18 is bridged to vmbr0

      root@vm:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto ens18
iface ens18 inet static
        address 45.94.x.3/24
        gateway 45.94.x.1

    It's a 9950X on a Supermicro board with 2x 40G NICs, nothing exotic.

    I've tried:

    • Using the vendors provided prefix
    • Using our prefix
    • With and without LACP on the host
    • Reinstalling the host and VM
    • Swapping IPs between the host and VM
    • Bridging the 2nd 40G interface to vmbr1 and giving that to the VM
    • Praying
    • A CT container
    • virtio and Intel E1000 NICs
    • Changing MTU
    • Spoofing the host MAC's unused interface for the VMs NIC

    Other boxes in this rack have VMs running fine. What could I be missing?

    I HAD THIS EXACT ISSUE WITH THE EXACT SPEC YOUR HAVING, WITH THE EXACT SAME HOST!!!!

    (although i had a 200G port & connectx6 mellanox NIC)

    good luck fixing it, because i couldnt even after a reinstall. Royale wont be able to help...

    GOOD LUCK!!!

    is this by any chance the 45.94.221.0/24 range?

    This is simply not the case. Additionally, we have been constantly assisting the customer to the best of our ability, and it is not at all related to any hardware or network-level issue. We have already carefully factored out these possibilities, even going as far as replacing the complete system just to make sure. We still have an active ticket with this customer, assisting them with any questions or configuration changes.

    well if they're on the range i mentioned & they're having the exact same issue im having... this isnt a coincidence.

    Your support was good to me aswell, just to be clear. its just we physically couldnt find a fix for this issue.

    The issue is not identical at all, I appreciate you commenting and trying to share your experience to see if the issues could be related, but they are not related in any way, there is a completely different network, hardware and configuration stack, we also managed to find the issue of what you experienced a while back and it turned out to be some sort of firmware issue between the NIC and the other parts in your custom system, which we resolved in our test lab after re-diagnosting your ticket, for our internal documentation so that we can resolve it quicker if ever experienced again :)

    I am glad you appreciated our support, we always try to help as best as we can.

    I see... well, as long as its not the same issue :D

    It unfortunately isn't, otherwise it would already have been resolved :)

    Would've loved to keep that dedi (If not upgrade it!) haha!

    oh well, it is what it is.

    Can I ask what firmware was running on the NIC? I'm certain it was compatible... I believe I chose a specific version because only an older version of the firmware was supported & worked on the OS?

    unsure, oh well!

    You're welcome to re-order anytime! :) The firmware version on the motherboard caused the issues with the NIC, not the firmware on the NIC.

  • ilikebeansilikebeans Member

    @RoyaleHosting said:

    @ilikebeans said:

    @RoyaleHosting said:

    @ilikebeans said:
    l> @RoyaleHosting said:

    @ilikebeans said:

    @RoyaleHosting said:

    @ilikebeans said:

    @mw said:
    $100 to the first person with a working fix

    I have a server running Proxmox that refuses to give me networking on a VM. The vendor confirmed the VM's IP shows up in the ARP table but it cannot ping anything, not even the gateway

    0-access-r02b08-drt-ams5.royalehosting.net(config)#show arp vrf internet <IP removed>

Address         Age (sec)  Hardware Addr   Interface
<IP removed>      0:00:51  bc24.116f.970e  Vlan100, Ethernet1/1

    It's a brand new Proxmox install, all I did was create the VM and configure it the way all our other VMs are configured

    Host:

    root@host:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
        address 45.94.x.2/24
        gateway 45.94.x.1
        bridge-ports enp1s0f0np0
        bridge-stp off
        bridge-fd 0

iface enp1s0f0np0 inet manual

iface enp1s0f1np1 inet manual


source /etc/network/interfaces.d/*

    VM:

    • ens18 is bridged to vmbr0

      root@vm:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto ens18
iface ens18 inet static
        address 45.94.x.3/24
        gateway 45.94.x.1

    It's a 9950X on a Supermicro board with 2x 40G NICs, nothing exotic.

    I've tried:

    • Using the vendors provided prefix
    • Using our prefix
    • With and without LACP on the host
    • Reinstalling the host and VM
    • Swapping IPs between the host and VM
    • Bridging the 2nd 40G interface to vmbr1 and giving that to the VM
    • Praying
    • A CT container
    • virtio and Intel E1000 NICs
    • Changing MTU
    • Spoofing the host MAC's unused interface for the VMs NIC

    Other boxes in this rack have VMs running fine. What could I be missing?

    I HAD THIS EXACT ISSUE WITH THE EXACT SPEC YOUR HAVING, WITH THE EXACT SAME HOST!!!!

    (although i had a 200G port & connectx6 mellanox NIC)

    good luck fixing it, because i couldnt even after a reinstall. Royale wont be able to help...

    GOOD LUCK!!!

    is this by any chance the 45.94.221.0/24 range?

    This is simply not the case. Additionally, we have been constantly assisting the customer to the best of our ability, and it is not at all related to any hardware or network-level issue. We have already carefully factored out these possibilities, even going as far as replacing the complete system just to make sure. We still have an active ticket with this customer, assisting them with any questions or configuration changes.

    well if they're on the range i mentioned & they're having the exact same issue im having... this isnt a coincidence.

    Your support was good to me aswell, just to be clear. its just we physically couldnt find a fix for this issue.

    The issue is not identical at all, I appreciate you commenting and trying to share your experience to see if the issues could be related, but they are not related in any way, there is a completely different network, hardware and configuration stack, we also managed to find the issue of what you experienced a while back and it turned out to be some sort of firmware issue between the NIC and the other parts in your custom system, which we resolved in our test lab after re-diagnosting your ticket, for our internal documentation so that we can resolve it quicker if ever experienced again :)

    I am glad you appreciated our support, we always try to help as best as we can.

    I see... well, as long as its not the same issue :D

    It unfortunately isn't, otherwise it would already have been resolved :)

    Would've loved to keep that dedi (If not upgrade it!) haha!

    oh well, it is what it is.

    Can I ask what firmware was running on the NIC? I'm certain it was compatible... I believe I chose a specific version because only an older version of the firmware was supported & worked on the OS?

    unsure, oh well!

    You're welcome to re-order anytime! :) The firmware version on the motherboard caused the issues with the NIC, not the firmware on the NIC.

    ahh I see... good to know.

    Thanks!

  • RoyaleHostingRoyaleHosting Member, Patron Provider

    @ilikebeans said:

    @RoyaleHosting said:

    @ilikebeans said:

    @RoyaleHosting said:

    @ilikebeans said:
    l> @RoyaleHosting said:

    @ilikebeans said:

    @RoyaleHosting said:

    @ilikebeans said:

    @mw said:
    $100 to the first person with a working fix

    I have a server running Proxmox that refuses to give me networking on a VM. The vendor confirmed the VM's IP shows up in the ARP table but it cannot ping anything, not even the gateway

    0-access-r02b08-drt-ams5.royalehosting.net(config)#show arp vrf internet <IP removed>

Address         Age (sec)  Hardware Addr   Interface
<IP removed>      0:00:51  bc24.116f.970e  Vlan100, Ethernet1/1

    It's a brand new Proxmox install, all I did was create the VM and configure it the way all our other VMs are configured

    Host:

    root@host:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
        address 45.94.x.2/24
        gateway 45.94.x.1
        bridge-ports enp1s0f0np0
        bridge-stp off
        bridge-fd 0

iface enp1s0f0np0 inet manual

iface enp1s0f1np1 inet manual


source /etc/network/interfaces.d/*

    VM:

    • ens18 is bridged to vmbr0

      root@vm:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto ens18
iface ens18 inet static
        address 45.94.x.3/24
        gateway 45.94.x.1

    It's a 9950X on a Supermicro board with 2x 40G NICs, nothing exotic.

    I've tried:

    • Using the vendors provided prefix
    • Using our prefix
    • With and without LACP on the host
    • Reinstalling the host and VM
    • Swapping IPs between the host and VM
    • Bridging the 2nd 40G interface to vmbr1 and giving that to the VM
    • Praying
    • A CT container
    • virtio and Intel E1000 NICs
    • Changing MTU
    • Spoofing the host MAC's unused interface for the VMs NIC

    Other boxes in this rack have VMs running fine. What could I be missing?

    I HAD THIS EXACT ISSUE WITH THE EXACT SPEC YOUR HAVING, WITH THE EXACT SAME HOST!!!!

    (although i had a 200G port & connectx6 mellanox NIC)

    good luck fixing it, because i couldnt even after a reinstall. Royale wont be able to help...

    GOOD LUCK!!!

    is this by any chance the 45.94.221.0/24 range?

    This is simply not the case. Additionally, we have been constantly assisting the customer to the best of our ability, and it is not at all related to any hardware or network-level issue. We have already carefully factored out these possibilities, even going as far as replacing the complete system just to make sure. We still have an active ticket with this customer, assisting them with any questions or configuration changes.

    well if they're on the range i mentioned & they're having the exact same issue im having... this isnt a coincidence.

    Your support was good to me aswell, just to be clear. its just we physically couldnt find a fix for this issue.

    The issue is not identical at all, I appreciate you commenting and trying to share your experience to see if the issues could be related, but they are not related in any way, there is a completely different network, hardware and configuration stack, we also managed to find the issue of what you experienced a while back and it turned out to be some sort of firmware issue between the NIC and the other parts in your custom system, which we resolved in our test lab after re-diagnosting your ticket, for our internal documentation so that we can resolve it quicker if ever experienced again :)

    I am glad you appreciated our support, we always try to help as best as we can.

    I see... well, as long as its not the same issue :D

    It unfortunately isn't, otherwise it would already have been resolved :)

    Would've loved to keep that dedi (If not upgrade it!) haha!

    oh well, it is what it is.

    Can I ask what firmware was running on the NIC? I'm certain it was compatible... I believe I chose a specific version because only an older version of the firmware was supported & worked on the OS?

    unsure, oh well!

    You're welcome to re-order anytime! :) The firmware version on the motherboard caused the issues with the NIC, not the firmware on the NIC.

    ahh I see... good to know.

    Thanks!

    No problem!

  • AndreixAndreix Member, Host Rep
    edited April 6

    May be a long shot... but is the subnet properly authenticated and visible in DFZ?
    Are you sure there's no one else (not even RADB or ALTDB) that validates another origin?

    If you don't fix it until tomorrow, I could try to help you out after 10 AM (EEST).

    Thanked by 1mw
  • mwmw Member

    @Andreix said:
    May be a long shot... but is the subnet properly authenticated and visible in DFZ?
    Are you sure there's no one else (not even RADB or ALTDB) that validates another origin?

    i dont think its to do with BGP/routing, the prefix works fine on all the others boxes in the rack we have VMs running on, and i tested with the vendors own prefix to rule out issues with mine

  • AndreixAndreix Member, Host Rep
    edited April 6

    @mw said:

    @Andreix said:
    May be a long shot... but is the subnet properly authenticated and visible in DFZ?
    Are you sure there's no one else (not even RADB or ALTDB) that validates another origin?

    i dont think its to do with BGP/routing, the prefix works fine on all the others boxes in the rack we have VMs running on, and i tested with the vendors own prefix to rule out issues with mine

    and it worked with provider's prefix?

    PS: Just as a suggestion, a service provider is usually referenced as "provider"... "vendor" is used more to refer to a product developer or manufacturer (eg. HP, Dell, WHMCS ... etc.)

  • mwmw Member

    @Andreix said:

    @mw said:

    @Andreix said:
    May be a long shot... but is the subnet properly authenticated and visible in DFZ?
    Are you sure there's no one else (not even RADB or ALTDB) that validates another origin?

    i dont think its to do with BGP/routing, the prefix works fine on all the others boxes in the rack we have VMs running on, and i tested with the vendors own prefix to rule out issues with mine

    and it worked with provider's prefix?

    PS: Just as a suggestion, a service provider is usually a referenced to as "provider"... "vendor" is used more to refer to a product developer or manufacturer (eg. HP, Dell, WHMCS ... etc.)

    it didnt work with their prefix, no

  • ehabehab Member
    edited April 6

    if its ovh then we need this face to cast away evil eyes

    Thanked by 1maverick
  • mwmw Member

    @ehab said:
    if its ovh then we need this face to cast away evil eyes

    my VMs on OVH work fine haha

  • nszervernszerver Member

    @mw said:
    $100 to the first person with a working fix

    I have a server running Proxmox that refuses to give me networking on a VM. The vendor confirmed the VM's IP shows up in the ARP table but it cannot ping anything, not even the gateway

    0-access-r02b08-drt-ams5.royalehosting.net(config)#show arp vrf internet <IP removed>

Address         Age (sec)  Hardware Addr   Interface
<IP removed>      0:00:51  bc24.116f.970e  Vlan100, Ethernet1/1

    It's a brand new Proxmox install, all I did was create the VM and configure it the way all our other VMs are configured

    Host:

    root@host:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
        address 45.94.x.2/24
        gateway 45.94.x.1
        bridge-ports enp1s0f0np0
        bridge-stp off
        bridge-fd 0

iface enp1s0f0np0 inet manual

iface enp1s0f1np1 inet manual


source /etc/network/interfaces.d/*

    VM:

    • ens18 is bridged to vmbr0

      root@vm:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto ens18
iface ens18 inet static
        address 45.94.x.3/24
        gateway 45.94.x.1

    It's a 9950X on a Supermicro board with 2x 40G NICs, nothing exotic.

    I've tried:

    • Using the vendors provided prefix
    • Using our prefix
    • With and without LACP on the host
    • Reinstalling the host and VM
    • Swapping IPs between the host and VM
    • Bridging the 2nd 40G interface to vmbr1 and giving that to the VM
    • Praying
    • A CT container
    • virtio and Intel E1000 NICs
    • Changing MTU
    • Spoofing the host MAC's unused interface for the VMs NIC

    Other boxes in this rack have VMs running fine. What could I be missing?

    sysctl net.ipv4.ip_forward=1

  • FalzoFalzo Member

    @mw said:

    @Falzo said:

    routed setup

    This works, the VM now has networking.

    guess you owe me $100 then.

    Thanked by 3Ympker adly Frameworks
  • AndreixAndreix Member, Host Rep

    @mw said:

    @Andreix said:

    @mw said:

    @Andreix said:
    May be a long shot... but is the subnet properly authenticated and visible in DFZ?
    Are you sure there's no one else (not even RADB or ALTDB) that validates another origin?

    i dont think its to do with BGP/routing, the prefix works fine on all the others boxes in the rack we have VMs running on, and i tested with the vendors own prefix to rule out issues with mine

    and it worked with provider's prefix?

    PS: Just as a suggestion, a service provider is usually a referenced to as "provider"... "vendor" is used more to refer to a product developer or manufacturer (eg. HP, Dell, WHMCS ... etc.)

    it didnt work with their prefix, no

    DM me with your t.me or discord ID and I'll reach you tomorrow morning.

  • roblowendroblowend Member

    I had the EXACT same issue. Are you using TempleOS on the VM per chance?

    Thanked by 2naphtha WyvernCo
  • nszervernszerver Member
    edited April 6

    If you give VPS to Gateway server IP address?
    so in proxmox:

    VM IP: 45.94.x.5/32 Gateway: 45.94.x.2 Nameserver 1.1.1.1 So did you try it?
    Or
    Just or VPS VM IP/24 Try IP/32

    VM IP: 45.94.x.3/32 Gateway: 45.94.x.1 Nameserver 1.1.1.1 So did you try it?

  • mwmw Member

    @nszerver said:

    @mw said:
    $100 to the first person with a working fix

    I have a server running Proxmox that refuses to give me networking on a VM. The vendor confirmed the VM's IP shows up in the ARP table but it cannot ping anything, not even the gateway

    0-access-r02b08-drt-ams5.royalehosting.net(config)#show arp vrf internet <IP removed>

Address         Age (sec)  Hardware Addr   Interface
<IP removed>      0:00:51  bc24.116f.970e  Vlan100, Ethernet1/1

    It's a brand new Proxmox install, all I did was create the VM and configure it the way all our other VMs are configured

    Host:

    root@host:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
        address 45.94.x.2/24
        gateway 45.94.x.1
        bridge-ports enp1s0f0np0
        bridge-stp off
        bridge-fd 0

iface enp1s0f0np0 inet manual

iface enp1s0f1np1 inet manual


source /etc/network/interfaces.d/*

    VM:

    • ens18 is bridged to vmbr0

      root@vm:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto ens18
iface ens18 inet static
        address 45.94.x.3/24
        gateway 45.94.x.1

    It's a 9950X on a Supermicro board with 2x 40G NICs, nothing exotic.

    I've tried:

    • Using the vendors provided prefix
    • Using our prefix
    • With and without LACP on the host
    • Reinstalling the host and VM
    • Swapping IPs between the host and VM
    • Bridging the 2nd 40G interface to vmbr1 and giving that to the VM
    • Praying
    • A CT container
    • virtio and Intel E1000 NICs
    • Changing MTU
    • Spoofing the host MAC's unused interface for the VMs NIC

    Other boxes in this rack have VMs running fine. What could I be missing?

    sysctl net.ipv4.ip_forward=1

    Already tried this, it didn't work and isn't needed as I'm not forwarding

    @Falzo said:

    @mw said:

    @Falzo said:

    routed setup

    This works, the VM now has networking.

    guess you owe me $100 then.

    Wish it was a valid solution

    @roblowend said:
    I had the EXACT same issue. Are you using TempleOS on the VM per chance?

    i can't tell if you're being serious or not

    @nszerver said:
    If you give VPS to Gateway server IP address?
    so in proxmox:

    VM IP: 45.94.x.5/32 Gateway: 45.94.x.2 Nameserver 1.1.1.1 So did you try it?

    This sounds like the routed configuration Falzo mentioned, if so, it gives the VM networking but won't work in our use case

    The provider is busy looking into it so I'm hoping they come up with a fix

Sign In or Register to comment.