6 months with NAT IPv4 only

Dear/madam,

I am writing to share my experience of six months with NAT IPv4 only, kindly requesting your feedback on my approach.

My setup was IPv6 native with port forwards for IPv4-only services. Gaming worked mostly, except for peer-to-peer matchmaking itself which required dedicated IP only. My bank access failed entirely after two months, redirecting to error page itself.

The migration to Hetzner with dedicated IP cost me double. IPv6 is future only, but present requires IPv4 still.

Has anyone managed banking with NAT IPv4 successfully? Kindly advise.

Thank you,
Priya

Actually, (this is (somewhat) common with CGNAT (carrier-grade NAT (RFC 6598)) implementations). The banking issue (specifically (certificate pinning (combined with (IP reputation checks)))) fails because (shared IPs (often (previously (abused)))).

My recommendation:
1. (tunnel (via (wireguard (to (VPS (with (dedicated IP)))))))
2. (or (use (mobile hotspot (for (banking (only))))))

(lessons learned (from (my (proxmox (cluster (setup))))): (IPv6 (is (not (yet (reliable (enough (for (critical (workloads))))))))))

Actually, "previously" is misspelled in your RFC citation. You wrote "previosuly" in your previous post. I will assume typo.

NAT IPv4 banking failures are well-documented. This is not a configuration error. The semicolon separates two independent clauses: banks block known hosting IP ranges. Shared IPs amplify the problem.

Your gaming worked because UDP hole punching functions adequately. TCP authentication streams do not. This is expected behavior. No correction needed.

I despise emojis in technical discussion.

| shared IP reputation: redirected to /dev/null
| bank security team: piped your traffic to fraud detection
| IPv6-only future: EOF not reached
| your patience: admirable, but ultimately redirected

I ran NAT IPv4 with RackNerd for eight months. All gaming traffic redirected successfully. Banking traffic redirected to error page. Support ticket redirected to auto-reply. My money redirected to new provider.

EOF