Date: Fri, 13 Mar 2009 23:17:47 +0000 From: Bruce Simpson <bms@incunabulum.net> To: "Sean C. Farley" <scf@FreeBSD.org> Cc: freebsd-net@FreeBSD.org, Rui Paulo <rpaulo@FreeBSD.org> Subject: Re: tap(4) SIOCSIFMTU patch Message-ID: <49BAE99B.2030508@incunabulum.net> In-Reply-To: <alpine.BSF.2.00.0903130918400.4522@thor.farley.org> References: <alpine.BSF.2.00.0903122048230.1704@thor.farley.org> <188BDECC-1064-4421-8687-F9759E25FD1F@freebsd.org> <alpine.BSF.2.00.0903130918400.4522@thor.farley.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Sean C. Farley wrote: > > Yes, this fixes my issue with bridging a tap device to an interface > with an MTU higher than 1500. > I will probably commit this patch this weekend. I can't think of any reason why not, other than you might want to ensure that tap's MTU is bounded within reasonable limits, 'cause yoi don't want to exhaust the jumbo cluster pool if say mtu is more than 9000. I think ifconfig already performs such a check but you might want to double check. cheers BMS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49BAE99B.2030508>