Kalin KOZHUHAROV writes:
> On Tue, Mar 6, 2018 at 11:14 PM, Jason A. Donenfeld wrote:
>> On Tue, Mar 6, 2018 at 11:08 PM, Toke Høiland-Jørgensen wrote:
>>> I think the idea of configuring both v4 and v6 on startup and caching
>>> them is a
On Tue, Mar 6, 2018 at 11:14 PM, Jason A. Donenfeld wrote:
> On Tue, Mar 6, 2018 at 11:08 PM, Toke Høiland-Jørgensen wrote:
>> I think the idea of configuring both v4 and v6 on startup and caching
>> them is a reasonable idea. Maybe even configure all available
"Jason A. Donenfeld" writes:
> Hey Toke,
>
> For incoming packets, this would be strange behavior, since it's
> listening on v4 and v6.
Yeah, I think the incoming side is fine (it works over both v4 and v6 as
long as I have connectivity on the other end).
> For outgoing
Hey Toke,
For incoming packets, this would be strange behavior, since it's
listening on v4 and v6. For outgoing packets, if wireguard thinks it
should be sending to a v6 address, then that's what it will do. One
way to fix this would be to re-resolve DNS from userspace, which is a
bit ugly.
Hi
Is wireguard supposed to be able to handle roaming between IPv4 and
IPv6? If I setup a tunnel to a dual-stack machine and establish the
tunnel using IPv6, then switch to a different interface (from WiFi to
cellular in this case) that doesn't have IPv6, the tunnel stops having
connectivity