Routing issue

Routing issue

[Florin Vlaicu]

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

Re: Routing issue

[Florin Vlaicu]

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