From owner-freebsd-questions@FreeBSD.ORG Tue Nov 4 13:10:26 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7B4081065680 for ; Tue, 4 Nov 2008 13:10:26 +0000 (UTC) (envelope-from joompz@gmail.com) Received: from po-out-1718.google.com (po-out-1718.google.com [72.14.252.157]) by mx1.freebsd.org (Postfix) with ESMTP id 49D168FC16 for ; Tue, 4 Nov 2008 13:10:26 +0000 (UTC) (envelope-from joompz@gmail.com) Received: by po-out-1718.google.com with SMTP id y22so11639560pof.3 for ; Tue, 04 Nov 2008 05:10:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=N007yy4A2BFoAM433SefUjhvJuat00tW5orbp1ET3p4=; b=lJHz/3kTgSOCgpfarWTm41YCmd1KjCVio+O+qV4oF2vEcM+JuRkjd/dpJD7Vpu+fCc lnbGR7TRUWBg6PFTP3UOpiOmC3FyLpl/hkzVyWXk01byp+v+bziJzQUNniU9F3M7SjUU 4BvWomk7WDA4VTyNoIFEURxK0cBll7YcvBTro= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=nCrpWLY9BI7swn25Q4r6ZTyBrXC02rHn+2HZyoNBhnKLJUHX7GUHNLjdfGkcwTqfah xytvW3d7zBZgNfALdcrqKX3d5/6/us9p/iulPehqmaIZTGkG72pCSakNnlnuFKSeDCbM 716a7deRbLoIuCxfu9ZkHeCO8iFtIfKVYopdU= Received: by 10.141.206.13 with SMTP id i13mr833837rvq.211.1225804225991; Tue, 04 Nov 2008 05:10:25 -0800 (PST) Received: by 10.140.174.19 with HTTP; Tue, 4 Nov 2008 05:10:25 -0800 (PST) Message-ID: Date: Tue, 4 Nov 2008 11:10:25 -0200 From: "J MPZ" To: freebsd-questions@freebsd.org In-Reply-To: <490FA51F.7010901@datapipe.com> MIME-Version: 1.0 References: <490FA51F.7010901@datapipe.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Problems with FreeBSD X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2008 13:10:26 -0000 Hi Paul, When my connections freeze, I open the tcpdump in other terminal. If I type something, type "Enter", on the terminal frozen, the tcpdump show packets, like that: 11:18:45.526256 IP (tos 0x0, ttl 51, id 651, offset 0, flags [DF], proto: TCP (6), length: 112) 189.21.230.195.20787 > 201.57.5.2.2264: P 193:241(48) ack 0 win 15136 11:18:45.625839 IP (tos 0x10, ttl 64, id 23438, offset 0, flags [DF], proto: TCP (6), length: 52) 201.57.5.2.2264 > 189.21.230.195.20787: ., cksum 0x4d03 (correct), 1664:1664(0) ack 241 win 65535 11:18:45.707825 IP (tos 0x0, ttl 51, id 652, offset 0, flags [DF], proto: TCP (6), length: 112) 189.21.230.195.20787 > 201.57.5.2.2264: P 241:289(48) ack 0 win 15136 11:18:45.807839 IP (tos 0x10, ttl 64, id 23493, offset 0, flags [DF], proto: TCP (6), length: 52) 201.57.5.2.2264 > 189.21.230.195.20787: ., cksum 0x4b4b (correct), 1664:1664(0) ack 289 win 65535 11:18:45.867181 IP (tos 0x0, ttl 51, id 653, offset 0, flags [DF], proto: TCP (6), length: 112) 189.21.230.195.20787 > 201.57.5.2.2264: P 289:337(48) ack 0 win 15136 11:18:45.966840 IP (tos 0x10, ttl 64, id 23529, offset 0, flags [DF], proto: TCP (6), length: 52) 201.57.5.2.2264 > 189.21.230.195.20787: ., cksum 0x49b5 (correct), 1664:1664(0) ack 337 win 65535 When I executed 'ls' on the terminal frozen, returns this on tcpdump: 11:19:35.738788 IP (tos 0x0, ttl 51, id 654, offset 0, flags [DF], proto: TCP (6), length: 112) 189.21.230.195.20787 > 201.57.5.2.2264: P 337:385(48) ack 0 win 15136 11:19:35.788428 IP (tos 0x0, ttl 51, id 655, offset 0, flags [DF], proto: TCP (6), length: 112) 189.21.230.195.20787 > 201.57.5.2.2264: P 385:433(48) ack 0 win 15136 11:19:35.788483 IP (tos 0x10, ttl 64, id 34519, offset 0, flags [DF], proto: TCP (6), length: 52) 201.57.5.2.2264 > 189.21.230.195.20787: ., cksum 0xc3d4 (correct), 1664:1664(0) ack 433 win 65535 11:19:36.229773 IP (tos 0x0, ttl 51, id 656, offset 0, flags [DF], proto: TCP (6), length: 112) 189.21.230.195.20787 > 201.57.5.2.2264: P 433:481(48) ack 0 win 15136 11:19:36.328854 IP (tos 0x10, ttl 64, id 34621, offset 0, flags [DF], proto: TCP (6), length: 52) 201.57.5.2.2264 > 189.21.230.195.20787: ., cksum 0xbf5c (correct), 1664:1664(0) ack 481 win 65535 I'm using: tcpdump -nvvv -i ste0 host REMOTE_IP 2008/11/3, Paul A. Procacci : > > J MPZ wrote: > >> Hi guys, >> >> I have some problem with my FreeBSD server. I have this: >> >> ######### ########### ######### >> # Linux1 # -> ASA -> Internet -> # FreeBSD # -> # Linux2 # >> ######### ########### ######### >> >> If I run a ssh for Linux1 to FreeBSD, my connection freeze when the return >> of some command is a big text. Example: >> >> I make a ssh connection in the from the Linux1 to FreeBSD server, then, I >> execute some commands, like: 'pwd', 'whoami', 'ls /'... this work >> perfectly. >> But, if I run some command that return a big text, like as: 'ls /dev/', or >> top, my connection freeze. >> >> In other terminal, the tcpdump continues showing packets in this >> connection >> that was freeze. >> >> If I try to access the Linux2, throught FreeBSD (redirect port on natd or >> redirect port with rinetd), the same thing happens. >> >> Is this a problem with FreeBSD? Someone know how I can fix it? Some >> sysctl? >> >> Regards, >> J. >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to " >> freebsd-questions-unsubscribe@freebsd.org" >> >> > The tcpdump that you say continues showing packets......are the packets > leaving the freeBSD machine or arriving at the FreeBSD machine. > My guess is you meant leaving the FreeBSD destined for your linux machine. > If this is the case, then the problem most likely lies with the ASA. > If you monitor the ASA's external interface during your testing, do you see > packets arriving? If so, do you see packets leaving the internal interface > going back to your Linux1 machine? >