Date: Wed, 29 Apr 2009 15:58:57 +0300 From: Nikolay Denev <ndenev@gmail.com> To: freebsd-net@freebsd.org Subject: bce(4) sees all incoming frames as 2026 bytes in length Message-ID: <5E915E92-2B82-4331-9493-739568CC6E8C@gmail.com>
next in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I have the following problem with the new bce(4) driver on a 7.2-=20 PRERELEASE from a few days ago. When I run tcpdump on the bce interface on the machine, all incoming =20 frames are shown as 2026 in size, but on the sending machine tcpdump reports that it's sending frames of =20= the correct size. This looks very strange because I don't have enabled Jumbo Frames on =20 this bce interface , and it is still with it's default MTU of 1500 =20 bytes. When I tried to capture the packets, they are zero padded to the 2026 =20= frame size. The checksums are correct, so I suspect a driver bug? P.S.: I experience this problem on several machines with bce =20 interfaces, and on all of them tcpdump sees all incoming frames with =20 length of 2026 bytes. Regards, Niki Denev -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (Darwin) iEYEARECAAYFAkn4TxIACgkQHNAJ/fLbfrmBKgCgkJ6j//+lLrrb+dL3HcLmDxym 4mQAn1qaY41CxWHiVthhCs6lYblX6UMd =3D+9XA -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5E915E92-2B82-4331-9493-739568CC6E8C>