diff options
| author | David Gibson <david@gibson.dropbear.id.au> | 2024-02-28 22:25:18 +1100 |
|---|---|---|
| committer | Stefano Brivio <sbrivio@redhat.com> | 2024-02-29 09:48:21 +0100 |
| commit | f15be719b370ab694b933ab7ceb7fc3481687284 (patch) | |
| tree | 724183bd198c19be95bd2957936768ef318b901c /Makefile | |
| parent | 3b59b9748aa13a244c173585dfbaf79dfff9ea8f (diff) | |
| download | passt-f15be719b370ab694b933ab7ceb7fc3481687284.tar passt-f15be719b370ab694b933ab7ceb7fc3481687284.tar.gz passt-f15be719b370ab694b933ab7ceb7fc3481687284.tar.bz2 passt-f15be719b370ab694b933ab7ceb7fc3481687284.tar.lz passt-f15be719b370ab694b933ab7ceb7fc3481687284.tar.xz passt-f15be719b370ab694b933ab7ceb7fc3481687284.tar.zst passt-f15be719b370ab694b933ab7ceb7fc3481687284.zip | |
tap: Disallow loopback addresses on tap interface
The "tap" interface, whether it's actually a tuntap device or a qemu
socket, presents a virtual external link between different network hosts.
Hence, loopback addresses make no sense there. However, nothing prevents
the guest from putting bogus packets with loopback addresses onto the
interface and it's not entirely clear what effect that will have on passt.
Explicitly test for such packets and drop them.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions