hole-punching

I'm working on a project that will require ea p2p server, but I haven't found any java-client php-server example code. I understand the concept of how udp hole punching works but I can't get anything to work in code. What I've tried: TheSocket.java public class TheSocket { public static String response = "hello"; public static String request; public static String webServerAddress; public static ServerSocket s; protected static ServerSocket getServerSocket(int port)throws Exception{ return new ServerSocket(port); } public static void handleRequest(Socket s){ BufferedReader is; PrintWriter os;

I wrote a program that sets-up peer-to-peer links. The programm, which can be found at http://basyl.co.uk/code/punch/doc/files/Readme-txt.html , is in two parts: a server that runs on a public host; and a client that is used by each end of the desired peer-to-peer link. I have access to two public servers: 'bonn' (home.contextshift.co.uk) and 'entropy' (home2.contextshift.co.uk) If the server is on bonn and clients are run on bonn, entropy and my home PC (behind NAT), a punched connection from entropy can talk to my PC without problem. However, a connection from bonn to the PC fails; data from

Can anyone give an example of a UDP Hole Punching ? Actually, I want to write a chat program with which people can chat when they know each other's IP. But both the machines will be behind a firewalled router. So, I need to punch a hole in order to communicate. I would like a function such that on calling the function, a hole would have been punched and future communications would move on easily - if that's not too much to ask for :) Short Answer: it can't be done reliably. Long Answer: "Hole Punching" refers to triggering automatic NAT rules of a router in order to allow inbound traffic. When

I'm trying to implement TCP hole punching with windows socket using mingw toolchain. I think the process is right but the hole doesn't seems to take. I used this as reference. A and B connect to the server S S sends to A , B 's router IP + the port it used to connect to S S does the same for B A start 2 threads: One thread tries connecting to B 's router with the info sent by S The other thread is waiting for an incoming connection on the same port used to connect to its router when it connected to S B does the same I have no issue in the code I think since: A and B does get each other ip and

I am trying to accomplish UDP hole punching. I am basing my theory on this article and this WIKI page , but I am facing some issues with the C# coding of it. Here is my problem: Using the code that was posted here I am now able to connect to a remote machine and listen on the same port for incoming connections (Bind 2 UDP clients to the same port). For some reason the two bindings to the same port block each other from receiving any data. I have a UDP server that responds to my connection so if I connect to it first before binding any other client to the port I get its responses back. If I