you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 1 year ago (5 children)

Idk man, NAT makes a lot of sense once you get used to it.

That's a lie, NAT is bullshit, sometimes necessary, but it will never "make sense".

  • source
  • parent
  • hideshow 5 child comments
  • [–] 6 points 1 year ago (4 children)

    I like that none of my local devices are externally addressable unless an outgoing connection has been established. You can (and should) achieve the same thing with ipv6, but then it's essentially just maintaining a NAT table without the translation piece. I think that makes sense in both protocols.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 3 points 1 year ago (1 child)

    exactly, I also like this peace of mind for my home network and see no benefit in using ipv6 there. Similarly for any VPC I deploy to an IaaS.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 1 year ago

    I'm actually trying a hybrid approach with some VPCs: use firewalled IPv6 ports for remote management, direct to the VMs; while siphoning off the IPv4 traffic to a basic Linux host with Netfilter rules acting as a NAT router. I keep the benefits of using IPv6, without eating up a bunch of external IPv4 addresses, that I would also have to account for on filtering.

  • source
  • parent
  • load more comments (2 replies)
  • load more comments (2 replies)