Date: Wed, 29 Apr 2009 17:59:58 +0400 From: pluknet <pluknet@gmail.com> To: Nikolay Denev <ndenev@gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: bce(4) sees all incoming frames as 2026 bytes in length Message-ID: <a31046fc0904290659h3c831abcy14318b73c1462068@mail.gmail.com> In-Reply-To: <5E915E92-2B82-4331-9493-739568CC6E8C@gmail.com> References: <5E915E92-2B82-4331-9493-739568CC6E8C@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2009/4/29 Nikolay Denev <ndenev@gmail.com>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hello, > > I have the following problem with the new bce(4) driver on a 7.2-PRERELEASE > from a few days ago. > When I run tcpdump on the bce interface on the machine, all incoming frames > are shown as 2026 in size, > but on the sending machine tcpdump reports that it's sending frames of the > correct size. > This looks very strange because I don't have enabled Jumbo Frames on this > bce interface , and it is still with it's default MTU of 1500 bytes. > When I tried to capture the packets, they are zero padded to the 2026 frame > size. The checksums are correct, so I suspect a driver bug? > > P.S.: I experience this problem on several machines with bce interfaces, and > on all of them tcpdump sees all incoming frames with length of 2026 bytes. hi. Please, give us more details. What is your network card model ? Share ifconfig, dmesg... I have a similar setup, except the frame size - mine are with expected values. -- wbr, pluknet
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a31046fc0904290659h3c831abcy14318b73c1462068>