Live data from Hacker News

NAT Is the Enemy of Low Power Devices

blog.golioth.io

1–10 of 180 posts

Re: NAT Is the Enemy of Low Power Devices

#7

Interestingly, IPv6 is not listed as the solution

An IPv6 router with a stateful firewall blocking incoming connections could have just the same issues with timeouts, I'd imagine. Switching to IPv6 doesn't just mean that anyone can make a P2P connection to anyone else (even STUN needs a third-party server to coordinate the two peers).

(D)TLS session resumption (I'm not sure if their "Connection IDs" are that or something similar) seems like the most foolproof solution to this scenario, assuming that the remote host can support it.

Re: NAT Is the Enemy of Low Power Devices

#8
post #5

Earlier quoted context omitted.

IPv6 is its own complexity.

Why?

In general, the IPv6 stack is not supported on many smaller mcu. It is not that options like FreeRTOS can't support the stack, but rather the resource constraints pose a challenge.

That being said, most modern SoCs are competitively priced... and will boot Linux just fine for under $5/part. =3

Re: NAT Is the Enemy of Low Power Devices

#9
post #5

Earlier quoted context omitted.

IPv6 is its own complexity.

Why?

Eliminating NAT makes virtual networking much hairier. E.g., my desktop is currently connected to a big enterprise network that keeps track of all devices and will only allocate one IP address per MAC address. That leaves no IPs for any VMs on my desktop to use, so they must go through NAT if they want to communicate with the outside world.
Post reply on HN