Thomas Eizinger
Thomas Eizinger
> > Good to close those and move remaining tasks to new issues? > > Yes. I'll do some house-keeping here today. Done.
I think the following idea is relevant here: https://github.com/firezone/firezone/issues/3343#issuecomment-1916027208.
> This would be a one-off callback from connlib -> JVM I think we should not do one-off callbacks. In fact, I think the only "callback" we should do is...
Ah I see! Once `snownet` is integrated, we only have two UDP file-descriptors, one for IP4 and one for IP6 but yes, we could make them part of the state...
Here are the integration tests for `firezone-connection`: https://github.com/firezone/firezone/tree/main/rust/connection-tests The main difference to the main `docker-compose.yml` is that this one is setting up a network topology where both clients are behind...
I am hoping that we can more easily test this once the tunnel is sans-io as it should be possible to run a client and a gateway tunnel next to...
Probably worth adding `shellcheck` right away too!
Irrelevant after #4994.
> With the changes above, connlib now manages tunnel state. When it receives a "command" (connect/disconnect/update) it reacts accordingly and then passes the `state` object back to the app. The...
I thought some more about this and what impact it may have. I realized that using this pattern, we can also solve a lot of awkwardness around device initialization on...