4 ms·

If you care about price this badly just use v6, it's free

• dns_snek 3y ago
  That's not an option if you need to support IPv4-only clients, which the vast majority of services do.
  • andrewaylett 3y ago
    IPv4 clients are a different problem, with a different solution -- NAT is for outbound connections. Of course, plenty of services you want to connect to could only support IPv4. IPv6 internally doesn't stop you running public IPv4-accessible services.
    • dns_snek 3y ago
      I see, I misunderstood, I thought this was for inbound connections.
    • dilyevsky 3y ago
      you will have same issue with ipv4-only servers too
  • ikiris 3y ago
    Start charging those clients an ipv4 fee then.
• andrepew 3y ago
  Unless you’re dependent on one of the many many AWS services that don’t support IPv6-only access. https://docs.aws.amazon.com/vpc/latest/userguide/aws-ipv6-support.html https://docs.aws.amazon.com/vpc/latest/userguide/aws-ipv6-su...
  • sonicanatidae 3y ago
    He's probably being paid by Big v6 to push it.
• p1mrx 3y ago
  There is an ongoing discussion about adding NAT64 support: https://github.com/AndrewGuenther/fck-nat/issues/41 https://github.com/AndrewGuenther/fck-nat/issues/41