-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
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
Feature request for [HOLEPUNCH] #260
Comments
Hi,
Sure, I've added those messages in that exact format.
Unfortunately the code is structured in such a way that this would probably require big changes and I can't think of a nice way to do this right now. I'll leave this open for the time being and maybe I'll figure something out later. |
Highly appreciated.
No worries. Thanks for considering. |
Holepunch has been fantastic and working well. Feature request; the ability to specify an ETH interface or interface IP that will be used for the punching. In our case we have everything on a VPN 10.102.102.0/24 but like using holepunch to route video traffic over the WAN and not riding on top of our VPN for a number of reasons... but we do like to keep the VPN online for other communication. In the example below it looks like (and verified) that holepunch is using the VPN interface 10.102.102.0/24 interfaces on the machines to route traffic as apposed to the WAN. Ironically the VPN interface is 10.102.102.0/24 on both machines with no gateway. Thoughts?
|
I've just added the option |
Fantastic, will give it a go when a new nightly armhf appimage is released. Appreciate you |
Hi
Marvelous job you did with the new [HOLEPUNCH] feature. I have built it into the telemersive-route, and it works very well.
But I have two features that would make it even better:
To be specific:
Currently the logoutput when starting up ultragrid with holepunch looks like this:
but doesn't give any indication it waits for another peer. Desireable would be something like:
[HOLEPUNCH] Connection: Waiting for remote client...
and once the connection is established:
[HOLEPUNCH] Connection: Established
it would be nice if PeerA falls back into waiting for a new Peer if the client PeerB stops:
At the moment PeerA does nothing and needs to be restarted.
The text was updated successfully, but these errors were encountered: