Page MenuHomeFreeBSD

Allow an MTU of up to 65535 bytes on tun interfaces
ClosedPublic

Authored by tuexen on May 19 2016, 2:09 PM.
Tags
None
Referenced Files
Unknown Object (File)
Dec 22 2023, 11:07 PM
Unknown Object (File)
Aug 23 2023, 9:09 PM
Unknown Object (File)
Jul 16 2023, 6:53 AM
Unknown Object (File)
Jul 2 2023, 11:14 PM
Unknown Object (File)
Jun 27 2023, 9:07 AM
Unknown Object (File)
Apr 6 2017, 10:10 PM
Unknown Object (File)
Mar 7 2017, 4:01 AM
Unknown Object (File)
Dec 14 2016, 5:20 PM
Subscribers

Details

Reviewers
rrs
Group Reviewers
network
transport
Summary

Currently tun interfaces can only receive packets up to 16384. To bump this to 65535, the struct tuninfo also needs to be changed. The mtu component is of type short and needs to be changed to unsigned short to allow for values up to 65535.

Using MTUs for up to 65535 bytes is useful for testing transport stacks with packetdrill for interfaces with large MTUs.

Test Plan

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

tuexen retitled this revision from to Allow an MTU of up to 65535 bytes on tun interfaces.
tuexen updated this object.
tuexen edited the test plan for this revision. (Show Details)
tuexen added reviewers: transport, network.
tuexen set the repository for this revision to rS FreeBSD src repository - subversion.

Seems usr.sbin/ppp is the only in-tree consumer and they assign from an unsigned long;
You might want to go and check openvpn and possibly mpd; not sure what other ports; hercules or qemu maybe?
Worst ask portmgr to do an exp run via bugs.

I'll look at some of the ports. I don't think the change will be a problem, but I'll double check.

I checked the ports, couldn't find any issues. Thanks for the suggestion. Will commit the patch.

rrs added a reviewer: rrs.
This revision is now accepted and ready to land.Jul 5 2016, 1:24 PM