Apple OS X SMB issues across VPN

[David Collier-Brown]

   Just a status: looking at these in ethereal and snoop shows
a distinct sloth pattern, probably a three-toed (;-))
I've not drilled down further as yet...

Christopher R. Hertel wrote:
> On Thu, Dec 01, 2005 at 09:42:33AM -0700, Dan Tappin wrote:
> 
>>Hi Chris,
>>
>>I'm back...
>>
>>I have my test RH 7 server up and running on the local LAN ready to  
>>test across the VPN.  One issue though:
>>
>>[root at localhost admin]# tcpdump -i eth0 -s0 -w capture.cap host  
>>192.168.0.150 and 192.168.2.46
>>tcpdump: invalid snaplen 0
>>
>>-s1 seems to work but not sure if this effects the data.
> 
> 
> The snap length (set via -s) determines how many bytes worth of each 
> packet is actually captured.  A snaplen setting of zero is *supposed* to 
> mean "all of it".  That is, it's supposed to tell tcpdump that it should 
> write each packet in its entirety to the capture file.
> 
> I've used some older versions of tcpdump that don't accept a zero value 
> for that parameter, so I figure that's the problem you've got.  The 
> work-around is to use a value like 2000, which is larger than the maximum 
> size of an Ethernet frame (assuming you're not using jumbo frames).
> 
> Lemme know if that works.  :)
> 
> Chris -)-----
> 

-- 
David Collier-Brown,      | Always do right. This will gratify
Sun Microsystems, Toronto | some people and astonish the rest
davecb at canada.sun.com     |                      -- Mark Twain
(416) 263-5733 (x65733)   |