Re: [Sheflug] NFS and fast machines

[Dave Mitchell <davem [at] xxxxxxxxxxxxxxxx>]

On Fri, Jan 23, 2004 at 05:06:22PM -0000, Morris, David (Allvac, UK) wrote:
> > > It might be something to do with tcpdump putting the
> > > interface into promiscuous mode. Try it with -p and see if it 
> > > stops having its magical effect.
> > 
> > Good idea. I (naively) thought that promiscuous mode wouldn't 
> > have a significant effect. I could be wrong.
> > 
> > Would that have any effect on LAN broadcasts and the 
> > likelihood of the NFS client seeing the server?
> > 
> > (NFS is a new ball game for me).
> 
> Doing 'tcpdump -i eth0 -p' also works.
> 
> Doing nothing still doesn't work.

Well, I wouldn't have expected running tcpdump  to make a difference, so
the -p was just a long shot. Another long shot would be to use -n as well,
to stop tcpdump doing name lookups (ie anything that makes tcpdump as
"passive" as possible). The only way that -p might reasonably have made a
change is if there was some sort of misconfiuration somewhere that causes
the server not to see broadcasts. 

If you have a spare machine, I'd be trmpted to connect it to the same LAN,
(by a hub not a switch), run tcpdump -n on that machine, then run tcpdump
on the server, and see whether any traffic is genreated that triggers
the response.

-- 
print+qq&$}$"$/$s$,$*${d}$g$s$@$.$q$,$:$.$q$^$,$@$*$~$;$.$q$m&if+map{m,^\d{0\,},,${$::{$'}}=chr($"+=$&||1)}q&10m22,42}6:17*2~2.3 [at] 3;^2dg3q/s"&=~m*\d\*.*g
___________________________________________________________________

Sheffield Linux User's Group -
http://www.sheflug.co.uk/mailfaq.html

  GNU the choice of a complete generation.