From owner-freebsd-net@FreeBSD.ORG Sun May 21 09:26:11 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D3BA16A420 for ; Sun, 21 May 2006 09:26:11 +0000 (UTC) (envelope-from b.candler@pobox.com) Received: from rune.pobox.com (rune.pobox.com [208.210.124.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2200343D6E for ; Sun, 21 May 2006 09:26:07 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from rune (localhost [127.0.0.1]) by rune.pobox.com (Postfix) with ESMTP id 3AADD7881D; Sun, 21 May 2006 05:26:28 -0400 (EDT) Received: from mappit.local.linnet.org (212-74-113-67.static.dsl.as9105.com [212.74.113.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by rune.sasl.smtp.pobox.com (Postfix) with ESMTP id D801678814; Sun, 21 May 2006 05:26:25 -0400 (EDT) Received: from lists by mappit.local.linnet.org with local (Exim 4.61 (FreeBSD)) (envelope-from ) id 1FhkCI-0005Hm-9C; Sun, 21 May 2006 10:26:02 +0100 Date: Sun, 21 May 2006 10:26:02 +0100 From: Brian Candler To: Mike Tancsa Message-ID: <20060521092602.GB20262@uk.tiscali.com> References: <6.2.3.4.0.20060519110026.05820230@64.7.153.2> <6.2.3.4.0.20060519121104.1126b480@64.7.153.2> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6.2.3.4.0.20060519121104.1126b480@64.7.153.2> User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@freebsd.org, Ian Smith Subject: Re: improving transport over lossy links ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 May 2006 09:26:11 -0000 On Fri, May 19, 2006 at 12:38:31PM -0400, Mike Tancsa wrote: > Thanks for the reply. Even at 28.8 I am seeing loss with > the connection dropping and seeing dropped packets (e.g. > May 19 12:04:43 soekris4801 ppp[3404]: tun0: Phase: 1: HDLC errors -> > FCS: 1, ADDR: 0, COMD: 0, PROTO: 0) If you have an error-correcting modem, but you are seeing data corruption, then I'd expect the data corruption is occuring on the RS232 link between the PC and the modem at one end or the other. You may have a handshaking problem (i.e. ensure the modem is configured for CTS/RTS handshaking, and the port is configured for this too; with pppd it's "crtscts", I don't know about userland ppp; and ensure the cables are wired properly) If your app could cope with the lack of bandwidth, forcing the modems to 2400bps operation can make links over dodgy lines a lot more reliable. Regards, Brian. From owner-freebsd-net@FreeBSD.ORG Sun May 21 12:40:44 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8998E16A421 for ; Sun, 21 May 2006 12:40:44 +0000 (UTC) (envelope-from gmicsko@szintezis.hu) Received: from mta05.mail.t-online.hu (mta05.mail.t-online.hu [195.228.240.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 11BBF43D49 for ; Sun, 21 May 2006 12:40:43 +0000 (GMT) (envelope-from gmicsko@szintezis.hu) Received: from localhost (localhost [127.0.0.1]) by mail.t-online.hu (Postfix) with ESMTP id 26B56E5A8F6; Sun, 21 May 2006 14:40:42 +0200 (CEST) Received: from dsl54025D66.pool.t-online.hu (dsl54025D66.pool.t-online.hu [84.2.93.102]) by mail.t-online.hu (Postfix) with ESMTP id 74C09E5A8F5; Sun, 21 May 2006 14:40:38 +0200 (CEST) From: Gabor MICSKO To: OxY In-Reply-To: <000801c67c06$973a34a0$0201a8c0@oxy> References: <001501c67c03$9c3457e0$8a01a8c0@ntpc> <000801c67c06$973a34a0$0201a8c0@oxy> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-h6XJMemM3nxeosqBryK/" Date: Sun, 21 May 2006 14:40:36 +0200 Message-Id: <1148215237.4555.2.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 Cc: freebsd-net@freebsd.org, Peter Blok Subject: Re: mbuf denied problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 May 2006 12:40:44 -0000 --=-h6XJMemM3nxeosqBryK/ Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sat, 2006-05-20 at 14:11 +0200, OxY wrote: > thank you, i'll try it in a couple of days! > it's sad that it's a returning question and no patch from the developers. Yes, It's a returning question.=20 http://marc.theaimsgroup.com/?l=3Dfreebsd-net&m=3D114305945916474&w=3D2 --=20 Micsk=C3=B3 G=C3=A1bor HP APS, AIS, ASE Szint=C3=A9zis Rt. H-9023 Gy=C5=91r, Tihanyi =C3=81. u. 2. Tel: +36 96 502 221 Fax: +36 96 318 658 E-mail: gmicsko@szintezis.hu --=-h6XJMemM3nxeosqBryK/ Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQBEcF/Eo75Oas+VX1ARAo4YAKC75OiNTOW6LCSXdRb+x89EahaYeACeKS15 /TpgX+zd1GzZ40RErZQ4BZU= =biL7 -----END PGP SIGNATURE----- --=-h6XJMemM3nxeosqBryK/-- From owner-freebsd-net@FreeBSD.ORG Sun May 21 15:09:29 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A461716A624 for ; Sun, 21 May 2006 15:09:29 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1585243D49 for ; Sun, 21 May 2006 15:09:28 +0000 (GMT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.13.6/8.13.6) with ESMTP id k4LF9QXx070987; Sun, 21 May 2006 11:09:26 -0400 (EDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.3P/8.13.3) with ESMTP id k4LF9Oci009610 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 21 May 2006 11:09:25 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.2.3.4.0.20060521104147.081af2d8@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Sun, 21 May 2006 11:09:23 -0400 To: Brian Candler From: Mike Tancsa In-Reply-To: <20060521092602.GB20262@uk.tiscali.com> References: <6.2.3.4.0.20060519110026.05820230@64.7.153.2> <6.2.3.4.0.20060519121104.1126b480@64.7.153.2> <20060521092602.GB20262@uk.tiscali.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new Cc: freebsd-net@freebsd.org, Ian Smith Subject: Re: improving transport over lossy links ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 May 2006 15:09:36 -0000 At 05:26 AM 21/05/2006, Brian Candler wrote: >On Fri, May 19, 2006 at 12:38:31PM -0400, Mike Tancsa wrote: > > Thanks for the reply. Even at 28.8 I am seeing loss with > > the connection dropping and seeing dropped packets (e.g. > > May 19 12:04:43 soekris4801 ppp[3404]: tun0: Phase: 1: HDLC errors -> > > FCS: 1, ADDR: 0, COMD: 0, PROTO: 0) > >If you have an error-correcting modem, but you are seeing data corruption, >then I'd expect the data corruption is occuring on the RS232 link between >the PC and the modem at one end or the other. You may have a handshaking >problem (i.e. ensure the modem is configured for CTS/RTS handshaking, and >the port is configured for this too; with pppd it's "crtscts", I don't know >about userland ppp; and ensure the cables are wired properly) > >If your app could cope with the lack of bandwidth, forcing the modems to >2400bps operation can make links over dodgy lines a lot more reliable. Hi, Its not so much data corruption of packets on the wire, but the modem dropping the connection, retraining and renegotiating. When the retrains and re negotiations happen, this can cause problems for the VPN as keep alives are missed, tx buffers can fill up etc. I have tried a number of modems, the current one being U.S. Robotics 56K FAX INT V5.22.70. and I am also trying an external Intel at the office ati4 Intel Corporation OK ati5 Full V.92 Upgradeable Present, 32K DSP RAM.000 Host I/F: Serial P. Mem. : 008 Bit 001 W.S. D. Mem : 008 Bit 001 W.S. DSP loc : INT ROM The internal USR seems to correctly see the carrier drop and PPP hence sees it. However, the 2 external Intels I am experimenting with on the USB serial ports do not. I suspect thats part of the reason the DCD is not working. Perhaps incorrect init string or something with the USB-Serial. Note, I only have the internal USRs deployed in the field right now Intels [vpn2]# stty -f /dev/cuaU0 speed 115200 baud; lflags: -icanon -isig -iexten -echo iflags: -icrnl -imaxbel ignbrk -brkint oflags: -opost -oxtabs cflags: cs8 -parenb clocal crtscts [vpn2]# stty -f /dev/cuaU1 speed 115200 baud; lflags: -icanon -isig -iexten -echo iflags: -icrnl -imaxbel ignbrk -brkint oflags: -opost -oxtabs cflags: cs8 -parenb clocal crtscts [vpn2]# live USR internal [Hastings109]# stty -f /dev/cuad4 speed 115200 baud; lflags: -icanon -isig -iexten -echo iflags: -icrnl -ixon -imaxbel ignbrk -brkint oflags: -opost -oxtabs cflags: cs8 -parenb clocal crtscts From the terminal servers perspective it sees show m12 Card Type: LU1674 Chipset State: ACTIVE Active Port: S2 Transmit Rate: 45333 Receive Rate: 16800 Connection Type: LAPM/V42BIS Chars Sent: 3166222761 Chars Received: 2925103984 Retrains: 1 Renegotiations: 6 (not sure why, but chats tx/rx are for all calls in the pas 216 days, not just this one). This is in the past 4hours. Perhaps with this one, I am just better off telling it not to try v.90. ---Mike From owner-freebsd-net@FreeBSD.ORG Sun May 21 15:49:27 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A6AB016A433 for ; Sun, 21 May 2006 15:49:27 +0000 (UTC) (envelope-from bv@bilver.wjv.com) Received: from wjv.com (fl-65-40-24-38.sta.sprint-hsd.net [65.40.24.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80B5F43D6A for ; Sun, 21 May 2006 15:49:26 +0000 (GMT) (envelope-from bv@bilver.wjv.com) Received: from bilver.wjv.com (localhost.wjv.com [127.0.0.1]) by wjv.com (8.13.6/8.13.1) with ESMTP id k4LFnNYh002144; Sun, 21 May 2006 11:49:23 -0400 (EDT) (envelope-from bv@bilver.wjv.com) Received: (from bv@localhost) by bilver.wjv.com (8.13.6/8.13.1/Submit) id k4LFnHoL002143; Sun, 21 May 2006 11:49:17 -0400 (EDT) (envelope-from bv) Date: Sun, 21 May 2006 11:49:17 -0400 From: Bill Vermillion To: Mike Tancsa Message-ID: <20060521154917.GB2053@wjv.com> References: <6.2.3.4.0.20060519110026.05820230@64.7.153.2> <6.2.3.4.0.20060519121104.1126b480@64.7.153.2> <20060521092602.GB20262@uk.tiscali.com> <6.2.3.4.0.20060521104147.081af2d8@64.7.153.2> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6.2.3.4.0.20060521104147.081af2d8@64.7.153.2> Organization: W.J.Vermillion / Orlando - Winter Park ReplyTo: bv@wjv.com User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on bilver.wjv.com Cc: freebsd-net@freebsd.org, Ian Smith , Brian Candler Subject: Re: improving transport over lossy links ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bv@wjv.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 May 2006 15:49:36 -0000 Throwing caution to the wind and speaking without thinking about what was being said on Sun, May 21, 2006 at 11:09 , Mike Tancsa blurted this: > At 05:26 AM 21/05/2006, Brian Candler wrote: > >On Fri, May 19, 2006 at 12:38:31PM -0400, Mike Tancsa wrote: > >> Thanks for the reply. Even at 28.8 I am seeing loss with > >> the connection dropping and seeing dropped packets (e.g. > >> May 19 12:04:43 soekris4801 ppp[3404]: tun0: Phase: 1: HDLC errors -> > >> FCS: 1, ADDR: 0, COMD: 0, PROTO: 0) > >If you have an error-correcting modem, but you are seeing data corruption, > >then I'd expect the data corruption is occuring on the RS232 link between > >the PC and the modem at one end or the other. You may have a handshaking > >problem (i.e. ensure the modem is configured for CTS/RTS handshaking, and > >the port is configured for this too; with pppd it's "crtscts", I don't know > >about userland ppp; and ensure the cables are wired properly) > >If your app could cope with the lack of bandwidth, forcing the modems to > >2400bps operation can make links over dodgy lines a lot more reliable. > > Hi, > Its not so much data corruption of packets on the wire, but > the modem dropping the connection, retraining and > renegotiating. When the retrains and re negotiations happen, this > can cause problems for the VPN as keep alives are missed, tx buffers > can fill up etc. I have tried a number of modems, the current one > being U.S. Robotics 56K FAX INT V5.22.70. and I am also trying an > external Intel at the office The best modems I've found are the ones from Multi-tech. Even their super-small ones. Before we added a PRI and a Livingston we were thinking about using the MT's in the 19" rack mount box they have. And when performing fax from email - using sendmail incoming and routing to fax [in the early days of the current 'net before many people had 'net connections] the MT's were the only ones that worked with virtually ever target fax machine. The MTs are external. Bill -- Bill Vermillion - bv @ wjv . com From owner-freebsd-net@FreeBSD.ORG Sun May 21 17:15:27 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 25FAE16A500 for ; Sun, 21 May 2006 17:15:27 +0000 (UTC) (envelope-from b.candler@pobox.com) Received: from rune.pobox.com (rune.pobox.com [208.210.124.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1BA243D45 for ; Sun, 21 May 2006 17:15:26 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from rune (localhost [127.0.0.1]) by rune.pobox.com (Postfix) with ESMTP id CBC137934F; Sun, 21 May 2006 13:15:47 -0400 (EDT) Received: from mappit.local.linnet.org (212-74-113-67.static.dsl.as9105.com [212.74.113.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by rune.sasl.smtp.pobox.com (Postfix) with ESMTP id 728FE79263; Sun, 21 May 2006 13:15:45 -0400 (EDT) Received: from brian by mappit.local.linnet.org with local (Exim 4.61 (FreeBSD)) (envelope-from ) id 1FhrWT-0007oC-BR; Sun, 21 May 2006 18:15:21 +0100 Date: Sun, 21 May 2006 18:15:21 +0100 From: Brian Candler To: Mike Tancsa Message-ID: <20060521171521.GA29990@uk.tiscali.com> References: <6.2.3.4.0.20060519110026.05820230@64.7.153.2> <6.2.3.4.0.20060519121104.1126b480@64.7.153.2> <20060521092602.GB20262@uk.tiscali.com> <6.2.3.4.0.20060521104147.081af2d8@64.7.153.2> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6.2.3.4.0.20060521104147.081af2d8@64.7.153.2> User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@freebsd.org, Ian Smith Subject: Re: improving transport over lossy links ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 May 2006 17:15:27 -0000 On Sun, May 21, 2006 at 11:09:23AM -0400, Mike Tancsa wrote: > The internal USR seems to correctly see the carrier drop and PPP > hence sees it. However, the 2 external Intels I am experimenting > with on the USB serial ports do not. USB-serial adaptors tend to be very broken, unfortunately. I don't know about under Windows, but under FreeBSD/Linux where drivers seem to be reverse-engineered, several I've tried don't seem to handshake properly. I tried two back-to-back to run a local pppd link and it failed (haven't had time to debug that one) IMO there's no substitute for a real COM port. > (not sure why, but chats tx/rx are for all calls in the pas 216 days, > not just this one). This is in the past 4hours. Perhaps with this > one, I am just better off telling it not to try v.90. A pair of analogue modems will never negotiate v90, as for this one end has to be digitally connected (typically T1/E1 trunk, although in theory you might be able to find a modem which is physically connected as ISDN BRI but which supports v90 analogue modulation) The best you'll get is v34bis (33.6K) Regards, Brian. From owner-freebsd-net@FreeBSD.ORG Sun May 21 18:54:07 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2233E16A70D for ; Sun, 21 May 2006 18:54:07 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from gaia.nimnet.asn.au (nimbin.lnk.telstra.net [139.130.45.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D67943D46 for ; Sun, 21 May 2006 18:54:02 +0000 (GMT) (envelope-from smithi@nimnet.asn.au) Received: from localhost (smithi@localhost) by gaia.nimnet.asn.au (8.8.8/8.8.8R1.4) with SMTP id EAA07028; Mon, 22 May 2006 04:53:37 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Mon, 22 May 2006 04:53:37 +1000 (EST) From: Ian Smith To: Mike Tancsa In-Reply-To: <6.2.3.4.0.20060521104147.081af2d8@64.7.153.2> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-net@freebsd.org, Brian Candler Subject: Re: improving transport over lossy links ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 May 2006 18:54:11 -0000 On Sun, 21 May 2006 at 11:09:23 -0400, Mike Tancsa wrote: > At 05:26 AM 21/05/2006, Brian Candler wrote: > >On Fri, May 19, 2006 at 12:38:31PM -0400, Mike Tancsa wrote: > > > Thanks for the reply. Even at 28.8 I am seeing loss with > > > the connection dropping and seeing dropped packets (e.g. > > > May 19 12:04:43 soekris4801 ppp[3404]: tun0: Phase: 1: HDLC errors -> > > > FCS: 1, ADDR: 0, COMD: 0, PROTO: 0) > > > >If you have an error-correcting modem, but you are seeing data corruption, > >then I'd expect the data corruption is occuring on the RS232 link between > >the PC and the modem at one end or the other. You may have a handshaking > >problem (i.e. ensure the modem is configured for CTS/RTS handshaking, and > >the port is configured for this too; with pppd it's "crtscts", I don't know > >about userland ppp; and ensure the cables are wired properly) 100% great advice Brian, modulo what I said about some modems (three differently branded V.90s with Cirrus/Ambient chips to be specific) that very often show 1 FCS error frame early on, that's really a false alarm. > >If your app could cope with the lack of bandwidth, forcing the modems to > >2400bps operation can make links over dodgy lines a lot more reliable. Well yes, but you usually don't need to go to quite that extreme :) > Its not so much data corruption of packets on the wire, but > the modem dropping the connection, retraining and > renegotiating. When the retrains and re negotiations happen, this > can cause problems for the VPN as keep alives are missed, tx buffers > can fill up etc. I have tried a number of modems, the current one > being U.S. Robotics 56K FAX INT V5.22.70. and I am also trying an > external Intel at the office Yes that's just the problem alright. Just to be clear, you're referring here only to various calling-in modems, calling to these fixed terminal server cards, of maybe Lucent origin, right? > ati4 > Intel Corporation > > OK > ati5 > Full V.92 Upgradeable > Present, 32K DSP RAM.000 > Host I/F: Serial > P. Mem. : 008 Bit 001 W.S. > D. Mem : 008 Bit 001 W.S. > DSP loc : INT ROM Interesting .. that's pretty much the same response as one of these Cirrus/Ambient chip modems mentioned that shows that one FCS error .. eg this one is a 'Swann Flash V.90' (pre V.92 upgradeable): ati1 CD08.55 - 642 (06/30/2000) SERIAL - SPEAKERPHONE 01 - DSP PATCH: 001.65 OK ati4 AMBIENT TECHNOLOGIES INC. ENGINEERING FIRMWARE DEPARTMENT OK ati5 Present, 32K DSP RAM.000 Host I/F: Serial P. Mem. : 008 Bit 001 W.S. D. Mem : 008 Bit 001 W.S. DSP code location = INT ROM OK ati22 Cirrus Logic, Inc. OK > The internal USR seems to correctly see the carrier drop and PPP > hence sees it. However, the 2 external Intels I am experimenting > with on the USB serial ports do not. I suspect thats part of the > reason the DCD is not working. Perhaps incorrect init string or > something with the USB-Serial. Note, I only have the internal USRs > deployed in the field right now Don't know about USB modems. Do USR still use their own chipsets, or what? In any case, they're probably highly tunable and well documented. > Intels > [vpn2]# stty -f /dev/cuaU0 > speed 115200 baud; > lflags: -icanon -isig -iexten -echo > iflags: -icrnl -imaxbel ignbrk -brkint > oflags: -opost -oxtabs > cflags: cs8 -parenb clocal crtscts [..] > live USR internal > [Hastings109]# stty -f /dev/cuad4 > speed 115200 baud; > lflags: -icanon -isig -iexten -echo > iflags: -icrnl -ixon -imaxbel ignbrk -brkint > oflags: -opost -oxtabs > cflags: cs8 -parenb clocal crtscts Only difference here on present cuaa0 is plus oflags: -onlcr but I doubt that matters in presumably transparent data mode. > From the terminal servers perspective it sees > > show m12 > Card Type: LU1674 Chipset > State: ACTIVE > Active Port: S2 > Transmit Rate: 45333 > Receive Rate: 16800 > Connection Type: LAPM/V42BIS > Chars Sent: 3166222761 > Chars Received: 2925103984 > Retrains: 1 > Renegotiations: 6 > > (not sure why, but chats tx/rx are for all calls in the pas 216 days, Ahah. 16800 rx isn't all that hot either. > not just this one). This is in the past 4hours. Perhaps with this > one, I am just better off telling it not to try v.90. Not V.90 full tilt, anyway. If 45333 is sort of usual for this one, then I'd probably try telling it to connect no higher than maybe 41333 or 40000; often about 10-15% or so less than 'normal' can make all the difference. If you can afford the bandwidth, go for slow and solid .. Our Massive Uplink is a V.90 modem, a WebExcel (Rockwell). While just giving it its head, it'd connect at 52000 or 50666, but redial at least twice a day and retrain much more often. Since forcing it to max 49333 - maybe 5 years ago - it holds connections up on average around 10 days, not so infrequently for 3 weeks, best about 47 days from memory. This one's only a few hundred metres from its local exchange, too: ati6 RCV56DPF-PLL L8571A Rev 33.00/33.00 OK at+ms? 12,1,300,49333,1,0,33600 And here's for one of those Cirrus/Ambient/(Intel?) modems, from 12.5km out bush to a V.34B modem, usually makes 31200 or 28800, default dialup: set dial "ABORT BUSY ABORT NO\\sCARRIER ABORT NO\\sANSWER TIMEOUT 10 \ \"\" ATZ OK-ATZ-OK ATE0Q0L1S7=50W3+MS=V34B,1,24000,33600 OK \ \\dATDT\\T TIMEOUT 60 CONNECT \\c \\n" but after lots of rain - we get 90+"/yr - when the line junctions are full of water and the lines are shot, I might try one like this, say: jetstream_24k: set dial "ABORT BUSY ABORT NO\\sCARRIER ABORT NO\\sANSWER TIMEOUT 10 \ \"\" ATZ OK-ATZ-OK ATE0Q0\\\\N2S7=50+MS=11,1,19200,24000 OK \ \\dATDT\\T TIMEOUT 60 CONNECT \\c \\n" That's a V.34B Rockwell. Extreme example, another Rockwell as I recall: gaia_mp: #% from m's very weird phoneline set dial "ABORT BUSY ABORT NO\\sCARRIER ABORT NO\\sANSWER TIMEOUT 10 \ \"\" ATZ OK-ATZ-OK ATE0Q0S7=45+MS=11,1,7200,19200 OK \ \\dATX3\\\\N3DT\\T TIMEOUT 60 CONNECT \\c \\n" Modems on poor lines are a necessary evil, but evil nonetheless .. cheers, Ian From owner-freebsd-net@FreeBSD.ORG Sun May 21 19:28:04 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ABB8716A44A for ; Sun, 21 May 2006 19:28:04 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id F183C43D46 for ; Sun, 21 May 2006 19:28:03 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id A3EA846CC6; Sun, 21 May 2006 15:28:02 -0400 (EDT) Date: Sun, 21 May 2006 20:28:02 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: OxY In-Reply-To: <20060520124702.B8068@fledge.watson.org> Message-ID: <20060521202612.D8068@fledge.watson.org> References: <002a01c67ac7$45354f40$0201a8c0@oxy> <20060520124702.B8068@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, "Jin Guojun \[VFFS\]" Subject: Re: mbuf denied problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 May 2006 19:28:06 -0000 On Sat, 20 May 2006, Robert Watson wrote: > On Fri, 19 May 2006, OxY wrote: > >> i have a problem with mbuf... when all my free memory is gone ( i have 2gb >> ram) and memory allocation looks like this: > > I recently received an informal problem report that there is a problem with > the "denied" statistics gathering, so I think it's likely that's what is > going on here. I'll follow up with the submitter and see if we can't figure > out something more definite. I have received some further information on the problem from the reporter. Could you give this patch a try and see what effect it has? Index: uma_core.c =================================================================== RCS file: /home/ncvs/src/sys/vm/uma_core.c,v retrieving revision 1.136 diff -u -r1.136 uma_core.c --- uma_core.c 11 Feb 2006 19:20:56 -0000 1.136 +++ uma_core.c 21 May 2006 19:25:56 -0000 @@ -2413,8 +2413,7 @@ * If nothing else caught this, we'll just do an internal free. */ zfree_internal: - uma_zfree_internal(zone, item, udata, SKIP_DTOR, ZFREE_STATFAIL | - ZFREE_STATFREE); + uma_zfree_internal(zone, item, udata, SKIP_DTOR, ZFREE_STATFREE); return; } Technically, there has been an allocation failure in this case in identifying a bucket to return the item to, but since the overall case is a free, generating a failure statistics update seems undesirable. Thanks, Robert N M Watson > > Robert N M Watson > >> >> Mem: 30M Active, 1607M Inact, 245M Wired, 84M Cache, 214M Buf, 3028K Free >> Swap: 695M Total, 695M Free >> >> mbuf starts to deny... >> netstat -m show 0 deny till has memory, after that i see this: >> >> Field root# netstat -m >> 629/466/1095 mbufs in use (current/cache/total) >> 512/176/688/65536 mbuf clusters in use (current/cache/total/max) >> 512/133 mbuf+clusters out of packet secondary zone in use (current/cache) >> 0/0/0/0 4k (page size) jumbo clusters in use (current/cache/total/max) >> 0/0/0/0 9k jumbo clusters in use (current/cache/total/max) >> 0/0/0/0 16k jumbo clusters in use (current/cache/total/max) >> 1181K/468K/1649K bytes allocated to network (current/cache/total) >> 7410219/101093/101499 requests for mbufs denied >> (mbufs/clusters/mbuf+clusters) >> 0/0/0 requests for jumbo clusters denied (4k/9k/16k) >> 0/0/0 sfbufs in use (current/peak/max) >> 0 requests for sfbufs denied >> 0 requests for sfbufs delayed >> 25288 requests for I/O initiated by sendfile >> 65 calls to protocol drain routines >> >> this is my sysctl.conf: >> net.inet.tcp.delayed_ack=0 >> net.inet.ip.intr_queue_maxlen=400 >> net.inet.tcp.inflight.enable=0 >> net.route.netisr_maxqlen=512 >> kern.ipc.somaxconn=1024 >> >> should i attach any other conf/log,etc? >> thanks! >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Sun May 21 19:32:55 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F0A016A611 for ; Sun, 21 May 2006 19:32:55 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6550C43D5E for ; Sun, 21 May 2006 19:32:50 +0000 (GMT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost2.sentex.ca (8.13.4P/8.13.4) with ESMTP id k4LJWmSE056319; Sun, 21 May 2006 15:32:48 -0400 (EDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.3P/8.13.3) with ESMTP id k4LJWlSf010982 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 21 May 2006 15:32:48 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.2.3.4.0.20060521152652.06cfce10@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Sun, 21 May 2006 15:32:45 -0400 To: Brian Candler From: Mike Tancsa In-Reply-To: <20060521171521.GA29990@uk.tiscali.com> References: <6.2.3.4.0.20060519110026.05820230@64.7.153.2> <6.2.3.4.0.20060519121104.1126b480@64.7.153.2> <20060521092602.GB20262@uk.tiscali.com> <6.2.3.4.0.20060521104147.081af2d8@64.7.153.2> <20060521171521.GA29990@uk.tiscali.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new Cc: freebsd-net@freebsd.org, Ian Smith Subject: Re: improving transport over lossy links ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 May 2006 19:33:00 -0000 At 01:15 PM 21/05/2006, Brian Candler wrote: >On Sun, May 21, 2006 at 11:09:23AM -0400, Mike Tancsa wrote: > > The internal USR seems to correctly see the carrier drop and PPP > > hence sees it. However, the 2 external Intels I am experimenting > > with on the USB serial ports do not. > >USB-serial adaptors tend to be very broken, unfortunately. I don't know >about under Windows, but under FreeBSD/Linux where drivers seem to be >reverse-engineered, several I've tried don't seem to handshake properly. I >tried two back-to-back to run a local pppd link and it failed (haven't had >time to debug that one) > >IMO there's no substitute for a real COM port. I was hoping to use some of the Soekris 4801s which have limited expandability. I need 2 serial ports for the application and then the modem of course. Under FreeBSD I have used the uftdi based adaptors for OOB console access and they seem to work OK. >A pair of analogue modems will never negotiate v90, This is the modem connected to my terminal server which is connected via PRI. I dont have any analog modem to analog modem setups. ---Mike From owner-freebsd-net@FreeBSD.ORG Sun May 21 19:45:23 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6FA6116A967 for ; Sun, 21 May 2006 19:45:22 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBA3943D45 for ; Sun, 21 May 2006 19:45:21 +0000 (GMT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.13.6/8.13.6) with ESMTP id k4LJjK5u089094; Sun, 21 May 2006 15:45:21 -0400 (EDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.3P/8.13.3) with ESMTP id k4LJjIC9011038 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 21 May 2006 15:45:19 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.2.3.4.0.20060521154316.11bd2598@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Sun, 21 May 2006 15:45:16 -0400 To: bv@wjv.com From: Mike Tancsa In-Reply-To: <20060521154917.GB2053@wjv.com> References: <6.2.3.4.0.20060519110026.05820230@64.7.153.2> <6.2.3.4.0.20060519121104.1126b480@64.7.153.2> <20060521092602.GB20262@uk.tiscali.com> <6.2.3.4.0.20060521104147.081af2d8@64.7.153.2> <20060521154917.GB2053@wjv.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new Cc: freebsd-net@freebsd.org Subject: Re: improving transport over lossy links ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 May 2006 19:45:27 -0000 At 11:49 AM 21/05/2006, Bill Vermillion wrote: >And when performing fax from email - using sendmail incoming and >routing to fax [in the early days of the current 'net before many >people had 'net connections] the MT's were the only ones that >worked with virtually ever target fax machine. Thanks, I have used them in the past. They are certainly quite a bit more expensive than the USRs (3x) but I might be able to justify it if they really do perform a lot better. ---Mike From owner-freebsd-net@FreeBSD.ORG Sun May 21 20:03:45 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F2ED16A834 for ; Sun, 21 May 2006 20:03:45 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5EFAF43D5E for ; Sun, 21 May 2006 20:03:44 +0000 (GMT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.13.6/8.13.6) with ESMTP id k4LK3hCu090267; Sun, 21 May 2006 16:03:43 -0400 (EDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.3P/8.13.3) with ESMTP id k4LK3fYO011116 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 21 May 2006 16:03:41 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.2.3.4.0.20060521154616.11bd1d60@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Sun, 21 May 2006 16:03:39 -0400 To: Ian Smith From: Mike Tancsa In-Reply-To: References: <6.2.3.4.0.20060521104147.081af2d8@64.7.153.2> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new Cc: freebsd-net@freebsd.org, Brian Candler Subject: Re: improving transport over lossy links ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 May 2006 20:03:52 -0000 At 02:53 PM 21/05/2006, Ian Smith wrote: > > Its not so much data corruption of packets on the wire, but > > the modem dropping the connection, retraining and > > renegotiating. When the retrains and re negotiations happen, this > > can cause problems for the VPN as keep alives are missed, tx buffers > > can fill up etc. I have tried a number of modems, the current one > > being U.S. Robotics 56K FAX INT V5.22.70. and I am also trying an > > external Intel at the office > >Yes that's just the problem alright. Just to be clear, you're referring >here only to various calling-in modems, calling to these fixed terminal >server cards, of maybe Lucent origin, right? Hi, Correct. Its always dialing into a terminal server that is connected via PRIs. Usually Lucent PM3, sometimes Cisco 5800s depending on the location they dial from. > > The internal USR seems to correctly see the carrier drop and PPP > > hence sees it. However, the 2 external Intels I am experimenting > > with on the USB serial ports do not. I suspect thats part of the > > reason the DCD is not working. Perhaps incorrect init string or > > something with the USB-Serial. Note, I only have the internal USRs > > deployed in the field right now > >Don't know about USB modems. Do USR still use their own chipsets, or >what? In any case, they're probably highly tunable and well documented. Actually, they are just regular external modems connected to USB to serial adaptors (using the uftdi driver) >Not V.90 full tilt, anyway. If 45333 is sort of usual for this one, >then I'd probably try telling it to connect no higher than maybe 41333 >or 40000; often about 10-15% or so less than 'normal' can make all the >difference. If you can afford the bandwidth, go for slow and solid .. Yes, for sure I will try and lower the speeds a bit, but ultimately I want to deal with situations where the carrier drops and the modem has to redial. The client is willing to put in an extra phone line if it would make the link more reliable. Typically these sites are too remote for other types of transport. I think if I can get mp working with reliable dcd I think that should do it. ---Mike From owner-freebsd-net@FreeBSD.ORG Sun May 21 21:01:21 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA49116A421; Sun, 21 May 2006 21:01:21 +0000 (UTC) (envelope-from pblok@bsd4all.org) Received: from altrade.nijmegen.internl.net (altrade.nijmegen.internl.net [217.149.192.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5317643D55; Sun, 21 May 2006 21:01:19 +0000 (GMT) (envelope-from pblok@bsd4all.org) Received: from mail.bsd4all.org by altrade.nijmegen.internl.net via 113-9.bbned.dsl.internl.net [82.215.9.113] with ESMTP id k4LL1G2b012003 (8.13.2/2.04); Sun, 21 May 2006 23:01:17 +0200 (MET DST) Received: from localhost (localhost.homebrew.bsd4all.org [127.0.0.1]) by mail.bsd4all.org (Postfix) with ESMTP id 5D7EA5CFF; Sun, 21 May 2006 23:01:16 +0200 (CEST) X-Virus-Scanned: amavisd-new at bsd4all.org Received: from mail.bsd4all.org ([127.0.0.1]) by localhost (fwgw.homebrew.bsd4all.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ZyZ0Yt1LrG-Q; Sun, 21 May 2006 23:01:09 +0200 (CEST) Received: from svrpc (svrpc [192.168.1.1]) by mail.bsd4all.org (Postfix) with ESMTP id 3860C5C7E; Sun, 21 May 2006 23:01:09 +0200 (CEST) From: "Peter J. Blok" Organization: HomeBrew To: freebsd-net@freebsd.org Date: Sun, 21 May 2006 23:01:06 +0200 User-Agent: KMail/1.9.1 References: <002a01c67ac7$45354f40$0201a8c0@oxy> <20060520124702.B8068@fledge.watson.org> <20060521202612.D8068@fledge.watson.org> In-Reply-To: <20060521202612.D8068@fledge.watson.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605212301.08355.pblok@bsd4all.org> Cc: "Jin Guojun \[VFFS\]" , Robert Watson , OxY Subject: Re: mbuf denied problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 May 2006 21:01:22 -0000 On Sunday 21 May 2006 21:28, Robert Watson wrote: > On Sat, 20 May 2006, Robert Watson wrote: > > On Fri, 19 May 2006, OxY wrote: > >> i have a problem with mbuf... when all my free memory is gone ( i have > >> 2gb ram) and memory allocation looks like this: > > > > I recently received an informal problem report that there is a problem > > with the "denied" statistics gathering, so I think it's likely that's > > what is going on here. I'll follow up with the submitter and see if we > > can't figure out something more definite. > > I have received some further information on the problem from the reporter. > Could you give this patch a try and see what effect it has? I already had made an identical patch and it worked. This seems to be the problem. > > Index: uma_core.c > =================================================================== > RCS file: /home/ncvs/src/sys/vm/uma_core.c,v > retrieving revision 1.136 > diff -u -r1.136 uma_core.c > --- uma_core.c 11 Feb 2006 19:20:56 -0000 1.136 > +++ uma_core.c 21 May 2006 19:25:56 -0000 > @@ -2413,8 +2413,7 @@ > * If nothing else caught this, we'll just do an internal free. > */ > zfree_internal: > - uma_zfree_internal(zone, item, udata, SKIP_DTOR, ZFREE_STATFAIL | > - ZFREE_STATFREE); > + uma_zfree_internal(zone, item, udata, SKIP_DTOR, ZFREE_STATFREE); > > return; > } > > Technically, there has been an allocation failure in this case in > identifying a bucket to return the item to, but since the overall case is a > free, generating a failure statistics update seems undesirable. > > Thanks, > > Robert N M Watson > > > Robert N M Watson > > > >> Mem: 30M Active, 1607M Inact, 245M Wired, 84M Cache, 214M Buf, 3028K > >> Free Swap: 695M Total, 695M Free > >> > >> mbuf starts to deny... > >> netstat -m show 0 deny till has memory, after that i see this: > >> > >> Field root# netstat -m > >> 629/466/1095 mbufs in use (current/cache/total) > >> 512/176/688/65536 mbuf clusters in use (current/cache/total/max) > >> 512/133 mbuf+clusters out of packet secondary zone in use > >> (current/cache) 0/0/0/0 4k (page size) jumbo clusters in use > >> (current/cache/total/max) 0/0/0/0 9k jumbo clusters in use > >> (current/cache/total/max) > >> 0/0/0/0 16k jumbo clusters in use (current/cache/total/max) > >> 1181K/468K/1649K bytes allocated to network (current/cache/total) > >> 7410219/101093/101499 requests for mbufs denied > >> (mbufs/clusters/mbuf+clusters) > >> 0/0/0 requests for jumbo clusters denied (4k/9k/16k) > >> 0/0/0 sfbufs in use (current/peak/max) > >> 0 requests for sfbufs denied > >> 0 requests for sfbufs delayed > >> 25288 requests for I/O initiated by sendfile > >> 65 calls to protocol drain routines > >> > >> this is my sysctl.conf: > >> net.inet.tcp.delayed_ack=0 > >> net.inet.ip.intr_queue_maxlen=400 > >> net.inet.tcp.inflight.enable=0 > >> net.route.netisr_maxqlen=512 > >> kern.ipc.somaxconn=1024 > >> > >> should i attach any other conf/log,etc? > >> thanks! > >> _______________________________________________ > >> freebsd-net@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-net > >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > > > _______________________________________________ > > freebsd-net@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Sun May 21 23:27:29 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D62F16A4E9 for ; Sun, 21 May 2006 23:27:29 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BC8143D60 for ; Sun, 21 May 2006 23:27:25 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id C0C9F46CCB; Sun, 21 May 2006 19:27:24 -0400 (EDT) Date: Mon, 22 May 2006 00:27:24 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: "Peter J. Blok" In-Reply-To: <200605212301.08355.pblok@bsd4all.org> Message-ID: <20060522002651.C8068@fledge.watson.org> References: <002a01c67ac7$45354f40$0201a8c0@oxy> <20060520124702.B8068@fledge.watson.org> <20060521202612.D8068@fledge.watson.org> <200605212301.08355.pblok@bsd4all.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, "Jin Guojun \[VFFS\]" , OxY Subject: Re: mbuf denied problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 May 2006 23:27:31 -0000 On Sun, 21 May 2006, Peter J. Blok wrote: > On Sunday 21 May 2006 21:28, Robert Watson wrote: >> On Sat, 20 May 2006, Robert Watson wrote: >>> On Fri, 19 May 2006, OxY wrote: >>>> i have a problem with mbuf... when all my free memory is gone ( i have >>>> 2gb ram) and memory allocation looks like this: >>> >>> I recently received an informal problem report that there is a problem >>> with the "denied" statistics gathering, so I think it's likely that's >>> what is going on here. I'll follow up with the submitter and see if we >>> can't figure out something more definite. >> >> I have received some further information on the problem from the reporter. >> Could you give this patch a try and see what effect it has? > I already had made an identical patch and it worked. > > This seems to be the problem. I have committed this patch as uma_core.c:1.137, and will MFC in a couple of weeks assuming no additional problems are reported, and it seems to resolve the issue. Robert N M Watson >> >> Index: uma_core.c >> =================================================================== >> RCS file: /home/ncvs/src/sys/vm/uma_core.c,v >> retrieving revision 1.136 >> diff -u -r1.136 uma_core.c >> --- uma_core.c 11 Feb 2006 19:20:56 -0000 1.136 >> +++ uma_core.c 21 May 2006 19:25:56 -0000 >> @@ -2413,8 +2413,7 @@ >> * If nothing else caught this, we'll just do an internal free. >> */ >> zfree_internal: >> - uma_zfree_internal(zone, item, udata, SKIP_DTOR, ZFREE_STATFAIL | >> - ZFREE_STATFREE); >> + uma_zfree_internal(zone, item, udata, SKIP_DTOR, ZFREE_STATFREE); >> >> return; >> } >> >> Technically, there has been an allocation failure in this case in >> identifying a bucket to return the item to, but since the overall case is a >> free, generating a failure statistics update seems undesirable. >> >> Thanks, >> >> Robert N M Watson >> >>> Robert N M Watson >>> >>>> Mem: 30M Active, 1607M Inact, 245M Wired, 84M Cache, 214M Buf, 3028K >>>> Free Swap: 695M Total, 695M Free >>>> >>>> mbuf starts to deny... >>>> netstat -m show 0 deny till has memory, after that i see this: >>>> >>>> Field root# netstat -m >>>> 629/466/1095 mbufs in use (current/cache/total) >>>> 512/176/688/65536 mbuf clusters in use (current/cache/total/max) >>>> 512/133 mbuf+clusters out of packet secondary zone in use >>>> (current/cache) 0/0/0/0 4k (page size) jumbo clusters in use >>>> (current/cache/total/max) 0/0/0/0 9k jumbo clusters in use >>>> (current/cache/total/max) >>>> 0/0/0/0 16k jumbo clusters in use (current/cache/total/max) >>>> 1181K/468K/1649K bytes allocated to network (current/cache/total) >>>> 7410219/101093/101499 requests for mbufs denied >>>> (mbufs/clusters/mbuf+clusters) >>>> 0/0/0 requests for jumbo clusters denied (4k/9k/16k) >>>> 0/0/0 sfbufs in use (current/peak/max) >>>> 0 requests for sfbufs denied >>>> 0 requests for sfbufs delayed >>>> 25288 requests for I/O initiated by sendfile >>>> 65 calls to protocol drain routines >>>> >>>> this is my sysctl.conf: >>>> net.inet.tcp.delayed_ack=0 >>>> net.inet.ip.intr_queue_maxlen=400 >>>> net.inet.tcp.inflight.enable=0 >>>> net.route.netisr_maxqlen=512 >>>> kern.ipc.somaxconn=1024 >>>> >>>> should i attach any other conf/log,etc? >>>> thanks! >>>> _______________________________________________ >>>> freebsd-net@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-net >>>> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >>> >>> _______________________________________________ >>> freebsd-net@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-net >>> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >> >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Mon May 22 09:17:07 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3DD8A16A45E for ; Mon, 22 May 2006 09:17:07 +0000 (UTC) (envelope-from eddy+public+spam@noc.everquick.net) Received: from a.mx.ict1.everquick.net (a.mx.ict1.everquick.net [204.10.191.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 34EB743D53 for ; Mon, 22 May 2006 09:17:04 +0000 (GMT) (envelope-from eddy+public+spam@noc.everquick.net) Received: from pop.ict1.everquick.net (localhost [127.0.0.1]) by a.mx.ict1.everquick.net (8.12.10/8.12.10) with ESMTP id k4M9H4Jk015546 for ; Mon, 22 May 2006 09:17:04 GMT X-Everquick-No-Abuse-1: Report any email abuse to or X-Everquick-No-Abuse-2: call +1 (785) 865-5885. Please be sure to reference X-Everquick-No-Abuse-3: the Message-Id and include GMT timestamps. Received: from localhost (eddy@localhost) by pop.ict1.everquick.net (8.13.3/8.13.3/Submit) with ESMTP id k4M9H3nE015543 for ; Mon, 22 May 2006 09:17:03 GMT X-Authentication-Warning: pop.ict1.everquick.net: eddy owned process doing -bs Date: Mon, 22 May 2006 09:17:02 +0000 (GMT) From: "Edward B. DREGER" X-X-Sender: eddy@pop.ict1.everquick.net To: freebsd-net@freebsd.org In-Reply-To: <20060521171521.GA29990@uk.tiscali.com> Message-ID: References: <6.2.3.4.0.20060519110026.05820230@64.7.153.2> <6.2.3.4.0.20060519121104.1126b480@64.7.153.2> <20060521092602.GB20262@uk.tiscali.com> <6.2.3.4.0.20060521104147.081af2d8@64.7.153.2> <20060521171521.GA29990@uk.tiscali.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: improving transport over lossy links ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 09:17:08 -0000 BC> Date: Sun, 21 May 2006 18:15:21 +0100 BC> From: Brian Candler BC> [I]n theory you might be able to find a modem which is physically BC> connected as ISDN BRI but which supports v90 analogue modulation) Ascend MAX 1800 or MAX 3000 Eddy -- Everquick Internet - http://www.everquick.net/ A division of Brotsman & Dreger, Inc. - http://www.brotsman.com/ Bandwidth, consulting, e-commerce, hosting, and network building Phone: +1 785 865 5885 Lawrence and [inter]national Phone: +1 316 794 8922 Wichita ________________________________________________________________________ DO NOT send mail to the following addresses: davidc@brics.com -*- jfconmaapaq@intc.net -*- sam@everquick.net Sending mail to spambait addresses is a great way to get blocked. Ditto for broken OOO autoresponders and foolish AV software backscatter. From owner-freebsd-net@FreeBSD.ORG Mon May 22 09:41:08 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9727616A424; Mon, 22 May 2006 09:41:08 +0000 (UTC) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0AB5143D45; Mon, 22 May 2006 09:41:02 +0000 (GMT) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from impact.jinmei.org (unknown [3ffe:501:100f:1010:4fe:37e7:871c:4a5c]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id BF8FB15218; Mon, 22 May 2006 18:40:59 +0900 (JST) Date: Mon, 22 May 2006 18:40:48 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: Ed Schouten , "Bruce A. Mah" In-Reply-To: References: <20060506172742.GM15353@hoeg.nl> <445EC341.60406@freebsd.org> <20060508065841.GN15353@hoeg.nl> User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: FreeBSD Net Subject: Re: nd6_lookup prints bogus messages with point to point devices X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 09:41:08 -0000 >>>>> On Thu, 18 May 2006 01:35:35 +0900, >>>>> JINMEI Tatuya said: >> I'm seeing the messages on the machine in Eindhoven (running RELENG_6 >> from a few days/weeks ago), but they also show up on my HEAD machine at >> home. Below is the output of `ifconfig gif0` on my machine at home: >> | gif0: flags=8051 mtu 1280 >> | tunnel inet 83.181.147.170 --> 193.109.122.244 >> | inet6 fe80::202:a5ff:fe58:4927%gif0 prefixlen 64 scopeid 0x7 >> | inet6 2001:7b8:310::1 --> 2001:7b8:2ff:a4::1 prefixlen 128 >> As far as I know, the latest FreeBSD releases show an error message when >> assigning an address with a non-128 prefixlen. > Sorry for not responding sooner, but I think I've figured out the > problem. I'm now testing a local patch to this problem, and will > report the details once I confirm the behavior. Could you try the patch attached below? It's for 6.1-RELEASE, but I guess it's pretty easy to apply to CURRENT. The essential reason of this problem is that the latest kernel regards the destination address of a point-to-point interface as a "neighbor" wrt Neighbor Discovery while a neighbor cache entry is not created on configuring the interface with the addresses. I believe it makes sense to treat the destination address as a neighbor, so the fix is to make sure that the cache entry is created when the interface is configured. Thanks, JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp Index: in6.c =================================================================== RCS file: /home/ncvs/src/sys/netinet6/in6.c,v retrieving revision 1.51.2.8 diff -u -r1.51.2.8 in6.c --- in6.c 9 Mar 2006 11:59:03 -0000 1.51.2.8 +++ in6.c 18 May 2006 05:27:07 -0000 @@ -1720,20 +1720,55 @@ /* we could do in(6)_socktrim here, but just omit it at this moment. */ + if (newhost && nd6_need_cache(ifp) != 0) { + /* set the rtrequest function to create llinfo */ + ia->ia_ifa.ifa_rtrequest = nd6_rtrequest; + } + /* * Special case: * If a new destination address is specified for a point-to-point * interface, install a route to the destination as an interface - * direct route. + * direct route. In addition, if the link is expected to have neighbor + * cache entries, specify RTF_LLINFO so that a cache entry for the + * destination address will be created. + * created * XXX: the logic below rejects assigning multiple addresses on a p2p - * interface that share a same destination. + * interface that share the same destination. */ plen = in6_mask2len(&ia->ia_prefixmask.sin6_addr, NULL); /* XXX */ if (!(ia->ia_flags & IFA_ROUTE) && plen == 128 && ia->ia_dstaddr.sin6_family == AF_INET6) { - if ((error = rtinit(&(ia->ia_ifa), (int)RTM_ADD, - RTF_UP | RTF_HOST)) != 0) + int rtflags = RTF_UP | RTF_HOST; + struct rtentry *rt = NULL, **rtp = NULL; + + if (nd6_need_cache(ifp) != 0) { + rtflags |= RTF_LLINFO; + rtp = &rt; + } + + error = rtrequest(RTM_ADD, (struct sockaddr *)&ia->ia_dstaddr, + (struct sockaddr *)&ia->ia_addr, + (struct sockaddr *)&ia->ia_prefixmask, + ia->ia_flags | rtflags, rtp); + if (error != 0) return (error); + if (rt != NULL) { + struct llinfo_nd6 *ln; + + RT_LOCK(rt); + ln = (struct llinfo_nd6 *)rt->rt_llinfo; + if (ln != NULL) { + /* + * Set the state to STALE because we don't + * have to perform address resolution on this + * link. + */ + ln->ln_state = ND6_LLINFO_STALE; + } + RT_REMREF(rt); + RT_UNLOCK(rt); + } ia->ia_flags |= IFA_ROUTE; } if (plen < 128) { @@ -1744,11 +1779,8 @@ } /* Add ownaddr as loopback rtentry, if necessary (ex. on p2p link). */ - if (newhost) { - /* set the rtrequest function to create llinfo */ - ia->ia_ifa.ifa_rtrequest = nd6_rtrequest; + if (newhost) in6_ifaddloop(&(ia->ia_ifa)); - } return (error); } Index: nd6.c =================================================================== RCS file: /home/ncvs/src/sys/netinet6/nd6.c,v retrieving revision 1.48.2.12 diff -u -r1.48.2.12 nd6.c --- nd6.c 29 Mar 2006 21:05:11 -0000 1.48.2.12 +++ nd6.c 18 May 2006 05:27:08 -0000 @@ -512,6 +512,19 @@ ln->ln_asked++; nd6_llinfo_settimer(ln, (long)ndi->retrans * hz / 1000); nd6_ns_output(ifp, dst, dst, ln, 0); + } else if (rt->rt_ifa != NULL && + rt->rt_ifa->ifa_addr->sa_family == AF_INET6 && + (((struct in6_ifaddr *)rt->rt_ifa)->ia_flags & IFA_ROUTE)) { + /* + * This is an unreachable neighbor whose address is + * specified as the destination of a p2p interface + * (see in6_ifinit()). We should not free the entry + * since this is sort of a "static" entry generated + * via interface address configuration. + */ + ln->ln_asked = 0; + ln->ln_expire = 0; /* make it permanent */ + ln->ln_state = ND6_LLINFO_STALE; } else { (void)nd6_free(rt, 0); ln = NULL; From owner-freebsd-net@FreeBSD.ORG Mon May 22 10:57:23 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 28E7116A42C; Mon, 22 May 2006 10:57:23 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [83.98.131.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id 481F643D82; Mon, 22 May 2006 10:57:08 +0000 (GMT) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id 7B60617082; Mon, 22 May 2006 12:57:07 +0200 (CEST) Date: Mon, 22 May 2006 12:57:07 +0200 From: Ed Schouten To: JINMEI Tatuya Message-ID: <20060522105707.GM63357@hoeg.nl> References: <20060506172742.GM15353@hoeg.nl> <445EC341.60406@freebsd.org> <20060508065841.GN15353@hoeg.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="kaF1vgn83Aa7CiXN" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Cc: "Bruce A. Mah" , FreeBSD Net Subject: Re: nd6_lookup prints bogus messages with point to point devices X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 10:57:23 -0000 --kaF1vgn83Aa7CiXN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * JINMEI Tatuya wrote: > Could you try the patch attached below? It's for 6.1-RELEASE, but I > guess it's pretty easy to apply to CURRENT. I've applied it on my CURRENT box at home and it works. Hooray! :) Yours, --=20 Ed Schouten WWW: http://g-rave.nl/ --kaF1vgn83Aa7CiXN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEcZkD52SDGA2eCwURAvKCAJ9G3bT7S9WsRWqV4oxUAXR5I7Y0hACeKgOv rboqT2j5TY93f0FhGt+WgYA= =3ffI -----END PGP SIGNATURE----- --kaF1vgn83Aa7CiXN-- From owner-freebsd-net@FreeBSD.ORG Mon May 22 11:02:56 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A5B216A5AC for ; Mon, 22 May 2006 11:02:56 +0000 (UTC) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B03C443D4C for ; Mon, 22 May 2006 11:02:55 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k4MB2tH3034936 for ; Mon, 22 May 2006 11:02:55 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k4MB2sMB034932 for freebsd-net@freebsd.org; Mon, 22 May 2006 11:02:54 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 22 May 2006 11:02:54 GMT Message-Id: <200605221102.k4MB2sMB034932@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-net@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 11:03:00 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2006/01/30] kern/92552 net A serious bug in most network drivers fro a [2006/02/12] kern/93220 net [inet6] nd6_lookup: failed to add route f 2 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/07/11] kern/54383 net [nfs] [patch] NFS root configurations wit o [2006/04/03] kern/95267 net packet drops periodically appear 2 problems total. From owner-freebsd-net@FreeBSD.ORG Mon May 22 11:50:23 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3088216A602 for ; Mon, 22 May 2006 11:50:23 +0000 (UTC) (envelope-from marko.lerota@optima-telekom.hr) Received: from redcloud.optima-telekom.hr (tirnanog.iskon.hr [213.191.139.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DAB043D55 for ; Mon, 22 May 2006 11:50:12 +0000 (GMT) (envelope-from marko.lerota@optima-telekom.hr) Received: (qmail 7192 invoked by uid 1001); 22 May 2006 11:50:24 -0000 To: freebsd-net@freebsd.org Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEWgnbRLVpRNVY9jMRPh s21jSlEyNVX45Mv4zI+sbUclFAtMVpT8V0lFAAACZ0lEQVR4nG3Tv2vbQBQHcFMogWyeNeVK BLXGl5j6xnABOaNTuXFGmWpwtw519yj4soW6AatT4GKD3+aDZrl/rt/Tr9qlGiz7Pn7v3bsf HVc/NrIiSfElqH53GgijcCqzk/+AmBF5cN0DsFlIRGMh/oHuqxkTM6VlzB4EoZEs2aSZOASb EQJYZpweQshE697GTDndBXtgp9LIT9+OpDGHEfb9knk+nx+jfN1JCVZMCl6XwFm0a2EXztZD 3s4fj47ZbKI2VeBmJImeEfGLJ+M9sDPilX7IB5rN6sdfcGhuoHU+LC4nxfnI7YOJtdb95Gb+ fbgJ2uJ2ZgaA++f5ZzBqNCCYfMTd5q0BfBVNqm7I8gUjQ+YtXotRW6PH9AEj+dKs/KuNQAl5 o/NY+QkonW8aQAl0oXMYPvRiXIM4pRJifbXytnhTA8alBx/jefG2ar3DBlt34/PXz9M+nMVN iNaPUdCApJc2ItejOmLGoK1qQLV9pJmXBnL10DYoBA5aHNfj8ZNwZa5O4CzgTJeilKJmrQJs IHIt1/7/Sg2p3iq/Hz0/5W05rq4M9aN2B5FLohUP4ylVyfxhEIjAs8J4PhIJ9U+CEroogib5 BXAf7bB4vkfAzgPFt1tM9sJZAOH+lCexhwswuNtim4QTZdokqo4o89LkH7V6iFxICeqfp+Wh fmUuGPunLj2Meti6Cn4DjJ/UReROqR+aqawAi/JkfgKE64rrfkhjU8MtT8ivR4S5n6Yo08A7 HvgAlHDWRSGlNSDxwK9HtXy4FS2I60EdUIJM+Ut9OZNJG4CpbEQW1VBQoQoPuBw2EVa4P0u0 TgzQF+VoAAAAAElFTkSuQmCC Organization: Unix Users - Fanatics Dept. X-Request-PGP: X-GNUPG-Fingerprint: CF5E 6862 2777 A471 5D2E 0015 8DA6 D56D 17E5 2A51 From: Marko Lerota Date: Mon, 22 May 2006 13:50:24 +0200 Message-ID: <861wum8ein.fsf@redcloud.local> User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.5-b26 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: nfsd and CPU/performance problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 11:50:26 -0000 My nfs server is chewing to much CPU even when nobody writes to nfs partition. The clients are RHES4. I don't know much about nfs but I followed the steps in handbook. Look: last pid: 43588; load averages: 0.46, 0.77, 0.81 28 processes: 1 running, 27 sleeping CPU states: 0.0% user, 0.0% nice, 2.4% system, 0.2% interrupt, 97.4% idle Mem: 9520K Active, 204M Inact, 142M Wired, 12K Cache, 112M Buf, 1648M Free Swap: 4071M Total, 4071M Free PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 429 root 1 4 0 1204K 820K - 0 581:42 13.48% nfsd 430 root 1 4 0 1204K 820K - 0 10:37 0.00% nfsd Here is the config rc.conf ####################### rpcbind_enable="YES" portmap_enable="YES" nfs_server_enable="YES" nfs_server_flags="-u -t -n 4 -h 10.3.11.43" mountd_flags="-r" nfs_client_enable="YES" ####################### /etc/exports ########################################### /nfs -alldirs 10.3.12.71 10.3.12.72 ########################################### -- One cannot sell the earth upon which the people walk Tacunka Witco From owner-freebsd-net@FreeBSD.ORG Mon May 22 11:57:23 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DEAA16A4EA for ; Mon, 22 May 2006 11:57:23 +0000 (UTC) (envelope-from nitro@263.net) Received: from smtp.263.net (263.net.cn [211.150.96.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 29C1643D58 for ; Mon, 22 May 2006 11:57:21 +0000 (GMT) (envelope-from nitro@263.net) Received: from intron.ac (unknown [127.0.0.1]) by smtp.263.net (Postfix) with SMTP id 15918F1590 for ; Mon, 22 May 2006 19:57:22 +0800 (CST) X-KSVirus-check: 0 From: mag@intron.ac To: freebsd-net@freebsd.org Date: Mon, 22 May 2006 19:51:33 +0800 Mime-Version: 1.0 Content-Type: text/plain; charset="gb2312"; format=flowed Content-Transfer-Encoding: 7bit Message-Id: <20060522115722.15918F1590@smtp.263.net> Subject: How to Quicken TCP Re-transmission? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 11:57:26 -0000 Hi, I want to transmit data between host A and host B. The link between these two hosts is really bad: PING reports 30% packet loss and about 60 ms return delay. This means if timed out for 1 second, the data must have been lost. I keep "net.inet.tcp.rexmit_min" and "net.inet.tcp.rexmit_slop" untouched. But TCPDUMP tells me that if some data are lost, re-transmission will be done 64 seconds after last transmission! How to quicken TCP re-transmission? How to tune "net.inet.tcp.rexmit_min" and "net.inet.tcp.rexmit_slop"? ------------------------------------------------------------------------ From Beijing, China From owner-freebsd-net@FreeBSD.ORG Mon May 22 12:51:11 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0231F16A7B8 for ; Mon, 22 May 2006 12:51:11 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FBF543D77 for ; Mon, 22 May 2006 12:51:07 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 057A25DAC; Mon, 22 May 2006 08:51:07 -0400 (EDT) X-Virus-Scanned: amavisd-new at codefab.com Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rZJlgTFiGyrE; Mon, 22 May 2006 08:51:04 -0400 (EDT) Received: from [192.168.1.251] (pool-68-160-242-211.ny325.east.verizon.net [68.160.242.211]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id 7A92D5D0B; Mon, 22 May 2006 08:51:04 -0400 (EDT) Message-ID: <4471B3B4.30908@mac.com> Date: Mon, 22 May 2006 08:51:00 -0400 From: Chuck Swiger User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: mag@intron.ac References: <20060522115722.15918F1590@smtp.263.net> In-Reply-To: <20060522115722.15918F1590@smtp.263.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: How to Quicken TCP Re-transmission? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 12:51:13 -0000 mag@intron.ac wrote: > Hi, > I want to transmit data between host A and host B. The link between > these two hosts is really bad: PING reports 30% packet loss and about > 60 ms return delay. OK. > This means if timed out for 1 second, the data must have been lost. Well, no, that's not necessarily the case. It's possible for traffic to get delayed (perhaps a router is sending some traffic the wrong way, causing a loop or non-ideal path) for longer. Try turning on the SACK TCP option... -- -Chuck From owner-freebsd-net@FreeBSD.ORG Mon May 22 13:06:53 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 42D0416A5DE for ; Mon, 22 May 2006 13:06:53 +0000 (UTC) (envelope-from b.candler@pobox.com) Received: from proof.pobox.com (proof.pobox.com [207.106.133.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id A77FD43D5E for ; Mon, 22 May 2006 13:06:52 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from proof (localhost [127.0.0.1]) by proof.pobox.com (Postfix) with ESMTP id E755224E13; Mon, 22 May 2006 09:06:50 -0400 (EDT) Received: from mappit.local.linnet.org (212-74-113-67.static.dsl.as9105.com [212.74.113.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by proof.sasl.smtp.pobox.com (Postfix) with ESMTP id B64D44D784; Mon, 22 May 2006 09:06:49 -0400 (EDT) Received: from lists by mappit.local.linnet.org with local (Exim 4.61 (FreeBSD)) (envelope-from ) id 1FiA7U-0008eq-Ge; Mon, 22 May 2006 14:06:48 +0100 Date: Mon, 22 May 2006 14:06:48 +0100 From: Brian Candler To: mag@intron.ac Message-ID: <20060522130648.GB33204@uk.tiscali.com> References: <20060522115722.15918F1590@smtp.263.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060522115722.15918F1590@smtp.263.net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@freebsd.org Subject: Re: How to Quicken TCP Re-transmission? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 13:06:54 -0000 On Mon, May 22, 2006 at 07:51:33PM +0800, mag@intron.ac wrote: > I want to transmit data between host A and host B. The link between > these two hosts is really bad: PING reports 30% packet loss How big are the pings? Try ping -c100 -s1472 x.x.x.x to send 1500-byte pings (20 bytes IP header + 8 bytes ICMP header + 1472 bytes padding). This will give you a more realistic indication of packet loss for TCP transfers than the small pings you get by default. TCP performs really, really badly on packet loss over 5%. I don't think that any amount of tweaking will cope with 30% packet loss. Perhaps a mechanism which sends each packet 3 times would work, but then tripling the load on your link will increase your packet loss even more, perhaps leading to total collapse. Regards, Brian. From owner-freebsd-net@FreeBSD.ORG Mon May 22 13:39:34 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E672716A423 for ; Mon, 22 May 2006 13:39:34 +0000 (UTC) (envelope-from lists@yazzy.org) Received: from mx1.yazzy.org (mx1.yazzy.org [84.247.145.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8596C43D45 for ; Mon, 22 May 2006 13:39:34 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from mail.witelcom.com ([84.247.144.144] helo=marcin) by mx1.yazzy.org with esmtps (TLSv1:AES256-SHA:256) (YazzY.org) id 1FiAcg-0001jp-0e; Mon, 22 May 2006 15:39:02 +0200 Date: Mon, 22 May 2006 15:39:32 +0200 From: Marcin Jessa To: mag@intron.ac Message-ID: <20060522153932.1c789788@marcin> In-Reply-To: <20060522115722.15918F1590@smtp.263.net> References: <20060522115722.15918F1590@smtp.263.net> Organization: YazzY.org X-Mailer: Sylpheed-Claws 2.2.0 (GTK+ 2.8.12; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Score: -2.5 (--) Cc: freebsd-net@freebsd.org Subject: Re: How to Quicken TCP Re-transmission? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 13:39:35 -0000 On Mon, 22 May 2006 19:51:33 +0800 mag@intron.ac wrote: > Hi, > I want to transmit data between host A and host B. The link > between these two hosts is really bad: PING reports 30% packet loss > and about 60 ms return delay. This means if timed out for 1 second, > the data must have been lost. > I keep "net.inet.tcp.rexmit_min" and "net.inet.tcp.rexmit_slop" > untouched. But TCPDUMP tells me that if some data are lost, > re-transmission will be done 64 seconds after last transmission! > How to quicken TCP re-transmission? > How to tune "net.inet.tcp.rexmit_min" and > "net.inet.tcp.rexmit_slop"? You can take a look at SCPS - http://www.scps.org/ Their protocol is used on lossy links with big latency and packet loss (such as satellites) and overcomes shortcomings of TCP. It works with divert mechanism of FreeBSD and I ported the tap device part as well to both NetBSD / FreeBSD (experimental). Cheers, Marcin. From owner-freebsd-net@FreeBSD.ORG Mon May 22 13:55:49 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C4D5616A77D for ; Mon, 22 May 2006 13:55:49 +0000 (UTC) (envelope-from jblanton@masaka.cs.ohiou.edu) Received: from ms-smtp-01.ohiordc.rr.com (ms-smtp-01.ohiordc.rr.com [65.24.5.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F25A43D4C for ; Mon, 22 May 2006 13:55:48 +0000 (GMT) (envelope-from jblanton@masaka.cs.ohiou.edu) Received: from mauser.ipx.ath.cx (cpe-24-165-123-44.cinci.res.rr.com [24.165.123.44]) by ms-smtp-01.ohiordc.rr.com (8.13.6/8.13.6) with ESMTP id k4MDtgFh001835; Mon, 22 May 2006 09:55:42 -0400 (EDT) Received: by mauser.ipx.ath.cx (Postfix, from userid 500) id 4CF7A102819; Mon, 22 May 2006 09:55:42 -0400 (EDT) Date: Mon, 22 May 2006 09:55:42 -0400 From: Joshua Blanton To: mag@intron.ac Message-ID: <20060522135542.GC22140@mauser.ipx.ath.cx> Mail-Followup-To: mag@intron.ac, freebsd-net@freebsd.org References: <20060522115722.15918F1590@smtp.263.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CblX+4bnyfN0pR09" Content-Disposition: inline In-Reply-To: <20060522115722.15918F1590@smtp.263.net> X-Operating-System: Linux User-Agent: Mutt/1.5.9i X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: freebsd-net@freebsd.org Subject: Re: How to Quicken TCP Re-transmission? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Joshua Blanton List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 13:55:52 -0000 --CblX+4bnyfN0pR09 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline mag@intron.ac wrote: > I want to transmit data between host A and host B. The link between > these two hosts is really bad: PING reports 30% packet loss and about > 60 ms return delay. This means if timed out for 1 second, the data must > have been lost. > I keep "net.inet.tcp.rexmit_min" and "net.inet.tcp.rexmit_slop" > untouched. But TCPDUMP tells me that if some data are lost, > re-transmission will be done 64 seconds after last transmission! > How to quicken TCP re-transmission? > How to tune "net.inet.tcp.rexmit_min" and "net.inet.tcp.rexmit_slop"? Is this a point-to-point link between the two hosts, or is there a network between them? If there is a network, you can't necessarily provide a hard bound on the upper limit of RTT (although if it's a small intranet of some sort, it may be reasonable to compute one)... If it's a point-to-point link, that's a whole different story. :-) I'm assuming, from your email, that the loss is corruption-based and not congestion-based - is this true? If it is a point-to-point link, SCPS (as previously mentioned) might provide the sort of solution you need. If it's not a point-to-point link, you'll just have to live with really crappy performance - as another poster said, TCP doesn't like packet loss at all. If there's a point-to-point link, but you need to be able to get out beyond the next hop, you might consider configuring a proxy on either end of the link. This proxy would have to terminate all connections on either side, and use a less-corruption-affected protocol across the bad link. One thing to note - you probably don't want to tune the *minimum* retransmission timeout, but rather the *maximum* retransmission timeout... What's happening is that your TCP senders are not getting reliable RTT samples, and so every timeout is doubling the RTT estimate until it's finally bounded by 64s. If you lower that maximum bound, you can reduce the penalty of timeouts - but with a 30% loss rate there's *no* way you'll ever get TCP to do anything other than timeout every other packet. --jtb --CblX+4bnyfN0pR09 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFEccLe1dp8qWK2G7QRAkaCAJ9z9bt0RAdkRZQen3i/c1s3qXpbfgCg9PCi X6EZXdvniooSh0D5ZJLsffs= =VvKo -----END PGP SIGNATURE----- --CblX+4bnyfN0pR09-- From owner-freebsd-net@FreeBSD.ORG Mon May 22 14:14:42 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E68416AB32 for ; Mon, 22 May 2006 14:14:42 +0000 (UTC) (envelope-from mallman@icir.org) Received: from wyvern.icir.org (wyvern.icir.org [192.150.187.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1570643D8A for ; Mon, 22 May 2006 14:14:01 +0000 (GMT) (envelope-from mallman@icir.org) Received: from guns.icir.org (adsl-69-222-35-58.dsl.bcvloh.ameritech.net [69.222.35.58]) by wyvern.icir.org (8.12.11/8.12.11) with ESMTP id k4MEDDep099874; Mon, 22 May 2006 07:13:13 -0700 (PDT) (envelope-from mallman@guns.icir.org) Received: from guns.icir.org (localhost [127.0.0.1]) by guns.icir.org (Postfix) with ESMTP id 5E1D477AF5C; Mon, 22 May 2006 10:13:12 -0400 (EDT) To: Marcin Jessa From: Mark Allman In-Reply-To: <20060522153932.1c789788@marcin> Organization: ICSI Center for Internet Research (ICIR) Song-of-the-Day: Jungle Love MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=_bOundary"; micalg=pgp-sha1; protocol="application/pgp-signature" Date: Mon, 22 May 2006 10:13:12 -0400 Sender: mallman@icir.org Message-Id: <20060522141312.5E1D477AF5C@guns.icir.org> Cc: freebsd-net@freebsd.org, mag@intron.ac Subject: Re: How to Quicken TCP Re-transmission? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mallman@icir.org List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 14:14:47 -0000 --=_bOundary Content-Type: text/plain Content-Disposition: inline > You can take a look at SCPS - http://www.scps.org/ Their protocol is > used on lossy links with big latency and packet loss (such as > satellites) and overcomes shortcomings of TCP. It works with divert > mechanism of FreeBSD and I ported the tap device part as well to both > NetBSD / FreeBSD (experimental). It's not clear to me that this is going to help. Fundamentally, TCP and SCTP share the same congestion control response. At 30% packet loss SCTP ought to be as unusable as TCP. Both consider losses to be indications of network congestion. SCTP does have some things built-in that need to be added onto TCP (e.g., SACK). So, we could expect more consistent behavior from SCTP across implementations and platforms. But, in the end the performance of both is proportional to 1/sqrt(p) where p is the loss rate. So, as the loss rate increases performance decreases. At 30% you're essentially cooked no matter which you use. allman --=_bOundary Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEccb4WyrrWs4yIs4RAtCyAKCEVBItiSlfoilRuTjJcF/onorQ+wCeJVng SvLrSgZHNA7rWxeRg9R/g64= =lh/s -----END PGP SIGNATURE----- --=_bOundary-- From owner-freebsd-net@FreeBSD.ORG Mon May 22 14:22:12 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C6C716AB38 for ; Mon, 22 May 2006 14:22:12 +0000 (UTC) (envelope-from mallman@icir.org) Received: from wyvern.icir.org (wyvern.icir.org [192.150.187.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id C50D543D5A for ; Mon, 22 May 2006 14:22:11 +0000 (GMT) (envelope-from mallman@icir.org) Received: from guns.icir.org (adsl-69-222-35-58.dsl.bcvloh.ameritech.net [69.222.35.58]) by wyvern.icir.org (8.12.11/8.12.11) with ESMTP id k4MEMBnw000194; Mon, 22 May 2006 07:22:11 -0700 (PDT) (envelope-from mallman@guns.icir.org) Received: from guns.icir.org (localhost [127.0.0.1]) by guns.icir.org (Postfix) with ESMTP id 2A8FF77AF5C; Mon, 22 May 2006 10:22:10 -0400 (EDT) To: Marcin Jessa , mag@intron.ac, freebsd-net@freebsd.org From: Mark Allman In-Reply-To: Organization: ICSI Center for Internet Research (ICIR) Song-of-the-Day: Jungle Love MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=_bOundary"; micalg=pgp-sha1; protocol="application/pgp-signature" Date: Mon, 22 May 2006 10:22:10 -0400 Sender: mallman@icir.org Message-Id: <20060522142210.2A8FF77AF5C@guns.icir.org> Cc: Subject: Re: How to Quicken TCP Re-transmission? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mallman@icir.org List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 14:22:14 -0000 --=_bOundary Content-Type: text/plain Content-Disposition: inline > > > You can take a look at SCPS - http://www.scps.org/ Their protocol is > > used on lossy links with big latency and packet loss (such as > > satellites) and overcomes shortcomings of TCP. It works with divert > > mechanism of FreeBSD and I ported the tap device part as well to both > > NetBSD / FreeBSD (experimental). > > It's not clear to me that this is going to help. Fundamentally, TCP and > SCTP share the same congestion control response. At 30% packet loss > SCTP ought to be as unusable as TCP. Both consider losses to be > indications of network congestion. > > SCTP does have some things built-in that need to be added onto TCP > (e.g., SACK). So, we could expect more consistent behavior from SCTP > across implementations and platforms. But, in the end the performance > of both is proportional to 1/sqrt(p) where p is the loss rate. So, as > the loss rate increases performance decreases. At 30% you're > essentially cooked no matter which you use. Ugh... Monday mornings... You'll note that what I quoted was about "SCPS" and what I wrote about was "SCTP". These are different. Ignore me. allman --=_bOundary Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEcckSWyrrWs4yIs4RAnr/AJ0UfzYCV1aI+b8LtqLk+H4G2GvV3gCcDr/r Tp7JKez5J8y8i66/u+beXEA= =USBM -----END PGP SIGNATURE----- --=_bOundary-- From owner-freebsd-net@FreeBSD.ORG Mon May 22 15:18:18 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A86BB16B3EC for ; Mon, 22 May 2006 15:18:18 +0000 (UTC) (envelope-from nitro@263.net) Received: from smtp.263.net (263.net.cn [211.150.96.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B68B143D62 for ; Mon, 22 May 2006 15:18:17 +0000 (GMT) (envelope-from nitro@263.net) Received: from intron.ac (unknown [127.0.0.1]) by smtp.263.net (Postfix) with SMTP id 8ACD0F11A3 for ; Mon, 22 May 2006 23:18:22 +0800 (CST) X-KSVirus-check: 0 References: <20060522115722.15918F1590@smtp.263.net> <20060522135542.GC22140@mauser.ipx.ath.cx> In-Reply-To: <20060522135542.GC22140@mauser.ipx.ath.cx> From: mag@intron.ac To: Joshua Blanton , Marcin Jessa , Brian Candler , Chuck Swiger Date: Mon, 22 May 2006 23:14:58 +0800 Mime-Version: 1.0 Content-Type: text/plain; charset="gb2312"; format=flowed Content-Transfer-Encoding: 7bit Message-Id: <20060522151822.8ACD0F11A3@smtp.263.net> Cc: freebsd-net@freebsd.org Subject: Re: How to Quicken TCP Re-transmission? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 15:18:27 -0000 Thank you for your answers, Joshua, Marcin, Brian and Chuck. Actually, I want to configure APACHE to distribute files (several mega bytes large each) to any Internet visitor. My server (host A) is served by a non-profitable Internet operator in China. But most of Chinese Internet users (host B) are served by two commercial Internet operators. Between the non-profitable Internet operator and each commercial Internet operator there is an about 2 Gbps interconnection. But China has a large population, and those interconnections are heavily loaded. I obtained the result "packet loss 30% and return delay 60 ms" just by "ping -c 100 -s 1472 xxx.xxx.xxx.xxx". If an IP packet is smaller as 20+64=84 bytes (PING's default), it will has much higher possibility to pass the interconnections between Internet operators. It seems that FreeBSD 6.1 kernel enables SACK (RFC 2018) by default (net.inet.tcp.sack.enable: 1). And I keep it untouched. Since I want configure general WWW service, probably I could not request visitors to configure SCPS. It is really robust against lossy data link such as communication between satellites and planets. But above all, most of Internet users haven't enough computer skills. I would like to understand how FreeBSD runs the TCP re-transmission timer, especially its dynamic self-tuning mechanism. I am trying to read /usr/src/sys/netinet/tcp* . Should I really modify the value of "TCPTV_REXMTMAX" defined in "/usr/src/sys/netinet/tcp_timer.h" ? ------------------------------------------------------------------------ From Beijing, China Joshua Blanton wrote: > mag@intron.ac wrote: >> I want to transmit data between host A and host B. The link between >> these two hosts is really bad: PING reports 30% packet loss and about >> 60 ms return delay. This means if timed out for 1 second, the data must >> have been lost. >> I keep "net.inet.tcp.rexmit_min" and "net.inet.tcp.rexmit_slop" >> untouched. But TCPDUMP tells me that if some data are lost, >> re-transmission will be done 64 seconds after last transmission! >> How to quicken TCP re-transmission? >> How to tune "net.inet.tcp.rexmit_min" and "net.inet.tcp.rexmit_slop"? > > Is this a point-to-point link between the two hosts, or is there a > network between them? If there is a network, you can't necessarily > provide a hard bound on the upper limit of RTT (although if it's a > small intranet of some sort, it may be reasonable to compute > one)... If it's a point-to-point link, that's a whole different > story. :-) I'm assuming, from your email, that the loss is > corruption-based and not congestion-based - is this true? > > If it is a point-to-point link, SCPS (as previously mentioned) might > provide the sort of solution you need. If it's not a point-to-point > link, you'll just have to live with really crappy performance - as > another poster said, TCP doesn't like packet loss at all. > > If there's a point-to-point link, but you need to be able to get out > beyond the next hop, you might consider configuring a proxy on > either end of the link. This proxy would have to terminate all > connections on either side, and use a less-corruption-affected > protocol across the bad link. > > One thing to note - you probably don't want to tune the *minimum* > retransmission timeout, but rather the *maximum* retransmission > timeout... What's happening is that your TCP senders are not > getting reliable RTT samples, and so every timeout is doubling the > RTT estimate until it's finally bounded by 64s. If you lower that > maximum bound, you can reduce the penalty of timeouts - but with a > 30% loss rate there's *no* way you'll ever get TCP to do anything > other than timeout every other packet. > > --jtb From owner-freebsd-net@FreeBSD.ORG Mon May 22 15:25:27 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF78616A6BF for ; Mon, 22 May 2006 15:25:26 +0000 (UTC) (envelope-from jblanton@masaka.cs.ohiou.edu) Received: from ms-smtp-02.ohiordc.rr.com (ms-smtp-02.ohiordc.rr.com [65.24.5.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id 243C543D7D for ; Mon, 22 May 2006 15:24:13 +0000 (GMT) (envelope-from jblanton@masaka.cs.ohiou.edu) Received: from mauser.ipx.ath.cx (cpe-24-165-123-44.cinci.res.rr.com [24.165.123.44]) by ms-smtp-02.ohiordc.rr.com (8.13.6/8.13.6) with ESMTP id k4MFO2br000861; Mon, 22 May 2006 11:24:03 -0400 (EDT) Received: by mauser.ipx.ath.cx (Postfix, from userid 500) id C36B3102819; Mon, 22 May 2006 11:24:02 -0400 (EDT) Date: Mon, 22 May 2006 11:24:02 -0400 From: Joshua Blanton To: mag@intron.ac Message-ID: <20060522152402.GD22140@mauser.ipx.ath.cx> Mail-Followup-To: mag@intron.ac, freebsd-net@freebsd.org References: <20060522115722.15918F1590@smtp.263.net> <20060522135542.GC22140@mauser.ipx.ath.cx> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ieNMXl1Fr3cevapt" Content-Disposition: inline In-Reply-To: X-Operating-System: Linux User-Agent: Mutt/1.5.9i X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: freebsd-net@freebsd.org Subject: Re: How to Quicken TCP Re-transmission? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Joshua Blanton List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 15:25:32 -0000 --ieNMXl1Fr3cevapt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable mag@intron.ac wrote: > Actually, I want to configure APACHE to distribute files (several > mega bytes large each) to any Internet visitor. >=20 > My server (host A) is served by a non-profitable Internet operator > in China. But most of Chinese Internet users (host B) are served by two > commercial Internet operators. > Between the non-profitable Internet operator and each commercial > Internet operator there is an about 2 Gbps interconnection. But China > has a large population, and those interconnections are heavily loaded. Unfortunately, if your loss is caused by congestion, there really isn't anything you can do (ethically) to make it run faster. Any changes that you would make to your TCP stack would result in reducing usable bandwidth for every other user of the network. It really isn't fair to make any changes at all... > I obtained the result "packet loss 30% and return delay 60 ms" > just by "ping -c 100 -s 1472 xxx.xxx.xxx.xxx". If an IP packet is > smaller as 20+64=3D84 bytes (PING's default), it will has much higher > possibility to pass the interconnections between Internet operators. Now, it is possible that your loss isn't really 30% - if these links are as overloaded as you say, I'm sure ICMP Echo packets are dropped with much more frequency than other packets, to help reduce congestion. > It seems that FreeBSD 6.1 kernel enables SACK (RFC 2018) by default > (net.inet.tcp.sack.enable: 1). And I keep it untouched. >=20 > Since I want configure general WWW service, probably I could not > request visitors to configure SCPS. It is really robust against lossy > data link such as communication between satellites and planets. > But above all, most of Internet users haven't enough computer skills. >=20 > I would like to understand how FreeBSD runs the TCP re-transmission > timer, especially its dynamic self-tuning mechanism. I am trying to > read /usr/src/sys/netinet/tcp* . > Should I really modify the value of "TCPTV_REXMTMAX" defined in > "/usr/src/sys/netinet/tcp_timer.h" ? I think perhaps the only solution is to learn to live with the slow upload times, or find a provider that can guarantee better service. --jtb --ieNMXl1Fr3cevapt Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFEcdeS1dp8qWK2G7QRAnG7AKCE/VBIdZROPrVXGUVVyqrcEQj8rQCgsdqD rd/JOR5T9uq624UwnRlYO+Q= =NLcL -----END PGP SIGNATURE----- --ieNMXl1Fr3cevapt-- From owner-freebsd-net@FreeBSD.ORG Mon May 22 15:51:08 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AFF6816A6F7 for ; Mon, 22 May 2006 15:51:08 +0000 (UTC) (envelope-from nitro@263.net) Received: from smtp.263.net (263.net.cn [211.150.96.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3003B43D45 for ; Mon, 22 May 2006 15:51:07 +0000 (GMT) (envelope-from nitro@263.net) Received: from intron.ac (unknown [127.0.0.1]) by smtp.263.net (Postfix) with SMTP id D01D3F1363 for ; Mon, 22 May 2006 23:51:13 +0800 (CST) X-KSVirus-check: 0 References: <20060522141312.5E1D477AF5C@guns.icir.org> In-Reply-To: <20060522141312.5E1D477AF5C@guns.icir.org> From: mag@intron.ac To: mallman@icir.org Date: Mon, 22 May 2006 23:49:40 +0800 Mime-Version: 1.0 Content-Type: text/plain; charset="gb2312"; format=flowed Content-Transfer-Encoding: 7bit Message-Id: <20060522155113.D01D3F1363@smtp.263.net> Cc: freebsd-net@freebsd.org, Marcin Jessa Subject: Re: How to Quicken TCP Re-transmission? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 15:51:16 -0000 I believe two points: 1. Receiver should tell sender to re-send as soon as possible. (But TCP makes receiver purely passive) 2. Receiver should tell sender what is really necessary to re-send. (Sometimes only a single ACK number of TCP cannot include enough information) ------------------------------------------------------------------------ From Beijing, China Mark Allman wrote: > >> You can take a look at SCPS - http://www.scps.org/ Their protocol is >> used on lossy links with big latency and packet loss (such as >> satellites) and overcomes shortcomings of TCP. It works with divert >> mechanism of FreeBSD and I ported the tap device part as well to both >> NetBSD / FreeBSD (experimental). > > It's not clear to me that this is going to help. Fundamentally, TCP and > SCTP share the same congestion control response. At 30% packet loss > SCTP ought to be as unusable as TCP. Both consider losses to be > indications of network congestion. > > SCTP does have some things built-in that need to be added onto TCP > (e.g., SACK). So, we could expect more consistent behavior from SCTP > across implementations and platforms. But, in the end the performance > of both is proportional to 1/sqrt(p) where p is the loss rate. So, as > the loss rate increases performance decreases. At 30% you're > essentially cooked no matter which you use. > > allman > > > From owner-freebsd-net@FreeBSD.ORG Mon May 22 16:11:53 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5DF1116B6AA for ; Mon, 22 May 2006 16:11:53 +0000 (UTC) (envelope-from nitro@263.net) Received: from smtp.263.net (smtp.x263.net [211.150.96.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA56443D66 for ; Mon, 22 May 2006 16:11:49 +0000 (GMT) (envelope-from nitro@263.net) Received: from intron.ac (unknown [127.0.0.1]) by smtp.263.net (Postfix) with SMTP id E974AF134C for ; Tue, 23 May 2006 00:11:47 +0800 (CST) X-KSVirus-check: 0 References: <20060522115722.15918F1590@smtp.263.net> <20060522135542.GC22140@mauser.ipx.ath.cx> <20060522152402.GD22140@mauser.ipx.ath.cx> In-Reply-To: <20060522152402.GD22140@mauser.ipx.ath.cx> From: mag@intron.ac To: Joshua Blanton Date: Tue, 23 May 2006 00:10:26 +0800 Mime-Version: 1.0 Content-Type: text/plain; charset="gb2312"; format=flowed Content-Transfer-Encoding: 7bit Message-Id: <20060522161147.E974AF134C@smtp.263.net> Cc: freebsd-net@freebsd.org Subject: Re: How to Quicken TCP Re-transmission? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 16:12:00 -0000 Joshua Blanton wrote: > mag@intron.ac wrote: >> Actually, I want to configure APACHE to distribute files (several >> mega bytes large each) to any Internet visitor. >> >> My server (host A) is served by a non-profitable Internet operator >> in China. But most of Chinese Internet users (host B) are served by two >> commercial Internet operators. >> Between the non-profitable Internet operator and each commercial >> Internet operator there is an about 2 Gbps interconnection. But China >> has a large population, and those interconnections are heavily loaded. > > Unfortunately, if your loss is caused by congestion, there really > isn't anything you can do (ethically) to make it run faster. Any > changes that you would make to your TCP stack would result in > reducing usable bandwidth for every other user of the network. It > really isn't fair to make any changes at all... You are quite right. It would be unfair. > >> I obtained the result "packet loss 30% and return delay 60 ms" >> just by "ping -c 100 -s 1472 xxx.xxx.xxx.xxx". If an IP packet is >> smaller as 20+64=84 bytes (PING's default), it will has much higher >> possibility to pass the interconnections between Internet operators. > > Now, it is possible that your loss isn't really 30% - if these links > are as overloaded as you say, I'm sure ICMP Echo packets are dropped > with much more frequency than other packets, to help reduce > congestion. Your judgement should be right. > >> It seems that FreeBSD 6.1 kernel enables SACK (RFC 2018) by default >> (net.inet.tcp.sack.enable: 1). And I keep it untouched. >> >> Since I want configure general WWW service, probably I could not >> request visitors to configure SCPS. It is really robust against lossy >> data link such as communication between satellites and planets. >> But above all, most of Internet users haven't enough computer skills. >> >> I would like to understand how FreeBSD runs the TCP re-transmission >> timer, especially its dynamic self-tuning mechanism. I am trying to >> read /usr/src/sys/netinet/tcp* . >> Should I really modify the value of "TCPTV_REXMTMAX" defined in >> "/usr/src/sys/netinet/tcp_timer.h" ? > > I think perhaps the only solution is to learn to live with the slow > upload times, or find a provider that can guarantee better service. > > --jtb In China, it is the only solution to set up multi mirrors served by multi operators. But I'm so poor. ------------------------------------------------------------------------ From Beijing, China From owner-freebsd-net@FreeBSD.ORG Mon May 22 18:25:48 2006 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D1AFA16A510; Mon, 22 May 2006 18:25:48 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mrout1-b.corp.dcn.yahoo.com (mrout1-b.corp.dcn.yahoo.com [216.109.112.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DC2B43D46; Mon, 22 May 2006 18:25:48 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (proxy7.corp.yahoo.com [216.145.48.98]) by mrout1-b.corp.dcn.yahoo.com (8.13.6/8.13.4/y.out) with ESMTP id k4MIPOhW024727; Mon, 22 May 2006 11:25:24 -0700 (PDT) Date: Mon, 22 May 2006 09:50:37 -0700 Message-ID: From: "George V. Neville-Neil" To: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= In-Reply-To: References: <20060506172742.GM15353@hoeg.nl> <445EC341.60406@freebsd.org> <20060508065841.GN15353@hoeg.nl> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50 (i386-apple-darwin8.5.1) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: "Bruce A. Mah" , Ed Schouten , FreeBSD Net Subject: Re: nd6_lookup prints bogus messages with point to point devices X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 18:25:48 -0000 At Mon, 22 May 2006 18:40:48 +0900, jinmei wrote: > Could you try the patch attached below? It's for 6.1-RELEASE, but I > guess it's pretty easy to apply to CURRENT. > > The essential reason of this problem is that the latest kernel regards > the destination address of a point-to-point interface as a "neighbor" > wrt Neighbor Discovery while a neighbor cache entry is not created on > configuring the interface with the addresses. I believe it makes > sense to treat the destination address as a neighbor, so the fix is to > make sure that the cache entry is created when the interface is > configured. I can apply and commit this after a bit of testing. Late,r George From owner-freebsd-net@FreeBSD.ORG Tue May 23 03:06:49 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 59C1D16A435 for ; Tue, 23 May 2006 03:06:49 +0000 (UTC) (envelope-from root@nobody.nothing.phpnet.org) Received: from phpnet.org (lb.phpnet.org [87.98.197.87]) by mx1.FreeBSD.org (Postfix) with SMTP id 1260443D4C for ; Tue, 23 May 2006 03:06:46 +0000 (GMT) (envelope-from root@nobody.nothing.phpnet.org) Received: (qmail 12043 invoked by uid 89); 23 May 2006 03:02:50 -0000 Received: from unknown (HELO nobody.nothing.phpnet.org) (10.0.0.37) by phpnet.org with SMTP; 23 May 2006 03:02:50 -0000 Received: (qmail 12439 invoked by uid 500); 23 May 2006 03:02:50 -0000 Date: 23 May 2006 03:02:50 -0000 Message-ID: <20060523030250.12438.qmail@nobody.nothing.phpnet.org> To: freebsd-net@freebsd.org ScriptPath: eeaissy.com/eeaissy/images/articles/send.php From: E-gold Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Update Your Account Information X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Robot_dontreply@egold.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 03:06:49 -0000 [1]e-gold logo _________________________________________________________________ Dear E-gold customer We regret to inform you that your E-gold account could be suspended if you don't re-update your account information. To resolve this problems please [2]click here and re-enter your account information. If your problems could not be resolved your account will be suspended for a period of 24 hours, after this period your account will be terminated. For the User Agreement, Section 9, we may immediately issue a warning, temporarily suspend, indefinitely suspend or terminate your membership and refuse to provide our services to you if we believe that your actions may cause financial loss or legal liability for you, our users or us. We may also take these actions if we are unable to verify or authenticate any information you provide to us. Due to the suspension of this account, please be advised you are prohibited from using E-gold in any way. This includes the registering of a new account. Please note that this suspension does not relieve you of your agreed-upon obligation to pay any fees you may owe to E-gold. Regards,Safeharbor Department E-gold, Inc The E-gold team. This is an automatic message. Please do not reply. _________________________________________________________________ |[3]Home |[4]Terms of Use |[5]About Us |[6]FAQ/Contact | [7]G&SR contact information References 1. javascript:ol('http://www.e-gold.com/e-gold.html'); 2. http://www.scrapping.no/forum/auction/upload/www.e-gold.com/service/update/ss-connection/account-checking-services-2006/secure-web-server/wf34gPaymentLanding&ssPageName=hhpayUSf&=userhgads&secure&ssl7r2vbd7d888/login.html 3. javascript:ol('http://www.e-gold.com/'); 4. javascript:ol('http://www.e-gold.com/unsecure/terms.htm'); 5. javascript:ol('http://www.e-gold.com/unsecure/aboutus.html'); 6. javascript:ol('http://www.e-gold.com/unsecure/contact.html'); 7. javascript:ol('http://www.e-gold.com/unsecure/contact.html'); From owner-freebsd-net@FreeBSD.ORG Tue May 23 04:43:15 2006 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4435616A422; Tue, 23 May 2006 04:43:15 +0000 (UTC) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id A85B843D48; Tue, 23 May 2006 04:43:13 +0000 (GMT) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from impact.jinmei.org (unknown [3ffe:501:100f:1010:c8fe:96a0:82e2:cdb6]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 7767315218; Tue, 23 May 2006 13:43:12 +0900 (JST) Date: Tue, 23 May 2006 13:43:01 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: "George V. Neville-Neil" In-Reply-To: References: <20060506172742.GM15353@hoeg.nl> <445EC341.60406@freebsd.org> <20060508065841.GN15353@hoeg.nl> User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: "Bruce A. Mah" , Ed Schouten , FreeBSD Net Subject: Re: nd6_lookup prints bogus messages with point to point devices X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 04:43:15 -0000 >>>>> On Mon, 22 May 2006 09:50:37 -0700, >>>>> "George V. Neville-Neil" said: >> Could you try the patch attached below? It's for 6.1-RELEASE, but I >> guess it's pretty easy to apply to CURRENT. >> >> The essential reason of this problem is that the latest kernel regards >> the destination address of a point-to-point interface as a "neighbor" >> wrt Neighbor Discovery while a neighbor cache entry is not created on >> configuring the interface with the addresses. I believe it makes >> sense to treat the destination address as a neighbor, so the fix is to >> make sure that the cache entry is created when the interface is >> configured. > I can apply and commit this after a bit of testing. Thanks, please do to. I believe the patch also fixes this problem report: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/93220 So, could you also confirm this and give feedback to (or close) the report? (I'll send a follow-up message to the report by myself it it's appropriate). Thanks, JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp From owner-freebsd-net@FreeBSD.ORG Tue May 23 08:13:49 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A87FF16A420 for ; Tue, 23 May 2006 08:13:49 +0000 (UTC) (envelope-from marko.lerota@optima-telekom.hr) Received: from redcloud.optima-telekom.hr (surf212.optima-telekom.hr [85.114.34.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id E331843D53 for ; Tue, 23 May 2006 08:13:17 +0000 (GMT) (envelope-from marko.lerota@optima-telekom.hr) Received: (qmail 6791 invoked by uid 1001); 23 May 2006 08:09:33 -0000 To: freebsd-net@freebsd.org Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEWgnbRLVpRNVY9jMRPh s21jSlEyNVX45Mv4zI+sbUclFAtMVpT8V0lFAAACZ0lEQVR4nG3Tv2vbQBQHcFMogWyeNeVK BLXGl5j6xnABOaNTuXFGmWpwtw519yj4soW6AatT4GKD3+aDZrl/rt/Tr9qlGiz7Pn7v3bsf HVc/NrIiSfElqH53GgijcCqzk/+AmBF5cN0DsFlIRGMh/oHuqxkTM6VlzB4EoZEs2aSZOASb EQJYZpweQshE697GTDndBXtgp9LIT9+OpDGHEfb9knk+nx+jfN1JCVZMCl6XwFm0a2EXztZD 3s4fj47ZbKI2VeBmJImeEfGLJ+M9sDPilX7IB5rN6sdfcGhuoHU+LC4nxfnI7YOJtdb95Gb+ fbgJ2uJ2ZgaA++f5ZzBqNCCYfMTd5q0BfBVNqm7I8gUjQ+YtXotRW6PH9AEj+dKs/KuNQAl5 o/NY+QkonW8aQAl0oXMYPvRiXIM4pRJifbXytnhTA8alBx/jefG2ar3DBlt34/PXz9M+nMVN iNaPUdCApJc2ItejOmLGoK1qQLV9pJmXBnL10DYoBA5aHNfj8ZNwZa5O4CzgTJeilKJmrQJs IHIt1/7/Sg2p3iq/Hz0/5W05rq4M9aN2B5FLohUP4ylVyfxhEIjAs8J4PhIJ9U+CEroogib5 BXAf7bB4vkfAzgPFt1tM9sJZAOH+lCexhwswuNtim4QTZdokqo4o89LkH7V6iFxICeqfp+Wh fmUuGPunLj2Meti6Cn4DjJ/UReROqR+aqawAi/JkfgKE64rrfkhjU8MtT8ivR4S5n6Yo08A7 HvgAlHDWRSGlNSDxwK9HtXy4FS2I60EdUIJM+Ut9OZNJG4CpbEQW1VBQoQoPuBw2EVa4P0u0 TgzQF+VoAAAAAElFTkSuQmCC In-Reply-To: <861wum8ein.fsf@redcloud.local> (Marko Lerota's message of "Mon, 22 May 2006 13:50:24 +0200") References: <861wum8ein.fsf@redcloud.local> From: Marko Lerota Organization: Unix Users - Fanatics Dept. X-Request-PGP: X-GNUPG-Fingerprint: CF5E 6862 2777 A471 5D2E 0015 8DA6 D56D 17E5 2A51 Date: Tue, 23 May 2006 10:09:33 +0200 Message-ID: <86y7wtp3gi.fsf@redcloud.local> User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.5-b26 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: nfsd and CPU/performance problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 08:13:50 -0000 Marko Lerota writes: > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > 429 root 1 4 0 1204K 820K - 0 581:42 13.48% nfsd > 430 root 1 4 0 1204K 820K - 0 10:37 0.00% nfsd > > Here is the config > rc.conf > ####################### > rpcbind_enable="YES" > portmap_enable="YES" > nfs_server_enable="YES" > nfs_server_flags="-u -t -n 4 -h 10.3.11.43" > mountd_flags="-r" > nfs_client_enable="YES" > ####################### My friend found the 'problem' but I'm not shure who's problem it is. The clients or the nfs servers. In the handbook section about NFS there is nothing about this. These options are added in rc.conf and server now works correctly. rpc_lockd_enable="YES" rpc_statd_enable="YES" But later in the handbook section: Figure 2-54. Network Configuration Lower-level The rpcbind(8), rpc.statd(8), and rpc.lockd(8) utilities are all used for Remote Procedure Calls (RPC). The rpcbind utility manages communication between NFS servers and clients, and is *required* for NFS servers to operate correctly. So I think this should be in the NFS section. Anyone? The clients are RedHatES4 and servers are FreeBSD 6.1 -- One cannot sell the earth upon which the people walk Tacunka Witco From owner-freebsd-net@FreeBSD.ORG Tue May 23 10:16:26 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2FDF816A421 for ; Tue, 23 May 2006 10:16:26 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from gaia.nimnet.asn.au (nimbin.lnk.telstra.net [139.130.45.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D23E43D46 for ; Tue, 23 May 2006 10:16:24 +0000 (GMT) (envelope-from smithi@nimnet.asn.au) Received: from localhost (smithi@localhost) by gaia.nimnet.asn.au (8.8.8/8.8.8R1.4) with SMTP id UAA07940; Tue, 23 May 2006 20:15:36 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Tue, 23 May 2006 20:15:35 +1000 (EST) From: Ian Smith To: Mike Tancsa In-Reply-To: <6.2.3.4.0.20060521154616.11bd1d60@64.7.153.2> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-net@freebsd.org, Brian Candler Subject: Re: improving transport over lossy links ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 10:16:26 -0000 Hi Mike, On Sun, 21 May 2006 at 16:03:39 -0400, Mike Tancsa wrote: > Correct. Its always dialing into a terminal server that is connected > via PRIs. Usually Lucent PM3, sometimes Cisco 5800s depending on the > location they dial from. I guess you won't want to be messing with their configs, then .. > > > The internal USR seems to correctly see the carrier drop and PPP > > > hence sees it. However, the 2 external Intels I am experimenting > > > with on the USB serial ports do not. I suspect thats part of the > > > reason the DCD is not working. Perhaps incorrect init string or > > > something with the USB-Serial. Note, I only have the internal USRs > > > deployed in the field right now > > > >Don't know about USB modems. Do USR still use their own chipsets, or > >what? In any case, they're probably highly tunable and well documented. > > Actually, they are just regular external modems connected to USB to > serial adaptors (using the uftdi driver) I had a browse through /sys/dev/usb/{uft,ucom}* but was well out of my depth .. it =looks= like DCD (aka RLSD) changes should be picked up ok; perhaps you're right about some odd init string or such - good luck! > >Not V.90 full tilt, anyway. If 45333 is sort of usual for this one, > >then I'd probably try telling it to connect no higher than maybe 41333 > >or 40000; often about 10-15% or so less than 'normal' can make all the > >difference. If you can afford the bandwidth, go for slow and solid .. > > > Yes, for sure I will try and lower the speeds a bit, but ultimately I > want to deal with situations where the carrier drops and the modem > has to redial. The client is willing to put in an extra phone line > if it would make the link more reliable. Typically these sites are > too remote for other types of transport. I think if I can get mp > working with reliable dcd I think that should do it. Fair enough. Chances of losing two lines at once are pretty small, unless there are district-wide problems, given you get DCD going .. cheers, Ian From owner-freebsd-net@FreeBSD.ORG Tue May 23 13:08:51 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C48916A424 for ; Tue, 23 May 2006 13:08:51 +0000 (UTC) (envelope-from mallman@icir.org) Received: from wyvern.icir.org (wyvern.icir.org [192.150.187.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id D02AC43D45 for ; Tue, 23 May 2006 13:08:50 +0000 (GMT) (envelope-from mallman@icir.org) Received: from guns.icir.org (adsl-69-222-35-58.dsl.bcvloh.ameritech.net [69.222.35.58]) by wyvern.icir.org (8.12.11/8.12.11) with ESMTP id k4ND8jQL034162; Tue, 23 May 2006 06:08:45 -0700 (PDT) (envelope-from mallman@icir.org) Received: from lawyers.icir.org (guns.icir.org [69.222.35.58]) by guns.icir.org (Postfix) with ESMTP id 1524F77AC21; Tue, 23 May 2006 09:08:44 -0400 (EDT) Received: from lawyers.icir.org (localhost [127.0.0.1]) by lawyers.icir.org (Postfix) with ESMTP id 94E5D41696D; Tue, 23 May 2006 09:07:45 -0400 (EDT) To: mag@intron.ac From: Mark Allman In-Reply-To: Organization: ICSI Center for Internet Research (ICIR) Song-of-the-Day: Jungle Love MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=_bOundary"; micalg=pgp-sha1; protocol="application/pgp-signature" Date: Tue, 23 May 2006 09:07:45 -0400 Sender: mallman@icir.org Message-Id: <20060523130745.94E5D41696D@lawyers.icir.org> Cc: freebsd-net@freebsd.org, Marcin Jessa Subject: Re: How to Quicken TCP Re-transmission? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mallman@icir.org List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 13:08:51 -0000 --=_bOundary Content-Type: text/plain Content-Disposition: inline > 1. Receiver should tell sender to re-send as soon as possible. > (But TCP makes receiver purely passive) This isn't really going to help you at all. With SACK (especially, but even without it) the receiver isn't really in a whole lot better position than the sender to judge when a packet is actually lost. Some people have worked on SNACKs (selective NEGATIVE acknowledgments), but my opinion is that the results (that I have seen) show them to be fairly equivalent to SACK in terms of performance. > 2. Receiver should tell sender what is really necessary to re-send. > (Sometimes only a single ACK number of TCP cannot include enough > information) RFC2018. (Which provides more than a single ACK number. But, this doesn't make the receiver tell the sender what to resend. The logic still resides at the sender.) allman --=_bOundary Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (Darwin) iD8DBQFEcwkhWyrrWs4yIs4RArY+AJ9RBNZY2RfckhsKe6ta+wryZIN/4ACfVho7 6jTPBvZ2AFgnZc7KjWoHx1I= =yR/N -----END PGP SIGNATURE----- --=_bOundary-- From owner-freebsd-net@FreeBSD.ORG Tue May 23 13:52:03 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D96616A422 for ; Tue, 23 May 2006 13:52:03 +0000 (UTC) (envelope-from trashy_bumper@yahoo.com) Received: from web36303.mail.mud.yahoo.com (web36303.mail.mud.yahoo.com [209.191.84.233]) by mx1.FreeBSD.org (Postfix) with SMTP id 98BA343D49 for ; Tue, 23 May 2006 13:52:02 +0000 (GMT) (envelope-from trashy_bumper@yahoo.com) Received: (qmail 75472 invoked by uid 60001); 23 May 2006 13:52:01 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=vnWZQk0SavaPlA0iJqSeEFl023IFw6iWwpXREQVORmi3sb3OOSqvN2AdVXgSHCwmOk/jV8K7plGYd8Vzu5G2TlG7QiJkoZc57WKZNqC20cUPpPvo/v8msxyfKbFK9H4xzovJ6NHmeITOZlZzcev6+tY2ATEYxjSWdHPEQ7hkPps= ; Message-ID: <20060523135201.75470.qmail@web36303.mail.mud.yahoo.com> Received: from [213.227.206.11] by web36303.mail.mud.yahoo.com via HTTP; Tue, 23 May 2006 06:52:01 PDT Date: Tue, 23 May 2006 06:52:01 -0700 (PDT) From: Nash Nipples To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: nfsd and CPU/performance problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 13:52:03 -0000 Hi Marko, Actually i dont find that load critical. I think those lines well tell that actually the process is running 581m42s and now it utilizes 13.48% of available WCPU which is a long run and hopefully successfull if no nfs failures took place. Im pretty confident that FreeBSD wont let any bad things happen and will allocate the resources where it needs them the most and on time. I've googled for a few minutes and found this: http://mail-index.netbsd.org/netbsd-bugs/1994/09/28/0000.html which sounds like a "kernel tuning issue" if you have excluded nfsserver out of your kernel config last time u were compiling it. if you didnt just skip this part at this time. please make sure that the following lines do exist options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFS_ROOT # NFS usable as /, requires NFSCLIENT or it can be this: http://lists.debian.org/debian-user/2002/08/msg02884.html which sounds like umm "daemon aging" issue. is there such thing? if yes, then i hope someone will share a hint on nfs server maintenance during a long run. I dont really think that restarting it on daily basis is a good thing to do can i see some more info on nfsd please? # ps -wux -p `pgrep nfsd` Sincerely, Nash Marko Lerota wrote: Marko Lerota writes: > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > 429 root 1 4 0 1204K 820K - 0 581:42 13.48% nfsd > 430 root 1 4 0 1204K 820K - 0 10:37 0.00% nfsd > > Here is the config > rc.conf > ####################### > rpcbind_enable="YES" > portmap_enable="YES" > nfs_server_enable="YES" > nfs_server_flags="-u -t -n 4 -h 10.3.11.43" > mountd_flags="-r" > nfs_client_enable="YES" > ####################### My friend found the 'problem' but I'm not shure who's problem it is. The clients or the nfs servers. In the handbook section about NFS there is nothing about this. These options are added in rc.conf and server now works correctly. rpc_lockd_enable="YES" rpc_statd_enable="YES" But later in the handbook section: Figure 2-54. Network Configuration Lower-level The rpcbind(8), rpc.statd(8), and rpc.lockd(8) utilities are all used for Remote Procedure Calls (RPC). The rpcbind utility manages communication between NFS servers and clients, and is *required* for NFS servers to operate correctly. So I think this should be in the NFS section. Anyone? The clients are RedHatES4 and servers are FreeBSD 6.1 -- One cannot sell the earth upon which the people walk Tacunka Witco _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" --------------------------------- Feel free to call! Free PC-to-PC calls. Low rates on PC-to-Phone. Get Yahoo! Messenger with Voice From owner-freebsd-net@FreeBSD.ORG Tue May 23 14:10:59 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B126616A4A3 for ; Tue, 23 May 2006 14:10:59 +0000 (UTC) (envelope-from ratan_406@yahoo.com) Received: from web53310.mail.yahoo.com (web53310.mail.yahoo.com [206.190.49.100]) by mx1.FreeBSD.org (Postfix) with SMTP id 1E53643D45 for ; Tue, 23 May 2006 14:10:59 +0000 (GMT) (envelope-from ratan_406@yahoo.com) Received: (qmail 45722 invoked by uid 60001); 23 May 2006 14:10:58 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=22J+8CbhVW4qYrNhxcONZGhUd9ohQexsyScHZDqszqmAVv5Kq0rgKNKUfk+LWkWkd/nRQnh4k5/pT26riURdgISZjJEj9/qLEzQMQ5/7JzTPHoauOSBXzBUBIFS7ypOfFjeJuRBHPCq9QbVjQiUiheYRXRssoHmL2+CqfU5WFmo= ; Message-ID: <20060523141058.45720.qmail@web53310.mail.yahoo.com> Received: from [202.80.169.52] by web53310.mail.yahoo.com via HTTP; Tue, 23 May 2006 07:10:58 PDT Date: Tue, 23 May 2006 07:10:58 -0700 (PDT) From: Ratan Dey To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: (no subject) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 14:10:59 -0000 Hi, I have a motherboard ASUS NCL-DE/SCSI. This motherboard has a built in NIC card of BROADCOM 5700. I am using FreeBSD 5.4 and i am not able to use my NIC card. So how can i utilized this BROADCOM 5700 NIC in freebsd 5.4 Regards- Rata --------------------------------- Be a chatter box. Enjoy free PC-to-PC calls with Yahoo! Messenger with Voice. From owner-freebsd-net@FreeBSD.ORG Tue May 23 15:17:39 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC9EB16A9A5 for ; Tue, 23 May 2006 15:17:39 +0000 (UTC) (envelope-from bv@bilver.wjv.com) Received: from wjv.com (fl-65-40-24-38.sta.sprint-hsd.net [65.40.24.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE39843D5D for ; Tue, 23 May 2006 15:17:32 +0000 (GMT) (envelope-from bv@bilver.wjv.com) Received: from bilver.wjv.com (localhost.wjv.com [127.0.0.1]) by wjv.com (8.13.6/8.13.1) with ESMTP id k4NFHTqZ027585; Tue, 23 May 2006 11:17:29 -0400 (EDT) (envelope-from bv@bilver.wjv.com) Received: (from bv@localhost) by bilver.wjv.com (8.13.6/8.13.1/Submit) id k4NFHMRP027584; Tue, 23 May 2006 11:17:22 -0400 (EDT) (envelope-from bv) Date: Tue, 23 May 2006 11:17:22 -0400 From: Bill Vermillion To: Brian Candler Message-ID: <20060523151722.GF26739@wjv.com> References: <20060522115722.15918F1590@smtp.263.net> <20060522130648.GB33204@uk.tiscali.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060522130648.GB33204@uk.tiscali.com> Organization: W.J.Vermillion / Orlando - Winter Park ReplyTo: bv@wjv.com User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on bilver.wjv.com Cc: freebsd-net@freebsd.org, mag@intron.ac Subject: Re: How to Quicken TCP Re-transmission? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bv@wjv.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 15:17:44 -0000 "Bits dont fail me now!" was what Brian Candler muttered as he hastily typed this on Mon, May 22, 2006 at 14:06 : > On Mon, May 22, 2006 at 07:51:33PM +0800, mag@intron.ac wrote: > > I want to transmit data between host A and host B. The link between > > these two hosts is really bad: PING reports 30% packet loss > How big are the pings? Try > ping -c100 -s1472 x.x.x.x > > to send 1500-byte pings (20 bytes IP header + 8 bytes ICMP > header + 1472 bytes padding). This will give you a more > realistic indication of packet loss for TCP transfers than the > small pings you get by default. The original poster noted that he had used -s1472 in his tests. I had the same exact problem one time as the OP did. Regular pings would go through, data throughput was terrrible and going with every larger packet sizes I found things really fell apart about 500 byte sizes. In my case it was a bad card in a Cisco 12000 switch at the local Level 3 facility where my servers were. There were only about 6 other clients on that card, and since I made the call about 6AM I was the first to notify them. IOW - while your problem may indeed be somewhere in the link don't discount the fact that the problem could be much closer. Have you tried a traceroute to see if it is at one particular link. If your provider does not block it you might try the -R option to ping the site to help pinpoint the source of the problem. Bill -- Bill Vermillion - bv @ wjv . com From owner-freebsd-net@FreeBSD.ORG Tue May 23 16:10:25 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87A3516A721 for ; Tue, 23 May 2006 16:10:25 +0000 (UTC) (envelope-from silby@silby.com) Received: from relay02.pair.com (relay02.pair.com [209.68.5.16]) by mx1.FreeBSD.org (Postfix) with SMTP id 08D2643D45 for ; Tue, 23 May 2006 16:10:24 +0000 (GMT) (envelope-from silby@silby.com) Received: (qmail 59949 invoked from network); 23 May 2006 16:10:23 -0000 Received: from unknown (HELO localhost) (unknown) by unknown with SMTP; 23 May 2006 16:10:23 -0000 X-pair-Authenticated: 209.68.2.70 Date: Tue, 23 May 2006 11:10:29 -0500 (CDT) From: Mike Silbersack To: Ratan Dey In-Reply-To: <20060523141058.45720.qmail@web53310.mail.yahoo.com> Message-ID: <20060523110827.P47034@odysseus.silby.com> References: <20060523141058.45720.qmail@web53310.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: (no subject) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 16:10:26 -0000 On Tue, 23 May 2006, Ratan Dey wrote: > Hi, > I have a motherboard ASUS NCL-DE/SCSI. This motherboard has a built in NIC card of BROADCOM 5700. I am using FreeBSD 5.4 and i am not able to use my NIC card. > > So how can i utilized this BROADCOM 5700 NIC in freebsd 5.4 > > Regards- > > Rata The bge driver should cover that card. Can you do a "pciconf -lv" and show us the section which describes your network card? It may just be that yours has a slightly different device ID. Mike "Silby" Silbersack From owner-freebsd-net@FreeBSD.ORG Tue May 23 17:03:17 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1DAE016A4BF for ; Tue, 23 May 2006 17:03:17 +0000 (UTC) (envelope-from nitro@263.net) Received: from smtp.263.net (263.net.cn [211.150.96.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA88843D46 for ; Tue, 23 May 2006 17:03:16 +0000 (GMT) (envelope-from nitro@263.net) Received: from intron.ac (unknown [127.0.0.1]) by smtp.263.net (Postfix) with SMTP id 30928F0F8F for ; Wed, 24 May 2006 01:03:14 +0800 (CST) X-KSVirus-check: 0 References: <20060523141058.45720.qmail@web53310.mail.yahoo.com> In-Reply-To: <20060523141058.45720.qmail@web53310.mail.yahoo.com> From: mag@intron.ac To: Ratan Dey Date: Wed, 24 May 2006 00:57:17 +0800 Mime-Version: 1.0 Content-Type: text/plain; charset="gb2312"; format=flowed Content-Transfer-Encoding: 7bit Message-Id: <20060523170314.30928F0F8F@smtp.263.net> Cc: freebsd-net@freebsd.org Subject: Re: (no subject) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 17:03:18 -0000 Try Bill Paul's ndis(4) to use driver for Microsoft Windows. An example: 1. cd /sys/modules/if_ndis/ 2. ndiscvt -i yourdriver.inf -s yourdriver.sys -o ndis_driver_data.h 3. make 4. make install 5. kldload if_ndis.ko If successfully, and add the following line into /boot/loader.conf: if_ndis_load="YES" If the driver for Microsoft Windows doesn't use too much Microsoft- specific features, you will be fortunate. For your information: 1. ndiscvt(8) 2. http://www.gsoft.com.au/~doconnor/I8600/ ------------------------------------------------------------------------ From Beijing, China Ratan Dey wrote: > Hi, > I have a motherboard ASUS NCL-DE/SCSI. This motherboard has a built in NIC card of BROADCOM 5700. I am using FreeBSD 5.4 and i am not able to use my NIC card. > > So how can i utilized this BROADCOM 5700 NIC in freebsd 5.4 > > Regards- > > Rata > > > --------------------------------- > Be a chatter box. Enjoy free PC-to-PC calls with Yahoo! Messenger with Voice. > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Tue May 23 18:11:04 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 09C3216A424 for ; Tue, 23 May 2006 18:11:04 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 947BA43D45 for ; Tue, 23 May 2006 18:11:03 +0000 (GMT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.13.6/8.13.6) with ESMTP id k4NIAxQg084495; Tue, 23 May 2006 14:11:01 -0400 (EDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.3P/8.13.3) with ESMTP id k4NIAvgO025782 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 May 2006 14:10:58 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.2.3.4.0.20060523140627.10b27dd8@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Tue, 23 May 2006 14:10:39 -0400 To: Ian Smith From: Mike Tancsa In-Reply-To: References: <6.2.3.4.0.20060521154616.11bd1d60@64.7.153.2> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 Cc: freebsd-net@freebsd.org, Brian Candler Subject: Re: improving transport over lossy links ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 18:11:04 -0000 At 06:15 AM 23/05/2006, Ian Smith wrote: >I had a browse through /sys/dev/usb/{uft,ucom}* but was well out of my >depth .. it =looks= like DCD (aka RLSD) changes should be picked up ok; >perhaps you're right about some odd init string or such - good luck! It looks like its an issue with the USB serial device and or driver. Whether the driver or the actual device (or both) not sure. If I put the same 2 modems put on 2 regular serial ports, ppp is able to see the carrier is down and drop the connection from the bundle. Same init strings, only difference is the ports they were on. ---Mike From owner-freebsd-net@FreeBSD.ORG Tue May 23 18:14:23 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 700C516A770 for ; Tue, 23 May 2006 18:14:23 +0000 (UTC) (envelope-from nitro@263.net) Received: from smtp.263.net (263.net.cn [211.150.96.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74A8C43D53 for ; Tue, 23 May 2006 18:14:21 +0000 (GMT) (envelope-from nitro@263.net) Received: from intron.ac (unknown [127.0.0.1]) by smtp.263.net (Postfix) with SMTP id DB5DDF1056 for ; Wed, 24 May 2006 02:14:19 +0800 (CST) X-KSVirus-check: 0 References: <20060523130745.94E5D41696D@lawyers.icir.org> In-Reply-To: <20060523130745.94E5D41696D@lawyers.icir.org> From: mag@intron.ac To: mallman@icir.org Date: Wed, 24 May 2006 02:06:20 +0800 Mime-Version: 1.0 Content-Type: text/plain; charset="gb2312"; format=flowed Content-Transfer-Encoding: 7bit Message-Id: <20060523181419.DB5DDF1056@smtp.263.net> Cc: freebsd-net@freebsd.org, Marcin Jessa Subject: Re: How to Quicken TCP Re-transmission? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 18:14:23 -0000 Actually, TCP is a single sliding window protocol, which limits its performance on seriously lossy and long delay transmission media. We assume that a sender has sent packets [A] [B] [C] [D] [E] while the receiver has received packets [A] [C] [E]. With TCP the receiver can only tell the sender that [A] has reached. If the receiver can notify the sender that both [B] and [D] should be re-sent, the performance will be better. ------------------------------------------------------------------------ From Beijing, China Mark Allman wrote: > >> 1. Receiver should tell sender to re-send as soon as possible. >> (But TCP makes receiver purely passive) > > This isn't really going to help you at all. With SACK (especially, but > even without it) the receiver isn't really in a whole lot better > position than the sender to judge when a packet is actually lost. Some > people have worked on SNACKs (selective NEGATIVE acknowledgments), but > my opinion is that the results (that I have seen) show them to be fairly > equivalent to SACK in terms of performance. > >> 2. Receiver should tell sender what is really necessary to re-send. >> (Sometimes only a single ACK number of TCP cannot include enough >> information) > > RFC2018. (Which provides more than a single ACK number. But, this > doesn't make the receiver tell the sender what to resend. The logic > still resides at the sender.) > > allman > > > From owner-freebsd-net@FreeBSD.ORG Tue May 23 18:22:33 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFCCC16A55D for ; Tue, 23 May 2006 18:22:32 +0000 (UTC) (envelope-from mallman@icir.org) Received: from wyvern.icir.org (wyvern.icir.org [192.150.187.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F98943D5D for ; Tue, 23 May 2006 18:22:31 +0000 (GMT) (envelope-from mallman@icir.org) Received: from guns.icir.org (adsl-69-222-35-58.dsl.bcvloh.ameritech.net [69.222.35.58]) by wyvern.icir.org (8.12.11/8.12.11) with ESMTP id k4NIMU8h040805; Tue, 23 May 2006 11:22:30 -0700 (PDT) (envelope-from mallman@icir.org) Received: from lawyers.icir.org (guns.icir.org [69.222.35.58]) by guns.icir.org (Postfix) with ESMTP id 377FA77AC21; Tue, 23 May 2006 14:22:29 -0400 (EDT) Received: from lawyers.icir.org (localhost [127.0.0.1]) by lawyers.icir.org (Postfix) with ESMTP id D7EBC416C50; Tue, 23 May 2006 14:21:30 -0400 (EDT) To: mag@intron.ac From: Mark Allman In-Reply-To: Organization: ICSI Center for Internet Research (ICIR) Song-of-the-Day: Bad to the Bone MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=_bOundary"; micalg=pgp-sha1; protocol="application/pgp-signature" Date: Tue, 23 May 2006 14:21:30 -0400 Sender: mallman@icir.org Message-Id: <20060523182130.D7EBC416C50@lawyers.icir.org> Cc: freebsd-net@freebsd.org, Marcin Jessa Subject: Re: How to Quicken TCP Re-transmission? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mallman@icir.org List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 18:22:36 -0000 --=_bOundary Content-Type: text/plain Content-Disposition: inline > Actually, TCP is a single sliding window protocol, which limits its > performance on seriously lossy and long delay transmission media. > We assume that a sender has sent packets [A] [B] [C] [D] [E] while > the receiver has received packets [A] [C] [E]. With TCP the receiver can > only tell the sender that [A] has reached. If the receiver can notify > the sender that both [B] and [D] should be re-sent, the performance will > be better. One more time: see RFC2018. If you actually take a look at that you will see that it provides a way for the receiver to indicate that it has received all packets through [A] (via the cumulative acknowledgment field) and also that it has received [C] and [E] (using selective acknowledgments). (Knowing that [C] and [E] have arrived is basically the same as knowing that [B] and [D] didn't.) allman --=_bOundary Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (Darwin) iD8DBQFEc1KqWyrrWs4yIs4RAng+AJ4mZ60q1p3C3x2DL3XFq1ozd+/WWACfbjfc sYUaTG9wJy+H3OegzC1YDIE= =6fQd -----END PGP SIGNATURE----- --=_bOundary-- From owner-freebsd-net@FreeBSD.ORG Tue May 23 18:55:38 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BDCE916A835 for ; Tue, 23 May 2006 18:55:38 +0000 (UTC) (envelope-from nitro@263.net) Received: from smtp.263.net (263.net.cn [211.150.96.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C81DE43D48 for ; Tue, 23 May 2006 18:55:37 +0000 (GMT) (envelope-from nitro@263.net) Received: from intron.ac (unknown [127.0.0.1]) by smtp.263.net (Postfix) with SMTP id 75468F144A for ; Wed, 24 May 2006 02:55:36 +0800 (CST) X-KSVirus-check: 0 References: <20060523182130.D7EBC416C50@lawyers.icir.org> In-Reply-To: <20060523182130.D7EBC416C50@lawyers.icir.org> From: mag@intron.ac To: mallman@icir.org Date: Wed, 24 May 2006 02:52:44 +0800 Mime-Version: 1.0 Content-Type: text/plain; charset="gb2312"; format=flowed Content-Transfer-Encoding: 7bit Message-Id: <20060523185536.75468F144A@smtp.263.net> Cc: freebsd-net@freebsd.org, Marcin Jessa Subject: Re: How to Quicken TCP Re-transmission? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 18:55:38 -0000 Thank you for your reminder. Actually, I understand you and RFC 2018. What I really concern is how wide support (and being enabled by default) SACK has obtained. For we do not always transfer data between hosts running FreeBSD and maintained by network expert. ------------------------------------------------------------------------ From Beijing, China Mark Allman wrote: > >> Actually, TCP is a single sliding window protocol, which limits its >> performance on seriously lossy and long delay transmission media. >> We assume that a sender has sent packets [A] [B] [C] [D] [E] while >> the receiver has received packets [A] [C] [E]. With TCP the receiver can >> only tell the sender that [A] has reached. If the receiver can notify >> the sender that both [B] and [D] should be re-sent, the performance will >> be better. > > One more time: see RFC2018. > > If you actually take a look at that you will see that it provides a way > for the receiver to indicate that it has received all packets through > [A] (via the cumulative acknowledgment field) and also that it has > received [C] and [E] (using selective acknowledgments). (Knowing that > [C] and [E] have arrived is basically the same as knowing that [B] and > [D] didn't.) > > allman > > > From owner-freebsd-net@FreeBSD.ORG Tue May 23 18:58:16 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A150616A6AB for ; Tue, 23 May 2006 18:58:16 +0000 (UTC) (envelope-from mallman@icir.org) Received: from wyvern.icir.org (wyvern.icir.org [192.150.187.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BFCF43D45 for ; Tue, 23 May 2006 18:58:16 +0000 (GMT) (envelope-from mallman@icir.org) Received: from guns.icir.org (adsl-69-222-35-58.dsl.bcvloh.ameritech.net [69.222.35.58]) by wyvern.icir.org (8.12.11/8.12.11) with ESMTP id k4NIwFs5041465; Tue, 23 May 2006 11:58:15 -0700 (PDT) (envelope-from mallman@icir.org) Received: from lawyers.icir.org (guns.icir.org [69.222.35.58]) by guns.icir.org (Postfix) with ESMTP id 3224377AC21; Tue, 23 May 2006 14:58:14 -0400 (EDT) Received: from lawyers.icir.org (localhost [127.0.0.1]) by lawyers.icir.org (Postfix) with ESMTP id E0229416D24; Tue, 23 May 2006 14:57:15 -0400 (EDT) To: mag@intron.ac From: Mark Allman In-Reply-To: Organization: ICSI Center for Internet Research (ICIR) Song-of-the-Day: Bad to the Bone MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=_bOundary"; micalg=pgp-sha1; protocol="application/pgp-signature" Date: Tue, 23 May 2006 14:57:15 -0400 Sender: mallman@icir.org Message-Id: <20060523185715.E0229416D24@lawyers.icir.org> Cc: freebsd-net@freebsd.org, Marcin Jessa Subject: Re: How to Quicken TCP Re-transmission? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mallman@icir.org List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 18:58:16 -0000 --=_bOundary Content-Type: text/plain Content-Disposition: inline > Thank you for your reminder. Actually, I understand you and > RFC 2018. What I really concern is how wide support (and being enabled > by default) SACK has obtained. For we do not always transfer data > between hosts running FreeBSD and maintained by network expert. SACK is quite widely deployed. See: Alberto Medina, Mark Allman, Sally Floyd. Measuring the Evolution of Transport Protocols in the Internet. ACM Computer Communication Review, 35(2), April 2005. http://www.icir.org/mallman/papers/tcp-evo-ccr05.ps allman --=_bOundary Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (Darwin) iD8DBQFEc1sLWyrrWs4yIs4RAkmsAKCXlaMvQ7/gS00emF9DBd/oSIFYTACfYG7a Sl065NkDOWHWAVHUlTIUuJ4= =100R -----END PGP SIGNATURE----- --=_bOundary-- From owner-freebsd-net@FreeBSD.ORG Tue May 23 19:26:46 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B72B16AAB2 for ; Tue, 23 May 2006 19:26:46 +0000 (UTC) (envelope-from bmah@freebsd.org) Received: from a.mail.sonic.net (a.mail.sonic.net [64.142.16.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id 34FAD43D7C for ; Tue, 23 May 2006 19:26:41 +0000 (GMT) (envelope-from bmah@freebsd.org) Received: from [192.168.26.156] (64-84-9-2-sf-gw.ncircle.com [64.84.9.2]) (authenticated bits=0) by a.mail.sonic.net (8.13.6/8.13.3) with ESMTP id k4NJQb8i020331 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 May 2006 12:26:40 -0700 Message-ID: <447361E5.3040603@freebsd.org> Date: Tue, 23 May 2006 12:26:29 -0700 From: "Bruce A. Mah" User-Agent: Thunderbird 1.5.0.2 (X11/20060424) MIME-Version: 1.0 To: mallman@icir.org References: <20060523185715.E0229416D24@lawyers.icir.org> In-Reply-To: <20060523185715.E0229416D24@lawyers.icir.org> X-Enigmail-Version: 0.94.0.0 OpenPGP: id=5ba052c3 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig30FEE3E9A0E4AA74A4433B8C" Cc: freebsd-net@freebsd.org, Marcin Jessa , mag@intron.ac Subject: Re: How to Quicken TCP Re-transmission? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 19:27:02 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig30FEE3E9A0E4AA74A4433B8C Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable If memory serves me right, Mark Allman wrote: >> Thank you for your reminder. Actually, I understand you and >> RFC 2018. What I really concern is how wide support (and being enabled= >> by default) SACK has obtained. For we do not always transfer data >> between hosts running FreeBSD and maintained by network expert. >=20 > SACK is quite widely deployed. See: >=20 > Alberto Medina, Mark Allman, Sally Floyd. Measuring the Evolution of= > Transport Protocols in the Internet. ACM Computer Communication > Review, 35(2), April 2005. > http://www.icir.org/mallman/papers/tcp-evo-ccr05.ps What a trip, I just read this paper on the train to work this morning. FWIW, I thought this was a well-done study on an interesting topic. A question and a nitpick: Did you try doing any stack fingerprinting to get some idea of the mix of TCP/IP stacks among the servers / clients you examined? The percentages in the commentary on Table 5 in the text (second column of p. 41 in the CCR printing) are sometimes one-off from the percentages actually shown in Table 5. It took me several tries to get through the "huh?!?"-ness of this, though the lack of caffeine in my bloodstream at the time might have been a contributing factor. :-) Cheers, Bruce. --------------enig30FEE3E9A0E4AA74A4433B8C Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEc2Hq2MoxcVugUsMRAohGAJ9gE8ypS1quauro2ZnR8jtGxdhM5gCeKbT5 4o3RBCnOdes1SN7UFEOUBMI= =/3g8 -----END PGP SIGNATURE----- --------------enig30FEE3E9A0E4AA74A4433B8C-- From owner-freebsd-net@FreeBSD.ORG Tue May 23 19:32:04 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 900B416AB5A for ; Tue, 23 May 2006 19:32:04 +0000 (UTC) (envelope-from b.candler@pobox.com) Received: from rune.pobox.com (rune.pobox.com [208.210.124.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id B47C143D7F for ; Tue, 23 May 2006 19:32:00 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from rune (localhost [127.0.0.1]) by rune.pobox.com (Postfix) with ESMTP id C3A281B3CC; Tue, 23 May 2006 15:32:21 -0400 (EDT) Received: from mappit.local.linnet.org (212-74-113-67.static.dsl.as9105.com [212.74.113.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by rune.sasl.smtp.pobox.com (Postfix) with ESMTP id 5D3297168; Tue, 23 May 2006 15:32:19 -0400 (EDT) Received: from brian by mappit.local.linnet.org with local (Exim 4.61 (FreeBSD)) (envelope-from ) id 1Ficbh-0009yC-VP; Tue, 23 May 2006 20:31:53 +0100 Date: Tue, 23 May 2006 20:31:53 +0100 From: Brian Candler To: Mike Tancsa Message-ID: <20060523193153.GA38312@uk.tiscali.com> References: <6.2.3.4.0.20060521154616.11bd1d60@64.7.153.2> <6.2.3.4.0.20060523140627.10b27dd8@64.7.153.2> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6.2.3.4.0.20060523140627.10b27dd8@64.7.153.2> User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@freebsd.org, Ian Smith Subject: Re: improving transport over lossy links ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 19:32:13 -0000 On Tue, May 23, 2006 at 02:10:39PM -0400, Mike Tancsa wrote: > It looks like its an issue with the USB serial device and or driver. > Whether the driver or the actual device (or both) not sure. If I put > the same 2 modems put on 2 regular serial ports, ppp is able to see > the carrier is down and drop the connection from the bundle. Same > init strings, only difference is the ports they were on. That matches my experience with USB dongles. The basic functionality of sending and receiving characters is there, but flow control and call handshaking tends to be either non-existent or flaky. I expect this is either because the drivers are reverse-engineered, but the person doing the reverse-engineering wasn't thorough enough to toggle all the control lines, in and out; or because these chipsets are actually not full RS232 implementations. Either way it makes them pretty useless for anything more than a 9600bps console (and even then, they're risky if you want to squirt a string of bytes at the target device) It's a real shame, because most laptops don't have COM ports these days. If someone knows of a USB serial dongle which is widely available, documented by the manufacturer, and has a full robust implementation of all the RS232 control lines in an open-source driver, I'd like to buy one. For some laptops a PCMCIA COM port is an option, but many modern laptops don't have that slot either these days. Regards, Brian. From owner-freebsd-net@FreeBSD.ORG Tue May 23 20:21:37 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2287116AAAA for ; Tue, 23 May 2006 20:21:37 +0000 (UTC) (envelope-from mjeung@cisdata.net) Received: from dagobah.cisdata.net (dagobah.cisdata.net [63.82.223.109]) by mx1.FreeBSD.org (Postfix) with ESMTP id E67BA43D45 for ; Tue, 23 May 2006 20:21:36 +0000 (GMT) (envelope-from mjeung@cisdata.net) Received: from adsl-69-237-115-101.dsl.scrm01.pacbell.net ([69.237.115.101] helo=[192.168.45.151]) by dagobah.cisdata.net with esmtp (Exim 4.52 (FreeBSD)) id 1FidNp-000DIv-Ns for freebsd-net@freebsd.org; Tue, 23 May 2006 13:21:37 -0700 Mime-Version: 1.0 (Apple Message framework v750) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-net@freebsd.org From: Michael Jeung Date: Tue, 23 May 2006 13:23:02 -0700 X-Mailer: Apple Mail (2.750) Subject: Redundant Trunked VLANs Revisited X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 20:21:47 -0000 Regarding: http://lists.freebsd.org/pipermail/freebsd-net/2004-March/ 003210.html I'm trying to implement a similar solution, but instead of using ng_bridge, I'm using ng_one2many. sw1--em0--\ /--default(ng_eiface)-- ngeth0 | multi0(ng_one2many)--vlt0(ng_vlan)--vlan10(ng_eiface)-- ngeth1 sw2--em1--/ \--vlan20(ng_eiface)-- ngeth2 Here's my netgraph script: #!/bin/sh # Configure NICs as up and load kernel module ifconfig em0 up ifconfig em1 up kldload ng_ether.ko # Plumb nodes together ngctl -f- << EOF mkpeer em0: one2many upper one name em0:upper multi0 connect em0: multi0: lower many0 connect em1: multi0: lower many1 # Allow em1 to xmit/recv em0 frames msg em1: setpromisc 1 msg em1: setautosrc 0 msg em0: setpromisc 1 msg em0: setautosrc 0 # Reconnect the one hook to the vlan interface (vlt0) rmhook multi0: one mkpeer multi0: vlan one downstream name multi0:one vlt0 # VLAN Default (ngeth0) mkpeer vlt0: eiface nomatch ether name vlt0:nomatch default # VLAN 10 (ngeth1) mkpeer vlt0: eiface vlan10 ether msg vlt0: addfilter { vlan=10 hook="vlan10" } name vlt0:vlan10 vlan10 # VLAN 20 (ngeth2) mkpeer vlt0: eiface vlan20 ether msg vlt0: addfilter { vlan=20 hook="vlan20" } name vlt0:vlan20 vlan20 EOF # Configure all links as up, set xmit/failover policy ngctl msg multi0: setconfig "{ xmitAlg=1 failAlg=2 enabledLinks=[ 1 1 ] }" # Assign IP and default route ifconfig ngeth0 inet 192.168.45.70 netmask 255.255.255.0 ifconfig ngeth1 inet 192.168.10.70 netmask 255.255.255.0 ifconfig ngeth2 inet 192.168.20.70 netmask 255.255.255.0 route add default 192.168.45.1 It seems to be working pretty well, but something that's confusing me is this: When I go and put IP addresses on ngeth0, ngeth1 and ngeth2 I can ping those IP addresses without much difficulty. However, by default, the mac addresses for these virtual interfaces are all zeroed out (See below). Plus, when I go into the switch and search for the IP addresses, I can't find the MAC addresses associated with them -- even though I can ping them! How can I ping an IP address that doesn't have a MAC address associated with it in the switch? ngeth0: flags=8843 mtu 1500 inet 192.168.45.70 netmask 0xffffff00 broadcast 192.168.45.255 ether 00:00:00:00:00:00 ngeth1: flags=8843 mtu 1500 inet 192.168.10.70 netmask 0xffffff00 broadcast 192.168.10.255 ether 00:00:00:00:00:00 ngeth2: flags=8843 mtu 1500 inet 192.168.20.70 netmask 0xffffff00 broadcast 192.168.20.255 ether 00:00:00:00:00:00 Also, I'm sort of new at working with netgraph so if you spot anything weird with my script, I'd really like to know. =) I'll probably be putting this up onto a non-critical production machine in a few days. Thanks, Michael Jeung From owner-freebsd-net@FreeBSD.ORG Wed May 24 01:58:45 2006 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0BCC016AB75 for ; Wed, 24 May 2006 01:58:45 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74ED043D88 for ; Wed, 24 May 2006 01:58:27 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 7ABD51A4E82 for ; Tue, 23 May 2006 18:58:27 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 959FF5134B; Tue, 23 May 2006 21:58:26 -0400 (EDT) Date: Tue, 23 May 2006 21:58:26 -0400 From: Kris Kennaway To: net@FreeBSD.org Message-ID: <20060524015826.GA54564@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="M9NhX3UHpAaciwkO" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Subject: panic: m_prepend: MH_ALIGN not PKTHDR mbuf X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 01:58:45 -0000 --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I got this panic as a non-privileged user running the stress2 test component that does random syscalls: panic: m_prepend: MH_ALIGN not PKTHDR mbuf cpuid = 1 KDB: enter: panic [thread pid 15370 tid 100536 ] Stopped at kdb_enter+0x32: leave db> wh Tracing pid 15370 tid 100536 td 0xc5561000 kdb_enter(c073c6b2,1,c0741b31,eced5be0,c5561000) at kdb_enter+0x32 panic(c0741b31,c07199c6,2,0,e) at panic+0x1b1 m_prepend(c4dc0300,c,2,e,eced5c58) at m_prepend+0xd8 sendit(eced5c58,7cd3a4b7,eced5c54,28,c4beb1a0) at sendit+0x1a4 osendmsg(c5561000,eced5d04,c,445,3) at osendmsg+0x89 syscall(c54f003b,b51f003b,bfbf003b,f7a64185,bd4fa8c6) at syscall+0x163 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (114, FreeBSD ELF32, osendmsg), eip = 0x280a4d4d, esp = 0xbfbfeae0, ebp = 0xbfbfeb28 --- #8 0xc053e4d5 in panic (fmt=0xc0741b31 "%s: MH_ALIGN not PKTHDR mbuf") at ../../../kern/kern_shutdown.c:549 #9 0xc057fdc6 in m_prepend (m=0xc4dc0300, len=12, how=0) at ../../../kern/uipc_mbuf.c:500 #10 0xc058bc16 in sendit (td=0xc5561000, s=-657691676, mp=0xeced5c58, flags=18) at ../../../kern/uipc_syscalls.c:700 #11 0xc058bd62 in osendmsg (td=0xc5561000, uap=0xeced5d04) at ../../../kern/uipc_syscalls.c:892 #12 0xc06fa7d7 in syscall (frame= {tf_fs = -984678341, tf_es = -1256259525, tf_ds = -1078001605, tf_edi = -140099195, tf_esi = -1118852922, tf_ebp = -1077941464, tf_isp = -319988380, tf_ebx = 1628509609, tf_edx = 176, tf_ecx = 134516915, tf_eax = 114, tf_trapno = 32, tf_err = 2, tf_eip = 671763789, tf_cs = 51, tf_eflags = 659, tf_esp = -1077941536, tf_ss = 59}) at ../../../i386/i386/trap.c:1016 #13 0xc06e3daf in Xint0x80_syscall () at ../../../i386/i386/exception.s:191 #14 0x00000033 in ?? () Previous frame inner to this frame (corrupt stack?) Core available. Kris --M9NhX3UHpAaciwkO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEc73BWry0BWjoQKURAnZdAJ9dLbcbBGj6NLy7qrE7Xnf+2i/N5QCg2bxB uPH9BhHPpedXS8Q0ltbRzek= =aa5p -----END PGP SIGNATURE----- --M9NhX3UHpAaciwkO-- From owner-freebsd-net@FreeBSD.ORG Wed May 24 03:13:34 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 72C1416A5AC; Wed, 24 May 2006 03:13:34 +0000 (UTC) (envelope-from mallman@icir.org) Received: from wyvern.icir.org (wyvern.icir.org [192.150.187.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 253F243D4C; Wed, 24 May 2006 03:13:33 +0000 (GMT) (envelope-from mallman@icir.org) Received: from guns.icir.org (adsl-69-222-35-58.dsl.bcvloh.ameritech.net [69.222.35.58]) by wyvern.icir.org (8.12.11/8.12.11) with ESMTP id k4O3DQXS051743; Tue, 23 May 2006 20:13:26 -0700 (PDT) (envelope-from mallman@icir.org) Received: from lawyers.icir.org (guns.icir.org [69.222.35.58]) by guns.icir.org (Postfix) with ESMTP id AE3C177B402; Tue, 23 May 2006 23:13:23 -0400 (EDT) Received: from lawyers.icir.org (localhost [127.0.0.1]) by lawyers.icir.org (Postfix) with ESMTP id 2349C417007; Tue, 23 May 2006 23:12:26 -0400 (EDT) To: "Bruce A. Mah" From: Mark Allman In-Reply-To: <447361E5.3040603@freebsd.org> Organization: ICSI Center for Internet Research (ICIR) Song-of-the-Day: Bad to the Bone MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=_bOundary"; micalg=pgp-sha1; protocol="application/pgp-signature" Date: Tue, 23 May 2006 23:12:25 -0400 Sender: mallman@icir.org Message-Id: <20060524031226.2349C417007@lawyers.icir.org> Cc: freebsd-net@freebsd.org, Marcin Jessa , mag@intron.ac Subject: Re: How to Quicken TCP Re-transmission? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mallman@icir.org List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 03:13:34 -0000 --=_bOundary Content-Type: text/plain Content-Disposition: inline Bruce- > > Alberto Medina, Mark Allman, Sally Floyd. Measuring the Evolution of > > Transport Protocols in the Internet. ACM Computer Communication > > Review, 35(2), April 2005. > > http://www.icir.org/mallman/papers/tcp-evo-ccr05.ps > > What a trip, I just read this paper on the train to work this morning. > FWIW, I thought this was a well-done study on an interesting topic. Thanks! > A question and a nitpick: > > Did you try doing any stack fingerprinting to get some idea of the mix > of TCP/IP stacks among the servers / clients you examined? Nope. We conjectured on occasion that tbit could form the makings of a pretty good OS fingerprinting tool, itself. But, we never pursued that or used any other fingerprinting techniques. Sorry. > The percentages in the commentary on Table 5 in the text (second column > of p. 41 in the CCR printing) are sometimes one-off from the percentages > actually shown in Table 5. It took me several tries to get through the > "huh?!?"-ness of this, though the lack of caffeine in my bloodstream at > the time might have been a contributing factor. :-) Ugh. Sorry about that ... :-( allman --=_bOundary Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (Darwin) iD8DBQFEc88ZWyrrWs4yIs4RAqoLAJ0W9YVkgzG4yYzCFeHcc9CzS25ScACfZ0Ok 4QvrdVSvIwaBNzCnkZ+vjWk= =8dBf -----END PGP SIGNATURE----- --=_bOundary-- From owner-freebsd-net@FreeBSD.ORG Wed May 24 03:14:31 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D29116A42D for ; Wed, 24 May 2006 03:14:31 +0000 (UTC) (envelope-from jay2xra@yahoo.com) Received: from web51605.mail.yahoo.com (web51605.mail.yahoo.com [206.190.38.210]) by mx1.FreeBSD.org (Postfix) with SMTP id 89E2D43D46 for ; Wed, 24 May 2006 03:14:30 +0000 (GMT) (envelope-from jay2xra@yahoo.com) Received: (qmail 86828 invoked by uid 60001); 24 May 2006 03:14:29 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=FQiiAhcObn418Uo5BtMvXbKezgmI1+E5QWsHqembUJauXAkf8vDaEGEJKNG9Fx/pooJXHPaNfmdWkx80JiBX0TcBeXr75nzkBuk9WD5vX7tnAyVL8LcO5TQR9ZZeqy9lYE99zQauW7H/RnJ6QbkgcYmlCEoUz0TgmnCHSBMc2UU= ; Message-ID: <20060524031429.86826.qmail@web51605.mail.yahoo.com> Received: from [202.90.158.202] by web51605.mail.yahoo.com via HTTP; Tue, 23 May 2006 20:14:29 PDT Date: Tue, 23 May 2006 20:14:29 -0700 (PDT) From: Mark Jayson Alvarez To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Anyone heard about Broadband over power lines??? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 03:14:31 -0000 Hi, A while ago, a group of individuals have demonstrated us with devices that can be used to extend your network throughout every corner of your company through the use of electric outlet... A quick googling tells me that such technologies are already existing long time ago and some Electric companies in other parts of the world also are now providing Internet services to their costumers at an added cost.. Do you know any ongoing opensource initiative regarding this technologies?? Thanks __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-net@FreeBSD.ORG Wed May 24 03:19:33 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5963A16A588 for ; Wed, 24 May 2006 03:19:33 +0000 (UTC) (envelope-from fooler@skyinet.net) Received: from smtp2.skyinet.net (smtp2.skyinet.net [202.78.97.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED6CD43D45 for ; Wed, 24 May 2006 03:19:32 +0000 (GMT) (envelope-from fooler@skyinet.net) Received: from fooler (fooler.ilo.skyinet.net [202.78.118.66]) by smtp2.skyinet.net (Postfix) with SMTP id B53995BA47; Wed, 24 May 2006 11:19:28 +0800 (PHT) Message-ID: <08bc01c67ee0$ddcd2120$42764eca@ilo.skyinet.net> From: "fooler" To: "Mark Jayson Alvarez" , References: <20060524031429.86826.qmail@web51605.mail.yahoo.com> Date: Wed, 24 May 2006 11:19:28 +0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 Cc: Subject: Re: Anyone heard about Broadband over power lines??? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 03:19:33 -0000 ----- Original Message ----- From: "Mark Jayson Alvarez" To: Sent: Wednesday, May 24, 2006 11:14 AM Subject: Anyone heard about Broadband over power lines??? > Hi, > > A while ago, a group of individuals have demonstrated > us with devices that can be used to extend your > network throughout every corner of your company > through the use of electric outlet... A quick googling > tells me that such technologies are already existing > long time ago and some Electric companies in other > parts of the world also are now providing Internet > services to their costumers at an added cost.. Do you > know any ongoing opensource initiative regarding this > technologies?? it is a hardware thing not a software thing... fooler. From owner-freebsd-net@FreeBSD.ORG Wed May 24 03:42:01 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 90E0216A800 for ; Wed, 24 May 2006 03:42:01 +0000 (UTC) (envelope-from oceanare@pacific.net.sg) Received: from smtpgate2.pacific.net.sg (smtpgate2.pacific.net.sg [203.120.90.32]) by mx1.FreeBSD.org (Postfix) with SMTP id A159B43D45 for ; Wed, 24 May 2006 03:42:00 +0000 (GMT) (envelope-from oceanare@pacific.net.sg) Received: (qmail 26049 invoked from network); 24 May 2006 03:41:57 -0000 Received: from maxwell2.pacific.net.sg (203.120.90.192) by smtpgate2.pacific.net.sg with SMTP; 24 May 2006 03:41:57 -0000 Received: from [192.168.0.107] ([210.24.123.195]) by maxwell2.pacific.net.sg with ESMTP id <20060524034156.EFBZ28656.maxwell2.pacific.net.sg@[192.168.0.107]>; Wed, 24 May 2006 11:41:56 +0800 Message-ID: <4473D5F7.7080204@pacific.net.sg> Date: Wed, 24 May 2006 11:41:43 +0800 From: Erich Dollansky Organization: oceanare pte ltd User-Agent: Thunderbird 1.5.0.2 (X11/20060501) MIME-Version: 1.0 To: Mark Jayson Alvarez References: <20060524031429.86826.qmail@web51605.mail.yahoo.com> In-Reply-To: <20060524031429.86826.qmail@web51605.mail.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Anyone heard about Broadband over power lines??? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 03:42:05 -0000 Hi, Mark Jayson Alvarez wrote: > Hi, > > A while ago, a group of individuals have demonstrated > us with devices that can be used to extend your yes, it works wonderful. But there is a huge but. It works wonderful as long as the data volume is low. The problem is that the powerlines are not shielded. Every bit of data going through a powerline transmit a signal in the radio frequency range. The frequency depends on many factors. The main problem is that it will interrupt the usage of those frequencies by their legal owners. The moment you hit the frequencies used by the military they will find the source and stop it. > long time ago and some Electric companies in other They use this also in many countries to read their own meters. But the large scale usage was or is blocked by the owners of the affeced frequencies. > know any ongoing opensource initiative regarding this > technologies?? You do not need much software to do it as the hardware speaks already TCP/IP. Erich From owner-freebsd-net@FreeBSD.ORG Wed May 24 06:15:05 2006 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CD2816A420; Wed, 24 May 2006 06:15:05 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mrout3.yahoo.com (mrout3.yahoo.com [216.145.54.173]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F3BE43D49; Wed, 24 May 2006 06:15:04 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from unknown-10-72-12-208.yahoo.com.neville-neil.com (proxy7.corp.yahoo.com [216.145.48.98]) by mrout3.yahoo.com (8.13.6/8.13.4/y.out) with ESMTP id k4O6DiMr095569; Tue, 23 May 2006 23:13:45 -0700 (PDT) Date: Tue, 23 May 2006 16:39:46 -0700 Message-ID: From: gnn@FreeBSD.org To: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= In-Reply-To: References: <20060506172742.GM15353@hoeg.nl> <445EC341.60406@freebsd.org> <20060508065841.GN15353@hoeg.nl> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50 (i386-apple-darwin8.5.1) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: "Bruce A. Mah" , Ed Schouten , FreeBSD Net Subject: Re: nd6_lookup prints bogus messages with point to point devices X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 06:15:05 -0000 At Tue, 23 May 2006 13:43:01 +0900, jinmei wrote: > Thanks, please do to. I believe the patch also fixes this problem > report: > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/93220 > > So, could you also confirm this and give feedback to (or close) the > report? (I'll send a follow-up message to the report by myself it > it's appropriate). > Will do. That was on my list to look at anyways. Thanks, George From owner-freebsd-net@FreeBSD.ORG Wed May 24 06:56:59 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C30316A420 for ; Wed, 24 May 2006 06:56:59 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from smtp-3.dlr.de (smtp-3.dlr.de [195.37.61.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 11BDA43D46 for ; Wed, 24 May 2006 06:56:58 +0000 (GMT) (envelope-from Hartmut.Brandt@dlr.de) Received: from beagle.kn.op.dlr.de ([129.247.173.6]) by smtp-3.dlr.de over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Wed, 24 May 2006 08:56:56 +0200 Date: Wed, 24 May 2006 08:56:56 +0200 (CEST) From: Harti Brandt X-X-Sender: brandt_h@beagle.kn.op.dlr.de To: Mark Jayson Alvarez In-Reply-To: <20060524031429.86826.qmail@web51605.mail.yahoo.com> Message-ID: <20060524085521.T13833@beagle.kn.op.dlr.de> References: <20060524031429.86826.qmail@web51605.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-OriginalArrivalTime: 24 May 2006 06:56:56.0945 (UTC) FILETIME=[3F3E5E10:01C67EFF] Cc: freebsd-net@freebsd.org Subject: Re: Anyone heard about Broadband over power lines??? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Harti Brandt List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 06:57:00 -0000 On Tue, 23 May 2006, Mark Jayson Alvarez wrote: MJA>Hi, MJA> MJA>A while ago, a group of individuals have demonstrated MJA>us with devices that can be used to extend your MJA>network throughout every corner of your company MJA>through the use of electric outlet... A quick googling MJA>tells me that such technologies are already existing MJA>long time ago and some Electric companies in other MJA>parts of the world also are now providing Internet MJA>services to their costumers at an added cost.. Do you MJA>know any ongoing opensource initiative regarding this MJA>technologies?? As somebody else said, that's a hardware thing. In any case there is an Austrian city (don't remember the name) where the provider is forced to put this down, because they cannot meet the requirements for off-band emission. harti From owner-freebsd-net@FreeBSD.ORG Wed May 24 08:16:24 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47B0316A609 for ; Wed, 24 May 2006 08:16:24 +0000 (UTC) (envelope-from oceanare@pacific.net.sg) Received: from smtpgate4.pacific.net.sg (smtpgate4.pacific.net.sg [203.81.36.24]) by mx1.FreeBSD.org (Postfix) with SMTP id 48B7B43D48 for ; Wed, 24 May 2006 08:16:22 +0000 (GMT) (envelope-from oceanare@pacific.net.sg) Received: (qmail 30654 invoked from network); 24 May 2006 08:16:20 -0000 Received: from maxwell2.pacific.net.sg (203.120.90.192) by smtpgate4.pacific.net.sg with SMTP; 24 May 2006 08:16:20 -0000 Received: from [192.168.0.107] ([210.24.123.195]) by maxwell2.pacific.net.sg with ESMTP id <20060524081619.IFYE28656.maxwell2.pacific.net.sg@[192.168.0.107]>; Wed, 24 May 2006 16:16:19 +0800 Message-ID: <44741644.7020308@pacific.net.sg> Date: Wed, 24 May 2006 16:16:04 +0800 From: Erich Dollansky Organization: oceanare pte ltd User-Agent: Thunderbird 1.5.0.2 (X11/20060501) MIME-Version: 1.0 To: Harti Brandt References: <20060524031429.86826.qmail@web51605.mail.yahoo.com> <20060524085521.T13833@beagle.kn.op.dlr.de> In-Reply-To: <20060524085521.T13833@beagle.kn.op.dlr.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Mark Jayson Alvarez Subject: Re: Anyone heard about Broadband over power lines??? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 08:16:24 -0000 Hi, Harti Brandt wrote: > On Tue, 23 May 2006, Mark Jayson Alvarez wrote: > > As somebody else said, that's a hardware thing. In any case there is an > Austrian city (don't remember the name) where the provider is forced to > put this down, because they cannot meet the requirements for off-band > emission. > the head quarter of the company is in Linz. I do not know if they are all over Austria or just in Upper Austria. Their name is something like Linz Power Line ... Erich From owner-freebsd-net@FreeBSD.ORG Wed May 24 08:43:03 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFD9216A514 for ; Wed, 24 May 2006 08:43:03 +0000 (UTC) (envelope-from lists@yazzy.org) Received: from mx1.yazzy.org (mx1.yazzy.org [84.247.145.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B1CE43D53 for ; Wed, 24 May 2006 08:43:00 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from mail.witelcom.com ([84.247.144.144] helo=marcin) by mx1.yazzy.org with esmtps (TLSv1:AES256-SHA:256) (YazzY.org) id 1Fiowj-0002mN-B0; Wed, 24 May 2006 10:42:28 +0200 Date: Wed, 24 May 2006 10:43:01 +0200 From: Marcin Jessa To: Mark Jayson Alvarez Message-ID: <20060524104301.5f171582@marcin> In-Reply-To: <20060524031429.86826.qmail@web51605.mail.yahoo.com> References: <20060524031429.86826.qmail@web51605.mail.yahoo.com> Organization: YazzY.org X-Mailer: Sylpheed-Claws 2.2.0 (GTK+ 2.8.12; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Score: -2.5 (--) Cc: freebsd-net@freebsd.org Subject: Re: Anyone heard about Broadband over power lines??? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 08:43:04 -0000 On Tue, 23 May 2006 20:14:29 -0700 (PDT) Mark Jayson Alvarez wrote: > Hi, > > A while ago, a group of individuals have demonstrated > us with devices that can be used to extend your > network throughout every corner of your company > through the use of electric outlet... A quick googling > tells me that such technologies are already existing > long time ago and some Electric companies in other > parts of the world also are now providing Internet > services to their costumers at an added cost.. Do you > know any ongoing opensource initiative regarding this > technologies?? I read both Google and IBM working on solutions like that. IBM works together with Centerpoint to supply people in Houston area with 7Mbit/s lines. According to news.com they hooked up 220 houses. Google invested about 100 million dollars in Current Communication Group - http://www.currentgroup.com/ which is working on the same thing. One of the el. companies here in Norway - Lyse Tele has about 300 pilot customers giving them 1mbit over power lines. They say they managed to reduce noise which could earlier affect devices like baby sitters. There are also end customer devices avaliable on the marked: http://www.devolo.com/co_EN/index.html http://www.netgear.com/products/details/XE104.php#performance read also http://www.homeplug.org/en/index.asp Cheers Marcin. From owner-freebsd-net@FreeBSD.ORG Wed May 24 09:13:25 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 68B0716A421 for ; Wed, 24 May 2006 09:13:25 +0000 (UTC) (envelope-from dmitry@atlantis.dp.ua) Received: from postman.atlantis.dp.ua (postman.atlantis.dp.ua [193.108.47.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C30143D46 for ; Wed, 24 May 2006 09:13:23 +0000 (GMT) (envelope-from dmitry@atlantis.dp.ua) Received: from smtp.atlantis.dp.ua (smtp.atlantis.dp.ua [193.108.46.231]) by postman.atlantis.dp.ua (8.13.1/8.13.1) with ESMTP id k4O9DDLk089722 for ; Wed, 24 May 2006 12:13:13 +0300 (EEST) (envelope-from dmitry@atlantis.dp.ua) Date: Wed, 24 May 2006 12:13:13 +0300 (EEST) From: Dmitry Pryanishnikov To: freebsd-net@freebsd.org Message-ID: <20060524114116.B43295@atlantis.atlantis.dp.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: IP fastforwarding in RELENG_4 and CURRENT/RELENG_6 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 09:13:25 -0000 Hello! What is the current status of the fast IP forwarding in RELENG_4 and in modern versions (CURRENT/RELENG_6)? I see that this code (either ip_flow.* in RELENG_4 or ip_fastfwd.c in RELENG_6) is always included into kernel (no separate option for it), but is disabled by default. What are drawbacks from enabling it (pure-IPv4 environment, heavy use of ipfw+divert+dummynet, occasionally use of IPSEC)? I haven't found any documentation for this option besides comments in ip_fastfwd.c, and those comments rose several questions: * Else if something is not pure IPv4 unicast forwarding we fall back to * the normal ip_input processing path. We should only be called from ----------------------------------------^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ * interfaces connected to the outside world. ---^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ How to achieve this aim? I see no fastforwarding-specific options in ifconfig. * IPSEC is not supported if this host is a tunnel broker. IPSEC is * supported for connections to/from local host. Is it true for FAST_IPSEC? Am I understand 'tunnel broker' correctly: it's the host that wraps other host's traffic into the ESP using IPSEC tunnel mode? How about IPSEC transport mode? And the main question: does this description stands for ip_flow implementation in RELENG_4? If not, what are the differences? Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: dmitry@atlantis.dp.ua nic-hdl: LYNX-RIPE From owner-freebsd-net@FreeBSD.ORG Wed May 24 10:02:58 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6550916A433 for ; Wed, 24 May 2006 10:02:58 +0000 (UTC) (envelope-from jhs@flat.berklix.net) Received: from thin.berklix.org (thin.berklix.org [194.246.123.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id C203A43D58 for ; Wed, 24 May 2006 10:02:57 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A5B92.dip.t-dialin.net [84.154.91.146]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id k4OA2sOx092699; Wed, 24 May 2006 12:02:55 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.net (8.12.11/8.12.11) with ESMTP id k4OA2rDF057505; Wed, 24 May 2006 12:02:53 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (localhost.jhs.private [127.0.0.1]) by fire.jhs.private (8.13.1/8.13.1) with ESMTP id k4OA5VjM042206; Wed, 24 May 2006 12:05:31 +0200 (CEST) (envelope-from jhs@fire.jhs.private) Message-Id: <200605241005.k4OA5VjM042206@fire.jhs.private> To: Marcin Jessa In-Reply-To: Message from Marcin Jessa of "Wed, 24 May 2006 10:43:01 +0200." <20060524104301.5f171582@marcin> Date: Wed, 24 May 2006 12:05:31 +0200 From: "Julian H. Stacey" Cc: freebsd-net@freebsd.org, Mark Jayson Alvarez Subject: Re: Anyone heard about Broadband over power lines??? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 10:02:58 -0000 Marcin Jessa wrote: > On Tue, 23 May 2006 20:14:29 -0700 (PDT) > Mark Jayson Alvarez wrote: > > > Hi, > > > > A while ago, a group of individuals have demonstrated > > us with devices that can be used to extend your > > network throughout every corner of your company > > through the use of electric outlet... A quick googling > > tells me that such technologies are already existing > > long time ago and some Electric companies in other > > parts of the world also are now providing Internet > > services to their costumers at an added cost.. Do you > > know any ongoing opensource initiative regarding this > > technologies?? http://www.vobis-shop.de/vobis/catalog/rubric.service?rubricid=101919 35.5 Euro Netgear XE102 Powerline Ethernet up to 14 M bit/s For in house use. Not to ISPs http://www.vobis-shop.de/vobis/catalog/factsheet1.service?articleid=124099 http://www.netgear.com/products/details/XE102.php Maybe for more info on what you want: cruise a few hardware manufacturer sites such as Netgear, find hardware that does what you want, then search with google or whoever, looking for hardware model numbers ? -- Julian Stacey. Consultant Unix Net & Sys. Eng., Munich. http://berklix.com Mail in Ascii, HTML=spam. Ihr Rauch = mein allergischer Kopfschmerz. From owner-freebsd-net@FreeBSD.ORG Wed May 24 12:22:23 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 42EAB16A467 for ; Wed, 24 May 2006 12:22:23 +0000 (UTC) (envelope-from nikolas.britton@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id EEDDA43D46 for ; Wed, 24 May 2006 12:22:21 +0000 (GMT) (envelope-from nikolas.britton@gmail.com) Received: by nz-out-0102.google.com with SMTP id l8so1447949nzf for ; Wed, 24 May 2006 05:22:21 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=aJQ7dHqj/kJ4B6wKpfyYWHrABCjkZtnbs7qoyoPfuQB/39I0H6T0jxbILULkYJAQrIajKzzZ/YysaTB86LOAg1C5D4agrdWRn8DV3wh2nQtPX9ZdsPIN0OQSg77YAn691j9bDiA9OYcY3NFCeUJ7tKQ7hlRz+J0mFqBZOudlJEs= Received: by 10.36.41.18 with SMTP id o18mr223014nzo; Wed, 24 May 2006 05:22:20 -0700 (PDT) Received: by 10.36.104.17 with HTTP; Wed, 24 May 2006 05:22:20 -0700 (PDT) Message-ID: Date: Wed, 24 May 2006 07:22:20 -0500 From: "Nikolas Britton" To: "Mark Jayson Alvarez" In-Reply-To: <20060524031429.86826.qmail@web51605.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060524031429.86826.qmail@web51605.mail.yahoo.com> Cc: freebsd-net@freebsd.org Subject: Re: Anyone heard about Broadband over power lines??? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 12:22:28 -0000 On 5/23/06, Mark Jayson Alvarez wrote: > Hi, > > A while ago, a group of individuals have demonstrated > us with devices that can be used to extend your > network throughout every corner of your company > through the use of electric outlet... A quick googling > tells me that such technologies are already existing > long time ago and some Electric companies in other > parts of the world also are now providing Internet > services to their costumers at an added cost.. Do you > know any ongoing opensource initiative regarding this > technologies?? > > Thanks > > The 'in-building' kind is called HomePlug. It's a good alternative when wireless, and wired, technology is infeasible. When setup correctly it's link stability is greater then 802.11x, but expect speeds in the range of 4 - 10Mbps and about half the range of a typical LOS wireless link. YMMV, oh and the spec does include encryption, 56-bit DES I believe. For the most flexibility look for Ethernet bridge devices. The other one your thinking of is called BPL, Broadband over Power Line: http://www.arrl.org/bpl/ A better solution to BPL is fiber on the poles and wireless for the 'last mile', they already have the easements to set everything up but are just to lazy to do it. --=20 BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ From owner-freebsd-net@FreeBSD.ORG Wed May 24 13:15:39 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D12BC16A427 for ; Wed, 24 May 2006 13:15:39 +0000 (UTC) (envelope-from marko.lerota@zg.t-com.hr) Received: from redcloud.optima-telekom.hr (tirnanog.iskon.hr [213.191.139.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id 513C643D5A for ; Wed, 24 May 2006 13:15:31 +0000 (GMT) (envelope-from marko.lerota@zg.t-com.hr) Received: (qmail 26784 invoked by uid 1001); 24 May 2006 13:15:42 -0000 To: Nash Nipples Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEWgnbRLVpRNVY9jMRPh s21jSlEyNVX45Mv4zI+sbUclFAtMVpT8V0lFAAACZ0lEQVR4nG3Tv2vbQBQHcFMogWyeNeVK BLXGl5j6xnABOaNTuXFGmWpwtw519yj4soW6AatT4GKD3+aDZrl/rt/Tr9qlGiz7Pn7v3bsf HVc/NrIiSfElqH53GgijcCqzk/+AmBF5cN0DsFlIRGMh/oHuqxkTM6VlzB4EoZEs2aSZOASb EQJYZpweQshE697GTDndBXtgp9LIT9+OpDGHEfb9knk+nx+jfN1JCVZMCl6XwFm0a2EXztZD 3s4fj47ZbKI2VeBmJImeEfGLJ+M9sDPilX7IB5rN6sdfcGhuoHU+LC4nxfnI7YOJtdb95Gb+ fbgJ2uJ2ZgaA++f5ZzBqNCCYfMTd5q0BfBVNqm7I8gUjQ+YtXotRW6PH9AEj+dKs/KuNQAl5 o/NY+QkonW8aQAl0oXMYPvRiXIM4pRJifbXytnhTA8alBx/jefG2ar3DBlt34/PXz9M+nMVN iNaPUdCApJc2ItejOmLGoK1qQLV9pJmXBnL10DYoBA5aHNfj8ZNwZa5O4CzgTJeilKJmrQJs IHIt1/7/Sg2p3iq/Hz0/5W05rq4M9aN2B5FLohUP4ylVyfxhEIjAs8J4PhIJ9U+CEroogib5 BXAf7bB4vkfAzgPFt1tM9sJZAOH+lCexhwswuNtim4QTZdokqo4o89LkH7V6iFxICeqfp+Wh fmUuGPunLj2Meti6Cn4DjJ/UReROqR+aqawAi/JkfgKE64rrfkhjU8MtT8ivR4S5n6Yo08A7 HvgAlHDWRSGlNSDxwK9HtXy4FS2I60EdUIJM+Ut9OZNJG4CpbEQW1VBQoQoPuBw2EVa4P0u0 TgzQF+VoAAAAAElFTkSuQmCC In-Reply-To: <20060523135201.75470.qmail@web36303.mail.mud.yahoo.com> (Nash Nipples's message of "Tue, 23 May 2006 06:52:01 -0700 (PDT)") References: <20060523135201.75470.qmail@web36303.mail.mud.yahoo.com> From: Marko Lerota Organization: Unix Users - Fanatics Dept. X-Request-PGP: X-GNUPG-Fingerprint: CF5E 6862 2777 A471 5D2E 0015 8DA6 D56D 17E5 2A51 Date: Wed, 24 May 2006 15:15:42 +0200 Message-ID: <86vervva0x.fsf@redcloud.local> User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.5-b26 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-net@freebsd.org Subject: Re: nfsd and CPU/performance problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 13:15:40 -0000 Nash Nipples writes: > Hi Marko, > > Actually i dont find that load critical. I think those lines well tell that actually the process is running 581m42s and now it utilizes 13.48% Sometimes it was 80% > which sounds like a "kernel tuning issue" if you have excluded nfsserver out of your kernel config last time u were compiling it. if you didnt just skip this part at this time. > please make sure that the following lines do exist > options NFSCLIENT # Network Filesystem Client > options NFSSERVER # Network Filesystem Server > options NFS_ROOT # NFS usable as /, requires NFSCLIENT No > These options are added in rc.conf and server now works correctly. > > rpc_lockd_enable="YES" > rpc_statd_enable="YES" It didn't help. Now cpu is like it should be, but BSD crashes twice a day with nothing in logs that I can find. I think RedHat clients or NetScreen firewall are the one to blame. -- Marko Lerota Sektor za nadzor i upravljanje OT - Optima Telekom d.o.o. Tel: 01 5492-161 Fax: 01 5492-109 http://www.optima.hr From owner-freebsd-net@FreeBSD.ORG Wed May 24 13:23:41 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 42F6C16A439 for ; Wed, 24 May 2006 13:23:41 +0000 (UTC) (envelope-from michel.gravey@7ici.biz) Received: from cocac.o.la (ds084-096-074-040.hosting.mediationtelecom.net [84.96.74.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1216143D49 for ; Wed, 24 May 2006 13:23:40 +0000 (GMT) (envelope-from michel.gravey@7ici.biz) Received: from localhost (webmail.7ici.biz [192.168.0.66]) by cocac.o.la (Postfix) with ESMTP id 3CD9773036 for ; Wed, 24 May 2006 15:23:47 +0200 (CEST) X-Virus-Scanned: amavisd-new at o.la X-Spam-Score: -3.387 X-Spam-Level: X-Spam-Status: No, score=-3.387 tagged_above=-20 required=4.31 tests=[ALL_TRUSTED=-1.8, AWL=1.012, BAYES_00=-2.599] Received: from cocac.o.la ([192.168.0.66]) by localhost (cocac.o.la [192.168.0.66]) (amavisd-new, port 10024) with ESMTP id EaY7zAuJQ5DE for ; Wed, 24 May 2006 15:23:46 +0200 (CEST) Received: by cocac.o.la (Postfix, from userid 80) id A37D47302F; Wed, 24 May 2006 15:23:46 +0200 (CEST) Received: from ARennes-351-1-110-83.w86-214.abo.wanadoo.fr (ARennes-351-1-110-83.w86-214.abo.wanadoo.fr [86.214.148.83]) by webmail.7ici.biz (Horde MIME library) with HTTP; Wed, 24 May 2006 15:23:46 +0200 Message-ID: <20060524152346.e4v0qc89w48g4cws@webmail.7ici.biz> Date: Wed, 24 May 2006 15:23:46 +0200 From: Michel Gravey To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=_4is5wj8fl2ck" Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.1) / FreeBSD-6.0 Subject: question about MPSAFE network stack disabled X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 13:23:41 -0000 This message is in MIME format. --=_4is5wj8fl2ck Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit Hello all, I've got the following message during boot (on a 6.1 release custom kernel) : WARNING: MPSAFE network stack disabled, expect reduced performance. I do not use ipv6 nor ipsec, and they are disabled in my kernel config. The network driver used is bge. bpf, pf and altq are set, but I don't know if they can cause the network stack to fallback in non-mpsafe mode. You will find my dmesg and kernel conf attached. Would you please help me to find the cause of that message, to fix the resulting degraded performance induced by that problem. Please answer on my email, since I'm not a subscribed user of the freebsd-net mailing list for now. Thanks in advance, Michel Gravey ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. --=_4is5wj8fl2ck Content-Type: application/octet-stream; name="PENEOX" Content-Disposition: attachment; filename="PENEOX" Content-Transfer-Encoding: 7bit # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.429.2.4 2005/10/28 19:21:27 jhb Exp $ machine i386 #cpu I486_CPU #cpu I586_CPU cpu I686_CPU ident PENEOX # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. #makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols #options SCHED_ULE # ULE scheduler options SCHED_4BSD # 4BSD scheduler options PREEMPTION # Enable kernel thread preemption options INET # InterNETworking #options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories #options MD_ROOT # MD is a potential root device #options NFSCLIENT # Network Filesystem Client #options NFSSERVER # Network Filesystem Server #options NFS_ROOT # NFS usable as /, requires NFSCLIENT #options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_GPT # GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev #options AHC_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~128k to driver. #options AHD_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~215k to driver. options ADAPTIVE_GIANT # Giant mutex is adaptive. device apic # I/O APIC options QUOTA # PF and ALTQ support device pf device pflog device pfsync options ALTQ options ALTQ_CBQ # Class Bases Queuing (CBQ) options ALTQ_RED # Random Early Detection (RED) #options ALTQ_RIO # RED In/Out #options ALTQ_HFSC # Hierarchical Packet Scheduler (HFSC) options ALTQ_PRIQ # Priority Queuing (PRIQ) options ALTQ_NOPCC # Required for SMP build options SMP # Bus support. #device eisa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata #device atadisk # ATA disk drives #device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives options ATA_STATIC_ID # Static device numbering # SCSI Controllers device ahc # AHA2940 and onboard AIC7xxx devices # SCSI peripherals device scbus # SCSI bus (required for SCSI) #device ch # SCSI media changers device da # Direct Access (disks) #device sa # Sequential Access (tape etc) #device cd # CD device pass # Passthrough device (direct SCSI access) #device ses # SCSI Environmental Services (and SAF-TE) # RAID controllers interfaced to the SCSI subsystem device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID options ASR_COMPAT # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc device agp # support several AGP chipsets # Power management support (see NOTES for more options) #device apm # Add suspend/resume support for the i8254. device pmtimer # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device bge # Broadcom BCM570xx Gigabit Ethernet # Pseudo devices. device loop # Network loopback device random # Entropy device device ether # Ethernet support #device sl # Kernel SLIP #device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device gif # IPv6 and IPv4 tunneling device faith # IPv6-to-IPv4 relaying (translation) # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # Note that 'bpf' is required for DHCP. device bpf # Berkeley packet filter --=_4is5wj8fl2ck Content-Type: application/octet-stream; name="dmesg.PENEOX" Content-Disposition: attachment; filename="dmesg.PENEOX" Content-Transfer-Encoding: 7bit Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-RELEASE #0: Tue May 23 15:16:37 CEST 2006 root@server:/usr/src/sys/i386/compile/PENEOX WARNING: MPSAFE network stack disabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2782.68-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf27 Stepping = 7 Features=0xbfebfbff Features2=0x4400> real memory = 3757965312 (3583 MB) avail memory = 3682856960 (3512 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 6 ioapic0: Changing APIC ID to 8 ioapic1: Changing APIC ID to 9 ioapic2: Changing APIC ID to 10 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-15 on motherboard ioapic1 irqs 16-31 on motherboard ioapic2 irqs 32-47 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 4.0 (no driver attached) pci0: at device 4.1 (no driver attached) pci0: at device 4.2 (no driver attached) pci0: at device 14.0 (no driver attached) atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x8b0-0x8bf at device 15.1 on pci0 ata0: on atapci0 ata1: on atapci0 pci0: at device 15.2 (no driver attached) isab0: at device 15.3 on pci0 isa0: on isab0 pcib1: on acpi0 pci5: on pcib1 pcib2: at device 8.0 on pci5 pci6: on pcib2 ahc0: port 0xcc00-0xccff mem 0xf7cff000-0xf7cfffff irq 30 at device 6.0 on pci6 ahc0: [GIANT-LOCKED] aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs ahc1: port 0xc800-0xc8ff mem 0xf7cfe000-0xf7cfefff irq 31 at device 6.1 on pci6 ahc1: [GIANT-LOCKED] aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs pcib3: on acpi0 pci4: on pcib3 bge0: mem 0xf7f10000-0xf7f1ffff irq 28 at device 6.0 on pci4 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:06:5b:f3:a7:c8 bge0: [GIANT-LOCKED] bge1: mem 0xf7f00000-0xf7f0ffff irq 29 at device 8.0 on pci4 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:06:5b:f3:a7:c9 bge1: [GIANT-LOCKED] pcib4: on acpi0 pci3: on pcib4 pcib5: on acpi0 pci1: on pcib5 pcib6: at device 8.0 on pci1 pci2: on pcib6 asr0: mem 0xf8000000-0xfbffffff irq 20 at device 8.1 on pci1 asr0: [GIANT-LOCKED] asr0: ADAPTEC 3410S FW Rev. 370F, 4 channel, 256 CCBs, Protocol I2O fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc7fff,0xc8000-0xcdfff,0xec000-0xeffff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec acd0: CDROM at ata0-master UDMA33 Waiting 5 seconds for SCSI devices to settle pass1 at asr0 bus 0 target 6 lun 0 pass1: Fixed Processor SCSI-2 device pass2 at asr0 bus 1 target 6 lun 0 pass2: Fixed Processor SCSI-2 device da0 at asr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Tagged Queueing Enabled da0: 140012MB (286744576 512 byte sectors: 255H 63S/T 17849C) SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/da0s1a bge1: link state changed to UP --=_4is5wj8fl2ck-- From owner-freebsd-net@FreeBSD.ORG Wed May 24 13:53:05 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6330B16A4CB for ; Wed, 24 May 2006 13:53:05 +0000 (UTC) (envelope-from steinex@nognu.de) Received: from shodan.nognu.de (shodan.nognu.de [85.14.216.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id D929143D46 for ; Wed, 24 May 2006 13:53:04 +0000 (GMT) (envelope-from steinex@nognu.de) Received: by shodan.nognu.de (Postfix, from userid 1002) id B177DB857; Wed, 24 May 2006 15:53:02 +0200 (CEST) Date: Wed, 24 May 2006 15:53:02 +0200 From: Frank Steinborn To: Michel Gravey Mail-Followup-To: Michel Gravey , freebsd-net@freebsd.org References: <20060524152346.e4v0qc89w48g4cws@webmail.7ici.biz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060524152346.e4v0qc89w48g4cws@webmail.7ici.biz> User-Agent: mutt-ng/devel-r804 (FreeBSD) Message-Id: <20060524135302.B177DB857@shodan.nognu.de> Cc: freebsd-net@freebsd.org Subject: Re: question about MPSAFE network stack disabled X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 13:53:05 -0000 Michel Gravey wrote: > Hello all, > I've got the following message during boot (on a 6.1 release custom kernel) > WARNING: MPSAFE network stack disabled, expect reduced performance. [...] > Would you please help me to find the cause of that message, to fix the > resulting degraded performance induced by that problem. First: What version are you running? IIRC, MPSAFE was disabled somewhere in the early stages of 5.x - are you running such a version? Second, please check your /boot/loader.conf - could it be that you added that line: debug.mpsafenet="0"? If so, remove it. It's only needed to workaround a bug in FreeBSD-pf AFAIK. From owner-freebsd-net@FreeBSD.ORG Wed May 24 14:56:58 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 254DB16A774 for ; Wed, 24 May 2006 14:56:58 +0000 (UTC) (envelope-from steinex@nognu.de) Received: from shodan.nognu.de (shodan.nognu.de [85.14.216.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4449E43D6A for ; Wed, 24 May 2006 14:56:52 +0000 (GMT) (envelope-from steinex@nognu.de) Received: by shodan.nognu.de (Postfix, from userid 1002) id 30515B856; Wed, 24 May 2006 16:56:51 +0200 (CEST) Date: Wed, 24 May 2006 16:56:50 +0200 From: Frank Steinborn To: Michel Gravey Mail-Followup-To: Michel Gravey , freebsd-net@freebsd.org References: <20060524152346.e4v0qc89w48g4cws@webmail.7ici.biz> <20060524135302.B177DB857@shodan.nognu.de> <20060524164758.3oe58zft0k8kwow4@webmail.7ici.biz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060524164758.3oe58zft0k8kwow4@webmail.7ici.biz> User-Agent: mutt-ng/devel-r804 (FreeBSD) Message-Id: <20060524145651.30515B856@shodan.nognu.de> Cc: freebsd-net@freebsd.org Subject: Re: question about MPSAFE network stack disabled X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 14:56:58 -0000 Michel Gravey wrote: > Hi Frank, > > I'm runnning a 6.1 release, installed first as 5.3 release in the past. > > Your trick does fix the warning (removing debug.mpsafenet line in > loader.conf). > > Since I'm using pf, does the bug you mentionned still be in the 6.1 release > (don't think so but I prefer to ask ?) > > Thanks again for your help, > > Michel Gravey The bug is not fixed yet. However, you only need to set debug.mpsafenet to 0, if you use the "group" and/or "user" filter parameters in your pf.conf. If you don't need filtering of user/groups, just leave debug.mpsafenet out of your loader.conf and it's okay. However, I depend on user/group filtering and had to set debug.mpsafenet too, so I get the same warning at bootup. I really don't see any noticeable problems with performance in cause of that, so you are safe to leave it in. The warning-message is not so bad as it seems, just don't worry. HTH, Frank From owner-freebsd-net@FreeBSD.ORG Wed May 24 16:22:20 2006 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F0E6B16A59A for ; Wed, 24 May 2006 16:22:20 +0000 (UTC) (envelope-from steinex@nognu.de) Received: from shodan.nognu.de (shodan.nognu.de [85.14.216.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8669D43D49 for ; Wed, 24 May 2006 16:22:20 +0000 (GMT) (envelope-from steinex@nognu.de) Received: by shodan.nognu.de (Postfix, from userid 1002) id 96616B856; Wed, 24 May 2006 18:22:18 +0200 (CEST) Date: Wed, 24 May 2006 18:22:18 +0200 From: Frank Steinborn To: net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: mutt-ng/devel-r804 (FreeBSD) Message-Id: <20060524162218.96616B856@shodan.nognu.de> Cc: Subject: Re: question about MPSAFE network stack disabled X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 16:22:21 -0000 ----- Forwarded message from Michel Gravey ----- Date: Wed, 24 May 2006 18:16:08 +0200 From: Michel Gravey To: Frank Steinborn Subject: Re: question about MPSAFE network stack disabled Message-ID: <20060524181608.eqjt8wsrz4ogw8g8@webmail.7ici.biz> User-Agent: Internet Messaging Program (IMP) H3 (4.1) / FreeBSD-6.0 Ok thanks for all the precise informations you gave me. Since I do not rely on such parameters, I'll keep my loader.conf without that line. Personnally, I didn't do any benchmarks with or without that parameters but the performance before was quite acceptable. (maybe better now, I did'nt notice it.) That warning was really bad, that's why I have post. Bye Michel Gravey Quoting Frank Steinborn : >Michel Gravey wrote: >>Hi Frank, >> >>I'm runnning a 6.1 release, installed first as 5.3 release in the past. >> >>Your trick does fix the warning (removing debug.mpsafenet line in >>loader.conf). >> >>Since I'm using pf, does the bug you mentionned still be in the 6.1 >>release >>(don't think so but I prefer to ask ?) >> >>Thanks again for your help, >> >>Michel Gravey > >The bug is not fixed yet. However, you only need to set >debug.mpsafenet to 0, if you use the "group" and/or "user" filter >parameters in your pf.conf. If you don't need filtering of user/groups, >just leave debug.mpsafenet out of your loader.conf and it's okay. > >However, I depend on user/group filtering and had to set >debug.mpsafenet too, so I get the same warning at bootup. I really >don't see any noticeable problems with performance in cause of that, >so you are safe to leave it in. The warning-message is not so bad as >it seems, just don't worry. > >HTH, >Frank > -- Michel Gravey www.7ici.biz phone: +33(0)682837863 fax: +33(0)229001387 ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. ----- End forwarded message ----- From owner-freebsd-net@FreeBSD.ORG Wed May 24 17:49:44 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DDD7A16A808 for ; Wed, 24 May 2006 17:49:44 +0000 (UTC) (envelope-from yamamoto436@oki.com) Received: from iscan1.intra.oki.co.jp (okigate.oki.co.jp [202.226.91.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE38A43D4C for ; Wed, 24 May 2006 17:49:41 +0000 (GMT) (envelope-from yamamoto436@oki.com) Received: from aoi.bmc.oki.co.jp (IDENT:root@localhost.localdomain [127.0.0.1]) by iscan1.intra.oki.co.jp (8.9.3/8.9.3) with SMTP id CAA04110 for ; Thu, 25 May 2006 02:49:39 +0900 Received: (qmail 2137 invoked from network); 25 May 2006 02:49:39 +0900 Received: from tulip.bmc.oki.co.jp (172.19.236.119) by aoi.bmc.oki.co.jp with SMTP; 25 May 2006 02:49:39 +0900 Received: from localhost (tulip.bmc.oki.co.jp [172.19.236.119]) by tulip.bmc.oki.co.jp (8.13.6/8.13.6) with ESMTP id k4OHncvW025052; Thu, 25 May 2006 02:49:39 +0900 (JST) (envelope-from yamamoto436@oki.com) Date: Thu, 25 May 2006 02:49:38 +0900 (JST) Message-Id: <20060525.024938.74731993.yamamoto436@oki.com> To: freebsd-net@freebsd.org, freebsd-pf@freebsd.org From: Hideki Yamamoto In-Reply-To: <20060508.054451.41688849.yamamoto436@oki.com> References: <20060508.054451.41688849.yamamoto436@oki.com> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Subject: Re: IPv6 raw socket to send original udp X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 17:49:45 -0000 Hi, One of my collegues helped me. bpf described in the following page is useful. http://canmore.sdf-eu.org/freebsd/bpf.html And libdnet is a wrapper of the bpf on FreeBSD. Code using libdnet seems to be portable with Linux and so on. From: Hideki Yamamoto Subject: IPv6 raw socket to send original udp Date: Mon, 08 May 2006 05:44:51 +0900 (JST) Message-ID: <20060508.054451.41688849.yamamoto436@oki.com> > > Hi, > > I tried to use pf as a traffic shaper for a streaming server, but > it does not work well. Input of pf is bursted packets within around 20 > msec, but is not bursted packets within around 100 msec or longer. > This traffic pattern is the feature of the streaming server. > > As pf is does not work well, I am thinking designinig original shaper > command on bridge-like freebsd box, and that the command will receive > the sever packet via libpcap, shape it and then send it constantly to > another device. To send packet from bridge-like freebsd box, I plan > to use RAW IPV6 socket. However in my small experiment, it does not > seems good, IP_HDRINCL option does not woks. > > I wonder if IPv6 raw socket can be used only for ICMPv6. > I would like to use IPv6 raw socket for original udp packet. > > Thanks in advance. > > Hideki Yamamoto > -- > > > _______________________________________________ > freebsd-pf@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-pf > To unsubscribe, send any mail to "freebsd-pf-unsubscribe@freebsd.org" --- From owner-freebsd-net@FreeBSD.ORG Wed May 24 19:53:16 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 98F8D16A435 for ; Wed, 24 May 2006 19:53:16 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAEF443D76 for ; Wed, 24 May 2006 19:53:09 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 92C961A4EAB; Wed, 24 May 2006 12:53:09 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 054B151616; Wed, 24 May 2006 15:53:08 -0400 (EDT) Date: Wed, 24 May 2006 15:53:08 -0400 From: Kris Kennaway To: Marko Lerota Message-ID: <20060524195308.GA87701@xor.obsecurity.org> References: <20060523135201.75470.qmail@web36303.mail.mud.yahoo.com> <86vervva0x.fsf@redcloud.local> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5vNYLRcllDrimb99" Content-Disposition: inline In-Reply-To: <86vervva0x.fsf@redcloud.local> User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@freebsd.org, Nash Nipples Subject: Re: nfsd and CPU/performance problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 19:53:18 -0000 --5vNYLRcllDrimb99 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 24, 2006 at 03:15:42PM +0200, Marko Lerota wrote: > Nash Nipples writes: >=20 > > Hi Marko, > > > > Actually i dont find that load critical. I think those lines well tell = that actually the process is running 581m42s and now it utilizes 13.48%=20 >=20 > Sometimes it was 80% >=20 > > which sounds like a "kernel tuning issue" if you have excluded nfsserve= r out of your kernel config last time u were compiling it. if you didnt jus= t skip this part at this time. > > please make sure that the following lines do exist > > options NFSCLIENT # Network Filesystem Client > > options NFSSERVER # Network Filesystem Server > > options NFS_ROOT # NFS usable as /, requires= NFSCLIENT >=20 > No=20 >=20 > > These options are added in rc.conf and server now works correctly. =20 > > > > rpc_lockd_enable=3D"YES" > > rpc_statd_enable=3D"YES" >=20 > It didn't help. See discussion on stable@ for what is believed to be the problem. Backing out the changes to vfs_lookup.c would work around the problem for now (although it reintroduces other bugs). > Now cpu is like it should be, but BSD crashes twice a day=20 > with nothing in logs that I can find. What do you mean "crashes" then? Do you need to configure crashdumps as described in the handbook and developers' handbook? Kris --5vNYLRcllDrimb99 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEdLmkWry0BWjoQKURAl9KAKCNtWcZ0haEzvxoiVaRmSMew+pevgCeLhR2 sYBKAFTj+ODVkalmykt16kI= =/kSc -----END PGP SIGNATURE----- --5vNYLRcllDrimb99-- From owner-freebsd-net@FreeBSD.ORG Wed May 24 21:00:11 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 42E7216A465 for ; Wed, 24 May 2006 21:00:11 +0000 (UTC) (envelope-from thompsa@freebsd.org) Received: from grunt5.ihug.co.nz (grunt5.ihug.co.nz [203.109.254.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 725BC43D48 for ; Wed, 24 May 2006 21:00:10 +0000 (GMT) (envelope-from thompsa@freebsd.org) Received: from 203-109-251-39.static.bliink.ihug.co.nz (heff.fud.org.nz) [203.109.251.39] by grunt5.ihug.co.nz with smtp (Exim 3.35 #1 (Debian)) id 1Fj0Se-00021z-00; Thu, 25 May 2006 09:00:09 +1200 Received: by heff.fud.org.nz (Postfix, from userid 1001) id CCC571CC1F; Thu, 25 May 2006 09:00:07 +1200 (NZST) Date: Thu, 25 May 2006 09:00:07 +1200 From: Andrew Thompson To: freebsd-net@freebsd.org Message-ID: <20060524210007.GB68191@heff.fud.org.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 Subject: interface notifications X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 21:00:12 -0000 Hi, I want to bring up the idea again of announcing all interfaces on creation/insert rather than just physical ones as it is right now. The difference will be that pseudo interfaces will be reported to devd and this lets actions be taken in userland. Anyone care to test. Andrew Index: etc/devd.conf =================================================================== RCS file: /home/ncvs/src/etc/devd.conf,v retrieving revision 1.32 diff -u -p -r1.32 devd.conf --- etc/devd.conf 16 Mar 2006 17:42:27 -0000 1.32 +++ etc/devd.conf 3 Apr 2006 00:21:00 -0000 @@ -28,17 +28,19 @@ options { # override these general rules. # -# For ethernet like devices start configuring the interface. Due to -# a historical accident, this script is called pccard_ether. +# Configure the interface on attach. Due to a historical accident, this +# script is called pccard_ether. # -attach 0 { - media-type "ethernet"; - action "/etc/pccard_ether $device-name start"; +notify 0 { + match "system" "IFNET"; + match "type" "ATTACH"; + action "/etc/pccard_ether $subsystem start"; }; -detach 0 { - media-type "ethernet"; - action "/etc/pccard_ether $device-name stop"; +notify 0 { + match "system" "IFNET"; + match "type" "DETACH"; + action "/etc/pccard_ether $subsystem stop"; }; # Index: sys/net/if.c =================================================================== RCS file: /home/ncvs/src/sys/net/if.c,v retrieving revision 1.255 diff -u -p -r1.255 if.c --- sys/net/if.c 21 Mar 2006 14:31:18 -0000 1.255 +++ sys/net/if.c 3 Apr 2006 00:22:22 -0000 @@ -505,6 +505,7 @@ if_attach(struct ifnet *ifp) if_attachdomain1(ifp); EVENTHANDLER_INVOKE(ifnet_arrival_event, ifp); + devctl_notify("IFNET", ifp->if_xname, "ATTACH", NULL); /* Announce the interface. */ rt_ifannouncemsg(ifp, IFAN_ARRIVAL); @@ -682,6 +683,7 @@ if_detach(struct ifnet *ifp) /* Announce that the interface is gone. */ rt_ifannouncemsg(ifp, IFAN_DEPARTURE); EVENTHANDLER_INVOKE(ifnet_departure_event, ifp); + devctl_notify("IFNET", ifp->if_xname, "DETACH", NULL); IF_AFDATA_LOCK(ifp); for (dp = domains; dp; dp = dp->dom_next) { From owner-freebsd-net@FreeBSD.ORG Wed May 24 23:38:48 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 69CE316A444 for ; Wed, 24 May 2006 23:38:48 +0000 (UTC) (envelope-from benjamin@cactus.org) Received: from cactus.org (linux.cactus.org [66.118.232.151]) by mx1.FreeBSD.org (Postfix) with SMTP id 007EF43D45 for ; Wed, 24 May 2006 23:38:47 +0000 (GMT) (envelope-from benjamin@cactus.org) Received: (qmail 8263 invoked by uid 2051); 24 May 2006 23:38:47 -0000 From: benjamin@cactus.org Date: Wed, 24 May 2006 18:38:46 -0500 To: freebsd-net@freebsd.org Message-ID: <20060524233846.GA8189@linux.cactus.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.5.1+cvs20040105i Subject: Blocking N consecutive packets with netgraph X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 23:38:48 -0000 I need to test a multicast streaming media application by selectively dropping packets in the network connecting the source to the viewer. The capability I need is to drop N consecutive packets, where N ranges from 1 to 50 and is chosen via the command line. I had hoped to do this with dummynet and ipfw, but apparently I can only drop packets with a specified probablity. The network topology for this method was to bridge two ethernet nics, then use dummynet pipes to vary the bandwith and packet loss rate. I also tested a method using ipfw to temporarily enable packet block rules using a short sleep interval, but there was only very coarse control of the number of packets blocked. Is it feasible to do this with netgraph? Please outline how this may be accomplihsed. TIA Tom Benjamin From owner-freebsd-net@FreeBSD.ORG Thu May 25 02:34:11 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DAA5016A420 for ; Thu, 25 May 2006 02:34:11 +0000 (UTC) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E3D443D4C for ; Thu, 25 May 2006 02:34:11 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [10.251.23.205]) ([10.251.23.205]) by a50.ironport.com with ESMTP; 24 May 2006 19:34:02 -0700 Message-ID: <44751799.8020405@elischer.org> Date: Wed, 24 May 2006 19:34:01 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.13) Gecko/20060414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: benjamin@cactus.org References: <20060524233846.GA8189@linux.cactus.org> In-Reply-To: <20060524233846.GA8189@linux.cactus.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Blocking N consecutive packets with netgraph X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 02:34:11 -0000 benjamin@cactus.org wrote: >I need to test a multicast streaming media application by selectively >dropping packets in the network connecting the source to the viewer. > >The capability I need is to drop N consecutive packets, where N ranges >from 1 to 50 and is chosen via the command line. > >I had hoped to do this with dummynet and ipfw, but apparently I can >only drop packets with a specified probablity. The network topology >for this method was to bridge two ethernet nics, then use dummynet pipes >to vary the bandwith and packet loss rate. > >I also tested a method using ipfw to temporarily enable packet block >rules using a short sleep interval, but there was only very coarse >control of the number of packets blocked. > >Is it feasible to do this with netgraph? Please outline how this may >be accomplihsed. > > Certainly it is as long as you are happy to write your own node. Now, don't be scared.. nodes are relatively simple to write. They can be loaded dynamically once written. check out all the nodes available at: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netgraph/ you can start easily with the "sample" node. change its name and compile it by adding a directory in the /sys/modules.netgraph directory, copying the Makefile from another one and modifying it accordingly. start hacking.. documantation is in: http://www.freebsd.org/cgi/man.cgi?query=netgraph&apropos=0&sektion=4&manpath=FreeBSD+7.0-current&format=html and all the other man pages for netgraph modules, >TIA > >Tom Benjamin >_______________________________________________ >freebsd-net@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-net >To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > From owner-freebsd-net@FreeBSD.ORG Thu May 25 12:59:44 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1939416A42C for ; Thu, 25 May 2006 12:59:44 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from smtp-3.dlr.de (smtp-3.dlr.de [195.37.61.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F3A743D4C for ; Thu, 25 May 2006 12:59:43 +0000 (GMT) (envelope-from Hartmut.Brandt@dlr.de) Received: from dlr.de ([172.21.151.2]) by smtp-3.dlr.de over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Thu, 25 May 2006 14:59:41 +0200 Message-ID: <4475AAFD.5080701@dlr.de> Date: Thu, 25 May 2006 15:02:53 +0200 From: Hartmut Brandt User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7b) Gecko/20040316 X-Accept-Language: en-us, en MIME-Version: 1.0 To: benjamin@cactus.org References: <20060524233846.GA8189@linux.cactus.org> In-Reply-To: <20060524233846.GA8189@linux.cactus.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 25 May 2006 12:59:42.0118 (UTC) FILETIME=[16B5F460:01C67FFB] Cc: freebsd-net@freebsd.org Subject: Re: Blocking N consecutive packets with netgraph X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 12:59:44 -0000 benjamin@cactus.org wrote: >I need to test a multicast streaming media application by selectively >dropping packets in the network connecting the source to the viewer. > >The capability I need is to drop N consecutive packets, where N ranges >from 1 to 50 and is chosen via the command line. > >I had hoped to do this with dummynet and ipfw, but apparently I can >only drop packets with a specified probablity. The network topology >for this method was to bridge two ethernet nics, then use dummynet pipes >to vary the bandwith and packet loss rate. > >I also tested a method using ipfw to temporarily enable packet block >rules using a short sleep interval, but there was only very coarse >control of the number of packets blocked. > >Is it feasible to do this with netgraph? Please outline how this may >be accomplihsed. > > Yes. Netgraph is really great for this kind of stuff. Four years ago I wrote a node that simulated a space ATM link. The entire thing controlled remotely via SNMP. Variable delay, various kinds of loss and so on. I got around 50MBit/sec throughput on a 2 CPU 1GHz machine, but the limiting factor was not the CPUs but the ATM cards. This year I did the same but for ethernet frames (to simulate a DVB-S2/RCS system). With two gigabit ethernet adaptors I get more than 100MBit/sec through the machine with a load in the order of 30%. It can probably do more, just didn't try it. Because you can load/unload the nodes without rebooting it is just great for development - just be a little careful not to crash the kernel. Your case should be easy: create a node with two hooks, connect them to the 'lower' hooks of the two ethernet nodes. Then in the receive function you just count the packets and drop as much as you need. What you don't drop you just send out the other hook. Control is via netgraph control messages. You just can enter them via ngctl. harti From owner-freebsd-net@FreeBSD.ORG Thu May 25 15:17:18 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1209F16A738 for ; Thu, 25 May 2006 15:17:18 +0000 (UTC) (envelope-from _pppp@mail.ru) Received: from f47.mail.ru (f47.mail.ru [194.67.57.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EA5C43D7B for ; Thu, 25 May 2006 15:17:17 +0000 (GMT) (envelope-from _pppp@mail.ru) Received: from mail by f47.mail.ru with local id 1FjHaN-000O9A-00 for freebsd-net@freebsd.org; Thu, 25 May 2006 19:17:15 +0400 Received: from [81.200.14.42] by koi.mail.ru with HTTP; Thu, 25 May 2006 19:17:15 +0400 From: dima <_pppp@mail.ru> To: freebsd-net@freebsd.org Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 X-Originating-IP: [81.200.14.42] Date: Thu, 25 May 2006 19:17:15 +0400 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Message-Id: Subject: CARP broken in 6.1 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dima <_pppp@mail.ru> List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 15:17:22 -0000 Assigning an IP address to a CARP interface leads to the new route table entry: UH 0 0 carp0 and such error in /var/log/messages: arp_rtrequest: bad gateway (!AF_LINK) Removing the entry manually seems to fix the issue. But I can't ping the CARP address from inside. From owner-freebsd-net@FreeBSD.ORG Thu May 25 15:22:34 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD63316A422 for ; Thu, 25 May 2006 15:22:34 +0000 (UTC) (envelope-from yb@bashibuzuk.net) Received: from a.6f2.net (a.6f2.net [213.189.5.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7334D43D4C for ; Thu, 25 May 2006 15:22:34 +0000 (GMT) (envelope-from yb@bashibuzuk.net) Received: by a.6f2.net (Postfix, from userid 66) id F3984BF8D2F; Thu, 25 May 2006 17:22:32 +0200 (CEST) Received: by cc.bashibuzuk.net (Postfix, from userid 1001) id 43456C207; Thu, 25 May 2006 17:22:28 +0200 (CEST) Date: Thu, 25 May 2006 17:22:28 +0200 From: Yann Berthier To: freebsd-net@freebsd.org Message-ID: <20060525152228.GL1424@bashibuzuk.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 7.0-CURRENT User-Agent: Mutt/1.5.11 Subject: netgraph on disc(4) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 15:22:35 -0000 Hello, I wanted to use ng_netflow on a disc interface, but it seems that no node is created for loopback and the like . Indeed, I found an old post from gnn@ dating back from march 2000 on this subject, along with the PR kern/17631. Is somebody reconsidering this idea by any chance ? thnaks, - yann From owner-freebsd-net@FreeBSD.ORG Thu May 25 15:52:33 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 697F516A7F1 for ; Thu, 25 May 2006 15:52:33 +0000 (UTC) (envelope-from marko.lerota@zg.t-com.hr) Received: from redcloud.optima-telekom.hr (tirnanog.iskon.hr [213.191.139.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0305743D48 for ; Thu, 25 May 2006 15:52:30 +0000 (GMT) (envelope-from marko.lerota@zg.t-com.hr) Received: (qmail 3612 invoked by uid 1001); 25 May 2006 15:52:42 -0000 To: dima <_pppp@mail.ru> Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEWgnbRLVpRNVY9jMRPh s21jSlEyNVX45Mv4zI+sbUclFAtMVpT8V0lFAAACZ0lEQVR4nG3Tv2vbQBQHcFMogWyeNeVK BLXGl5j6xnABOaNTuXFGmWpwtw519yj4soW6AatT4GKD3+aDZrl/rt/Tr9qlGiz7Pn7v3bsf HVc/NrIiSfElqH53GgijcCqzk/+AmBF5cN0DsFlIRGMh/oHuqxkTM6VlzB4EoZEs2aSZOASb EQJYZpweQshE697GTDndBXtgp9LIT9+OpDGHEfb9knk+nx+jfN1JCVZMCl6XwFm0a2EXztZD 3s4fj47ZbKI2VeBmJImeEfGLJ+M9sDPilX7IB5rN6sdfcGhuoHU+LC4nxfnI7YOJtdb95Gb+ fbgJ2uJ2ZgaA++f5ZzBqNCCYfMTd5q0BfBVNqm7I8gUjQ+YtXotRW6PH9AEj+dKs/KuNQAl5 o/NY+QkonW8aQAl0oXMYPvRiXIM4pRJifbXytnhTA8alBx/jefG2ar3DBlt34/PXz9M+nMVN iNaPUdCApJc2ItejOmLGoK1qQLV9pJmXBnL10DYoBA5aHNfj8ZNwZa5O4CzgTJeilKJmrQJs IHIt1/7/Sg2p3iq/Hz0/5W05rq4M9aN2B5FLohUP4ylVyfxhEIjAs8J4PhIJ9U+CEroogib5 BXAf7bB4vkfAzgPFt1tM9sJZAOH+lCexhwswuNtim4QTZdokqo4o89LkH7V6iFxICeqfp+Wh fmUuGPunLj2Meti6Cn4DjJ/UReROqR+aqawAi/JkfgKE64rrfkhjU8MtT8ivR4S5n6Yo08A7 HvgAlHDWRSGlNSDxwK9HtXy4FS2I60EdUIJM+Ut9OZNJG4CpbEQW1VBQoQoPuBw2EVa4P0u0 TgzQF+VoAAAAAElFTkSuQmCC In-Reply-To: (dima's message of "Thu, 25 May 2006 19:17:15 +0400") References: From: Marko Lerota Organization: Unix Users - Fanatics Dept. X-Request-PGP: X-GNUPG-Fingerprint: CF5E 6862 2777 A471 5D2E 0015 8DA6 D56D 17E5 2A51 Date: Thu, 25 May 2006 17:52:42 +0200 Message-ID: <86wtcadrud.fsf@redcloud.local> User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.5-b26 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-net@freebsd.org Subject: Re: CARP broken in 6.1 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 15:52:36 -0000 dima <_pppp@mail.ru> writes: > Assigning an IP address to a CARP interface leads to the new route table entry: > UH 0 0 carp0 Maybe this is OK? > and such error in /var/log/messages: > arp_rtrequest: bad gateway (!AF_LINK) > > Removing the entry manually seems to fix the issue. But I can't ping the CARP address from inside. I also see this in my logs. But everything is OK. I can ping it, ssh to it, and eveything else. -- One cannot sell the earth upon which the people walk Tacunka Witco From owner-freebsd-net@FreeBSD.ORG Thu May 25 16:14:22 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 035D516A899 for ; Thu, 25 May 2006 16:14:22 +0000 (UTC) (envelope-from sullrich@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 364C543D58 for ; Thu, 25 May 2006 16:14:21 +0000 (GMT) (envelope-from sullrich@gmail.com) Received: by py-out-1112.google.com with SMTP id s49so3128582pyc for ; Thu, 25 May 2006 09:14:20 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=js/xe42Pg5nt2XuNz0oM4ZjE2Y+otB2lx7MdyvlmJqepg4+sKaeQHRK2rFvXe1FR2+3aFEsAs974wWJzq3AaMAzx5AR4H1d8Hpvc+54jbPl+IlQgXrrUzXKw/YpvzLiM89+LlMmZSAy5kMZJB1puYfWTetL21DdJBUamuGbZ8og= Received: by 10.35.77.18 with SMTP id e18mr3093560pyl; Thu, 25 May 2006 09:14:20 -0700 (PDT) Received: by 10.35.94.6 with HTTP; Thu, 25 May 2006 09:14:20 -0700 (PDT) Message-ID: Date: Thu, 25 May 2006 12:14:20 -0400 From: "Scott Ullrich" To: "Marko Lerota" In-Reply-To: <86wtcadrud.fsf@redcloud.local> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <86wtcadrud.fsf@redcloud.local> Cc: dima <_pppp@mail.ru>, freebsd-net@freebsd.org Subject: Re: CARP broken in 6.1 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 16:14:28 -0000 On 5/25/06, Marko Lerota wrote: > > and such error in /var/log/messages: > > arp_rtrequest: bad gateway (!AF_LINK) This behavior has been the case for as long as CARP has been in the kernel. I have seen it ever since starting the pfSense project. It appears to be harmless in nature; I have never seen anything negative out of these diagnostic messages. Scott From owner-freebsd-net@FreeBSD.ORG Thu May 25 17:33:18 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E98F16AC4F for ; Thu, 25 May 2006 17:33:18 +0000 (UTC) (envelope-from ed@questinformation.com) Received: from mta-01.sdf.hosting.com (mta-01.sdf.hosting.com [65.182.208.99]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC01043D48 for ; Thu, 25 May 2006 17:33:17 +0000 (GMT) (envelope-from ed@questinformation.com) Received: from ss004.sdf.hosting.com (ss004.sdf.hosting.com [65.182.208.14]) by mta-01.sdf.hosting.com (8.13.4/8.13.4) with ESMTP id k4PHXGv8002389 for ; Thu, 25 May 2006 13:33:16 -0400 Received: from [65.42.141.49] (adsl-65-42-141-49.dsl.chcgil.ameritech.net [65.42.141.49]) by ss004.sdf.hosting.com (8.13.2/8.13.2) with ESMTP id k4PHXFJ0027715 for ; Thu, 25 May 2006 13:33:15 -0400 (EDT) X-HDC-Tracker: Thu, 25 May 2006 13:33:15 -0400 (EDT)||Edgar Pigg |[65.42.141.49]|ss004.sdf.hosting.com|k4PHXFJ0027715 Mime-Version: 1.0 (Apple Message framework v623) Content-Transfer-Encoding: 7bit Message-Id: <7f069fa78ec3dc019935486d1d960424@questinformation.com> Content-Type: text/plain; charset=US-ASCII; format=flowed To: freebsd-net@freebsd.org From: Ed Pigg Date: Thu, 25 May 2006 12:33:16 -0500 X-Mailer: Apple Mail (2.623) Received-SPF: none (ss004.sdf.hosting.com: domain of ed@questinformation.com does not designate permitted sender hosts) X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on mta-01.sdf.hosting.com X-Virus-Status: Clean Subject: Help moving from local lan to internet X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 17:33:19 -0000 Hi all. Please be kind. Help. I have been using a server to develop on and am prepared to move to the internet. I orginally set up the server on a 192.168.x.x network and have been using it for about a month. I want to move it to the internet and am having trouble configuring the network manually. I set the ip address with subnet mask and default router in /etc/rc.conf. I edited /etc/resolv.conf and changed the name servers to the correct name server address. Now when the server starts it hangs for aboutn 5 minutes when the "starting sshd" message is displayed. I can ping the name servers, but nslookup times out when querying well known web sites. I must have overlooked something or left something out? Any help appreciated. Ed Pigg From owner-freebsd-net@FreeBSD.ORG Thu May 25 17:54:14 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81F7E16A580 for ; Thu, 25 May 2006 17:54:14 +0000 (UTC) (envelope-from reed@pilchuck.reedmedia.net) Received: from pilchuck.reedmedia.net (pilchuck.reedmedia.net [209.166.74.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26AB843D4C for ; Thu, 25 May 2006 17:54:13 +0000 (GMT) (envelope-from reed@pilchuck.reedmedia.net) Received: from reed by pilchuck.reedmedia.net with local (Exim 4.44) id 1FjK2J-0006Kt-UT; Thu, 25 May 2006 10:54:15 -0700 Date: Thu, 25 May 2006 10:54:15 -0700 (PDT) From: "Jeremy C. Reed" To: Ed Pigg In-Reply-To: <7f069fa78ec3dc019935486d1d960424@questinformation.com> Message-ID: References: <7f069fa78ec3dc019935486d1d960424@questinformation.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: "Jeremy C. Reed" Cc: freebsd-net@freebsd.org Subject: Re: Help moving from local lan to internet X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 17:54:24 -0000 On Thu, 25 May 2006, Ed Pigg wrote: > Now when the server starts it hangs for aboutn 5 minutes when the "starting > sshd" message is displayed. I can ping the name servers, but nslookup times > out when querying well known web sites. I must have overlooked something or > left something out? Any help appreciated. Just because you can ping a nameserver doesn't mean that the name server is there (or available for you). You can easily test by using some other nameserver (unless you have some firewall restrictions somewhere). For example, does the following work for you? host www.freebsd.org NS0.FREEBSD.ORG Then also test using your IP for nameserver as listed in your /etc/resolv.conf (replace A.B.C.D below): host www.freebsd.org A.B.C.D Make sure your /etc/resolv.conf file is correct format and has correct name servers that you have permission to use. Or run named on your FreeBSD box and use it. Have a look at the handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-dns.html http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-configfiles.html Jeremy C. Reed echo '9,J8HD,fDGG8B@?:536FC5=8@I;C5?@H5B0D@5GBIELD54DL>@8L?:5GDEJ8LDG1' |\ sed ss,s50EBsg | tr 0-M 'p.wBt SgiIlxmLhan:o,erDsduv/cyP' From owner-freebsd-net@FreeBSD.ORG Thu May 25 18:01:04 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D24D416B20A for ; Thu, 25 May 2006 18:01:04 +0000 (UTC) (envelope-from _pppp@mail.ru) Received: from f24.mail.ru (f24.mail.ru [194.67.57.160]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7419743D5D for ; Thu, 25 May 2006 18:01:04 +0000 (GMT) (envelope-from _pppp@mail.ru) Received: from mail by f24.mail.ru with local id 1FjK8s-0006Bw-00; Thu, 25 May 2006 22:01:02 +0400 Received: from [81.200.14.42] by koi.mail.ru with HTTP; Thu, 25 May 2006 22:01:02 +0400 From: dima <_pppp@mail.ru> To: Scott Ullrich Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 X-Originating-IP: [81.200.14.42] Date: Thu, 25 May 2006 22:01:02 +0400 In-Reply-To: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Message-Id: Cc: freebsd-net@freebsd.org, Marko Lerota Subject: Re[2]: CARP broken in 6.1 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dima <_pppp@mail.ru> List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 18:01:20 -0000 > On 5/25/06, Marko Lerota wrote: > > > and such error in /var/log/messages: > > > arp_rtrequest: bad gateway (!AF_LINK) > > This behavior has been the case for as long as CARP has been in the > kernel. I have seen it ever since starting the pfSense project. > > It appears to be harmless in nature; I have never seen anything > negative out of these diagnostic messages. That's not true. I have several CARP deployments on 5.x. None of them either adds this route or writes anything to logs. From owner-freebsd-net@FreeBSD.ORG Thu May 25 18:07:08 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E452416B389 for ; Thu, 25 May 2006 18:07:08 +0000 (UTC) (envelope-from tfotoglidis@netscape.net) Received: from imo-d01.mx.aol.com (imo-d01.mx.aol.com [205.188.157.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2AAE943DC8 for ; Thu, 25 May 2006 18:06:57 +0000 (GMT) (envelope-from tfotoglidis@netscape.net) Received: from tfotoglidis@netscape.net by imo-d01.mx.aol.com (mail_out_v38_r7.5.) id 2.e9.15554116 (16239); Thu, 25 May 2006 14:06:48 -0400 (EDT) Received: from mblkn-m13 (mblkn-m13.mblk.aol.com [64.12.170.131]) by air-in03.mx.aol.com (v109.12) with ESMTP id MAILININ33-3f6f4475f238165; Thu, 25 May 2006 14:06:48 -0400 Date: Thu, 25 May 2006 14:06:48 -0400 Message-Id: <8C84E3D20420BCE-60C-FEDD@mblkn-m13.sysops.aol.com> From: tfotoglidis@netscape.net References: <7f069fa78ec3dc019935486d1d960424@questinformation.com> Received: from 81.149.156.243 by mblkn-m13.sysops.aol.com (64.12.170.131) with HTTP (WebMailUI); Thu, 25 May 2006 14:06:48 -0400 X-MB-Message-Source: WebUI X-MB-Message-Type: User In-Reply-To: <7f069fa78ec3dc019935486d1d960424@questinformation.com> X-Mailer: Netscape WebMail 17673 MIME-Version: 1.0 To: ed@questinformation.com, freebsd-net@freebsd.org X-AOL-IP: 64.12.170.131 X-Spam-Flag: NO Content-Type: text/plain; charset="us-ascii" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: Help moving from local lan to internet X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 18:07:18 -0000 I take it the name servers are not your, right? SSH gets problematic if DNS does not work properly.. Could it be a firewall problem? Do the name-servers know who you are (Is your host in the zone?). You can try dig @name-server some.box.here to query a specific NS, try doing this with your name servers.. thanos ____________________________________________ Visit www.7mphotos.com to upload and share pictures. -----Original Message----- From: Ed Pigg To: freebsd-net@freebsd.org Sent: Thu, 25 May 2006 12:33:16 -0500 Subject: Help moving from local lan to internet Hi all. Please be kind. Help. I have been using a server to develop on and am prepared to move to the internet. I orginally set up the server on a 192.168.x.x network and have been using it for about a month. I want to move it to the internet and am having trouble configuring the network manually. I set the ip address with subnet mask and default router in /etc/rc.conf. I edited /etc/resolv.conf and changed the name servers to the correct name server address. Now when the server starts it hangs for aboutn 5 minutes when the "starting sshd" message is displayed. I can ping the name servers, but nslookup times out when querying well known web sites. I must have overlooked something or left something out? Any help appreciated. Ed Pigg _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" ___________________________________________________ Try the New Netscape Mail Today! Virtually Spam-Free | More Storage | Import Your Contact List http://mail.netscape.com From owner-freebsd-net@FreeBSD.ORG Thu May 25 18:10:21 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 68C1916B3D1 for ; Thu, 25 May 2006 18:10:21 +0000 (UTC) (envelope-from ed@questinformation.com) Received: from mta-01.sdf.hosting.com (mta-01.sdf.hosting.com [65.182.208.99]) by mx1.FreeBSD.org (Postfix) with ESMTP id E22BD43D48 for ; Thu, 25 May 2006 18:10:20 +0000 (GMT) (envelope-from ed@questinformation.com) Received: from ss004.sdf.hosting.com (ss004.sdf.hosting.com [65.182.208.14]) by mta-01.sdf.hosting.com (8.13.4/8.13.4) with ESMTP id k4PIAEAQ008206; Thu, 25 May 2006 14:10:14 -0400 Received: from [65.42.141.49] (adsl-65-42-141-49.dsl.chcgil.ameritech.net [65.42.141.49]) by ss004.sdf.hosting.com (8.13.2/8.13.2) with ESMTP id k4PIACsd006814; Thu, 25 May 2006 14:10:13 -0400 (EDT) X-HDC-Tracker: Thu, 25 May 2006 14:10:12 -0400 (EDT)||Edgar Pigg |[65.42.141.49]|ss004.sdf.hosting.com|k4PIACsd006814 In-Reply-To: References: <7f069fa78ec3dc019935486d1d960424@questinformation.com> Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <25966be530ab7185d3e61ff179d8b7ce@questinformation.com> Content-Transfer-Encoding: 7bit From: Ed Pigg Date: Thu, 25 May 2006 13:10:13 -0500 To: "Jeremy C. Reed" X-Mailer: Apple Mail (2.623) Received-SPF: none (ss004.sdf.hosting.com: domain of ed@questinformation.com does not designate permitted sender hosts) X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on mta-01.sdf.hosting.com X-Virus-Status: Clean Cc: freebsd-net@freebsd.org Subject: Re: Help moving from local lan to internet X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 18:10:29 -0000 On May 25, 2006, at 12:54 PM, Jeremy C. Reed wrote: > On Thu, 25 May 2006, Ed Pigg wrote: > >> Now when the server starts it hangs for aboutn 5 minutes when the >> "starting >> sshd" message is displayed. I can ping the name servers, but nslookup >> times >> out when querying well known web sites. I must have overlooked >> something or >> left something out? Any help appreciated. > > Just because you can ping a nameserver doesn't mean that the name > server > is there (or available for you). > > You can easily test by using some other nameserver (unless you have > some > firewall restrictions somewhere). For example, does the following work > for > you? Thanks Jeremy! You made me go back and look at the firewall rules again. Sure enough I was only accepting upd 53 from the name servers on the development lan. Once I changed the rule everything worked as I expected. Ed Pigg From owner-freebsd-net@FreeBSD.ORG Thu May 25 18:46:19 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A86A616B5E9 for ; Thu, 25 May 2006 18:46:19 +0000 (UTC) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E0C443D55 for ; Thu, 25 May 2006 18:46:19 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [192.168.2.4]) ([10.251.60.46]) by a50.ironport.com with ESMTP; 25 May 2006 11:46:18 -0700 Message-ID: <4475FB7A.50202@elischer.org> Date: Thu, 25 May 2006 11:46:18 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.13) Gecko/20060414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Yann Berthier References: <20060525152228.GL1424@bashibuzuk.net> In-Reply-To: <20060525152228.GL1424@bashibuzuk.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: netgraph on disc(4) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 18:46:25 -0000 Yann Berthier wrote: I think that Gleb had some changes that allowed netgraph to attach to ANY interface. Gleb? > Hello, > > I wanted to use ng_netflow on a disc interface, but it seems that no > node is created for loopback and the like . Indeed, I found an old > post from gnn@ dating back from march 2000 on this subject, along > with the PR kern/17631. Is somebody reconsidering this idea by any > chance ? > > thnaks, > > - yann >_______________________________________________ >freebsd-net@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-net >To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > From owner-freebsd-net@FreeBSD.ORG Thu May 25 19:05:48 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9A5816B679 for ; Thu, 25 May 2006 19:05:48 +0000 (UTC) (envelope-from sullrich@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 873AC43D55 for ; Thu, 25 May 2006 19:05:45 +0000 (GMT) (envelope-from sullrich@gmail.com) Received: by py-out-1112.google.com with SMTP id s49so3178473pyc for ; Thu, 25 May 2006 12:05:45 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=NfpXkj6C10NSecVcwEjyiDMQrzH4Dlo2xxv/9maASyg7JEHDeJ0yyqaL4IxaYBF3ua1zNE1/To0IFHhc1PatDWTfD1pQ6s2wDeznxdcTaSl5mUs6yUYGnaNhhWzwKMg8BSVjRGRH4cJXY5/gjVUYi71JGCfXayk2d/Rw0TyXM0w= Received: by 10.35.8.1 with SMTP id l1mr1095647pyi; Thu, 25 May 2006 12:05:44 -0700 (PDT) Received: by 10.35.94.6 with HTTP; Thu, 25 May 2006 12:05:44 -0700 (PDT) Message-ID: Date: Thu, 25 May 2006 15:05:44 -0400 From: "Scott Ullrich" To: dima <_pppp@mail.ru> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: Cc: freebsd-net@freebsd.org, Marko Lerota Subject: Re: Re[2]: CARP broken in 6.1 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 19:06:03 -0000 On 5/25/06, dima <_pppp@mail.ru> wrote: > That's not true. I have several CARP deployments on 5.x. None of them eit= her adds this route or writes anything to logs. I cannot speak for 5.X. I speak only for RELENG_6_X. Looking back I cannot recall if this was the behavior that I saw when we where on 5.X. Either way it happens on 6.X in a lot of (search for "bad gateway" on http://forum.pfsense.com) pfSense installs and has became a FAQ rather quickly. Scott From owner-freebsd-net@FreeBSD.ORG Thu May 25 19:15:40 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4C2716B839 for ; Thu, 25 May 2006 19:15:40 +0000 (UTC) (envelope-from yb@bashibuzuk.net) Received: from a.6f2.net (a.6f2.net [213.189.5.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02A6D43D5F for ; Thu, 25 May 2006 19:15:33 +0000 (GMT) (envelope-from yb@bashibuzuk.net) Received: by a.6f2.net (Postfix, from userid 66) id 9CC4CBF8CF7; Thu, 25 May 2006 21:15:32 +0200 (CEST) Received: by cc.bashibuzuk.net (Postfix, from userid 1001) id ACC9EBFDC; Thu, 25 May 2006 21:15:04 +0200 (CEST) Date: Thu, 25 May 2006 21:15:04 +0200 From: Yann Berthier To: Julian Elischer Message-ID: <20060525191504.GN1424@bashibuzuk.net> References: <20060525152228.GL1424@bashibuzuk.net> <4475FB7A.50202@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4475FB7A.50202@elischer.org> X-Operating-System: FreeBSD 7.0-CURRENT User-Agent: Mutt/1.5.11 Cc: freebsd-net@freebsd.org Subject: Re: netgraph on disc(4) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 19:15:55 -0000 On Thu, 25 May 2006, at 11:46, Julian Elischer wrote: > Yann Berthier wrote: > > I think that Gleb had some changes that allowed netgraph to attach to > ANY interface. this may well be a pilot error on my side, i can very well miss something trivial i tried something like: + mkpeer disc0: netflow lower iface0 ngctl: send msg: No such file or directory and then found this post back in 2000, along with the PR, so i haven't looked further - yann From owner-freebsd-net@FreeBSD.ORG Fri May 26 06:43:18 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7FEDE16A7B4 for ; Fri, 26 May 2006 06:43:18 +0000 (UTC) (envelope-from rebehn@ant.uni-bremen.de) Received: from antsrv1.ant.uni-bremen.de (antsrv1.ant.uni-bremen.de [134.102.176.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18CDC43D48 for ; Fri, 26 May 2006 06:43:17 +0000 (GMT) (envelope-from rebehn@ant.uni-bremen.de) Received: from bremerhaven.ant.uni-bremen.de ([134.102.176.10]) by antsrv1.ant.uni-bremen.de with esmtp (Exim 4.62 (FreeBSD)) (envelope-from ) id 1FjW2U-0004Dy-E1; Fri, 26 May 2006 08:43:14 +0200 Message-ID: <4476A382.4040505@ant.uni-bremen.de> Date: Fri, 26 May 2006 08:43:14 +0200 From: Heinrich Rebehn User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.2) Gecko/20060405 SeaMonkey/1.0.1 MIME-Version: 1.0 To: Kris Kennaway References: <20060523135201.75470.qmail@web36303.mail.mud.yahoo.com> <86vervva0x.fsf@redcloud.local> <20060524195308.GA87701@xor.obsecurity.org> In-Reply-To: <20060524195308.GA87701@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Marko Lerota , Nash Nipples Subject: Re: nfsd and CPU/performance problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 06:43:18 -0000 Kris Kennaway wrote: [snip] > See discussion on stable@ for what is believed to be the problem. > Backing out the changes to vfs_lookup.c would work around the problem > for now (although it reintroduces other bugs). > Hi, since i am being bitten by the same bug, i would like to try that out. I am not sure however, which version of vfs_lookup.c i should revert to and what other bugs would be reintroduced by that. Our server has become really slow since the upgrade from 6.1-RC to 6.1, exactly as described on stable@. --Heinrich -- Heinrich Rebehn University of Bremen Physics / Electrical and Electronics Engineering - Department of Telecommunications - Phone : +49/421/218-4664 Fax : -3341 From owner-freebsd-net@FreeBSD.ORG Fri May 26 07:13:54 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0DCB916A4F5 for ; Fri, 26 May 2006 07:13:54 +0000 (UTC) (envelope-from freebsd@dir-slovenia.com) Received: from mail-gw.select-tech.si (ns1.select-tech.si [81.24.96.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CFE043D46 for ; Fri, 26 May 2006 07:13:52 +0000 (GMT) (envelope-from freebsd@dir-slovenia.com) Received: from stsrv.select-tech.si (stsrv.select-tech.si [193.77.112.44]) by mail-gw.select-tech.si (Postfix) with ESMTP id 6E82EAB617 for ; Fri, 26 May 2006 09:13:46 +0200 (CEST) Received: from prak (prak [193.77.112.82]) by stsrv.select-tech.si (8.10.0.Beta10/8.10.0.Beta10) with ESMTP id k4Q7DkN15375 for ; Fri, 26 May 2006 09:13:47 +0200 (MET DST) From: Jan Zorz To: freebsd-net@freebsd.org Date: Fri, 26 May 2006 08:13:35 +0100 User-Agent: KMail/1.5.2 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605260913.35506.freebsd@dir-slovenia.com> Subject: Re: CARP broken in 6.1 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 07:13:54 -0000 On Thursday 25 of May 2006 17:17, dima wrote: > Assigning an IP address to a CARP interface leads to the new route table > entry: UH 0 0 carp0 > > and such error in /var/log/messages: > arp_rtrequest: bad gateway (!AF_LINK) > > Removing the entry manually seems to fix the issue. But I can't ping the > CARP address from inside. On which interface you try to setup carp? Fiber, copper, which brand? /jan From owner-freebsd-net@FreeBSD.ORG Fri May 26 09:17:10 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 722FE16A463 for ; Fri, 26 May 2006 09:17:10 +0000 (UTC) (envelope-from _pppp@mail.ru) Received: from f22.mail.ru (f22.mail.ru [194.67.57.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1283943D46 for ; Fri, 26 May 2006 09:17:10 +0000 (GMT) (envelope-from _pppp@mail.ru) Received: from mail by f22.mail.ru with local id 1FjYRQ-000FnS-00; Fri, 26 May 2006 13:17:08 +0400 Received: from [81.200.14.42] by koi.mail.ru with HTTP; Fri, 26 May 2006 13:17:08 +0400 From: dima <_pppp@mail.ru> To: Jan Zorz Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 X-Originating-IP: [81.200.14.42] Date: Fri, 26 May 2006 13:17:08 +0400 In-Reply-To: <200605260913.35506.freebsd@dir-slovenia.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Message-Id: Cc: freebsd-net@freebsd.org Subject: Re[2]: CARP broken in 6.1 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dima <_pppp@mail.ru> List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 09:17:11 -0000 > On Thursday 25 of May 2006 17:17, dima wrote: >> Assigning an IP address to a CARP interface leads to the new route table >> entry: UH 0 0 carp0 >> >> and such error in /var/log/messages: >> arp_rtrequest: bad gateway (!AF_LINK) >> >> Removing the entry manually seems to fix the issue. But I can't ping the >> CARP address from inside. > > On which interface you try to setup carp? Fiber, copper, which brand? em(4), copper. Does it matter? From owner-freebsd-net@FreeBSD.ORG Fri May 26 10:32:56 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A7A116A420 for ; Fri, 26 May 2006 10:32:56 +0000 (UTC) (envelope-from freebsd@dir-slovenia.com) Received: from mail-gw.select-tech.si (ns1.select-tech.si [81.24.96.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A47843D5D for ; Fri, 26 May 2006 10:32:55 +0000 (GMT) (envelope-from freebsd@dir-slovenia.com) Received: from stsrv.select-tech.si (stsrv.select-tech.si [193.77.112.44]) by mail-gw.select-tech.si (Postfix) with ESMTP id 28B91AB5DA for ; Fri, 26 May 2006 12:32:53 +0200 (CEST) Received: from prak (prak [193.77.112.82]) by stsrv.select-tech.si (8.10.0.Beta10/8.10.0.Beta10) with ESMTP id k4QAWtN21005 for ; Fri, 26 May 2006 12:32:55 +0200 (MET DST) From: Jan Zorz To: freebsd-net@freebsd.org Date: Fri, 26 May 2006 11:32:41 +0100 User-Agent: KMail/1.5.2 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605261232.41307.freebsd@dir-slovenia.com> Subject: Re: CARP broken in 6.1 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 10:32:58 -0000 > > On which interface you try to setup carp? Fiber, copper, which brand? > > em(4), copper. Does it matter? Yup. For me works well on em (copper), but not at all on em (fiber). Patch is on it's way... (somewhere). /jan From owner-freebsd-net@FreeBSD.ORG Fri May 26 14:05:08 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 92C1E16A465 for ; Fri, 26 May 2006 14:05:08 +0000 (UTC) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E1DD43D66 for ; Fri, 26 May 2006 14:05:04 +0000 (GMT) (envelope-from dunstan@freebsd.czest.pl) Received: from dunstan.freebsd.czest.pl (gw98.internetdsl.tpnet.pl [80.53.74.98]) by freebsd.czest.pl (8.13.4/8.12.9) with ESMTP id k4QEHnVa051332 for ; Fri, 26 May 2006 14:17:49 GMT (envelope-from dunstan@freebsd.czest.pl) Received: from dunstan.freebsd.czest.pl (localhost [127.0.0.1]) by dunstan.freebsd.czest.pl (8.13.6/8.13.6) with ESMTP id k4QEAuCf002535 for ; Fri, 26 May 2006 16:10:56 +0200 (CEST) (envelope-from dunstan@dunstan.freebsd.czest.pl) Received: (from dunstan@localhost) by dunstan.freebsd.czest.pl (8.13.6/8.13.6/Submit) id k4QEAtC0002534 for freebsd-net@freebsd.org; Fri, 26 May 2006 16:10:55 +0200 (CEST) (envelope-from dunstan) Date: Fri, 26 May 2006 16:10:55 +0200 From: "Wojciech A. Koszek" To: freebsd-net@freebsd.org Message-ID: <20060526141055.GA2511@FreeBSD.czest.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-2.0.2 (freebsd.czest.pl [80.48.250.4]); Fri, 26 May 2006 14:17:49 +0000 (UTC) Subject: Locking fixes for ef(4) - testers needed X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 14:05:08 -0000 Hello, Here is a patch for ef(4) which adds some locking: http://freebsd.czest.pl/dunstan/FreeBSD/if_ef.1.patch It's known to be not entirely right, but could be commited to improve current situation of ef(4). Testers are welcome. Thanks, -- Wojciech A. Koszek wkoszek@FreeBSD.org http://FreeBSD.czest.pl/dunstan/ From owner-freebsd-net@FreeBSD.ORG Fri May 26 15:03:48 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD1CE16A434 for ; Fri, 26 May 2006 15:03:48 +0000 (UTC) (envelope-from sullrich@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24C8E43D68 for ; Fri, 26 May 2006 15:03:45 +0000 (GMT) (envelope-from sullrich@gmail.com) Received: by py-out-1112.google.com with SMTP id f28so161751pyf for ; Fri, 26 May 2006 08:03:44 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=badjImbqfALyczORa5jLnKqc+R15FzJPfiwPfjIpA1B2NIRuWUD4xOejDIEAMvgi43qtOcPb/rJXkm4AXK67wcom5Um8IynLTwrJLLlUKiUngXwrXzEHnWfnY/EM+ztQhxkRT6FdincpkHzM1Tji46xtUoSjG50u6Fx+m7NmBXQ= Received: by 10.35.21.1 with SMTP id y1mr758672pyi; Fri, 26 May 2006 08:03:43 -0700 (PDT) Received: by 10.35.94.6 with HTTP; Fri, 26 May 2006 08:03:43 -0700 (PDT) Message-ID: Date: Fri, 26 May 2006 11:03:43 -0400 From: "Scott Ullrich" To: "Jan Zorz" In-Reply-To: <200605261232.41307.freebsd@dir-slovenia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200605261232.41307.freebsd@dir-slovenia.com> Cc: freebsd-net@freebsd.org Subject: Re: CARP broken in 6.1 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 15:03:49 -0000 On 5/26/06, Jan Zorz wrote: > > > > On which interface you try to setup carp? Fiber, copper, which brand? > > > > em(4), copper. Does it matter? > > Yup. For me works well on em (copper), but not at all on em (fiber). > > Patch is on it's way... (somewhere). > > /jan Until they hit the tree you can manually patch from http://cvs.pfsense.com/cgi-bin/cvsweb.cgi/tools/patches/if_em.c.diff?rev=3D= 1.2;content-type=3Dtext%2Fplain Scott From owner-freebsd-net@FreeBSD.ORG Fri May 26 19:17:07 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4E0E16B4FC for ; Fri, 26 May 2006 19:16:58 +0000 (UTC) (envelope-from benjamin@cactus.org) Received: from cactus.org (linux.cactus.org [66.118.232.151]) by mx1.FreeBSD.org (Postfix) with SMTP id 1251643D58 for ; Fri, 26 May 2006 19:16:57 +0000 (GMT) (envelope-from benjamin@cactus.org) Received: (qmail 15391 invoked by uid 2051); 26 May 2006 19:16:56 -0000 From: benjamin@cactus.org Date: Fri, 26 May 2006 14:16:56 -0500 To: freebsd-net@freebsd.org Message-ID: <20060526191656.GA15237@linux.cactus.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.5.1+cvs20040105i Subject: Netgraph: Ethernet interfaces missing from persistent node list X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 19:17:20 -0000 Using ngctl as suggested in the "All About Netgraph" Daemon News article (http://people.freebsd.org/~julian/netgraph.html ) by Archie Cobbs I get the following output: root@ntp-2# nghook -a fxp0: divert nghook: can't connect to node root@ntp-2# ngctl list There are 1 total nodes: Name: ngctl4352 Type: socket ID: 00000005 Num hooks: 0 According to the article my four Ethernet interefaces (see ifconfig output below) should display as persistent nodes. Any reason why they do not appear? I compiled a custom kernel on two separate occasions, first to support IPFW/Dummynet, then later, Netgraph. Thanks, Tom Benjamin ##### kernel options added for 1st compile (IPFW) options BRIDGE options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT options DUMMYNET options NMBCLUSTERS options HZ=1000 ##### kernel options added for 2nd compile (NETGRAPH, plus forgot IPDIVERT in 1st compile) options IPDIVERT options NETGRAPH ##### end kernel options # uname -a FreeBSD ntp-2.labs.iptv 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Thu May 25 14:34:57 CDT 2006 root@ntp-2# sysctl -a|grep graph netgraph_path 0 0K - 30 16 netgraph_sock 0 0K - 5 64 netgraph_msg 0 0K - 30 64,128,256,1024 netgraph_node 0 0K - 5 256 net.graph.maxalloc: 512 net.graph.abi_version: 11 net.graph.msg_version: 8 net.graph.control.proto: 2 net.graph.data.proto: 1 net.graph.family: 32 net.graph.recvspace: 20480 net.graph.maxdgram: 20480 # ifconfig fxp0: flags=8843 mtu 1500 options=8 inet6 fe80::2b0:d0ff:fee1:1754%fxp0 prefixlen 64 scopeid 0x1 inet 192.168.10.1 netmask 0xffffff00 broadcast 192.168.10.255 ether 00:b0:d0:e1:17:54 media: Ethernet autoselect (100baseTX) status: active fxp1: flags=8843 mtu 1500 options=8 inet6 fe80::2b0:d0ff:fee1:1755%fxp1 prefixlen 64 scopeid 0x2 inet 10.3.40.250 netmask 0xffffff00 broadcast 10.3.40.255 ether 00:b0:d0:e1:17:55 media: Ethernet autoselect (100baseTX ) status: active sis0: flags=8843 mtu 1500 options=8 inet6 fe80::20f:b5ff:fe46:8e17%sis0 prefixlen 64 scopeid 0x3 inet 144.60.43.147 netmask 0xffffff00 broadcast 144.60.43.255 ether 00:0f:b5:46:8e:17 media: Ethernet autoselect (100baseTX ) status: active sis1: flags=8842 mtu 1500 options=8 ether 00:0f:b5:46:59:63 media: Ethernet autoselect (100baseTX ) status: active lo0: flags=8049 mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 inet 127.0.0.1 netmask 0xff000000 netgraph_24may2006.txt netgraph_26may2006.txt -- ==++==++==++==++==++==++==++==++==++==++==++==++==++==++== Thomas Benjamin From owner-freebsd-net@FreeBSD.ORG Fri May 26 19:23:47 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 85A0A16AD67 for ; Fri, 26 May 2006 19:23:47 +0000 (UTC) (envelope-from benjamin@cactus.org) Received: from cactus.org (linux.cactus.org [66.118.232.151]) by mx1.FreeBSD.org (Postfix) with SMTP id 0BAF743D48 for ; Fri, 26 May 2006 19:23:46 +0000 (GMT) (envelope-from benjamin@cactus.org) Received: (qmail 15694 invoked by uid 2051); 26 May 2006 19:23:46 -0000 From: benjamin@cactus.org Date: Fri, 26 May 2006 14:23:46 -0500 To: freebsd-net@freebsd.org Message-ID: <20060526192346.GA15539@linux.cactus.org> References: <20060526191656.GA15237@linux.cactus.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060526191656.GA15237@linux.cactus.org> User-Agent: Mutt/1.5.5.1+cvs20040105i Subject: Netgraph: Ethernet interfaces missing from persistent node list X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 19:23:54 -0000 My bad ... I forgot to do . Here they are: root@ntp-2# ngctl list There are 5 total nodes: Name: ngctl4476 Type: socket ID: 0000000d Num hooks: 0 Name: sis1 Type: ether ID: 0000000b Num hooks: 0 Name: sis0 Type: ether ID: 0000000a Num hooks: 0 Name: fxp1 Type: ether ID: 00000009 Num hooks: 0 Name: fxp0 Type: ether ID: 00000008 Num hooks: 0 Tom -- ==++==++==++==++==++==++==++==++==++==++==++==++==++==++== Thomas Benjamin From owner-freebsd-net@FreeBSD.ORG Fri May 26 20:40:08 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E66C516A4CB for ; Fri, 26 May 2006 20:40:08 +0000 (UTC) (envelope-from amit.freebsd@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9CC843D46 for ; Fri, 26 May 2006 20:40:07 +0000 (GMT) (envelope-from amit.freebsd@gmail.com) Received: by py-out-1112.google.com with SMTP id 39so303318pyu for ; Fri, 26 May 2006 13:40:06 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=l6tftJvryb0CGjysVo4QwIQFFuMy3HXd2p2JJC/c6DT6R5RpBSlVhjaMUplvYFVjZ9zhSX6Hh/mSpvHnSX+DyFCShtv8wuSSvbu9QfKEzcm21SL5Var9MmAM7gwyvlzwqtTY/i6OziXhhu4L9O5e4YXc6dT6nI1+f/U6vVZFQV0= Received: by 10.35.112.3 with SMTP id p3mr1217317pym; Fri, 26 May 2006 13:40:06 -0700 (PDT) Received: by 10.35.99.6 with HTTP; Fri, 26 May 2006 13:40:06 -0700 (PDT) Message-ID: Date: Fri, 26 May 2006 15:40:06 -0500 From: "Amit Mondal" To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: TCP checksum X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 20:40:13 -0000 Hi, Could anyone pls tell me the function freebsd provides for calculating TCP checksum. What I am doing, I am sniffing packet using divert packet and changing the destination address of the packet. Now, since TCP checksum calculation include Pseudo head (src dest IP ....) I need to recalculate TCP checksum. Is there any way to recalculate the checksum incrementally. Thanks in advance. Rgds -Amit From owner-freebsd-net@FreeBSD.ORG Fri May 26 21:24:48 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4CC3A16B9D9 for ; Fri, 26 May 2006 21:24:48 +0000 (UTC) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8D1E43D7D for ; Fri, 26 May 2006 21:24:47 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [10.251.23.205]) ([10.251.23.205]) by a50.ironport.com with ESMTP; 26 May 2006 14:24:47 -0700 Message-ID: <4477721F.2010406@elischer.org> Date: Fri, 26 May 2006 14:24:47 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.13) Gecko/20060414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: benjamin@cactus.org References: <20060526191656.GA15237@linux.cactus.org> In-Reply-To: <20060526191656.GA15237@linux.cactus.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Netgraph: Ethernet interfaces missing from persistent node list X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 21:24:55 -0000 benjamin@cactus.org wrote: >Using ngctl as suggested in the "All About Netgraph" Daemon News >article (http://people.freebsd.org/~julian/netgraph.html ) by Archie >Cobbs I get the following output: > >root@ntp-2# nghook -a fxp0: divert >nghook: can't connect to node > >root@ntp-2# ngctl list >There are 1 total nodes: > Name: ngctl4352 Type: socket ID: 00000005 Num hooks: 0 > >According to the article my four Ethernet interefaces (see ifconfig output below) should display >as persistent nodes. Any reason why they do not appear? I compiled a custom kernel on two separate >occasions, first to support IPFW/Dummynet, then later, Netgraph. > >Thanks, >Tom Benjamin > >##### kernel options added for 1st compile (IPFW) >options BRIDGE >options IPFIREWALL >options IPFIREWALL_VERBOSE >options IPFIREWALL_VERBOSE_LIMIT >options DUMMYNET >options NMBCLUSTERS >options HZ=1000 >##### kernel options added for 2nd compile (NETGRAPH, plus forgot IPDIVERT in 1st compile) >options IPDIVERT >options NETGRAPH > > You need to also compile in or load the nodes you need. options NETGRAPH_ETHER (I think) (I forget the names.. look in LINT) or kldload ng_ether to load it dynamically also, there is no "divert" hook for ng_ether hooks. hooks for ng-ether are: lower (to get incoming packets and accept outgoing packets )(connects to the physical interface) upper (to get outgoing packets and acceept incoming packets)(connects to the protocol mux/demux) orphan (above the protocol demux. only gives you packets that would otherwise have been discarded due to not being a known protocol.) man 4 ng_ether >##### end kernel options > ># uname -a >FreeBSD ntp-2.labs.iptv 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Thu May 25 14:34:57 CDT 2006 > >root@ntp-2# sysctl -a|grep graph >netgraph_path 0 0K - 30 16 >netgraph_sock 0 0K - 5 64 >netgraph_msg 0 0K - 30 64,128,256,1024 >netgraph_node 0 0K - 5 256 >net.graph.maxalloc: 512 >net.graph.abi_version: 11 >net.graph.msg_version: 8 >net.graph.control.proto: 2 >net.graph.data.proto: 1 >net.graph.family: 32 >net.graph.recvspace: 20480 >net.graph.maxdgram: 20480 > ># ifconfig >fxp0: flags=8843 mtu 1500 > options=8 > inet6 fe80::2b0:d0ff:fee1:1754%fxp0 prefixlen 64 scopeid 0x1 > inet 192.168.10.1 netmask 0xffffff00 broadcast 192.168.10.255 > ether 00:b0:d0:e1:17:54 > media: Ethernet autoselect (100baseTX) > status: active >fxp1: flags=8843 mtu 1500 > options=8 > inet6 fe80::2b0:d0ff:fee1:1755%fxp1 prefixlen 64 scopeid 0x2 > inet 10.3.40.250 netmask 0xffffff00 broadcast 10.3.40.255 > ether 00:b0:d0:e1:17:55 > media: Ethernet autoselect (100baseTX ) > status: active >sis0: flags=8843 mtu 1500 > options=8 > inet6 fe80::20f:b5ff:fe46:8e17%sis0 prefixlen 64 scopeid 0x3 > inet 144.60.43.147 netmask 0xffffff00 broadcast 144.60.43.255 > ether 00:0f:b5:46:8e:17 > media: Ethernet autoselect (100baseTX ) > status: active >sis1: flags=8842 mtu 1500 > options=8 > ether 00:0f:b5:46:59:63 > media: Ethernet autoselect (100baseTX ) > status: active >lo0: flags=8049 mtu 16384 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 > inet 127.0.0.1 netmask 0xff000000 >netgraph_24may2006.txt >netgraph_26may2006.txt > > From owner-freebsd-net@FreeBSD.ORG Fri May 26 21:30:42 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CAE9B16BB0C for ; Fri, 26 May 2006 21:30:42 +0000 (UTC) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E1F343D72 for ; Fri, 26 May 2006 21:30:42 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [10.251.23.205]) ([10.251.23.205]) by a50.ironport.com with ESMTP; 26 May 2006 14:30:42 -0700 Message-ID: <44777382.9070602@elischer.org> Date: Fri, 26 May 2006 14:30:42 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.13) Gecko/20060414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Amit Mondal References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: TCP checksum X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 21:30:48 -0000 Amit Mondal wrote: > Hi, > > Could anyone pls tell me the function freebsd provides for calculating > TCP > checksum. > > What I am doing, I am sniffing packet using divert packet and changing > the > destination address of the packet. Now, since TCP checksum calculation > include Pseudo head (src dest IP ....) I need to recalculate TCP > checksum. > Is there any way to recalculate the checksum incrementally. look at libalias. (also check the port for the divert based daemon that does the mss fixup. I forget what it is called) if you change a few bytes in the packet you can change the checksum appropriatly without recalculating the whole thing. You should be able to find lots of examples from google, and I'm pretty sure libalias does it.. > > Thanks in advance. > > Rgds > -Amit > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Fri May 26 22:19:15 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 62DB816A632 for ; Fri, 26 May 2006 22:19:15 +0000 (UTC) (envelope-from fox@verio.net) Received: from dfw-smtpout4.email.verio.net (dfw-smtpout4.email.verio.net [129.250.36.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CC9943D48 for ; Fri, 26 May 2006 22:19:14 +0000 (GMT) (envelope-from fox@verio.net) Received: from [129.250.36.64] (helo=dfw-mmp4.email.verio.net) by dfw-smtpout4.email.verio.net with esmtp id 1FjkeH-0007ce-VE for freebsd-net@freebsd.org; Fri, 26 May 2006 22:19:13 +0000 Received: from [129.250.40.241] (helo=limbo.int.dllstx01.us.it.verio.net) by dfw-mmp4.email.verio.net with esmtp id 1FjkeH-0002ya-S2 for freebsd-net@freebsd.org; Fri, 26 May 2006 22:19:13 +0000 Received: by limbo.int.dllstx01.us.it.verio.net (Postfix, from userid 1000) id 3DE148E2E7; Fri, 26 May 2006 17:19:10 -0500 (CDT) Date: Fri, 26 May 2006 17:19:10 -0500 From: David DeSimone To: freebsd-net@freebsd.org Message-ID: <20060526221909.GA31000@verio.net> Mail-Followup-To: freebsd-net@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Precedence: bulk User-Agent: Mutt/1.5.9i Subject: How to force full sync using pfsync? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 22:19:16 -0000 I have a strange problem between two PF firewalls in a cluster, with pfsync enabled. When I reboot one of the cluster members, the state tables do synchronize and populate with some of the same connection states, but not all of them. In particular, long-lived, extant connections seem to never show up in the rebooted member's state table. I figured that doing ifconfig down/up would send some sort of "full sync" message between the two members, to cause the entire state table to be sent in bulk. But, no such behavior seems to come about. It seems to me that only connection updates are being sent between the cluster members. There is no "full sync" done at startup. Do I misunderstand? Is there a misconfiguration that can lead to this strange behavior? -- David DeSimone == Network Admin == fox@verio.net "It took me fifteen years to discover that I had no talent for writing, but I couldn't give it up because by that time I was too famous. -- Robert Benchley From owner-freebsd-net@FreeBSD.ORG Fri May 26 23:31:38 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 79AEE16A83B for ; Fri, 26 May 2006 23:31:38 +0000 (UTC) (envelope-from mjeung@cisdata.net) Received: from dagobah.cisdata.net (dagobah.cisdata.net [63.82.223.109]) by mx1.FreeBSD.org (Postfix) with ESMTP id 487C743D46 for ; Fri, 26 May 2006 23:31:38 +0000 (GMT) (envelope-from mjeung@cisdata.net) Received: from adsl-69-237-115-101.dsl.scrm01.pacbell.net ([69.237.115.101] helo=[192.168.45.151]) by dagobah.cisdata.net with esmtp (Exim 4.52 (FreeBSD)) id 1FjlmP-0009BO-TR for freebsd-net@freebsd.org; Fri, 26 May 2006 16:31:42 -0700 Mime-Version: 1.0 (Apple Message framework v750) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-net@freebsd.org From: Michael Jeung Date: Fri, 26 May 2006 16:33:06 -0700 X-Mailer: Apple Mail (2.750) Subject: "Private" MAC Addresses X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 23:31:46 -0000 Hi folks, I'm interested in assigning a bunch of virtual MAC addresses on my network but I want to make sure that I'm not conflicting with MAC addresses that are already out there. (I've already taken a look at this nice resource: http:// www.cavebear.com/CaveBear/Ethernet/vendor.html) Are there any MAC address ranges which are reserved as private? I'm talking about an equivalent to the 10.0.0.0/8, 192.168.0.0/26 and 172.16.0.0 ranges for IP addresses - basically a range of MAC addresses that I can use without fear that it'll interfere with some future network device. Thanks, Michael Jeung From owner-freebsd-net@FreeBSD.ORG Fri May 26 23:45:12 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E6AA16A429 for ; Fri, 26 May 2006 23:45:12 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC56543D55 for ; Fri, 26 May 2006 23:45:11 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 621AA1FFACE; Sat, 27 May 2006 01:45:09 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id C42F61FFACC; Sat, 27 May 2006 01:45:05 +0200 (CEST) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 147F84448D6; Fri, 26 May 2006 23:40:28 +0000 (UTC) Date: Fri, 26 May 2006 23:40:28 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Michael Jeung In-Reply-To: Message-ID: <20060526233953.A9690@maildrop.int.zabbadoz.net> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: freebsd-net@freebsd.org Subject: Re: "Private" MAC Addresses X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 23:45:15 -0000 On Fri, 26 May 2006, Michael Jeung wrote: > Hi folks, > > I'm interested in assigning a bunch of virtual MAC addresses on my network > but I want to make sure that I'm not conflicting with MAC addresses that are > already out there. > > (I've already taken a look at this nice resource: > http://www.cavebear.com/CaveBear/Ethernet/vendor.html) > > Are there any MAC address ranges which are reserved as private? I'm talking look at http://standards.ieee.org/regauth/groupmac/tutorial.html and check for the locally administered bit. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-net@FreeBSD.ORG Sat May 27 16:59:55 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 919E216BCDC; Sat, 27 May 2006 16:59:55 +0000 (UTC) (envelope-from coven@cottonpromotion.org) Received: from chr119.neoplus.adsl.tpnet.pl (chr119.neoplus.adsl.tpnet.pl [83.31.15.119]) by mx1.FreeBSD.org (Postfix) with SMTP id 8478A43D46; Sat, 27 May 2006 16:59:53 +0000 (GMT) (envelope-from coven@cottonpromotion.org) Date: Sat, 27 May 2006 17:00:10 +0000 From: "shavonne zygmund" X-Mailer: The Bat! (v3.63.20) Professional X-Priority: 3 (Normal) Message-ID: <86582620.20060201060614@83.31.15.119> To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: multipart/related; boundary="----------53D40CE1F627A89B" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Time is just nature's way of keeping everything from happening at once X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: coven@cottonpromotion.org List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 May 2006 17:00:17 -0000 ------------53D40CE1F627A89B Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Hearty reception, [cid:53D40CE1.F627A89B.53D40CE1.F627A89B_csseditor] upadukadel[dot]com ---- possible. Today he was too much agitated. He would have covered the picture, but he stopped, holding the cloth in his hand, and, smiling blissfully, gazed a long while at the figure of John. At last, as it were regretfully tearing himself away, he dropped the cloth, and, exhausted but happy, went home. Vronsky, Anna, and Golenishtchev, on their way home, were particularly lively and cheerful. They talked of Mihailov and his pictures. The word _talent_, by which they meant an inborn, almost physical, aptitude apart from brain and heart, and in which they tried to find an expression for all the artist had gained from life, recurred particularly often in their talk, as though it were necessary for them to sum up what they had no conception of, though they wanted to talk of it. They said that there was no denying his talent, but that his talent could not develop for want of education--the common defect of our Russian artists. But the picture of the boys had imprinted itself on their memories, and they were continually coming back to it. "What an exquisite thing! How he has succeeded in it, and how simply! He doesn't even comprehend how good it is. Yes, I ------------53D40CE1F627A89B--