Replies: 2 comments 2 replies
-
Dcutr is a hole-punching protocol. I am not sure it is possible to hole-punch through docker's networking interface? |
Beta Was this translation helpful? Give feedback.
1 reply
-
Agreed with Thomas above, I don't think you can use hole punching to overcome Docker's (/Linux') network namespace security system. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey, did anyone managed to simulate a simple relay/dcutr setup using docker and docker-compose? I tried to make two node-containers and one relay-container, each having it's own network to connect to relay, so nodes couldn't connect directly to each other.
Here's my docker-compose:
And docker files:
relay:
listening_node:
dialing_node:
But if I run it like that I get:
As you can see I get
RemoteInitiatedDirectConnectionUpgrade
, but noDirectConnectionUpgradeSucceeded
log after this.Has anyone have tried to make a setup like this? I think it would help with testing my p2p application with a setup like that.
Here is the more verbose debug output:
A long debug log
Or maybe there is some better solution to make a p2p connection between docker or some containers in a one physical host machine, which avoids using a separate (owned by me) VPS provider?
Thanks :)
Beta Was this translation helpful? Give feedback.
All reactions