3 ms·

> How does NAT not block incoming traffic? https://samy.pl/pwnat/ https://samy.pl/pwnat/ NAT != firewall

• umanwizard 7y ago
  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 ?
  • crankylinuxuser 7y ago
    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 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?
    • deleted 7y ago
      [deleted]