Jake McGinty

Hey @jedahan! Yeah, we don't currently have any concept of an "exit node," to steal a term from Tor. You could, however, have a peer run a separate WireGuard interface...

@canselcik feel free to open a separate issue for your connection problems. I'm certain there are improvements we can make to diagnosing connection issues and improving NAT traversal.

@rohithmeethal innernet isn't meant to forward internet traffic - everything about it is hard-coded to assume that one peer has one IP, and peers do not forward each other's packets....

This is definitely something that is worth adding, totally agree. I think the general strategy as of now is to fix some more basic NAT traversal issues (tracking in #109),...

Yeah, right now there's no way to do this. The larger feature you're looking for is "site-to-site" but there hasn't been development time yet to introduce it. I think at...

It seems like you've made good headway with working out the API via the code - I'd delayed making any more official looking API docs since the requests were still...

It's only there to prevent naïve CSRF attacks (i.e. a random website you load that has JS that sends a `POST http://10.42.0.1:51820/admin/peer`). There are ideas for a more complete solution...

> BTW, for API use it's hard to extract server public key if you have no peer configured. May be innernet-server should report server public key (`innernet-server server-pubkey mynetwork`)? `wg...

Hey @bramvdbogaerde, very sorry for the late reply! I would *love* to help you work on GUIs for innernet, including refactoring the client code to provide an easy API for...

Interestingly, I added a quick section in the docker tests that spins up two peers redeeming invitations at about the same time, and it didn't error out. Will have to...