Avoid gretap fragmentation with nftables on bridge
Status from this message: Applied, thanks.
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | nftables: add frag-needed (ipv4) to reject optionsdoc/ src/ | +3 | 0 replies | |
| 2/3 | nftables: enable reject with 802.1qsrc/ | +1 | 0 replies | |
| 3/3 | netfilter: enable reject with bridge vlannet/ | +6 | 1 reply |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] Avoid gretap fragmentation with nftables on bridge
Hi,
I have a bridge with connects an gretap tunnel with some ethernet lan. On the gretap device I use ignore-df to avoid packets being lost without icmp reject to the sender of the bridged packet.
Still I want to avoid packet fragmentation with the gretap packets. So I though about adding an nftables rule like this:
nft insert rule bridge filter FORWARD \
ip protocol tcp \
ip length > 1400 \
ip frag-off & 0x4000 != 0 \
reject with icmp type frag-needed
This would reject all tcp packets with ip dont-fragment bit set that are bigger than some threshold (here 1400 bytes). The sender would then receive ICMP unreachable - fragmentation needed and reduce its packet size (as defined with PMTU).
This patch series
1. adds frag-needed ipv4 flag to nftables
2. enables to use this with bridge vlans.
For IPv6, this would need ICMPV6_PKT_TOOBIG instead of ICMPV6_DEST_UNREACH in nft_reject_br_send_v6_unreach, so this is not part of this series.
Regards,
M. Braun
Signature · 1 line
2.20.1