[afics]

This looks great!

Is a TCP mode planned? This would be useful for networks where outbound UDP isn't allowed. (hotel wifi, other public wifis)

Do you plan to add automatic key rollover/expiry?

[clpwn]

Thanks!

There aren't any current plans to bake in TCP support, but you can rig it up yourself using something like udptunnel.

Related old HN comment with basic instructions: https://news.ycombinator.com/item?id=17847008

Also see: the "TCP Mode" section in https://www.wireguard.com/known-limitations/.

[afics]

I know about those. Since the whole point of innernet is making wireguard configuration simpler, I figured maybe integrating something like that is worth doing.

[clpwn]

Ah, gotcha - sorry I misunderstood your question.

I feel that adding TCP support would push innernet beyond a WireGuard configuration manager and into something a bit more behemoth. I'm quite fond of the fact that innernet doesn't "touch the packets" in its current state.

That said, if a strong need arises over time it's not out of the question, and in the mean time anybody is welcome to add their own wrapper around innernet or fork it to support that.

[pdimitar]

Do you feel Innernet could one day work through QUIC? It's kind of neither TCP nor UDP (although definitely much more UDP).

[afics]

Aye, noted. Do you support the case where nodes can not talk directly to each other and relaying is required?

[clpwn]

Not currently, but I'm interested in supporting that.