diff options
| author | David Gibson <david@gibson.dropbear.id.au> | 2023-07-05 14:35:16 +1000 |
|---|---|---|
| committer | Stefano Brivio <sbrivio@redhat.com> | 2023-07-07 19:07:12 +0200 |
| commit | e01759e2fab0f66fa5876794425d3ec8489562a9 (patch) | |
| tree | 84ebebed56de3f9d1cd844b31f88f38d4a8797c3 /makedocs.pl | |
| parent | 4c98d3be800de94776b1ebdb7834be805af41d2d (diff) | |
| download | passt-e01759e2fab0f66fa5876794425d3ec8489562a9.tar passt-e01759e2fab0f66fa5876794425d3ec8489562a9.tar.gz passt-e01759e2fab0f66fa5876794425d3ec8489562a9.tar.bz2 passt-e01759e2fab0f66fa5876794425d3ec8489562a9.tar.lz passt-e01759e2fab0f66fa5876794425d3ec8489562a9.tar.xz passt-e01759e2fab0f66fa5876794425d3ec8489562a9.tar.zst passt-e01759e2fab0f66fa5876794425d3ec8489562a9.zip | |
tap: Explicitly drop IPv4 fragments, and give a warning
We don't handle defragmentation of IP packets coming from the tap side,
and we're unlikely to any time soon (with our large MTU, it's not useful
for practical use cases). Currently, however, we simply ignore the
fragmentation flags and treat fragments as though they were whole IP
packets. This isn't ideal and can lead to rather cryptic behaviour if we
do receive IP fragments.
Change the code to explicitly drop fragmented packets, and print a rate
limited warning if we do encounter them.
Link: https://bugs.passt.top/show_bug.cgi?id=62
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Diffstat (limited to 'makedocs.pl')
0 files changed, 0 insertions, 0 deletions