Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: wireguard@lists.zx2c4.com
Subject: Roaming between IPv4 and IPv6?
Date: Tue, 06 Mar 2018 22:53:47 +0100	[thread overview]
Message-ID: <871sgwna50.fsf@toke.dk> (raw)

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. Whereas if I go in the other direction (first establish
the tunnel over IPv4), I can seamlessly roam between different
connections.

Is this expected behaviour, or should v4/v6 roaming work?

-Toke

             reply	other threads:[~2018-03-06 21:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-06 21:53 Toke Høiland-Jørgensen [this message]
2018-03-06 21:57 ` Jason A. Donenfeld
2018-03-06 22:08   ` Toke Høiland-Jørgensen
2018-03-06 22:14     ` Jason A. Donenfeld
2018-03-07  0:31       ` Kalin KOZHUHAROV
2018-03-07  8:56         ` Toke Høiland-Jørgensen
2018-03-06 22:59     ` Matthias Urlichs

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871sgwna50.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).