Date: Fri, 27 May 2016 06:00:58 +0000 (UTC) From: Dustin Marquess <dmarquess@gmail.com> To: Garrett Wollman <wollman@hergotha.csail.mit.edu> Cc: <freebsd-net@freebsd.org> Subject: Re: Changing MTU on cxgbe Message-ID: <CCED15396D3461DF.B0AC7F2F-4141-4B32-B961-F77B1C62F2EE@mail.outlook.com> In-Reply-To: <201605270457.u4R4vYqu018911@hergotha.csail.mit.edu> References: <CAJpsHY4vF5Ky6GuAusLOOROgiQuyD2CcRmVxu8x3cArQRZxcbg@mail.gmail.com> <201605270457.u4R4vYqu018911@hergotha.csail.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
I tried setting it via ifconfig_cxgbe0 in rc.conf, but that didn't seem to work either. -Dustin On Thu, May 26, 2016 at 9:57 PM -0700, "Garrett Wollman" <wollman@hergotha.csail.mit.edu> wrote: In article you write: ># ifconfig -m cxgbe0 >cxgbe0: flags=8943 ># ifconfig cxgbe0 mtu 9000 >ifconfig: ioctl SIOCSIFMTU (set mtu): Invalid argument I believe this device, like many others, does not allow the MTU (or actually the MRU) to be changed once the receive ring has been set up You may be able to do it if you down the interface first, or you may have to do it at boot time before anything else (and in particular before the interface is marked "up" for the first time). -GAWollman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CCED15396D3461DF.B0AC7F2F-4141-4B32-B961-F77B1C62F2EE>