From owner-freebsd-net@FreeBSD.ORG Thu Feb 10 21:37:20 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 44112106564A for ; Thu, 10 Feb 2011 21:37:20 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id EF69E8FC15 for ; Thu, 10 Feb 2011 21:37:19 +0000 (UTC) Received: by gyc15 with SMTP id 15so812258gyc.13 for ; Thu, 10 Feb 2011 13:37:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=ZtBa2b8i3qscFlemFi1Nkem5tFcrcllNt/DoyOmUMmc=; b=DiU+lo3n4CSBTSJlwdA55CoQpyjivWAKcA2Yr/O5inFaoRX2NrNWi+qvf3zvyOmyEc PFKcZ8xq3cvrj7S8cAql7LQdMyDXCszsi5g2PusQKoZP/PvooZ69srg6LGuJnoDQtHhv zHnYeNA/6Rstgngvs5nu72r51DvfK2IuaRPr0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=OTyj843jqhORsZUxvr5meChVNwtA7hNplUY5UsJ7ytETc6TpIW3c6dhL2ZZTp0UY8y d7aOqtxRIMVkcG69ITCSqQ0lnmDWv68bM+W8t2NEOznbj1wpAn/8eqib16/p2L4myGrp KcTVGAYuFTlDYvstOVhdJ1vZhthTyKjM4npPc= MIME-Version: 1.0 Received: by 10.236.110.14 with SMTP id t14mr2773266yhg.57.1297373838456; Thu, 10 Feb 2011 13:37:18 -0800 (PST) Received: by 10.147.167.5 with HTTP; Thu, 10 Feb 2011 13:37:18 -0800 (PST) In-Reply-To: References: <19796.13124.805432.342309@oz.mt.att.com> Date: Thu, 10 Feb 2011 13:37:18 -0800 Message-ID: From: Jack Vogel To: Sergey Kandaurov Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org, Jay Borkenhagen Subject: Re: cannot set mtu > 1500 on em0 optical Gig-E X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Feb 2011 21:37:20 -0000 Thanks Sergey :) Jack On Thu, Feb 10, 2011 at 12:28 PM, Sergey Kandaurov wrote= : > On 10 February 2011 21:49, Jay Borkenhagen wrote: > > Hi, > > > > For quite a while now it appears that mtu on my gigabit ethernet fiber > > em0 cards cannot be configured higher than the default 1500 bytes. > > > > Here's what I get when I attempt to set it lower and higher on a brand > > new 8.2-RC3 box: > > > > =3D=3D=3D > > sandbox# uname -v > > FreeBSD 8.2-RC3 #0: Sun Jan 30 06:52:51 UTC 2011 > root@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC > > sandbox# > > > > sandbox# ifconfig em0 > > em0: flags=3D8843 metric 0 mtu = 1500 > > options=3D18 > > ether 00:d0:b7:7c:f8:01 > > inet 10.1.2.3 netmask 0xffffff00 broadcast 10.1.2.255 > > media: Ethernet autoselect > > status: no carrier > > sandbox# ifconfig em0 mtu 1499 > > sandbox# ifconfig em0 | grep mtu > > em0: flags=3D8843 metric 0 mtu = 1499 > > sandbox# ifconfig em0 mtu 1501 > > ifconfig: ioctl (set mtu): Invalid argument > > sandbox# ifconfig em0 | grep mtu > > em0: flags=3D8843 metric 0 mtu = 1499 > > sandbox# ifconfig em0 mtu 1500 > > sandbox# ifconfig em0 | grep mtu > > em0: flags=3D8843 metric 0 mtu = 1500 > > sandbox# > > > > sandbox# pciconf -lv | sed -n '/em0@/,/em1/p' > > em0@pci0:0:2:0: class=3D0x020000 card=3D0x10008086 chip=3D0x10008086 r= ev=3D0x03 > hdr=3D0x00 > > vendor =3D 'Intel Corporation' > > device =3D '82542 Gigabit Ethernet Controller' > > class =3D network > > subclass =3D ethernet > > em1@pci0:0:4:0: class=3D0x020000 card=3D0x10008086 chip=3D0x10008086 r= ev=3D0x03 > hdr=3D0x00 > > sandbox# > > > > =3D=3D=3D > > > > However, back in the 6.2 days it allowed it: > > > > =3D=3D=3D > > > > [jayb@cactus ~]$ uname -v > > FreeBSD 6.2-PRERELEASE #0: Tue Dec 26 16:53:18 EST 2006 > root@cactus.iplabs.att.com:/usr/obj/usr/src/sys/CACTUS > > [jayb@cactus ~]$ > > > > [jayb@cactus ~]$ ifconfig em0 > > em0: flags=3D8843 mtu 1500 > > options=3D8 > > inet 10.0.1.152 netmask 0xfffffffc broadcast 10.0.1.155 > > ether 00:90:27:e3:0a:67 > > media: Ethernet autoselect > > status: no carrier > > [jayb@cactus ~]$ > > > > [jayb@cactus ~]$ sudo ifconfig em0 mtu 9000 > > [jayb@cactus ~]$ ifconfig em0 | grep mtu > > em0: flags=3D8843 mtu 9000 > > [jayb@cactus ~]$ > > > > [jayb@cactus ~]$ pciconf -lv | sed -n '/em0@/,/none0@/p' > > em0@pci0:2:0: class=3D0x020000 card=3D0x10008086 chip=3D0x10008086 r= ev=3D0x02 > hdr=3D0x00 > > vendor =3D 'Intel Corporation' > > device =3D '82542 Gigabit Ethernet Controller' > > class =3D network > > subclass =3D ethernet > > none0@pci0:4:0: class=3D0x088000 card=3D0x0767101e chip=3D0x9063101e re= v=3D0x04 > hdr=3D0x00 > > [jayb@cactus ~]$ > > > > Hmm.. Did jumbo frames really work on these cards for you? Intel claims: > "Adapters based on the Intel=AE 82542 and 82573V/E controller do not > support Jumbo Frames. These correspond to the following product names: > > * Intel=AE PRO/1000 Gigabit Server Adapter > * Intel=AE PRO/1000 PM Network Connection " > > As seen from code, the behavior was changed to match the description ("ke= ep > old 82542 from using jumbo frames") and merged to 6-STABLE before 6.3. > > -- > wbr, > pluknet > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >