Post #2488632
2026-04-26 21:53 UTC
@yala@degrowth.social This is on a Netcup VM, and when you order additional IPv4 from them, you just get a random address from one of their allocations, usually outside of the network your main address is in. Should still work as a pointopoint interface when assigned directly to a container on a bridged network, but I don't particularly like that kind of setup either.
IPv6 would be less of a problem (but I primarily need IPv4 connectivity in this case).
Anyway, I thought there maybe would be some configuration like floating public IPs in Openstack, where you just map one to a VM, and Openstack does all the NAT magic for traffic towards the Internet.
Replies (1)
-
@yala@degrowth.social 2026-04-26 22:44
@galaxis@mastodon.infra.de They still would need to have a marker, even with SNAT, to know which IP traffic came from. Which then also can be just a separate interface as well. I did this once with Ubuntu and Netplan, which is a huge mess, looking at the world from inside Hetzner. The 33 of wiki is not even declared and IPv6 just works, since the container attaches to the bridge and picks a range within the /64. 35 and 36 are not even assigned to LXD system containers, but have local Docker Ports mapped.