We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
I am doing my master thesis on NAT traversal and wanted to try your tool pwnat.
I wanted to test two linphone clients. On one of the clients the server side is running (192.168.0.121): sudo ./pwnat -s -v 3333 &
sudo ./pwnat -s -v 3333 &
The other one has the client side running (192.168.188.70): sudo ./pwnat -v -c 5060 192.168.0.121 3333 192.168.0.121 5060 &
sudo ./pwnat -v -c 5060 192.168.0.121 3333 192.168.0.121 5060 &
It is not working so far. The client displays, that it is listening to a tcp connection, while the server side is listening to a udp connection.
Is there something wrong with my program calls?
EDIT: The first address of the client command has to match the WAN IP of the server: sudo ./pwnat -v -c 5060 192.168.188.2 3333 192.168.0.121 5060 &
sudo ./pwnat -v -c 5060 192.168.188.2 3333 192.168.0.121 5060 &
BR, Chris
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi,
I am doing my master thesis on NAT traversal and wanted to try your tool pwnat.
I wanted to test two linphone clients.
On one of the clients the server side is running (192.168.0.121):
sudo ./pwnat -s -v 3333 &
The other one has the client side running (192.168.188.70):
sudo ./pwnat -v -c 5060 192.168.0.121 3333 192.168.0.121 5060 &
It is not working so far. The client displays, that it is listening to a tcp connection,
while the server side is listening to a udp connection.
Is there something wrong with my program calls?
EDIT: The first address of the client command has to match the WAN IP of the server:
sudo ./pwnat -v -c 5060 192.168.188.2 3333 192.168.0.121 5060 &
BR,
Chris
The text was updated successfully, but these errors were encountered: