From owner-freebsd-java@FreeBSD.ORG Tue Sep 9 02:41:35 2003 Return-Path: Delivered-To: freebsd-java@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A4FA16A4BF for ; Tue, 9 Sep 2003 02:41:35 -0700 (PDT) Received: from armadillo.lan.eorigen.com (82-68-60-9.dsl.in-addr.zen.co.uk [82.68.60.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id A393843FCB for ; Tue, 9 Sep 2003 02:41:34 -0700 (PDT) (envelope-from dhardiker@eorigen.com) Received: from ws4 (ws4.lan.eorigen.com [192.168.1.54]) by armadillo.lan.eorigen.com (Postfix) with SMTP id E165A582F; Tue, 9 Sep 2003 10:41:32 +0100 (BST) Message-ID: <00a701c376b6$8e232820$3601a8c0@ws4> From: "Dan Hardiker" To: "Michael Bretterklieber" Date: Tue, 9 Sep 2003 10:41:33 +0100 Organization: eOrigen MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 cc: freebsd-java@FreeBSD.org Subject: Re: MPD Issues - Errors and Mysterious Packet Loss X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Dan Hardiker List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Sep 2003 09:41:35 -0000 > try from the XP Box: > > ping -l 1500 www.yahoo.de > > If you get no reply then try decreasing the ICMP packet size (-l switch), > until you get a reply. Pinging 192.168.1.3 (internal ip of MPD server) from 192.168.1.101 (assigned ip of xp box) as external traffic isnt routed via vpn's gateway. 1500 - no reply x4 1400 - no reply x4 1300 - no reply x3 + 1 reply on the 3rd attempt 1200 - no reply x2 + 2 reply on the 1st / 4th attempt 1100 - no reply x3 + 1 reply on the 2nd attempt 1000 - no reply x2 + 2 reply on the 1st / 4th attempt 900 - no reply x3 + 1 reply on the 2nd attempt 800 - no reply x2 + 2 reply on the 1st / 4th attempt 700 - no reply x3 + 1 reply on the 2nd attempt // stopped the pinging for about 5 mins here // 600 - no reply x1 + 3 reply on the 1st / 2nd / 3rd attempt 500 - no reply x1 + 3 reply on the 1st / 2nd / 3rd attempt 400 - no reply x2 + 2 reply on the 1st / 2nd attempt 300 - no reply x2 + 2 reply on the 1st / 4th attempt 200 - no reply x2 + 2 reply on the 1st / 4th attempt 100 - no reply x2 + 2 reply on the 1st / 2nd attempt 50 - no reply x1 + 3 reply on the 1st / 2nd / 3rd attempt Heres a bit of info for you - while I doing some of the duplicate tests (pinging 1000 more than just 1 set of 4 for example) I though I would try pinging 192.168.1.101 from the mpd server to see if I could get through. Heres what I found: [10:29:32][root@armadillo]:~$ ping 192.168.1.101 PING 192.168.1.101 (192.168.1.101): 56 data bytes ping: sendto: No buffer space available ping: sendto: No buffer space available ping: sendto: No buffer space available 64 bytes from 192.168.1.101: icmp_seq=3 ttl=128 time=0.922 ms 64 bytes from 192.168.1.101: icmp_seq=4 ttl=128 time=0.889 ms 64 bytes from 192.168.1.101: icmp_seq=5 ttl=128 time=0.882 ms 64 bytes from 192.168.1.101: icmp_seq=6 ttl=128 time=0.877 ms 64 bytes from 192.168.1.101: icmp_seq=7 ttl=128 time=0.871 ms NOTE: the TTL on the pings from the XP box are notabley 64 where as the mpd server has them set to 128 Buffer space seems to be running out somewhere? PS: I applied the TCP MSS patch, and even with TCP web traffic, Im still clocking up receiving errors by the dozen. I hope that helps -- Dan Hardiker [dhardiker@eorigen.com] ADAM Systems Engineer eOrigen Ltd