diff options
| author | David Gibson <david@gibson.dropbear.id.au> | 2025-02-12 18:07:14 +1100 |
|---|---|---|
| committer | Stefano Brivio <sbrivio@redhat.com> | 2025-02-12 19:47:17 +0100 |
| commit | 155cd0c41e549cea956b7f8506cda7803cf63419 (patch) | |
| tree | 0fdc02fcd3f65bbfd889e744f31d34a165a4b4bd /util.c | |
| parent | 5911e08c0f53e46547e7eeb1dd824c8ab96e512e (diff) | |
| download | passt-155cd0c41e549cea956b7f8506cda7803cf63419.tar passt-155cd0c41e549cea956b7f8506cda7803cf63419.tar.gz passt-155cd0c41e549cea956b7f8506cda7803cf63419.tar.bz2 passt-155cd0c41e549cea956b7f8506cda7803cf63419.tar.lz passt-155cd0c41e549cea956b7f8506cda7803cf63419.tar.xz passt-155cd0c41e549cea956b7f8506cda7803cf63419.tar.zst passt-155cd0c41e549cea956b7f8506cda7803cf63419.zip | |
migrate: Migrate guest observed addresses
Most of the information in struct ctx doesn't need to be migrated.
Either it's strictly back end information which is allowed to differ
between the two ends, or it must already be configured identically on
the two ends.
There are a few exceptions though. In particular passt learns several
addresses of the guest by observing what it sends out. If we lose
this information across migration we might get away with it, but if
there are active flows we might misdirect some packets before
re-learning the guest address.
Avoid this by migrating the guest's observed addresses.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
[sbrivio: Coding style stuff, comments, etc.]
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Diffstat (limited to 'util.c')
0 files changed, 0 insertions, 0 deletions