From owner-freebsd-current@FreeBSD.ORG Fri Nov 23 17:26:53 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C54516A41B for ; Fri, 23 Nov 2007 17:26:53 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from conducive.net (lindfield.ch [203.194.153.81]) by mx1.freebsd.org (Postfix) with ESMTP id BDD1A13C448 for ; Fri, 23 Nov 2007 17:26:52 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from cm218-253-81-177.hkcable.com.hk ([218.253.81.177]:62419 helo=pb.local) by conducive.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1IvcIh-0002CQ-Lq for freebsd-current@freebsd.org; Fri, 23 Nov 2007 17:26:51 +0000 Message-ID: <47470D55.9000203@conducive.net> Date: Fri, 23 Nov 2007 17:26:45 +0000 From: =?UTF-8?B?6Z+T5a625qiZIEJpbGwgSGFja2Vy?= User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <474288AE.1040106@gmail.com> <47452703.1020008@gmail.com> <47453BCF.1060908@conducive.net> <474558C7.1090801@gmail.com> <4745D9CE.8010707@conducive.net> <47462ED9.2030902@gmail.com> In-Reply-To: <47462ED9.2030902@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: who do I report this to? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Nov 2007 17:26:53 -0000 Aryeh M. Friedman wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > 韓家標 Bill Hacker wrote: >> Aryeh M. Friedman wrote: *snip* > > My roommates XP machine seems to have none of these issues and it is ACK - but that is yet-another set of variables of limited utility to an re(4) coder. We don't know what MB, BIOS, 'glue' chipset, NIC ... yada yada.. Vista is using - nor would it be lot of help as regards *BSD if we DID know. *snip* > > Personally I think the unpredictable parts are part of the issue since > as you said you have pretty much the same setup and no issue... thus Sure they are. But they have to be either quantized (hard) or removed (easy). > the only way to do a local test I can think of is write a network > simulator and throw in different loss characteristics No need to write it. tcpdump has lots of 'steering', dummynet has what you need, and wireshark may be of use. More stuff yet is in ports. But you still need two boxes, and at least two NICS - preferably 3 or more so that you can do re to re and re to 'non-re'. >> You will need at least one other 'local' box. It need not be fancy, >> but it has to be under your observation and control. > > If the XP machine above will do (keep in mind I can make minor > alterations to it but I will be skinned alive if I do anything like > install an OS) It *might* do if you can protect your friend's Vista from interference by booting it from an outboard HDD or USB stick - even a 'LiveCD' that is a bit better suited to providing analytical tools. *snip* > That is what the original post was asking but Pyun (and most other > private replies I have gotten) point to re(4) As they should. Remember - I didnt say that re(4) might not have need of fixing - I just said you were not the one best equipped to contribute good test data. *snip* >> What you are calling a 'phantom' is the product of a combination of >> circumstances - too many of which are literally 'outside the house'. > > this very well be true but the lack of problems on vista/xp says other > wise I think. > Perhaps. But, as said - it is mostly just a different set of confusables. *snip* > > The only thing I have for this is the XP machine and Belkin router. > Lack of specialized resources is no sin. But best to face that and concentrate your energy on issues that you can more easily test accurately - not with what you wish you had - but with what you DO have. Others will have access to better re(4) test environments - or the resources to implement such. Meanwhile, I suspect that if you force your re to downshift to 10-base speed when using the uplink, you will see real-world throughput actually go up, not down. Bill