Thomas Eizinger

> What are we using for the source of truth for the latest gateway version? https://github.com/firezone/firezone/blob/947db254cc968ca0f4112d0aa54f78b3131700c6/scripts/Makefile#L23 You can put a ``` # mark:current-gateway-version ``` Wherever you need it in the...

I failed to reproduce the issue on my Windows VM. The only difference we know about is that @conectado appears to be behind a symmetric NAT. I also couldn't reproduce...

Weirdly enough, we do still receive binding requests via our data channel from the gateway so I don't think it is a NAT issue. Maybe the gateway and client's ICE...

> Weirdly enough, we do still receive binding requests via our data channel from the gateway so I don't think it is a NAT issue. This however doesn't explain why...

I went through the gateway logs in detail and what happens is: - We find multiple viable paths to the client (several relay combinations + a direct one) - All...

As indicated on https://wiki.qemu.org/Documentation/Networking, QEMU uses an internal DNS server. I checked on my setup and sending a DNS query from inside the VM triggers a DNS query to my...

The bit that I don't understand is why a NAT would do this. There is no reason why traffic originating from the same IP + port going to different IPs...

> I just tested, by sending packets, to a destination with a random port, and just by sending I don't see this behavior reproduced Can you test the following: -...

> > > I just tested, by sending packets, to a destination with a random port, and just by sending I don't see this behavior reproduced > > > >...

> > > > > I just tested, by sending packets, to a destination with a random port, and just by sending I don't see this behavior reproduced > >...