Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 24 Sep 2002 12:41:30 -0500
From:      Eric Anderson <anderson@centtech.com>
To:        Terry Lambert <tlambert2@mindspring.com>
Cc:        freebsd-chat@freebsd.org
Subject:   Re: FreeBSD NFS server using two NICs
Message-ID:  <3D90A3CA.7070004@centtech.com>
References:  <3D8A3E52.2090202@centtech.com> <3D8A428B.B96FBE75@mindspring.com> <3D8A458B.2080608@centtech.com> <3D8A4B40.67C8E2A2@mindspring.com> <3D8F66AB.8020309@centtech.com> <3D8F8401.E77A5DA9@mindspring.com> <3D90775C.9080804@centtech.com> <3D9078D2.8090401@centtech.com> <3D9097BB.3241C644@mindspring.com>

next in thread | previous in thread | raw e-mail | index | archive | help

[-- Attachment #1 --]
Terry Lambert wrote:
> 
> Try:
> 
> 	netstat -s | head -25 | tail -2
> 
> ... and tell us if you see anything different from:
> 
>                 0 discarded for bad checksums
>                 0 discarded for bad header offset fields
> 
> It's possible that the problem is that you have bad hardware
> checdksum hardware in the senders, and the packets are being
> dropped intentionally because of this.
> 
> 
> It could also be that the reassembly buffers are not being
> mixed... which still means you need to look at the wire
> contents again.

Ok, here's some more goodies.. Netstat -s looks fine..
On the server, a netstat -a shows:
Proto Recv-Q Send-Q  Local Address          Foreign Address        (state)
tcp4    2392      0  otter.nfsd             netman.1009 
ESTABLISHED

Server's name is otter and netman is the solaris 7 client (using 
autmounter to use the nfs share).

The server is running FreeBSD 4.6.2.

And I've attached a small tcpdump (-w filename.txt -vvv host netman) run 
from the server to capture the "trigger".  It's only a few packets, but 
these are the packets that make it go bad.

Also, I'm running nfsd on the server like so:
nfsd -h ip.of.nic.1 -h ip.of.nic.2 -t -u -n 10

If I run nfsd like:
nfsd -h ip.of.nic.1 -t -u -n 10
it works fine.

It isn't a bad NIC on the server (I've tried multiple nics, mutliple 
servers, and different FreeBSD OS versions) - but it could possibly be a 
bad NIC on the client side.

What other data do you need?

Heck, if I need to, I'll set up a "test bed" that you can access, and we 
can go from there.

Eric


-- 
------------------------------------------------------------------
Eric Anderson	   Systems Administrator      Centaur Technology
The moon may be smaller than Earth, but it's further away.
------------------------------------------------------------------

[-- Attachment #2 --]
ò`=<< `NxTE,@
$
%Y+`"8)UU=::`NxT E,9@
%
$?Z`%9=H<< `NxTE(@
$
%Z?P"8UUUUUU=ϖ` `NxTE@&
$
%Z?P"8id==
66`NxT E(:@@
%
$?P8 =
\\`NxTEN@`~
$
:!1: EDEFEOFEEBFFFCDBCACACACACACACABN !=l\\`NxTEN@`}
$
:!1: EDEFEOFEEBFFFCDBCACACACACACACABN #=Y\\`NxTEN@`|
$
:!1: EDEFEOFEEBFFFCDBCACACACACACACABN #=Y\\`NxTEN@`{
$
:!1: EDEFEOFEEBFFFCDBCACACACACACACABN 

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D90A3CA.7070004>