On 12/16/11, Eugene Grosbein wrote:
(Sorry Eugene, I didn't get your message until I searched the web).
Do you use NAT? man ipfw clearly states:
ipfw nat is not compatible with
the TCP segmentation offloading (TSO). Thus, to reliably nat
your net-
work traffic, please
On Sun, Dec 18, 2011 at 08:10:20PM +0100, Andrea Venturoli wrote:
On 12/16/11, Eugene Grosbein wrote:
(Sorry Eugene, I didn't get your message until I searched the web).
Do you use NAT? man ipfw clearly states:
ipfw nat is not compatible with
the TCP segmentation offloading
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
15.12.2011 02:33, Andrea Venturoli пишет:
Hello.
I recently installed 8.2 with the following card:
dmesg
...
fxp0: Intel 82550 Pro/100 Ethernet port 0xdc00-0xdc3f mem
0xfebfb000-0xfebfbfff,0xfebc-0xfebd irq 20 at device 5.0 on pci4
...
pciconv -lv
...
On 12/14/11 22:32, YongHyeon PYUN wrote:
Wireshark showed some wrong checksums (I believe on the ICMP packet, but
I might remember wrong).
You can check whether you received bad checksummed frames with
netstat(1).
I tried netstat -ind, but it shows no Ierrs/Idrop/Oerrs/Odrop.
Is
On Thu, Dec 15, 2011 at 03:16:51PM +0100, Andrea Venturoli wrote:
On 12/14/11 22:32, YongHyeon PYUN wrote:
Wireshark showed some wrong checksums (I believe on the ICMP packet, but
I might remember wrong).
You can check whether you received bad checksummed frames with
netstat(1).
I
Hello.
I recently installed 8.2 with the following card:
dmesg
...
fxp0: Intel 82550 Pro/100 Ethernet port 0xdc00-0xdc3f mem
0xfebfb000-0xfebfbfff,0xfebc-0xfebd irq 20 at device 5.0 on pci4
...
pciconv -lv
...
fxp0@pci0:4:5:0:class=0x02 card=0x00408086
On Wed, Dec 14, 2011 at 08:33:36PM +0100, Andrea Venturoli wrote:
Hello.
I recently installed 8.2 with the following card:
dmesg
...
fxp0: Intel 82550 Pro/100 Ethernet port 0xdc00-0xdc3f mem
0xfebfb000-0xfebfbfff,0xfebc-0xfebd irq 20 at device 5.0 on pci4
...
pciconv -lv
On 12/14/11 20:59, YongHyeon PYUN wrote:
AFAIK the firmware of controller has no known TSO issue so it
indicates a bug in driver.
What makes me wonder is ICMP ECHO packet should not be affected by
TSO and I have no clue at this moment.
I wasn't talking about ICMP ECHO.
What happened was:
a)
On Wed, Dec 14, 2011 at 10:17:41PM +0100, Andrea Venturoli wrote:
On 12/14/11 20:59, YongHyeon PYUN wrote:
AFAIK the firmware of controller has no known TSO issue so it
indicates a bug in driver.
What makes me wonder is ICMP ECHO packet should not be affected by
TSO and I have no clue at
On Wed, Dec 14, 2011 at 01:32:42PM -0800, YongHyeon PYUN wrote:
On Wed, Dec 14, 2011 at 10:17:41PM +0100, Andrea Venturoli wrote:
On 12/14/11 20:59, YongHyeon PYUN wrote:
AFAIK the firmware of controller has no known TSO issue so it
indicates a bug in driver.
What makes me wonder is
On Wed, Dec 14, 2011 at 03:22:06PM -0800, YongHyeon PYUN wrote:
On Wed, Dec 14, 2011 at 01:32:42PM -0800, YongHyeon PYUN wrote:
On Wed, Dec 14, 2011 at 10:17:41PM +0100, Andrea Venturoli wrote:
On 12/14/11 20:59, YongHyeon PYUN wrote:
AFAIK the firmware of controller has no known TSO
12 matches
Mail list logo
