Networking on a Cloud Server

Gunner Iwinski

New Member
Mar 16, 2019
2
0
1
I recently purchased a cloud server through IONOS Cloud. With my package, they gave me 1 public IPv4 address and a IPv6/64 network.
I installed Proxmox VE without any issue and I can ping out from the host console.
However, I cannot seem to get any of my containers to ping out (either the "destination host is uncreachable" or "network unreachable" depending on how I configured the container.)

My question is, what should the network settings of my container be in order for it to reach the public and be accessible via one of my assigned IPv6 addresses?

Currently my settings are:

Host
<code>
auto lo
iface lo inet loopback

allow-hotplug ens192
iface ens192 inet dhcp

iface ens192 inet6 static
accept_ra 0
address 2607:f1c0:1800:50::1 (public IPv6 for server)
netmask 64
gateway fe80::1


auto vmbr0
iface vmbr0 inet dhcp
bridge_ports ens192
bridge_stp off
bridge_fd 0
</code>


Container
IP - 2607:f1c0:1800:50::2/64 (public IPv6 from assigned range)
Gateway - fe80::1


Thank you in advance for any ideas!
 
Last edited:
I recently purchased a cloud server through IONOS Cloud. With my package, they gave me 1 public IPv4 address and a IPv6/64 network.

Even you've got an "IPv6/64 network" it does not implicitly mean that you can use them for extending the provider's your network by your virtual one inside Proxmox VE. Most providers do not allow any unknown MAC in their network (and that is the case when you connect your container's NIC directly to vmbr0)

My question is, what should the network settings of my container be in order for it to reach the public and be accessible via one of my assigned IPv6 addresses?

Currently my settings are:

Host
<code>
auto lo
iface lo inet loopback

allow-hotplug ens192
iface ens192 inet dhcp

iface ens192 inet6 static
accept_ra 0
address 2607:f1c0:1800:50::1 (public IPv6 for server)
netmask 64
gateway fe80::1


auto vmbr0
iface vmbr0 inet dhcp
bridge_ports ens192
bridge_stp off
bridge_fd 0
</code>


Container
IP - 2607:f1c0:1800:50::2/64 (public IPv6 from assigned range)
Gateway - fe80::1

As mentioned before: 2607:f1c0:1800:50::2/64 is assigned to an unknown (from provider's point of view) MAC address.

Not 100% sure, but that's probably the reason for the problem you described.
 
I see. So I would need to touch base with my provider and see what their conditions are on allowing my MACs?
Or could this be solved through setting ProxMox to a NATed bridge?
 
I see. So I would need to touch base with my provider and see what their conditions are on allowing my MACs?
Or could this be solved through setting ProxMox to a NATed bridge?
Both options are possible - the first one is more straight forward, but the question is if your provider supports it - maybe it requires additional fee to be paid.

The second one will work for sure but it depends on your needs if it is sufficient respectively convenient.
 
Hello, I´m facing the same trouble with the dedicated server on ionos every time they figure out I´m using the VM´s they block my outside connection.

My question is if you could resolve your trouble, please.
 
Hello,

Cloud Providers such as Hetzner Online or 1&1 are routing the IPv6 Block to the link local address of your machine, which depends on the mac address...

Because of this you can not use the bridge method.

You have to route between your VMs and the network of your provider.

Your Interface in the network of the provider
Code:
iface ens192 inet6 static
accept_ra 0
address 2607:f1c0:1800:50:ffff::1 (public IPv6 for server)
netmask 112 (choose a relative small piece of the network)
gateway fe80::1

VMBR0 (your VM Bridge)
Code:
auto vmbr0
iface vmbr0 inet manual
bridge_ports none
bridge_stp off
bridge_fd 0

iface vmbr0 inet6 static
    address 2607:f1c0:1800:50::1/65


Enable IPv6 forwarding by editing /etc/sysctl.conf and uncommenting the line for net.ipv6.conf.all.forwarding. Then make the same change for the running kernel or reboot the host System.


Now you can assign IPv6 IPs from the following Range to your VMs

2607:f1c0:1800:50::2 - 2607:f1c0:1800:50:7fff:ffff:ffff:fffe
Netmask 65
Gateway 2607:f1c0:1800:50::1


the last point is to allow traffic via iptables on the hostsystem.

please try and report if it is not working
 

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!

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!