Date: Sat, 17 Dec 2011 13:46:47 +0100 From: Andrea Venturoli <ml@netfence.it> To: pyunyh@gmail.com Cc: freebsd-net@freebsd.org Subject: Re: Intel 82550 Pro/100 Ethernet and TSO troubles Message-ID: <4EEC8F37.5030209@netfence.it> In-Reply-To: <20111215221337.GA15187@michelle.cdnetworks.com> References: <4EE8FA10.8090502@netfence.it> <20111214195918.GC11426@michelle.cdnetworks.com> <4EE91275.3060808@netfence.it> <20111214213242.GD11426@michelle.cdnetworks.com> <4EEA0153.5010305@netfence.it> <20111215221337.GA15187@michelle.cdnetworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/15/11 23:13, YongHyeon PYUN wrote: >> I tried "netstat -ind", but it shows no Ierrs/Idrop/Oerrs/Odrop. >> > > Use -s option which will show statistics for each network > protocols. Search 'discarded for bad checksums' from the output. Still all bad counters at zero. >> You'll see tso.dump and notso.dump: they are both from the same client >> downloading the same (random) file (the file name was changed only to >> prevent possible caching). >> See notso.dump is perfect, while tso.dump shows a lot of potential problems. >> > > Thanks. Thanks go to you! :-) > Thanks for testing. Based on dump file, I tried various MTU > configuration and I was not able to reproduce it. By chance, are > you using firewall(pf/ipfw/ipf) or bridge(4)? If I remember > correctly some firewall rules are not compatible with TSO. > For bridge, if one member of bridge does not support TSO, TSO > should be disabled. Very interesting: I'm not using bridge on this host, but I'm using ipfw! Which rules are incompatible? Any pointer on this? I'm also using CARP, in case it could matter, but not on this interface. bye & Thanks av.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EEC8F37.5030209>