https://github.com/samyk/pwnat

The only tool/technique to punch holes through firewalls/NATs where multiple clients & server can be behind separate NATs without any 3rd party involvement. Pwnat is a newly developed technique, exploiting a property of NAT translation tables, with no 3rd party, port forwarding, DMZ, DNS, router admin requirements, STUN/TURN/UPnP/ICE, or spoofing.
https://github.com/samyk/pwnat

Last synced: about 1 month ago
JSON representation

The only tool/technique to punch holes through firewalls/NATs where multiple clients & server can be behind separate NATs without any 3rd party involvement. Pwnat is a newly developed technique, exploiting a property of NAT translation tables, with no 3rd party, port forwarding, DMZ, DNS, router admin requirements, STUN/TURN/UPnP/ICE, or spoofing.

• Host: GitHub
• URL: https://github.com/samyk/pwnat
• Owner: samyk
• License: gpl-3.0
• Created: 2012-08-10T05:55:11.000Z (over 12 years ago)
• Default Branch: master
• Last Pushed: 2024-07-05T23:28:10.000Z (4 months ago)
• Last Synced: 2024-09-27T02:45:04.429Z (about 2 months ago)
• Language: C
• Homepage: https://samy.pl/pwnat/
• Size: 131 KB
• Stars: 3,305
• Watchers: 147
• Forks: 486
• Open Issues: 22
• Metadata Files:
  • Readme: README-udptunnel
  • Changelog: Changes
  • License: COPYING-pingtunnel

Awesome Lists containing this project

• awesome-termux-hacking - pwnat - The only tool and technique to punch holes through firewalls/NATs where both clients and server can be behind separate NATs without any 3rd party involvement. Pwnat uses a newly developed technique, exploiting a property of NAT translation tables, with no 3rd party, port forwarding, DMZ, router administrative requirements, STUN/TURN/UPnP/ICE, or spoofing required..[](https://github.com/samyk/pwnat/stargazers/) (Uncategorized / Uncategorized)

README

        
=============================================================================

  UDPTUNNEL README

  Author: Daniel Meekins

  Contact: dmeekins - gmail

  Copyright (C) 2009 Daniel Meekins

=============================================================================

This project tunnels TCP data through a UDP tunnel. The executable can act as

the server or client. The server acts as a proxy for the client, listening

on a specified UDP port and creating a connection to a TCP server that the

client specifies. The client listens on a TCP port, acting as the server that

some TCP client connects to. The client recevies any TCP data on that port 

and sends the data to the udpserver, which sends it to the TCP connection it

made with the desired TCP server.

-----------------------------------------------------------------------------

1.) Building

On *nix systems in Makefile, make sure that the correct value is set for the 

"OS" variable. Then just run 'make'.

On Windows, if using GCC in Cygwin, make sure the "OS" variable is set to

CYGWIN in Makefile and run 'make'.

If using the VC++ compiler (cl.exe), make sure to be in the "Visual Studio

Command Prompt", or at least have all the environment variables set correctly,

then run 'nmake.exe /f Makefile.Win32'. Also make sure the location of 

WS2_32.Lib is specified correctly fo the LIBS variable.

-----------------------------------------------------------------------------

2.) Running

usage: ./udptunnel - [-6] 

  -c    client mode (default)

        : [local host]   

                 

  -s    server mode

        : [host] port [[host]:[port] ...]

  -6    use IPv6

  -h    show this junks and exit

To run the server:

    udptunnel -s [-6] [host] port

where the port is a UDP port to listen for messages from the udpclient and host

is the address to listen on. Use the -6 option to listen on IPv6 addresses.

Examples: 

    udpserver -s 4444

    udpserver -s -6 2001::10:3 4444

To run the client:

    udptunnel -c [-6] [local host]   

             

local host/port - Host and port for the TCP server to listen on. If the host

                  isn't supplied, it will listen on all available addresses.

proxy host/port - Host and port that udpserver is listening on.

remote host/port - Host and port to forward the received TCP data to. The host

                   is relative to the proxy machine (e.g. specifiying 127.0.0.1

                   is the proxy machine itself).

Use the -6 option to listen and connect using IPv6 addresses.

Example for tunneling ssh data through the tunnel between two computers with IP

addresses 192.168.1.2 (client) and 192.168.1.1 (server):

    server# ./udptunnel -s 192.168.1.1 4444

    client# ./udptunnel -c 127.0.0.1 3333 192.168.1.1 4444 127.0.0.1 22

    client# ssh -p 3333 [email protected]

Specified destination list:

After the args in server mode, a list of hosts and ports can be included to

control who the client tries to connect to. Current this doesn't work with IPv6

and no names are translated yet, so the destination host used in the client

must be the same string as that used in the list.

This code has been tested and works on Linux, Solaris 10 x86, and Cygwin (but

requires the IPv6 extension - http://win6.jp/Cygwin/index.html). Please send

any bugs or issues to the contact listed above.