From: Leon Schuermann
This patch series is an attempt to integrate a per-peer MTU setting
into WireGuard. With matching changes to the wireguard-tools,
individual MTU values can be set and retrieved for each registered
peer.
While Linux supports setting an MTU metric for specific FIB route
From: Leon Schuermann
Add an optional function `ndo_lookup_mtu` to the `struct
net_device_ops`. This function can be used to allow other parts of the
network stack to let the destination netdevice determine the allowed
packet MTU. This is done on a per-packet basis, providing the `struct
sk_buff
From: Leon Schuermann
This integrates the newly introduced dynamic MTU lookup mechanism with
the IPv6 stack. It will attempt to query the destination netdevice for
the individual packet MTU and, if not found or the mechanism is not
implemented, fall back to the device MTU.
`ndo_lookup_mtu
From: Leon Schuermann
WireGuard is, as of now, unable to detect an insufficient link MTU and
adjust the MTU of transmitted frames accordingly, as ICMP messages
which would indicate this are unauthenticated. This poses a problem in
an environment where multiple peers connect to a shared endpoint
From: Leon Schuermann
This integrates the newly introduced dynamic MTU lookup mechanism with
the IPv4 stack. It will attempt to query the destination netdevice for
the individual packet MTU and, if not found or the mechanism is not
implemented, fall back to the device MTU.
`ndo_lookup_mtu
ood:
mininet> h4 ip link set h4-eth1 mtu 1400
mininet> h5 ip link set h5-eth0 mtu 1400
mininet> h1 ping -c1 -Mdo -s1384 -W1 h5
PING 192.168.1.2 (192.168.1.2) 1384(1412) bytes of data.
From 192.168.0.2 icmp_seq=1 Frag needed and DF set (mtu = 1400)
#+END_EXAMPLE
Let me
excellent Ethernet/PCIe
FPGA NIC, as a starting point for our development.
Regards,
Leon Woestenberg
l...@sidebranch.com
(their_counter) before the received Type 4 packet was
authenticated?
Regards,
Leon.
