pwnat – NAT To NAT Client Communication Tool


pwnat, pronounced “poe-nat”, is a tool that allows any number of clients behind NATs to communicate with a server behind a separate NAT with *no* port forwarding and *no* DMZ setup on any routers in order to directly communicate with each other. The server does not need to know anything about the clients trying to connect.

Simply put, this is a proxy server that works behind a NAT, even when the client is behind a NAT, without any 3rd party. There is no middle man, no proxy, no 3rd party, no UPnP/STUN/ICE required, no spoofing, and no DNS tricks. More importantly, the client can then connect to any host or port on any remote host or to a fixed host and port decided by the server.

pwnat is based off of the UDP tunneling software by Daniel Meekins, udptunnel, and my original chownat.

pwnat will work on most *nix operating systems. Tested on Linux and OS X.

You can download pwnat v0.2-beta here:

pwnat-0.2-beta.tgz

Or read more here.

Posted in: Hacking Tools, Networking Hacking Tools

,


Latest Posts:


Karkinos - Beginner Friendly Penetration Testing Tool Karkinos – Beginner Friendly Penetration Testing Tool
Karkinos is a light-weight Beginner Friendly Penetration Testing Tool, which is basically a 'Swiss Army Knife' for pen-testing and/or hacking CTF's.
Aclpwn.Py - Exploit ACL Based Privilege Escalation Paths in Active Directory Aclpwn.Py – Exploit ACL Based Privilege Escalation Paths in Active Directory
Aclpwn.py is a tool that interacts with BloodHound< to identify and exploit ACL based privilege escalation paths.
Vulhub - Pre-Built Vulnerable Docker Environments For Learning To Hack Vulhub – Pre-Built Vulnerable Docker Environments For Learning To Hack
Vulhub is an open-source collection of pre-built vulnerable docker environments for learning to hack. No pre-existing knowledge of docker is required, just execute two simple commands.
LibInjection - Detect SQL Injection (SQLi) and Cross-Site Scripting (XSS) LibInjection – Detect SQL Injection (SQLi) and Cross-Site Scripting (XSS)
LibInjection is a C library to Detect SQL Injection (SQLi) and Cross-Site Scripting (XSS) through lexical analysis of real-world Attacks.
Grype - Vulnerability Scanner For Container Images & Filesystems Grype – Vulnerability Scanner For Container Images & Filesystems
Grype is a vulnerability scanner for container images and filesystems with an easy to install binary that supports the packages for most major *nix based OS.
APT-Hunter - Threat Hunting Tool via Windows Event Log APT-Hunter – Threat Hunting Tool via Windows Event Log
APT-Hunter is a threat hunting tool for windows event logs made from the perspective of the purple team mindset to provide detection for APT movements hidden in the sea of windows event logs.


7 Responses to pwnat – NAT To NAT Client Communication Tool

  1. GZero April 4, 2010 at 3:12 pm #

    This looks really useful, I would imagine people with restrictive filters on their internet might find a really good use for this.

    It’s also made by Samy Kamkar, who, if memory serves, was the chap who did the Samy friends worm XSS thing on MySpace a few years ago.

    Cool tool

  2. Akagi Kong April 4, 2010 at 3:39 pm #

    Somebody port this bad boy =P

    Sigh, this would be even cooler if it had a Windows port. FreeBSD is my default OS, but I have to work with Windows boxes–a lot.

  3. AnyMoose April 4, 2010 at 7:28 pm #

    @Akagi Kong:
    Try setting up any old computer with Puppy Linux, 2 NICs and min 256MB RAM. When you setup the firewall, share the connection.

    bada-bing-bada-boom?

  4. mendark April 5, 2010 at 11:56 am #

    does it really work?

  5. GZero April 6, 2010 at 10:40 am #

    Akagi Kong:

    If you were to get a copy of MinGW and try to compile this on windows, I

  6. Akagi Kong April 6, 2010 at 12:30 pm #

    Geez, I can do this without pwnat, but if I can do it with pwnat and none of the BS that

  7. antitree April 29, 2010 at 12:01 am #

    This is a cool tool and Samy did some good research but in practice it works only with NAT and not through a firewall like some may thing. By messing with the source and destination IP’s between the header and the datagram, any firewall worth it’s weight purporting “deep packet inspection” will detect this.