Navigation



pwnat – NAT To NAT Client Communication Tool

Last updated: September 9, 2015 | 11,357 views

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.

Share2
Tweet
Share
Buffer
WhatsApp
Email
2 Shares
Posted in: Hacking Tools, Networking Hacking

,


Latest Posts:


Memhunter - Automated Memory Resident Malware Detection Memhunter – Automated Memory Resident Malware Detection
Memhunter is an Automated Memory Resident Malware Detection tool for the hunting of memory resident malware at scale, improving threat hunter analysis process.
March 29, 2020 - 163 Shares
Sandcastle - AWS S3 Bucket Enumeration Tool Sandcastle – AWS S3 Bucket Enumeration Tool
March 24, 2020 - 106 Shares
Astra - API Automated Security Testing For REST Astra – API Automated Security Testing For REST
Astra is a Python-based tool for API Automated Security Testing, REST API penetration testing is complex due to continuous changes in existing APIs.
February 27, 2020 - 559 Shares
Judas DNS - Nameserver DNS Poisoning Attack Tool Judas DNS – Nameserver DNS Poisoning Attack Tool
Judas DNS is a Nameserver DNS Poisoning Attack Tool which functions as a DNS proxy server built to be deployed in place of a taken over nameserver to perform targeted exploitation.
February 19, 2020 - 245 Shares
dsniff Download - Tools for Network Auditing & Password Sniffing dsniff Download – Tools for Network Auditing & Password Sniffing
Dsniff download is a collection of tools for network auditing & penetration testing. Dsniff, filesnarf, mailsnarf, msgsnarf, URLsnarf, and WebSpy passively monitor a network
February 14, 2020 - 298 Shares
OWASP Amass - DNS Enumeration, Attack Surface Mapping & External Asset Discovery OWASP Amass – DNS Enumeration, Attack Surface Mapping & External Asset Discovery
The OWASP Amass Project is a DNS Enumeration, Attack Surface Mapping & External Asset Discovery tool to help information security professionals perform network mapping of attack surfaces.
February 10, 2020 - 254 Shares


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.