From owner-freebsd-stable@FreeBSD.ORG Sun May 7 07:24:05 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7792216A408 for ; Sun, 7 May 2006 07:24:05 +0000 (UTC) (envelope-from duane@greenmeadow.ca) Received: from smtpout.eastlink.ca (smtpout.eastlink.ca [24.222.0.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A74643D53 for ; Sun, 7 May 2006 07:23:51 +0000 (GMT) (envelope-from duane@greenmeadow.ca) Received: from ip01.eastlink.ca ([24.222.10.5]) by mta01.eastlink.ca (Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005)) with ESMTP id <0IYV00HI3WIMHI21@mta01.eastlink.ca> for freebsd-stable@freebsd.org; Sun, 07 May 2006 04:23:10 -0300 (ADT) Received: from blk-224-199-230.eastlink.ca (HELO [192.168.0.103]) ([24.224.199.230]) by ip01.eastlink.ca with ESMTP; Sun, 07 May 2006 04:23:51 -0300 Date: Sun, 07 May 2006 04:22:55 -0300 From: Duane Whitty In-reply-to: <20060507023942.B36981@ganymede.hub.org> To: "Marc G. Fournier" Message-id: <445DA04F.4010808@greenmeadow.ca> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAQAAA+k= References: <20060507023942.B36981@ganymede.hub.org> User-Agent: Thunderbird 1.5.0.2 (X11/20060503) Cc: freebsd-stable@freebsd.org Subject: Re: fxp0: ethernet freezes sporatically ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 May 2006 07:24:05 -0000 Marc G. Fournier wrote: > > g'day ... > > I've recently started having an issue on my desktop that I've been > kinda hounding the cable provider about, but, from their end, they see > absolutely no issues ... so I figured I'd see if there was maybe > something happening within the OS itself ... > > Here is the issue ... periodically, for 60-120 secs, my SSH > connections to servers in both Panama, Central America and Toronto, > Canada, will hang ... seems to be totally random ... > > Web *appears* to work during that time, and I have Azureas running > and *it* appears to keep running during that time ... I suspect that > my IMAP connections (fetchmail) are also being affected, since I get > the original "timeout" emails from fetchmail ... > > I am running: > > FreeBSD 6.1-RC #21: Sun Apr 30 20:56:36 ADT 2006 > > On: > > CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2394.01-MHz 686-class CPU) > > And my Internet connection is running on: > > fxp0: > > As I've mentioned above, I have been bugging my cable company about > this, but they can find no reasons on their ends to account for this > ... I have a business account, so I'm not dealing with "Residential > QoS" issues on this one ... > > Is there *anything* on the OS side of things that I should be > looking at that I may be overlooking? Any known issues with the fxp > driver that might be causing this? I've always found it to be a more > then stable driver, but things can happen ... > > Also, please note that I don't have a router between the 'Net and I > ... my desktop is our network router, so the fxp device is directly > connected ... > > Thoughts? > > Thanks ... > > ---- > Marc G. Fournier Hub.Org Networking Services > (http://www.hub.org) > Email: scrappy@hub.org Yahoo!: yscrappy ICQ: > 7615664 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > Hi, Have you considered it might be an Azureas issue? Older Azureas clients have caused me many headaches on my home network. I understand your network is much more robust than what I am running on. However, Azureas runnign on MS Windows XP clients caused network problems which affected my FreeBSD installation. I never did trace the cause except that when Azureas went away so did the problems. The newest Azureas client seems to play much nicer though and I haven't been experienceing any network issues. The symptoms you describe sound very similar in general to the ones everyone on my network experienced, albeit with different applications in play. Best Regards, Duane Whitty -- duane@greenmeadow.ca