News for hackers. Stuff that matters.
Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by tenebrisalietum on Monday October 28, 2019 @12:35PM (#21378502)
NAT destroys the end-to-end principle and encourages things like CGNAT, which make side-stepping centralized services impossible. I really hope IPv6 starts becoming commonplace and that the outcome isn't that CGNAT becomes the norm for residential Internet connections.
Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by cnst on Monday October 28, 2019 @12:47PM (#21378646)
The best part about IPv6 is that it's now possible to SSH directly into your laptop if you're using a hotspot from T-Mobile US, for example — it gives you at least a whole /64, so, your laptop gets a fully-routable IPv6 address.

Which is kind of ironic, because you don't get that with most wireline connections, as they're all done through IPv4 NAT.

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by cfallin on Monday October 28, 2019 @12:52PM (#21378723)
This is my favorite bit about native IPv6 at home [0]. No more port forwarding to expose particular services -- I can just `ssh desktop.home.net` or `ssh other.home.net`, and they both get to run on default ports! (Of course, one probably wants a firewall -- I block inbound IPv6 by default except ssh.)

[0] Comcast is surprisingly good here -- they'll give you a /60 (16 /64 networks) if you ask for it with the right DHCP option!

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by tialaramex on Monday October 28, 2019 @08:21PM (#21383183)
Yes, you probably should have a firewall but the sheer size of IPv6 means that whereas I'll have several idiots banging their heads on my SSH services at any one time on IPv4 I'm not sure I've ever had one trying on IPv6 in the years that I've had service available on both public IPv4 and IPv6.

If you set a machine to try just one IP address per second in IPv4 you'll explore a significant fraction of the whole public address space per year. In IPv6 doing that is extremely unlikely to find even a single valid address to connect to in a human lifetime.

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by magicalhippo on Monday October 28, 2019 @05:57PM (#21382154)
That was one of my motivations to try IPv6 at home, only to quickly get disappointed because my ISP gives me a new prefix change very often (in stark contrast to my IPv4 address for some reason).
Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by ripdog on Monday October 28, 2019 @07:08PM (#21382755)
I have this issue too, so I use Ddclient-curl to do dynamic dns via cloudflare.

DDNS is something that I once thought would be an artifact of a less civilized time, but ISPs gotta upsell, I guess.

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by magicalhippo on Monday October 28, 2019 @07:19PM (#21382827)
Main problem for me is that my router doesn't update firewall rules when prefix changes, and I can't get it to not advertise its public ip for the DNS resolver running on the router which of course breaks when the prefix changes.
Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by ripdog on Monday October 28, 2019 @08:13PM (#21383135)
Hmm. I run pfsense, it advertises its own v6 address as a DNS resolver, and I've never had any issues with it breaking. Admittedly, I don't know it isn't just falling back to v4 for a period when the prefix changes. But I did just check and my PC is getting the correct v6 addr of my router as DNS resolver.
Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by magicalhippo on Monday October 28, 2019 @08:24PM (#21383204)
> Admittedly, I don't know it isn't just falling back to v4 for a period when the prefix changes.

At the very least, IPv4 fallback takes a few seconds for each DNS query, and I've experienced it failing completely in some cases (can't recall if I ever figured out why). So regardless it's a PITA when it happens.

I tried disabling the option for it to advertise itself as a DNS and instead insert the local IPv4 address in the DHCP options but to no avail, clients still ended up with public IPv6 as main DNS.

After a few hours of trying to fix it I just turned off IPv6 again.

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by floren on Monday October 28, 2019 @12:55PM (#21378748)
> [0] Comcast is surprisingly good here -- they'll give you a /60 (16 /64 networks) if you ask for it with the right DHCP option!

Can you go into more detail or point me to instructions? I'm on Comcast and would be interested in getting v6 at home.

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by cfallin on Monday October 28, 2019 @01:04PM (#21378897)
Sure! The keyword to look for is "DHCP-PD" (DHCP prefix delegation).

I run a little OpenBSD router and my dhcpcd.conf is here [1], but I've done this before on a Linux router box too -- here are some instructions from Arch's wiki [2]. IIRC, the stock firmware on my old consumer router was also able to request a prefix and advertise it on the network.

[1] https://gist.github.com/cfallin/e5865a6a93c75ace8d26d6a85287... [2] https://wiki.archlinux.org/index.php/IPv6#Prefix_delegation_...

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by xfalcox on Monday October 28, 2019 @01:22PM (#21379168)
I want to study about the technologies around this part of networking, prefix delegation, radvd, etc. Any materials you can recommend?
Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by sedachv on Monday October 28, 2019 @02:28PM (#21380000)
Hagen's _IPv6 Essentials_ covers the basics, Coffeen's _IPv6 Address Planning_ shows the amazing things you can do with IPv6.
Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by Aloha on Monday October 28, 2019 @01:02PM (#21378868)
I think Comcast is native dual stack across their entire footprint so long as you have new enough hardware
Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by kadoban on Monday October 28, 2019 @01:45PM (#21379465)
This may be a dumb question, but why does one need with a /60 ? Isn't a /64 already ridiculously huge to the point that I could never possibly use it all?
Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by oarsinsync on Monday October 28, 2019 @01:51PM (#21379561)
IETF recommend a /64 as the smallest subnet size to use, as stateless auto address configuration (SLAAC) only works with that subnet size.

Any user that wants more than a single subnet at home is supposed to receive a /48 by the same recommendation base. A lot of ISPs settled on /56s. Comcast is a bit more stingy than some.

That introduces a whole other set of problems.

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by cfallin on Monday October 28, 2019 @01:54PM (#21379590)
The RIPE guidelines at [0] line up with what I've heard as justification before: basically, /64 is the smallest you can go without lots of manual configuration (the way that SLAAC auto-assigns addresses from Ethernet MACs or random bytes only works when the host part of the address is 64 bits). There may be valid technical reasons to want > 1 subnet at a customer site.

And finally, the space is huge -- an ISP would typically get a /32 at least (Whois says that Comcast is using a /26 just for the Bay area), so if every customer gets a /60, that's 2^28, or 256M, delegations. (With the /26, Comcast could hand out 16 billion /60 delegations to their SFBA subscribers.)

[0] https://www.ripe.net/publications/docs/ripe-690#4--size-of-e...

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by zaphoyd on Monday October 28, 2019 @01:53PM (#21379575)
Not a dumb question at all! The smallest IPv6 subnet is /64, so a /60 lets you split your network into multiple subnets without all the software that assumes a subnet is /64 (like address autoconfig) breaking. Why might you need multiple subnets? Lots of reasons, common ones are for security. It lets you do things like split up a home office network from home from guest wifi from IoT/home automation. Also allows new services to be created that use that capability.
Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by anticensor on Tuesday October 29, 2019 @08:07AM (#21386182)
I only need a /100. More internet addresses than Europe has in IPv4. I can statically assign devices their own individual addresses.
Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by snagglegaggle on Monday October 28, 2019 @01:50PM (#21379541)
Not with that attitude.
Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by virusduck on Monday October 28, 2019 @01:19PM (#21379134)
Do you also have an IPv4 address that you can use for NAT for those things that cant use IPv6? (Also do you have devices that aren't capable of using IPv6?)
Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by cfallin on Monday October 28, 2019 @01:34PM (#21379321)
Yes, I have native IPv4 too, with the usual NAT. I think the default router that Comcast will rent to you actually is dualstack in this way too -- IPv4 NAT, and IPv6 prefix advertised for devices that want it.

I actually played with NAT64 for a bit (IPv6-only internally, all IPv4 space is mapped to a special /96 in IPv6-space and NAT'd at the router, and local DNS server on the router returns translated AAAA records for IPv4-only hosts), but dropped that when I simplified my router config. It works, it just takes a bit of config :-)

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by apk17 on Monday October 28, 2019 @02:13PM (#21379817)
Theoretically, yes.

Practically, my laptop is in some Wifi network and has an IPv6 address, but that isn't accessible from the outside because the Wifi/router box blocks incoming connection. That is a wise decision overall, but unforunately replaces the "can't connect because NAT" by "glorious IPv6, bit still can't connect".

And I'm not the owner of those boxes.

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by cnst on Monday October 28, 2019 @02:33PM (#21380046)
It depends.™

I've had a static IPv4 subnet allocation from AT&T on AT&T U-verse, and tried using it on a couple of consumer routers for the local network. Well, guess what — all these devices from major brands that are called "routers" don't actually route between the interfaces, after all — all they did was NAT between my public IPv4 allocation and the main IPv4 address assigned by DHCP. And disabling the NAT simply disconnected the networks — instead of rounting one interface to the other. I actually opened up a support ticket with ZyXEL, which got escalated to their engineering managers, and they did confirm my finding that their routers had a bug in sysctl settings that stops them from routing the interfaces (e.g., sysctl net.ipv4.ip_forward not set to 1).

Anyhow, back to T-Mobile US IPv6 on a hotspot — when I originally tried ssh'ing back to my own box via the public IPv6, things didn't work, either; but I then found out that it was some sort of a local policy on the local machine, because another laptop without a firewall was able to receive connections on IPv6 from the internet without any issues.

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by anticensor on Wednesday October 30, 2019 @01:53PM (#21400500)
Were they all just selling NAT-ing bridges instead of routers? This is a serious fraud.
Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by dvdbloc on Monday October 28, 2019 @12:59PM (#21378815)
Was the former more secure? Most people don’t want their laptop exposed with a fully routable address.
Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by msbarnett on Monday October 28, 2019 @01:38PM (#21379373)
NAT is not a security measure. You want a firewall regardless of whether you’re running IPv4 or IPv6
Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by cnst on Monday October 28, 2019 @01:01PM (#21378862)
That's why you have firewalls. You're already often exposed to all the other users in your coffee shop anyways.

SSH is normally not enabled, either.

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by booi on Monday October 28, 2019 @01:45PM (#21379474)
What do you do for something like printers? I highly doubt Epson's "firewall" is totally secure.
Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by Jonnax on Monday October 28, 2019 @01:57PM (#21379619)
Your home has a gateway router.

You can configure firewall rules on that.

In fact, the default is almost always to disallow all inbound and allow all outbound.

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by jlgaddis on Monday October 28, 2019 @02:36PM (#21380073)
IMO, the "right" answer is that printers go on their own subnet. Access control is managed on their default gateway.
Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by rohan1024 on Monday October 28, 2019 @01:30PM (#21379271)
If you are on Ubuntu, you can run

sudo ufw default deny incoming

and your laptop is now secure.

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by JohnFen on Monday October 28, 2019 @04:23PM (#21381211)
> NAT destroys the end-to-end principle

Yes, and that precisely why I use it in my home network, and will continue to use is with IPv6. I explicitly don't want any IP addresses in my green zone to be directly accessibly from my red zone.

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by Dagger2 on Monday October 28, 2019 @05:19PM (#21381803)
Then you're doing something very wrong. You can't rely on NAT to stop connections, because that's not a thing NAT does.

You need to be using a firewall. NAT is just an extra, useless, complicated and unnecessary thing to be adding to the top of that; one that makes it hard to understand how your network is even working, and which makes it harder rather than easier to secure.

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by umanwizard on Monday October 28, 2019 @10:50PM (#21383904)
Can you explain how an outside person (other than my ISP) can make an outside connection to my laptop despite being behind a NAT? Assuming for concreteness that my laptop's internal (NATted) address is 192.168.1.123 and my router's public address is 123.45.67.89. What sequence of commands would you type to open a TCP connection to my laptop?
Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by takeda on Tuesday October 29, 2019 @12:09AM (#21384198)
NAT is implemented on a firewall, the blocking of incoming connections is a side effect and isn't even intentional (that's why UPnP exists).

Since you already have a firewall you can just add a single rule that block incoming connections and that's all you actually need.

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by ATsch on Tuesday October 29, 2019 @01:27AM (#21384441)
You are right that it would be hard to open a TCP connection with you on a specific target port on a 1:N NAT without UPnP. If you could, IPv4 exhaustion would not be an issue.

However, NAT is just a mapping from an internal IP to an external Port number. With pure NAT, once you have created a connection to the outside, anyone can send packets to that external port, and have them delivered to your device.

Of course, this mapping is inherently lossy. You are mapping the port space of one device onto N devices. This does mean external IPs can only send your devices packets on ports they have previously used as source ports, but you are still not safe. You might own devices that, for example, have vulnerabilities in their networking stack. Not that rare. You also might not want to disclose the number of devices active in a network, allow them to be fingerprinted by their response, or similar. Some UDP client applications might also not check the IP addresses of incoming packets. UDP server applications also commonly use the same socket for connections to other hosts as it listens on.

So, to elaborate on that last example, you might run, say, a video surveillance server. It might listen for RTP on UDP port 12345. It then uses that same socket to send a UDP packet to licensecheck.example.com. That packet will have a source port of 12345. NAT will then map internal_ip:12345 to external_ip:xyz. Anyone can now view your cameras on external_ip:xyz.

So either way, you'll want a stateful firewall. Deny incoming, allow outgoing. That's what firewalls are there for, and that's what gives you your security, NAT or no NAT.

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by Dagger2 on Tuesday October 29, 2019 @09:34AM (#21386916)
If you have routing to the IP, then it's just a matter of:

  $ telnet <ip> <port>
If you don't have routing, then you'll need to arrange it somehow. With the example addresses you gave, you could do it by being on your immediate upstream network and then running:

  $ ip route add 192.168.1.123/24 via 123.45.67.89
  $ telnet 192.168.1.123 <port>
Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by JohnFen on Tuesday October 29, 2019 @01:26PM (#21389718)
> You need to be using a firewall.

Indeed, I never said otherwise.

What I'm saying is that I want to disallow all incoming connections to any machine that isn't in my yellow zone, and selectively forward some traffic to servers in my green zone. I can absolutely use router and firewall rules to accomplish that. But when I do, I've essentially implemented a NAT.

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by msbarnett on Monday October 28, 2019 @06:52PM (#21382625)
Then you want a firewall whether or not you’re NATing. NAT is not a security measure. It offers you no blocking of incoming traffic. It has no inherent security value.
Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by umanwizard on Monday October 28, 2019 @10:23PM (#21383763)
How does NAT not block incoming traffic? I'm genuinely confused. Let's assume my laptop is behind a typical home network NAT with public address 123.45.67.89 and internal address 192.168.1.123 . What sequence of commands do you type to send traffic to my laptop?
Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by dijit on Tuesday October 29, 2019 @01:19AM (#21384417)
FWIW. Most video games that create peer meshes (and bittorrent) will “punch” the NAT. Even with the stateful firewall that is built in to most routers to prevent unestablished connections inbound.

Think of it like this. You need to go to the internet for something. Your NAT will just kludge the packet to make it look like it came from the NAT machine, altering the port and IP.

That port and IP combo needs to get back to your PC so the router keeps the mapping it used in a table and looks up all inbound packets to match on that table.

So if you have sent a packet, you’ve opened a random port.

NAT tries (lazily) to use the source port that matches the destination port. So if you ssh outbound; most NAT implementations will open port 22 to your machine.

But the stateful firewall that usually comes with your router will block random inbound connection attempts or packets from your destination that are not acknowledged.

Tbh, NAT+firewall doesn’t give you anything extra (security-wise) than a plain stateful firewall gives you.

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by takeda on Monday October 28, 2019 @11:49PM (#21384122)
First of all there are multiple kinds of NATs, such as SNAT, DNAT, PAT etc. You can for example have one IP being mapped to another IP statically without changing anything. That's the simplest kind of NAT (it is called SNAT) and doesn't do any blocking.

Most people when they say NAT they mean PAT, that solution translates basically takes an outbound connection, it allocates a port and maps that port to that local computer.

That creates an illusion, of security, but that's all as a side effect, NAT inherently doesn't care about security. There are multiple ways to bypass it, most known is UPnP where hosts can actually request to open an inbound port.

The correct way to block inbound traffic is actually to use firewall. If you have a statefull firewall (currently pretty much all of them are statefull) you basically block inbound traffic to your network and that's it.

UCLA has /16 address space and it doesn't use NAT it just gives static IP addresses to computers. By default all incoming communication is blocked, but you can submit request to have certain ports opened.

Also from my own experience, if you have network with multiple devices, and you want to do something more advanced like traffic shaping, NAT actually makes things much more complicated. You need to keep in mind if you're doing filtering before or after NAT is applied.

For example I had a person on my network catch a virus and started sending mail, which got my mail server blacklisted. So I decided to block outbound connections to port 25, forcing everyone to use local SMTP server. In PF the filtering rules apply after NAT, so at that point the user has the same IP as the server. To correctly filter I need to tag the connection when NAT happens and then perform filtering on tags. Without NAT I could simply just use source IP address to do the filtering. Things become even more complex when you also want to do QoS and label traffic.

To do NAT you do need firewall, and if you have a stateful firewall you can just do the filtering by firewall. NAT was never designed as a security feature and shouldn't be treated as one.

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by msbarnett on Tuesday October 29, 2019 @01:46AM (#21384508)
Most consumer NATs are completely permissive. Put a single device behind it, through some traffic at the NAT, and it will cheerfully forward it to the host despite the data not being correlated with any outbound packets.

With multiple hosts it’s going to depend on the implementation, but it will likely forward it to something it thinks can handle it, because most NATs try to be as transparent as they can, to not trip up unknowledgeable consumers.

NAT is not, and has never been a security measure. Just run a damn firewall if you want to drop incoming traffic. The firewall gives you everything you want; you aren’t gaining a damn thing from the NAT.

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by crankylinuxuser on Monday October 28, 2019 @10:56PM (#21383934)
> How does NAT not block incoming traffic?

https://samy.pl/pwnat/

NAT != firewall

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by umanwizard on Monday October 28, 2019 @11:01PM (#21383949)
This seems to require both ends to be running the pwnat software.

Again, assuming I am not running any special software, what sequence of commands would you type to send a packet to 192.168.1.123 natted behind 123.45.67.89 ?

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by crankylinuxuser on Monday October 28, 2019 @11:07PM (#21383970)
It's indeed true, if in your contrived case, you have a VM doing nothing inside a NAT behind a public IP, you couldn't access it.

https://tools.ietf.org/html/rfc2663 might bee a good start to see where flaws are and how it works. And it's also a great way to see how a destination machine that you're talking with can puncture through your NAT, cause you did already.

And Pwnat didn't strike you as "interesting" in that it could join 2 internal networks as if they were the same collision domain, but not really?

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by tenebrisalietum on Tuesday October 29, 2019 @09:00AM (#21386593)
> I explicitly don't want any IP addresses in my green zone to be directly accessibly from my red zone.

This is exactly what the job of a firewall is.

NAT is a hack due to IP address exhaustion. Any security is a side effect. Nothing that says "NAT" on the tin is obligated to protect you.

NAT on your own network if you really drink that kool-aid is fine. I'm more concerned about CGNAT. If ISPs implement NAT (called CGNAT), it means you can't accept incoming connections without your ISP approving/supporting it. I don't want to have to beg my ISP to open ports for me and question/approve why I'm doing it.

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by JohnFen on Tuesday October 29, 2019 @01:30PM (#21389772)
> This is exactly what the job of a firewall is.

Well, I agree (if you include the router in that). I never asserted otherwise. In fact, this is how I've implemented my NAT.

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by paulddraper on Monday October 28, 2019 @08:06PM (#21383097)
I recommend a firewall in that case.

NAT itself would only be security-through-obscurity.

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by vpzom on Monday October 28, 2019 @09:08PM (#21383415)
Is that actually true? How would outside traffic get through a NAT?
Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by zAy0LfpBZLC8mAC on Monday October 28, 2019 @10:34PM (#21383827)
It doesn't have to get "through NAT", that's not how NAT works. NAT is an address remapping function that can be configured to happen for some particular packets and has nothing to do with the forwarding function/routing that is completely orthogonal to it. Typically, NAT on home routers would be configured to remap the source address of packets coming from the LAN interface destined to the WAN interface as well as any packets in the opposite direction that match flows that were remapped in the outbound direction.

If someone (your ISP, someone who compromised your ISP's router, someone who happens to be your neighbour on an ISP with misconfigured routers ...) sends a packets directly addressed to your internal address range to your WAN interface, that is of no interest to the NAT function and will simply be routed to the LAN interface unchanged.

That is: Unless the device happens to also have a stateful firewall that would prevent that. But then, the firewall would work just as well without NAT.

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by zajio1am on Monday October 28, 2019 @10:17PM (#21383727)
NAT is not a barrier for traffic, so question 'how traffic get through a NAT' does not make sense. Router by default forwards packets. NAT just means that in some cases it also translates src/dst addresses of packets.

If you have a router with NAT and without (stateful) firewall or RPF, and such router receives a packet on wan port with dst address from your private LAN range, then such packet is just passed to your LAN (as NAT does not apply here). Obviously, such packet is unroutable on general Internet, but could be send by our ISP or by other customers of your ISP if they are on the same network (e.g. wifi AP) as your wan port. There are also more sophisticated ways, like abusing automatic decapsulation of packets (if enabled). Fortunately, in most cases a router with NAT also has enabled stateful firewall, so this is moot.

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by umanwizard on Monday October 28, 2019 @10:41PM (#21383866)
> Obviously, such packet is unroutable on general Internet

You buried the lede here. This makes a huge difference. I am much more willing to trust my ISP (a major company who would be quickly found out if they were trying to hack random people) than the entire set of people on the global internet.

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by paulddraper on Monday October 28, 2019 @09:59PM (#21383662)
Outside traffic gets through a NAT all the time.

Including HN, moments before reading this page.

It's true that outside networks usually cannot send a TCP SYN to your local network without IP spoofing or other hackery.

But a firewall is sufficient; there is no need for network address translation.

Re:Ripe NIC: 'In Five Weeks We'll Run Out of IPv4 Internet A... by apk17 on Monday October 28, 2019 @02:48PM (#21380189)
From my vantage point, it is already. The only parties that don't have IPv6 are my employer (which I maybe need to nag about since we're an ISP and have our own AS), and the customer I'm dealing with.