4 ms·
A NAT is going to have to have a timeout, otherwise it will gradually leak and run out of ports. All protocols that operate behind NAT must implement keepalive.
by api 6y ago
A NAT is going to have to have a timeout, otherwise it will gradually leak and run out of ports. All protocols that operate behind NAT must implement keepalive.
The solution is IPv6. Then you don't need your ISP to maintain a stateful connection table.
- arghwhat 6y agoI'll be pedantic: you mean that the solution is no NAT, with IPv6 being something needed to get there. Nothing stops you from NAT'ing IPv6.
- api 6y ago> Nothing stops you from NAT'ing IPv6. Nothing stops you from filling your car with orange juice either.
- fulafel 6y agoAs proven by Microsoft in Azure's IPv6 support.
- arghwhat 6y agoNAT'ing IPv6 works and is merely not a necessity. It could still have a purpose, It just won't be address exhaustion. Filling your car with orange juice presumably stops it from working and is likely to cause damage, all while your parents question where things went wrong.