diff options
author | David Gibson <david@gibson.dropbear.id.au> | 2024-08-21 14:20:15 +1000 |
---|---|---|
committer | Stefano Brivio <sbrivio@redhat.com> | 2024-08-21 12:00:31 +0200 |
commit | 935bd81936cf118eed7ddf78a6e87e975ef0a558 (patch) | |
tree | b3bb5974291aa05c159279846f9975414487a923 /test/run | |
parent | 90e83d50a9bdeb0697843fc9917c3070b69d5c7d (diff) | |
download | passt-935bd81936cf118eed7ddf78a6e87e975ef0a558.tar passt-935bd81936cf118eed7ddf78a6e87e975ef0a558.tar.gz passt-935bd81936cf118eed7ddf78a6e87e975ef0a558.tar.bz2 passt-935bd81936cf118eed7ddf78a6e87e975ef0a558.tar.lz passt-935bd81936cf118eed7ddf78a6e87e975ef0a558.tar.xz passt-935bd81936cf118eed7ddf78a6e87e975ef0a558.tar.zst passt-935bd81936cf118eed7ddf78a6e87e975ef0a558.zip |
conf, fwd: Split notion of gateway/router from guest-visible host address
The @gw fields in the ip4_ctx and ip6_ctx give the (host's) default
gateway. We use this for two quite distinct things: advertising the
gateway that the guest should use (via DHCP, NDP and/or --config-net)
and for a limited form of NAT. So that the guest can access services
on the host, we map the gateway address within the guest to the
loopback address on the host.
Using the gateway address for this isn't necessarily the best choice
for this purpose, certainly not for all circumstances. So, start off
by splitting the notion of these into two different values: @guest_gw
which is the gateway address the guest should use and @nat_host_loopback,
which is the guest visible address to remap to the host's loopback.
Usually nat_host_loopback will have the same value as guest_gw. However
when --no-map-gw is specified we leave them unspecified instead. This
means when we use nat_host_loopback, we don't need to separately check
c->no_map_gw to see if it's relevant.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Diffstat (limited to 'test/run')
0 files changed, 0 insertions, 0 deletions