From charford@kajack.2y.net  Fri Mar 29 18:40:15 2002
Return-Path: <charford@kajack.2y.net>
Received: from kajack.2y.net (bwif20epy7qc.ab.hsia.telus.net [142.59.95.28])
	by hub.freebsd.org (Postfix) with ESMTP id 0C64337B405
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 29 Mar 2002 18:40:08 -0800 (PST)
Received: (from root@localhost)
	by kajack.2y.net (8.11.6/8.11.6) id g2U2dhT31429;
	Fri, 29 Mar 2002 19:39:43 -0700 (MST)
	(envelope-from charford)
Message-Id: <200203300239.g2U2dhT31429@kajack.2y.net>
Date: Fri, 29 Mar 2002 19:39:43 -0700 (MST)
From: Colin Harford <charford@su.ualberta.ca>
Reply-To: Colin Harford <charford@su.ualberta.ca>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject:
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         36519
>Category:       kern
>Synopsis:       
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    gnats-admin
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Mar 29 18:50:01 PST 2002
>Closed-Date:    Sat Mar 30 05:14:31 PST 2002
>Last-Modified:  Wed Oct 26 05:00:18 GMT 2005
>Originator:     
>Release:        
>Organization:
>Environment:
>Description:
Strange Network Problems in RELENG_4, 

See below email for info on it, basically network is sluggish and takes 
forever to establish connection.

I have duplicated the exact same problem on some of my FreeBSD 
workstations at work, all with a xl0 interface and a 3com switch, not all 
machines are affected, but some are.

I would appreciate some sort of correspondence regarding the outcome of 
your investigation, as I do not want to keep all my production machines 
running RELENG_4_5

One machine at home has a direct internet connection and passes the 
connection along to a switch to serve my home network. The problem plagued 
both interfaces, replacing swtich, dsl modem and cables did not fix the 
problem.   I have also worked with my  ISP on this, and there does not 
seem to be a problem. 

My second home FreeBSD machine also boots into WinXP and when in WinXP it 
does not have the same problem...

 On 19/3/02 4:48 PM, "Doug White" 
<dwhite@resnet.uoregon.edu> wrote:

> On 19 Mar 2002, Aaron Baugher wrote:
> 
>How-To-Repeat:
<unknown...can not find the cause or common similarities between affected 
machines>
	
>Fix:
	Temporary solution, use RELENG_4_5
	


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: keramida 
State-Changed-When: Sat Mar 30 05:13:59 PST 2002 
State-Changed-Why:  
Misfiled followup. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=36519 
>Unformatted:
 Submitter-Id:	current-users
 Originator:	Colin Harford
 Organization:	University of Alberta Students' Union
 Confidential:	no <FreeBSD PRs are public data>
 Synopsis:	strange network problems
 Severity:	serious<[ non-critical | serious | critical ] (one line)>
 Priority:	high <[ low | medium | high ] (one line)>
 Category:	misc
 Class:		<[ sw-bug | doc-bug | change-request | update | maintainer-update ] (one line)>
 Release:	FreeBSD 4.5-RELEASE-p2 i386
 Environment:
 System: FreeBSD kajack.2y.net 4.5-RELEASE-p2 FreeBSD 4.5-RELEASE-p2 #19: Sun Mar 17 13:47:15 MST 2002 root@kajack.2y.net:/usr/obj/usr/src/sys/KAJACK i386
 
 
 	<machine, os, target, libraries (multiple lines)>
 >> To add to the previous info, here's a chunk of a tcpdump.  I logged in
 >> through ssh, and ran 'top' to generate some traffic.  My home machine
 >> (Mandrake Linux, connected with a modem) is 11.22.33.44, and the
 >> FreeBSD machine having the problem is 55.66.77.88.  (I should stress
 >> that the problem occurs from several different client machines and
 >> OS's, so it's definitely caused at the server end.)
 > 
 > This looks like simple packet loss on the network. Can you set up a
 > monitor port on the Cisco switch and confirm the packet that is retried 
 is
 > actually making it onto the wire? Also set up other monitors downstream
 > and see if you can isolate where the packet disappears.
 > 
 >> 09:41:22.371874 55.66.77.88.22 > 11.22.33.44.4257: P 33324:33472(148) 
 ack 161 
 >> win 65535 [tos 0x10]
 >> 09:41:23.371716 55.66.77.88.22 > 11.22.33.44.4257: P 33324:33472(148) 
 ack 161 
 >> win 65535 [tos 0x10]
 >> 
 >> That's the same packet sent twice, right?
 >> 
 >> 09:41:24.381831 55.66.77.88.22 > 11.22.33.44.4257: P 33472:33628(156) 
 ack 161 
 >> win 65535 [tos 0x10]
 >> 09:41:24.629822 11.22.33.44.4257 > 55.66.77.88.22: . ack 33324 win 
 51360 (DF) 
 >> [tos 0x10]
 >> 09:41:25.371763 55.66.77.88.22 > 11.22.33.44.4257: P 33324:33628(304) 
 ack 161 
 >> win 65535 [tos 0x10]
 >> 
 >> Now here's the same number (33324) as the doubled packet above, but
 >> with a different second number and size.
 > 
 > The change in size is the system gluing the payloads of the two packets
 > together since the remote sent an ACK up to 33324.
 > 
 >> 09:41:34.666565 11.22.33.44.4257 > 55.66.77.88.22: . ack 33324 win 
 51360 (DF) 
 >> [tos 0x10]
 >> 09:41:34.666621 55.66.77.88.22 > 11.22.33.44.4257: P 33324:34336(1012) 
 ack 
 >> 161 win 65535 [tos 0x10]
 >> 09:41:35.147334 11.22.33.44.4257 > 55.66.77.88.22: . ack 34336 win 
 51360 (DF) 
 >> [tos 0x10]
 > 
 > Look like your network keeled over for 10 seconds. Bandwidth problems
 > downstream?
 > 
 > Also make sure something downstream isn't, say, loosing the ARP entry 
 for
 > it's default gateway.
 > 
 > Doug White                    |  FreeBSD: The Power to Serve
 > dwhite@resnet.uoregon.edu     |  www.FreeBSD.org
 > 
 > 
 > To Unsubscribe: send mail to majordomo@FreeBSD.org
 > with "unsubscribe freebsd-stable" in the body of the message
 
 
 I was having a similar situation as Aaron at home on both my FreeBSD 
 machines
 
 • K6-3-450, 512 RAM, rl interface
 • K7-1.2Ghz, 1GB RAM, xl interface
 
 Both started happening in FreeBSD 4.5, both are connected to an internal 
 10/100 switch at 100T and are about 10 inches from each other... 
 
 The k7 is a dual boot machine, and when I am in winblowdoze I do not have 
 the same problem, so I have mostly ruled out hardware problems...(that and 
 hardware has been tested in other situations without problems)
 
 I updated both machines this past weekened, to RELENG_4_5 and no longer do 
 I have this problem.   
 
 HTH
 
 
 Colin Harford    
 
                        
                
 Systems and Network Administrator         Apple Product Professional
 =================================     
 Computer and Network Support         
 University of Alberta Students' Union                  
 Phone: (780) 492-4241   Fax:  (780) 492-4643
 http://www.su.ualberta.ca
 
 
 "I sense much NT in you, NT leads to Blue Screen.
 Blue Screen leads to downtime, downtime leads to suffering.
 NT is the path to the darkside."
          - Unknown Unix Jedi
 
 	
