You are viewing a single thread.
View all comments View context
16 points

NAT still has its place in obfuscating the internal network. Also, it’s easier to think about firewall/routing when you segregate a network behind a router on its own subnet, IMO.

permalink
report
parent
reply
11 points

Given how large the address space is, it’s super easy to segregate out your networks to the nth degree and apply proper firewall rules.

There’s no reason your clients can’t have public, world routeable IPs as well as security.

Security via obfuscation isn’t security. It’s a crutch.

permalink
report
parent
reply
9 points
*

There’s no reason your clients can’t have public, world routeable IPs as well as security.

There are a lot of valid reasons, other than security, for why you wouldn’t want that though. You don’t necessarily want to allow any client’s activity to be traceable on an individual level, nor do you want to allow people to do things like count the number of clients at a particular location. Information like that is just unnecessary to expose, even if hiding it doesn’t make anything more secure per se.

permalink
report
parent
reply
12 points

Well good news. Because ipv6 has a thing called privacy extensions which has been switched on by default on every device I’ve used.

That generates random ipv6 addresses (which are regularly rotated) that are used for outgoing connections. Your router should block incoming connections to those ips but the os will too. The proper permanent ip address isn’t used for outgoing connections and the address space allocated to each user makes a brute force scan more prohibitive than scanning the whole Ipv4 Internet.

So I’m going to say that using routable ipv6 addresses with privacy extensions is more secure than a single Ipv4 Nat address with dnat.

permalink
report
parent
reply
6 points

Obfuscation is not security, and not having IPv6 causes other issues. Including some security/privacy ones.

There is no problem having a border firewall in IPv6. NAT does not help that situation at all.

permalink
report
parent
reply
6 points

Obfuscation is not security

Yes, of course. But saying trite things like that doesn’t get around the idea that giving out a map of the internal network by default isn’t the best policy.

permalink
report
parent
reply
1 point

So instead we open up a bunch of other issues.

With CGNAT, governments still spy on individual addresses when they want. Since those individual addresses now cover a whole bunch of people, they effectively spy on large groups, most of whom have nothing to do with whatever they’re investigating. At least with IPv6, it’d be targetted.

NAT obscurity comes at a cost. Its gain is so little that even a small cost eliminates its benefit.

permalink
report
parent
reply
2 points

You don’t need to give up IPV6 to have NAT though.

permalink
report
parent
reply
2 points
*

But why bother? “Let’s make my network slower and more complicated so it works like a hack on the old thing”.

permalink
report
parent
reply
6 points

That’s what temporary privacy addresses are for. Clients can just keep generating new addresses in your /64, which is it’s own subnet.

permalink
report
parent
reply

Programmer Humor

!programmerhumor@lemmy.ml

Create post

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

  • Posts must be relevant to programming, programmers, or computer science.
  • No NSFW content.
  • Jokes must be in good taste. No hate speech, bigotry, etc.

Community stats

  • 6.2K

    Monthly active users

  • 775

    Posts

  • 6.8K

    Comments

Community moderators