Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Florin Vlaicu <florin@vlaicu.com>
To: wireguard@lists.zx2c4.com
Subject: Re: Routing issue
Date: Tue, 9 Mar 2021 09:21:13 +0200	[thread overview]
Message-ID: <CAGpywxMdNnkx2yZR5y0-P1Czuy1FAWYn-=4EaRDWbE_Rz=60cg@mail.gmail.com> (raw)
In-Reply-To: <CAOAVeL0mxeXGJXs6idBXyi8ibVvJ2d3qAtEo2Yd2Bby37zQ1RQ@mail.gmail.com>

In the meantime I was able to debug and fix this issue with the help
of the IRC channel.
It turns out the container on the other host had different mac
addresses as soon as I synced them things started working.

Thanks,
Florin

On Tue, Mar 9, 2021 at 8:55 AM Henning Reich <henningreich@gmail.com> wrote:
>
> Have you check time/timezone and wait enough time to clean/rebuild arp caches?
>
> Florin Vlaicu <florin@vlaicu.com> schrieb am So. 7. März 2021 um 18:26:
>>
>> I am running a server in a container that uses a macvlan interface to
>> have a static IP address in my local LAN. Then from my router I DNAT
>> to that IP address.
>> If I stop the container and then start it on another host (with the
>> exact same configuration) existing tunnels will fail, but new ones
>> will work.
>> If I just restart the container (or even reboot the host) the existing
>> tunnels will come back up.
>> Is there something I can change on the clients to not have to restart
>> the tunnel?
>>
>> Thanks,
>> Florin

      parent reply	other threads:[~2021-03-09 21:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-06 19:12 Florin Vlaicu
     [not found] ` <CAOAVeL0mxeXGJXs6idBXyi8ibVvJ2d3qAtEo2Yd2Bby37zQ1RQ@mail.gmail.com>
2021-03-09  7:21   ` Florin Vlaicu [this message]

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='CAGpywxMdNnkx2yZR5y0-P1Czuy1FAWYn-=4EaRDWbE_Rz=60cg@mail.gmail.com' \
    --to=florin@vlaicu.com \
    --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).