kate3
Member
- Joined:
- Jul 2024
- Posts:
- 208
- From:
- Utrecht, NL
Which kernel was openvz 7 running
5.4.203-1-pve on that particular node. But the issue is not the kernel version, it is the OpenVZ kernel patchset. They carry a massive out-of-tree netfilter patch that predates nftables flowtable support for v6. So every packet hits conntrack userspace helper lookup even when no helper is registered.
I tested on Proxmox VE 8 with 6.5 kernel, same hardware, virtio-net: 1.9 Mpps at 14% CPU. The difference is the bridge path, not the hypervisor.
OVHcloud's resolve what? Their DNS64 resolvers are 2001:41d0:3:163::1 and ::2. I have not tested them under load.
virsh list --all | wc -l: 47
danfra
Member
- Joined:
- Jun 2024
- Posts:
- 159
- From:
- Frankfurt, DE
/24 will cost you a kidney by 2028
The broker market is overheated but not irrational. RIPE last /8 policy means you cannot get a new allocation smaller than /22, and only if you are an LIR. End users buy /24 because it is the minimum routable prefix on the global table. Most transit filters reject /25 and longer.
OVHcloud charging €2/month for a single v4 is actually cheap compared to amortized purchase + SWIP fees. A /24 at $48k over 5 years is $800/month. If you need 256 addresses. Most people need one.
NAT64 + v6-only is economically rational for anything that does not need inbound v4. The problem is the long tail of v4-only services. Not the big ones. Google, Cloudflare, Facebook have had v6 for a decade. It is the B2B API from some bank in Germany that breaks.
mitigated 800Gbps before breakfast
Zurich1984
Member
- Joined:
- Jun 2024
- Posts:
- 118
- From:
- Zurich, CH
A /24 at $48k over 5 years is $800/month
You do not amortize IP addresses like a car. They appreciate. That /24 bought in 2020 for $22k sells today for $48k. It is an asset, not a cost.
The people paying €2/month to OVHcloud are renting. The people buying /24s are holding. Different markets, same squeeze.
I predict we see v4-as-a-service from hyperscalers soon. AWS already does this with Elastic IP pricing that scales nonlinearly. Azure will follow. The hobbyist gets priced out first, then the SME, then everyone except Fortune 500 with legacy compliance requirements.
IPv6-only is not the future. It is the present for anyone who cannot pass through the v4 toll booth.
/24 for sale. No lowballs.
GeorgeNmp
Member
OP
AS64512
- Joined:
- May 2024
- Posts:
- 218
- From:
- Ashburn, US
Alerts need to reach PagerDuty and they are still v4-only on some endpoints.
Thank you, this is exactly the kind of operational detail I needed. I had considered tcp_mtu_probing but was concerned about the 10-second black hole detection delay on initial SYN. For interactive workloads that is noticeable.
OVHcloud charging €2/month for a single v4 is actually cheap compared to amortized purchase + SWIP fees.
Cogent's v6 peering disputes are legendary. They depeered HE.net in 2014 and still do not peer with Google over v6 in some regions. Any NAT64 gateway using Cogent for v4 but not v6 creates exactly this kind of asymmetry.
I am going to provision a test instance in OVHcloud Gravelines and run tayga + local unbound with DNS64. Will report back with PMTUD findings across a few target ASNs.
Has anyone here actually gotten OVHcloud's v6-only VPS to route to their Singapore datacenter? The pricing page says "Europe only" but their v6 anycast seems to announce globally. I used https://www.ovhcloud.com/en/vps/ to check the plans.
iBGP, eBGP, don't care, just peer