From owner-freebsd-net Sun Sep 22 20:50:10 2002 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 9682737B401 for ; Sun, 22 Sep 2002 20:50:09 -0700 (PDT) Received: from coconut.itojun.org (coconut.itojun.org [219.101.47.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id F322A43E3B for ; Sun, 22 Sep 2002 20:50:08 -0700 (PDT) (envelope-from itojun@itojun.org) Received: from itojun.org (localhost [127.0.0.1]) by coconut.itojun.org (Postfix) with ESMTP id F1D0A4B24; Mon, 23 Sep 2002 12:50:03 +0900 (JST) To: Mark_Andrews@isc.org Cc: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= , Juan Francisco Rodriguez Hervella , Lista , "(Lista) bind9-users@isc.org" In-reply-to: Mark_Andrews's message of Fri, 20 Sep 2002 15:48:53 +1000. <200209200548.g8K5mrB5067818@drugs.dv.isc.org> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: RES_INSECURE and CHECK_SRVR_ADDR in resolver functions (IPv6 anycast response problem) From: itojun@iijlab.net Date: Mon, 23 Sep 2002 12:50:03 +0900 Message-Id: <20020923035004.F1D0A4B24@coconut.itojun.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > Yes, and I know why the restriction is in RFC 1884 and it > is a reasonable restriction. I don't think so, IP source address is easy to forge and it does not add any meaning protection. DNSSEC is the only way if you want trusted responsees. therefore, i agree with enabling RES_INSECURE1 by default. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Sep 22 20:54:37 2002 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 7F5C937B401 for ; Sun, 22 Sep 2002 20:54:36 -0700 (PDT) Received: from coconut.itojun.org (coconut.itojun.org [219.101.47.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CC8043E6E for ; Sun, 22 Sep 2002 20:54:36 -0700 (PDT) (envelope-from itojun@itojun.org) Received: from itojun.org (localhost [127.0.0.1]) by coconut.itojun.org (Postfix) with ESMTP id 657EA4B26; Mon, 23 Sep 2002 12:54:35 +0900 (JST) To: Mark_Andrews@isc.org Cc: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= , Juan Francisco Rodriguez Hervella , Lista , "(Lista) bind9-users@isc.org" X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 In-reply-to: Mark_Andrews's message of Fri, 20 Sep 2002 15:48:53 +1000. <200209200548.g8K5mrB5067818@drugs.dv.isc.org> Subject: Re: RES_INSECURE and CHECK_SRVR_ADDR in resolver functions (IPv6 anycast response problem) Date: Mon, 23 Sep 2002 12:54:35 +0900 From: Jun-ichiro itojun Hagino Message-Id: <20020923035435.657EA4B26@coconut.itojun.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > Yes, and I know why the restriction is in RFC 1884 and it > is a reasonable restriction. I don't think so, IP source address is easy to forge and it does not add any meaning protection. DNSSEC is the only way if you want trusted responsees. therefore, i agree with enabling RES_INSECURE1 by default. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Sep 22 21:29:10 2002 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 5538C37B401 for ; Sun, 22 Sep 2002 21:29:09 -0700 (PDT) Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CD1943E65 for ; Sun, 22 Sep 2002 21:29:08 -0700 (PDT) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from localhost ([3ffe:501:100f:f::6]) by shuttle.wide.toshiba.co.jp (8.11.6/8.9.1) with ESMTP id g8N4SMt76823; Mon, 23 Sep 2002 13:28:31 +0900 (JST) Date: Mon, 23 Sep 2002 13:28:48 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: Jun-ichiro itojun Hagino Cc: Mark_Andrews@isc.org, Juan Francisco Rodriguez Hervella , Lista , "(Lista) bind9-users@isc.org" Subject: Re: RES_INSECURE and CHECK_SRVR_ADDR in resolver functions (IPv6 anycast response problem) In-Reply-To: <20020923035435.657EA4B26@coconut.itojun.org> User-Agent: Wanderlust/2.6.1 (Upside Down) Emacs/21.2 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. References: <20020923035435.657EA4B26@coconut.itojun.org> MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Dispatcher: imput version 20000228(IM140) Lines: 19 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >>>>> On Mon, 23 Sep 2002 12:54:35 +0900, >>>>> Jun-ichiro itojun Hagino said: >> Yes, and I know why the restriction is in RFC 1884 and it >> is a reasonable restriction. > I don't think so, IP source address is easy to forge and it does not > add any meaning protection. DNSSEC is the only way if you want trusted > responsees. therefore, i agree with enabling RES_INSECURE1 by default. Please let me check. Mark said the restriction was reasonable, and he didn't say checking the source address of a DNS response provide better security. In my understanding his main opinion is effects and compatibility against existing applications. JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Sep 22 21:52:48 2002 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 DE74937B401 for ; Sun, 22 Sep 2002 21:52:47 -0700 (PDT) Received: from coconut.itojun.org (coconut.itojun.org [219.101.47.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 341D543E3B for ; Sun, 22 Sep 2002 21:52:47 -0700 (PDT) (envelope-from itojun@itojun.org) Received: from itojun.org (localhost [127.0.0.1]) by coconut.itojun.org (Postfix) with ESMTP id 9EBE34B28; Mon, 23 Sep 2002 13:52:45 +0900 (JST) To: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= Cc: Lista , "(Lista) bind9-users@isc.org" In-reply-to: jinmei's message of Mon, 23 Sep 2002 13:28:48 +0900. X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: RES_INSECURE and CHECK_SRVR_ADDR in resolver functions (IPv6 anycast response problem) Date: Mon, 23 Sep 2002 13:52:45 +0900 From: Jun-ichiro itojun Hagino Message-Id: <20020923045245.9EBE34B28@coconut.itojun.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >>> Yes, and I know why the restriction is in RFC 1884 and it >>> is a reasonable restriction. >> I don't think so, IP source address is easy to forge and it does not >> add any meaning protection. DNSSEC is the only way if you want trusted >> responsees. therefore, i agree with enabling RES_INSECURE1 by default. > >Please let me check. Mark said the restriction was reasonable, and he >didn't say checking the source address of a DNS response provide >better security. In my understanding his main opinion is effects and >compatibility against existing applications. correct. i've quoted the wrong portion. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Sep 22 22: 1:29 2002 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 18F7737B401 for ; Sun, 22 Sep 2002 22:01:28 -0700 (PDT) Received: from drugs.dv.isc.org (drugs.dv.isc.org [130.155.191.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9E0E43E42 for ; Sun, 22 Sep 2002 22:01:26 -0700 (PDT) (envelope-from marka@drugs.dv.isc.org) Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.12.5/8.12.5) with ESMTP id g8N51PB5078220; Mon, 23 Sep 2002 15:01:25 +1000 (EST) (envelope-from marka@drugs.dv.isc.org) Message-Id: <200209230501.g8N51PB5078220@drugs.dv.isc.org> To: itojun@iijlab.net Cc: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= , Lista , "(Lista) bind9-users@isc.org" From: Mark.Andrews@isc.org Subject: Re: RES_INSECURE and CHECK_SRVR_ADDR in resolver functions (IPv6 anycast response problem) In-reply-to: Your message of "Mon, 23 Sep 2002 12:50:03 +0900." <20020923035004.F1D0A4B24@coconut.itojun.org> Date: Mon, 23 Sep 2002 15:01:25 +1000 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > Yes, and I know why the restriction is in RFC 1884 and it > > is a reasonable restriction. > > I don't think so, Are you saying we should source packets from the anycast address? If not you should quote better. > IP source address is easy to forge and it does not > add any meaning protection. DNSSEC is the only way if you want trusted > responsees. therefore, i agree with enabling RES_INSECURE1 by default. > > itojun Source addresses can be used to seperate multiple queries with the same query id. While the stub resolver rarely needs to do this a nameserver will to this all the time. Enabling RES_INSECURE1 just hides the real problem that IPv6 anycast is broken, encourages broken nameserver implementations and leaves you with the situation where the tools using stub resolver "work" but the nameserver doesn't. Mark -- Mark Andrews, Internet Software Consortium 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews@isc.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Sep 23 16:24:10 2002 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 80E6037B401 for ; Mon, 23 Sep 2002 16:24:09 -0700 (PDT) Received: from swordfish.cs.caltech.edu (swordfish.cs.caltech.edu [131.215.44.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32D3243E6E for ; Mon, 23 Sep 2002 16:24:09 -0700 (PDT) (envelope-from chengjin@cs.caltech.edu) Received: from fast2.cs.caltech.edu (fast2.cs.caltech.edu [131.215.45.55]) by swordfish.cs.caltech.edu (Postfix) with ESMTP id 1BD88DF273 for ; Mon, 23 Sep 2002 16:23:46 -0700 (PDT) Received: from localhost (chengjin@localhost) by fast2.cs.caltech.edu (8.11.6/8.9.3) with ESMTP id g8NNNC620551 for ; Mon, 23 Sep 2002 16:23:12 -0700 X-Authentication-Warning: fast2.cs.caltech.edu: chengjin owned process doing -bs Date: Mon, 23 Sep 2002 16:22:42 -0700 (PDT) From: Cheng Jin To: Subject: TCP receiving buffer Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi all, I am having a hard time setting TCP receiving buffer space to be large than 512K using setsockopt under FreeBSD 4.6.2-RELEASE #0. I have tried playing with various sysctl variables, but I can't seem to break the 512K barrier. I looked at my kernel config file and didn't really find any hard limit either. here are the systcl vars that I have tried. nmbclusters is small, but I should still be able to get about 12 MB of clusters. Any idea on what sockbuf_waste_factor is?? It was 8 by default. Do I have to reduce the number of sockets for this to work? kern.ipc.maxsockbuf: 4094305 kern.ipc.sockbuf_waste_factor: 4 kern.ipc.somaxconn: 512 kern.ipc.nmbclusters: 6656 kern.ipc.nmbufs: 26624 kern.ipc.maxsockets: 12328 net.inet.tcp.sendspace: 32768 net.inet.tcp.recvspace: 4094305 Please cc me a copy when you reply. Thank you very much, Cheng To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Sep 23 17:37:19 2002 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 A418237B401 for ; Mon, 23 Sep 2002 17:37:17 -0700 (PDT) Received: from drugs.dv.isc.org (drugs.dv.isc.org [130.155.191.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5902C43E4A for ; Mon, 23 Sep 2002 17:37:16 -0700 (PDT) (envelope-from marka@drugs.dv.isc.org) Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.12.5/8.12.5) with ESMTP id g8O0b9B5081828; Tue, 24 Sep 2002 10:37:13 +1000 (EST) (envelope-from marka@drugs.dv.isc.org) Message-Id: <200209240037.g8O0b9B5081828@drugs.dv.isc.org> To: Juan Francisco Rodriguez Hervella Cc: Lista , "(Lista) bind9-users@isc.org" From: Mark.Andrews@isc.org Subject: Re: RES_INSECURE and CHECK_SRVR_ADDR in resolver functions (IPv6 anycast response problem) In-reply-to: Your message of "Thu, 19 Sep 2002 10:44:27 +0200." <3D898E6B.692C3C43@it.uc3m.es> Date: Tue, 24 Sep 2002 10:37:09 +1000 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > Hello: > > I need to make some tests with IPv6 anycast addresses, > and I've found out that when /etc/resolv.conf has an > IPv6 anycast address, the DNS response isn't accepted because > it comes from an unicast IPv6 address. > > I've been digging into the source code of > /usr/src/lib/libc/net/res_* > and I've found these constants: > > RES_INSECURE1 > RES_INSECURE2 > > and a compilation option called: > > CHECK_SRVR_ADDR > > > What I would like to do is re-compile > the resolver library to accept DNS responses > coming from a unicast IPv6 address to solve > the problem mentioned above. > > What's better... to *un*define CHECK_SRVR_ADDR > or to include RES_INSECURE1 into RES_DEFAULT ? > Do you think it's a good idea to do this ? > what are the security implications ? > > PS: RES_DEFAULT appears in "resolv.h" > > Best Regards. > > -- > JFRH. > If you have to set it then do it in /etc/resolv.conf. options insecure1 Mark -- Mark Andrews, Internet Software Consortium 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews@isc.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Sep 24 4:31:45 2002 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 8741A37B401 for ; Tue, 24 Sep 2002 04:31:44 -0700 (PDT) Received: from pina.terra.com.br (pina.terra.com.br [200.176.3.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id D51F543E3B for ; Tue, 24 Sep 2002 04:31:43 -0700 (PDT) (envelope-from eick.jac@terra.com.br) Received: from engenho.terra.com.br (engenho.terra.com.br [200.176.3.42]) by pina.terra.com.br (Postfix) with ESMTP id 39B2F53120 for ; Tue, 24 Sep 2002 08:31:42 -0300 (EST) Received: from terra.com.br (webmail1.terra.com.br [200.176.3.176]) (authenticated user eick.jac) by engenho.terra.com.br (Postfix) with ESMTP id 343C6680C8 for ; Tue, 24 Sep 2002 08:31:42 -0300 (EST) Date: Tue, 24 Sep 2002 08:31:42 -0300 Message-Id: Subject: Routed Log MIME-Version: 1.0 Content-Type: text/plain;charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable From: "Eicke Felipe" To: "freebsd-net" X-XaM3-API-Version: 2.4 R5 B5 JSC SMTP AUTH X-SenderIP: 200.162.114.126 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi folks, There are a lot of messages in /var/log/messages file as follow: Sep 23 23:57:50 rtint routed[58]: sendto(fxp0, 224.0.0.1): Permission denied Sep 23 23:59:51 rtint routed[58]: sendto(xl0, 224.0.0.1): Permission denied My routed ipfw rules are: 00010 allow udp from any 520 to any 00011 allow udp from any to any 520 Could anybody help me? Thanks, Eicke. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Sep 24 12:30:51 2002 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 31A4237B401 for ; Tue, 24 Sep 2002 12:30:49 -0700 (PDT) Received: from mail4.uunet.ca (mail4.uunet.ca [209.167.141.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73EC443E42 for ; Tue, 24 Sep 2002 12:30:48 -0700 (PDT) (envelope-from kfl@xiphos.ca) Received: from tick ([216.95.199.148]) by mail4.uunet.ca with SMTP id <1033102-17801>; Tue, 24 Sep 2002 15:30:44 -0400 From: "kfl" To: "freebsd - net" , "Cheng Jin" Subject: RE: TCP receiving buffer Date: Tue, 24 Sep 2002 15:33:28 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, If you want to set it more than 512KB you need to grow maxsockbuf so: #sysctl -w kern.ipc.maxsockbuf=2147483648 The waste factor is used (see /sys/kern/uipc_socket2.c) to make the socket buffer specifed a multiple of 8 (basically your buffers becomes a multiple of 32bits) for efficient usilisation of memory. good luck. Karim Fodil-Lemelin. Xiphos Technologies. -----Original Message----- From: owner-freebsd-net@FreeBSD.ORG [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Cheng Jin Sent: Monday, September 23, 2002 7:23 PM To: freebsd-net@freebsd.org Subject: TCP receiving buffer Hi all, I am having a hard time setting TCP receiving buffer space to be large than 512K using setsockopt under FreeBSD 4.6.2-RELEASE #0. I have tried playing with various sysctl variables, but I can't seem to break the 512K barrier. I looked at my kernel config file and didn't really find any hard limit either. here are the systcl vars that I have tried. nmbclusters is small, but I should still be able to get about 12 MB of clusters. Any idea on what sockbuf_waste_factor is?? It was 8 by default. Do I have to reduce the number of sockets for this to work? kern.ipc.maxsockbuf: 4094305 kern.ipc.sockbuf_waste_factor: 4 kern.ipc.somaxconn: 512 kern.ipc.nmbclusters: 6656 kern.ipc.nmbufs: 26624 kern.ipc.maxsockets: 12328 net.inet.tcp.sendspace: 32768 net.inet.tcp.recvspace: 4094305 Please cc me a copy when you reply. Thank you very much, Cheng To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Sep 24 13:19:56 2002 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 8C9DA37B401 for ; Tue, 24 Sep 2002 13:19:55 -0700 (PDT) Received: from isilon.com (isilon.com [65.101.129.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C08143E7B for ; Tue, 24 Sep 2002 13:19:55 -0700 (PDT) (envelope-from pete@isilon.com) Received: from localhost (localhost [127.0.0.1]) by isilon.com (8.12.2/8.11.1) with ESMTP id g8OKJsUc037655 for ; Tue, 24 Sep 2002 13:19:54 -0700 (PDT) (envelope-from pete@isilon.com) Date: Tue, 24 Sep 2002 13:19:54 -0700 (PDT) From: Peter Godman To: freebsd-net@freebsd.org Subject: NewReno implementation questions. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org While looking at why packet loss was so disastrous in the application I'm working on, I noticed an oddity in a CURRENT snapshot taken in January, which I believe is the same today. Basically, there's some ack handling code that looks like: if (SEQ_LEQ(th->th_ack, tp->snd_una)) { if (tlen == 0 && tiwin == tp->snd_wnd) { /* dupack handling code */ ... } else { tp->t_dupacks = 0; } So what this seems to say to my untrained eye is that we should reset the dupacks, i.e. leave newreno fast recovery, if non-ack-only traffic comes from the other end. However, that the remote side decided to send data seems unrelated to whether we have successfully completed recovery and consequently don't need to retransmit in response to partial acks. I appreciate any and all advice about this code and whether this is desirable behaviour for some reason I haven't thought of. I will triple check RFC 2852 to see whether and if so why this is prescribed behaviour. Thanks Peter Godman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Sep 24 13:29:45 2002 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 943EB37B401 for ; Tue, 24 Sep 2002 13:29:44 -0700 (PDT) Received: from out5.mx.nwbl.wi.voyager.net (out5.mx.nwbl.wi.voyager.net [169.207.3.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id 032B343E4A for ; Tue, 24 Sep 2002 13:29:44 -0700 (PDT) (envelope-from silby@silby.com) Received: from pop2.nwbl.wi.voyager.net (pop2.nwbl.wi.voyager.net [169.207.3.115]) by out5.mx.nwbl.wi.voyager.net (Postfix) with ESMTP id D08D6C6CE1; Tue, 24 Sep 2002 15:27:07 -0500 (CDT) Received: from [10.1.1.6] (d88.as14.nwbl0.wi.voyager.net [169.207.134.88]) by pop2.nwbl.wi.voyager.net (8.10.2/8.10.2) with ESMTP id g8OKQx160847; Tue, 24 Sep 2002 15:26:59 -0500 (CDT) Date: Tue, 24 Sep 2002 15:31:01 -0500 (CDT) From: Mike Silbersack To: Peter Godman Cc: freebsd-net@freebsd.org Subject: Re: NewReno implementation questions. In-Reply-To: Message-ID: <20020924152936.Y39482-100000@patrocles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, 24 Sep 2002, Peter Godman wrote: > While looking at why packet loss was so disastrous in the application I'm > working on, I noticed an oddity in a CURRENT snapshot taken in January, > which I believe is the same today. Basically, there's some ack handling > code that looks like: There are quite a few oddities in the New Reno implementation, and the point you raise is somewhat valid. (It would be even moreso if you could provide tcpdumps to show the effect! ) Jeffrey Hsu has been working on improving our NewReno implementation. You should drop him an e-mail to see if what he has developed so far will be helpful to your case. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Sep 24 14:13:32 2002 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 7EB6837B401 for ; Tue, 24 Sep 2002 14:13:31 -0700 (PDT) Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18BDF43E3B for ; Tue, 24 Sep 2002 14:13:31 -0700 (PDT) (envelope-from crist.clark@attbi.com) Received: from blossom.cjclark.org ([12.234.91.48]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020924211330.LBFA16629.rwcrmhc51.attbi.com@blossom.cjclark.org>; Tue, 24 Sep 2002 21:13:30 +0000 Received: from blossom.cjclark.org (localhost. [127.0.0.1]) by blossom.cjclark.org (8.12.3/8.12.3) with ESMTP id g8OLDUWn047925; Tue, 24 Sep 2002 14:13:30 -0700 (PDT) (envelope-from crist.clark@attbi.com) Received: (from cjc@localhost) by blossom.cjclark.org (8.12.3/8.12.3/Submit) id g8OLDU5Z047924; Tue, 24 Sep 2002 14:13:30 -0700 (PDT) X-Authentication-Warning: blossom.cjclark.org: cjc set sender to crist.clark@attbi.com using -f Date: Tue, 24 Sep 2002 14:13:30 -0700 From: "Crist J. Clark" To: Eicke Felipe Cc: freebsd-net Subject: Re: Routed Log Message-ID: <20020924211330.GD46609@blossom.cjclark.org> Reply-To: "Crist J. Clark" References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-URL: http://people.freebsd.org/~cjc/ Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Sep 24, 2002 at 08:31:42AM -0300, Eicke Felipe wrote: > Hi folks, > There are a lot of messages in /var/log/messages file as follow: > Sep 23 23:57:50 rtint routed[58]: sendto(fxp0, 224.0.0.1): Permission > denied > Sep 23 23:59:51 rtint routed[58]: sendto(xl0, 224.0.0.1): Permission > denied > > My routed ipfw rules are: > 00010 allow udp from any 520 to any > 00011 allow udp from any to any 520 > > Could anybody help me? Are those all of your rules? Particularly any rules before those? -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Sep 24 14:16:26 2002 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 3FD8D37B401 for ; Tue, 24 Sep 2002 14:16:25 -0700 (PDT) Received: from sccrmhc03.attbi.com (sccrmhc03.attbi.com [204.127.202.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E46543E42 for ; Tue, 24 Sep 2002 14:16:24 -0700 (PDT) (envelope-from crist.clark@attbi.com) Received: from blossom.cjclark.org ([12.234.91.48]) by sccrmhc03.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020924211624.OTQV28420.sccrmhc03.attbi.com@blossom.cjclark.org>; Tue, 24 Sep 2002 21:16:24 +0000 Received: from blossom.cjclark.org (localhost. [127.0.0.1]) by blossom.cjclark.org (8.12.3/8.12.3) with ESMTP id g8OLGNWn047939; Tue, 24 Sep 2002 14:16:23 -0700 (PDT) (envelope-from crist.clark@attbi.com) Received: (from cjc@localhost) by blossom.cjclark.org (8.12.3/8.12.3/Submit) id g8OLGNRA047938; Tue, 24 Sep 2002 14:16:23 -0700 (PDT) X-Authentication-Warning: blossom.cjclark.org: cjc set sender to crist.clark@attbi.com using -f Date: Tue, 24 Sep 2002 14:16:23 -0700 From: "Crist J. Clark" To: Eicke Felipe Cc: freebsd-net Subject: Re: Routed Log Message-ID: <20020924211623.GE46609@blossom.cjclark.org> Reply-To: "Crist J. Clark" References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-URL: http://people.freebsd.org/~cjc/ Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Sep 24, 2002 at 08:31:42AM -0300, Eicke Felipe wrote: > Hi folks, > There are a lot of messages in /var/log/messages file as follow: > Sep 23 23:57:50 rtint routed[58]: sendto(fxp0, 224.0.0.1): Permission > denied > Sep 23 23:59:51 rtint routed[58]: sendto(xl0, 224.0.0.1): Permission > denied > > My routed ipfw rules are: > 00010 allow udp from any 520 to any > 00011 allow udp from any to any 520 > > Could anybody help me? Whoops! Hit send a bit too fast there. As I said in the other mail, what are your other rules? The second point I was going to make is that those blocked packets are not 520/udp, but rather ICMP. -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Sep 24 15:45:12 2002 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 852C937B401 for ; Tue, 24 Sep 2002 15:45:11 -0700 (PDT) Received: from smtpproxy2.mitre.org (smtpproxy2.mitre.org [192.80.55.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0A2743E65 for ; Tue, 24 Sep 2002 15:45:10 -0700 (PDT) (envelope-from cyoon@mitre.org) Received: from avsrv2.mitre.org (avsrv2.mitre.org [128.29.154.4]) by smtpproxy2.mitre.org (8.11.3/8.11.3) with ESMTP id g8OMjAL28816 for ; Tue, 24 Sep 2002 18:45:10 -0400 (EDT) Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18]) by smtpsrv2.mitre.org (8.11.3/8.11.3) with ESMTP id g8OMj8l16835 for ; Tue, 24 Sep 2002 18:45:08 -0400 (EDT) Received: from mm112480-2k.mitre.org (128.29.48.49) by mailhub2.mitre.org with SMTP id 11694305; Tue, 24 Sep 2002 18:45:01 -0400 Message-ID: <3D90EAF0.423E361D@mitre.org> Date: Tue, 24 Sep 2002 18:45:04 -0400 From: "PSI, Chan Yoon" Reply-To: cyoon@mitre.org Organization: The MITRE Corporation X-Mailer: Mozilla 4.79 [en]C-20020130M (Windows NT 5.0; U) X-Accept-Language: en,ko MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: MPLS on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Is there any freeware/shareware implementation of MPLS on FreeBSD? It seems that NIST version is no longer updated. Any comments will be welcomed! Thanks, Chan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Sep 24 15:57:31 2002 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 590E237B401 for ; Tue, 24 Sep 2002 15:57:30 -0700 (PDT) Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [12.13.247.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A03DC43E75 for ; Tue, 24 Sep 2002 15:57:29 -0700 (PDT) (envelope-from thomas.r.henderson@boeing.com) Received: from slb-av-02.boeing.com ([129.172.13.7]) by stl-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id RAA08905; Tue, 24 Sep 2002 17:57:28 -0500 (CDT) Received: from slb-hub-01.boeing.com (localhost [127.0.0.1]) by slb-av-02.boeing.com (8.9.3/8.9.2/MBS-AV-02) with ESMTP id PAA06780; Tue, 24 Sep 2002 15:57:27 -0700 (PDT) Received: from xch-nwbh-02.nw.nos.boeing.com (xch-nwbh-02.nw.nos.boeing.com [192.54.12.28]) by slb-hub-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id g8OMvPO11040; Tue, 24 Sep 2002 15:57:26 -0700 (PDT) Received: by xch-nwbh-02.nw.nos.boeing.com with Internet Mail Service (5.5.2650.21) id ; Tue, 24 Sep 2002 15:57:24 -0700 Message-ID: <6938661A6EDA8A4EA8D1419BCE46F24C2B06B5@XCH-NW-27.nw.nos.boeing.com> From: "Henderson, Thomas R" To: "'Peter Godman'" , freebsd-net@freebsd.org Subject: RE: NewReno implementation questions. Date: Tue, 24 Sep 2002 15:56:53 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > -----Original Message----- > From: Peter Godman [mailto:pete@isilon.com] > Sent: Tuesday, September 24, 2002 1:20 PM > To: freebsd-net@freebsd.org > Subject: NewReno implementation questions. > I appreciate any and all advice about this code and whether this is > desirable behaviour for some reason I haven't thought of. I > will triple > check RFC 2852 to see whether and if so why this is > prescribed behaviour. > You can find this in RFC 2581. Duplicate acks are defined as acks that are sent immediately upon receipt of out-of-order data, hence implying that they are data-less (the Net/3 code back to Reno has defined dupacks this way). Then, fast retransmit is defined as: "The fast retransmit algorithm uses the arrival of 3 duplicate ACKs (4 identical ACKs without the arrival of any other intervening packets) as an indication that a segment has been lost." RFC 2582 for NewReno is based on 2581 with addition of "recover" and partial ack handling. However, in the FreeBSD code, the counter t_dupacks is also used as a record of whether the sender entered and is leaving recovery mode-- this causes problems such as the case you described. Jeffrey Hsu has been working on a fix for the general problem of overloading the t_dupacks counter like this. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Sep 24 16:15:57 2002 Delivered-To: freebsd-net@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 916) id 4A6B937B401; Tue, 24 Sep 2002 16:15:56 -0700 (PDT) Date: Tue, 24 Sep 2002 16:15:56 -0700 From: Prafulla Deuskar To: freebsd-net@freebsd.org Subject: Fwd: mbuf chain Message-ID: <20020924161556.A63584@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-Operating-System: FreeBSD 4.7-RC on an i386 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Sorry for the cross-posting. ---------------------------- All, Is there a pre-set limit on maximum number of fragments in a mbuf chain ? I see 64 fragments with jumboframes (mtu 9000) using nttcp. Thanks, Prafulla ----- End forwarded message ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Sep 24 21:27:21 2002 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 32A3137B401; Tue, 24 Sep 2002 21:27:20 -0700 (PDT) Received: from iguana.icir.org (iguana.icir.org [192.150.187.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD76B43E4A; Tue, 24 Sep 2002 21:27:19 -0700 (PDT) (envelope-from rizzo@iguana.icir.org) Received: from iguana.icir.org (localhost [127.0.0.1]) by iguana.icir.org (8.12.3/8.11.3) with ESMTP id g8P4RJIb042448; Tue, 24 Sep 2002 21:27:19 -0700 (PDT) (envelope-from rizzo@iguana.icir.org) Received: (from rizzo@localhost) by iguana.icir.org (8.12.3/8.12.3/Submit) id g8P4RJ3R042447; Tue, 24 Sep 2002 21:27:19 -0700 (PDT) (envelope-from rizzo) Date: Tue, 24 Sep 2002 21:27:19 -0700 From: Luigi Rizzo To: Prafulla Deuskar Cc: freebsd-net@FreeBSD.ORG Subject: Re: Fwd: mbuf chain Message-ID: <20020924212719.A42295@iguana.icir.org> References: <20020924161556.A63584@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020924161556.A63584@hub.freebsd.org>; from pdeuskar@FreeBSD.ORG on Tue, Sep 24, 2002 at 04:15:56PM -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Sep 24, 2002 at 04:15:56PM -0700, Prafulla Deuskar wrote: > Sorry for the cross-posting. > ---------------------------- > > All, > > Is there a pre-set limit on maximum number of fragments in a > mbuf chain ? > > I see 64 fragments with jumboframes (mtu 9000) using nttcp. aha... (this is related to the problem with the em driver and jumbo frames, right ?) o limit that i know of. And now i clearly see how the long chain might arise -- sosend puts each write in one ro more mbufs, then down in the call chain, sbappend() is called which in turn calls sbcompress(). The problem is, for short writes on a TCP socket (say 128 bytes at a time) the data goes into regular mbufs, not clusters, so sbcompress does not have a chance to compress the chain because of lack of space in the mbufs. A possible workaround would be to modify sbcompress to allocate clusters replacing existing mbufs when such a situation exists. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Sep 24 23: 9:25 2002 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 5E0E637B401 for ; Tue, 24 Sep 2002 23:09:24 -0700 (PDT) Received: from venus.vincentjardin.net (AVelizy-102-1-3-174.abo.wanadoo.fr [217.128.244.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2A7543E3B for ; Tue, 24 Sep 2002 23:09:23 -0700 (PDT) (envelope-from jardin@venus.vincentjardin.net) Received: by venus.vincentjardin.net (Postfix, from userid 501) id E69C31503A0; Wed, 25 Sep 2002 08:24:19 +0200 (CEST) Content-Type: text/plain; charset="iso-8859-1" From: Vincent Jardin To: freebsd-net@freebsd.org Subject: Re: MPLS on FreeBSD Date: Wed, 25 Sep 2002 08:24:19 +0200 X-Mailer: KMail [version 1.3.1] References: <3D90EAF0.423E361D@mitre.org> In-Reply-To: <3D90EAF0.423E361D@mitre.org> Cc: cyoon@mitre.org MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020925062419.E69C31503A0@venus.vincentjardin.net> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Did you check the Ayame's MPLS support ? It is written for NetBSD, however, it could be ported to FreeBSD. Moreover they have added the LDP support for Zebra. The source code is available on http://www.ayame.org/Download.php Vincent Le Mercredi 25 Septembre 2002 00:45, PSI, Chan Yoon a écrit : > Is there any freeware/shareware implementation of MPLS on FreeBSD? > It seems that NIST version is no longer updated. > > Any comments will be welcomed! > > Thanks, > Chan > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Sep 25 4:49:23 2002 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 870AC37B401; Wed, 25 Sep 2002 04:49:21 -0700 (PDT) Received: from pina.terra.com.br (pina.terra.com.br [200.176.3.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2098443E65; Wed, 25 Sep 2002 04:49:10 -0700 (PDT) (envelope-from eick.jac@terra.com.br) Received: from smtp4-poa.terra.com.br (smtp4-poa.terra.com.br [200.176.3.35]) by pina.terra.com.br (Postfix) with ESMTP id 179D652F53; Wed, 25 Sep 2002 08:48:31 -0300 (EST) Received: from terra.com.br (webmail2.terra.com.br [200.176.3.177]) (authenticated user eick.jac) by smtp4-poa.terra.com.br (Postfix) with ESMTP id C0F7BAC632; Wed, 25 Sep 2002 08:48:30 -0300 (EST) Date: Wed, 25 Sep 2002 08:48:30 -0300 Message-Id: Subject: Re: Routed Log MIME-Version: 1.0 Content-Type: text/plain;charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable From: "Eicke Felipe" To: "cjc" Cc: "freebsd-net" X-XaM3-API-Version: 2.4 R5 B5 JSC SMTP AUTH X-SenderIP: 200.162.114.126 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi tks! Let me see if I undestood...routed uses ICMP protrocol? I do not permit any ICMP packages... What could I do to solve this?Permit ICMP 520? Thanks a lot. Eicke. > ---------- Mensagem original ----------- > > De : owner-freebsd-net@FreeBSD.ORG > Para : Eicke Felipe > Cc : freebsd-net > Data : Tue, 24 Sep 2002 14:16:23 -0700 > Assunto : Re: Routed Log > > On Tue, Sep 24, 2002 at 08:31:42AM -0300, Eicke Felipe wrote: > Hi folks, > > There are a lot of messages in /var/log/messages file as follow: > > Sep 23 23:57:50 rtint routed[58]: sendto(fxp0, 224.0.0.1): Permission > > denied > > Sep 23 23:59:51 rtint routed[58]: sendto(xl0, 224.0.0.1): Permission > > denied > > > > My routed ipfw rules are: > > 00010 allow udp from any 520 to any > > 00011 allow udp from any to any 520 > > > > Could anybody help me? > > Whoops! Hit send a bit too fast there. > > As I said in the other mail, what are your other rules? > > The second point I was going to make is that those blocked packets are > not 520/udp, but rather ICMP. > -- > Crist J. Clark | cjclark@alum.mit.edu > | cjclark@jhu.edu > http://people.freebsd.org/~cjc/ | cjc@freebsd.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Sep 25 7: 2:54 2002 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 6594437B401; Wed, 25 Sep 2002 07:02:53 -0700 (PDT) Received: from hotmail.com (f130.law9.hotmail.com [64.4.9.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E47E43E75; Wed, 25 Sep 2002 07:02:53 -0700 (PDT) (envelope-from soheil_h_y@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 25 Sep 2002 07:02:47 -0700 Received: from 62.217.112.170 by lw9fd.law9.hotmail.msn.com with HTTP; Wed, 25 Sep 2002 14:02:47 GMT X-Originating-IP: [62.217.112.170] From: "soheil h" To: freebsd-net@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: IP OPTION Date: Wed, 25 Sep 2002 17:32:47 +0330 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 25 Sep 2002 14:02:47.0643 (UTC) FILETIME=[3A59BAB0:01C2649C] Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi list I wrote two function i run them on one computer to see if they are reverse the functions are for tunnel i insert the addresses to optional ip section with option no. 111 like this: type 111 , len 12 , src, dst when i decode them and call the reverse func. it makes all of 12 bytes to 1 NOOPT option . but when i traceroute through it by one client some routers at the end of the path drop my packet it goes truely to 13th or 15th node ( router and path through ) but after some routers doesn't accept my packet i don't know why the ip checksum is true' i use ip_insertoption() function to do so when i use the ip_strip option for reverse it doesn't work at all thanx _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Sep 25 11:51:19 2002 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 2517337B401 for ; Wed, 25 Sep 2002 11:51:18 -0700 (PDT) Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id B088143E77 for ; Wed, 25 Sep 2002 11:51:17 -0700 (PDT) (envelope-from crist.clark@attbi.com) Received: from blossom.cjclark.org ([12.234.91.48]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020925185117.WWBF16629.rwcrmhc51.attbi.com@blossom.cjclark.org>; Wed, 25 Sep 2002 18:51:17 +0000 Received: from blossom.cjclark.org (localhost. [127.0.0.1]) by blossom.cjclark.org (8.12.3/8.12.3) with ESMTP id g8PIpGWn051821; Wed, 25 Sep 2002 11:51:16 -0700 (PDT) (envelope-from crist.clark@attbi.com) Received: (from cjc@localhost) by blossom.cjclark.org (8.12.3/8.12.3/Submit) id g8PIpFgb051820; Wed, 25 Sep 2002 11:51:15 -0700 (PDT) X-Authentication-Warning: blossom.cjclark.org: cjc set sender to crist.clark@attbi.com using -f Date: Wed, 25 Sep 2002 11:51:14 -0700 From: "Crist J. Clark" To: Eicke Felipe Cc: freebsd-net Subject: Re: Routed Log Message-ID: <20020925185114.GA51787@blossom.cjclark.org> Reply-To: cjclark@alum.mit.edu References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-URL: http://people.freebsd.org/~cjc/ Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Sep 25, 2002 at 08:48:30AM -0300, Eicke Felipe wrote: > Hi tks! > Let me see if I undestood...routed uses ICMP protrocol? RTFM, man routed, DESCRIPTION Routed is a daemon invoked at boot time to manage the network routing tables. It uses Routing Information Protocol, RIPv1 (RFC 1058), RIPv2 (RFC 1723), and Internet Router Discovery Protocol (RFC 1256) to maintain the kernel routing table. The RIPv1 protocol is based on the reference 4.3BSD daemon. It listens on the udp(4) socket for the route(8) service (see services(5)) for Routing Information Protocol packets. It also sends and receives multicast Router Discovery ICMP messages. If the host is a ^^^^^^^^^ ^^^^^^ ^^^^^^^^^ ^^^^ ^^^^^^^^ router, routed periodically supplies copies of its routing tables to any directly connected hosts and networks. It also advertises or solicits default routes using Router Discovery ICMP messages. ^^^^^^ ^^^^^^^^^ ^^^^ ^^^^^^^^ > I do not permit any ICMP packages... > What could I do to solve this?Permit ICMP 520? ICMP 520? ICMP Router Advertisements are ICMP type 9. Again, if we RTFM, no_rdisc disables the Internet Router Discovery Protocol. Do you maybe just want to turn this off? Another question might be, if you don't know what all of this stuff is, do you really need to be running routed(8) at all? -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Sep 25 12:15:54 2002 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 DC35437B401 for ; Wed, 25 Sep 2002 12:15:53 -0700 (PDT) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F01243E6E for ; Wed, 25 Sep 2002 12:15:53 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (#6@localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.12.5/8.12.5) with ESMTP id g8PJFmkM029716; Wed, 25 Sep 2002 15:15:48 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <200209251915.g8PJFmkM029716@whizzo.transsys.com> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: cjclark@alum.mit.edu Cc: Eicke Felipe , freebsd-net X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: Routed Log References: <20020925185114.GA51787@blossom.cjclark.org> In-reply-to: Your message of "Wed, 25 Sep 2002 11:51:14 PDT." <20020925185114.GA51787@blossom.cjclark.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Sep 2002 15:15:48 -0400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > I do not permit any ICMP packages... > > What could I do to solve this?Permit ICMP 520? Sigh, and this is why Path MTU discovery is broken on the Internet. You know, that ICMP stuff actually gets used for useful purposes. Just blocking it completely has implications that you should think about; ICMP is not entirely optional despite the appearance otherwise. E.g., don't wonder why you have problems using PPPoE and other network media with MTUs smaller than 1500 bytes along the path.. Louis Mamakos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Sep 25 12:40:33 2002 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 3C95537B406; Wed, 25 Sep 2002 12:40:32 -0700 (PDT) Received: from ambrisko.com (adsl-64-174-51-42.dsl.snfc21.pacbell.net [64.174.51.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id B673543E3B; Wed, 25 Sep 2002 12:40:31 -0700 (PDT) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.11.6/8.11.6) id g8PJdjr10039; Wed, 25 Sep 2002 12:39:45 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200209251939.g8PJdjr10039@ambrisko.com> Subject: Re: Fwd: mbuf chain In-Reply-To: <20020924212719.A42295@iguana.icir.org> To: Luigi Rizzo Date: Wed, 25 Sep 2002 12:39:45 -0700 (PDT) Cc: Prafulla Deuskar , freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Luigi Rizzo writes: | On Tue, Sep 24, 2002 at 04:15:56PM -0700, Prafulla Deuskar wrote: | > Sorry for the cross-posting. | > ---------------------------- | > | > All, | > | > Is there a pre-set limit on maximum number of fragments in a | > mbuf chain ? | > | > I see 64 fragments with jumboframes (mtu 9000) using nttcp. | | aha... (this is related to the problem with the em driver and jumbo | frames, right ?) | | o limit that i know of. | And now i clearly see how the long chain might arise -- sosend puts | each write in one ro more mbufs, then down in the call chain, | sbappend() is called which in turn calls sbcompress(). The problem | is, for short writes on a TCP socket (say 128 bytes at a time) the | data goes into regular mbufs, not clusters, so sbcompress does not | have a chance to compress the chain because of lack of space in the | mbufs. | | A possible workaround would be to modify sbcompress to allocate | clusters replacing existing mbufs when such a situation exists. Various drivers have code to deal with this when the structure it is putting the frags into runs out :-( See a recent bug fix to the ste(4) gleaned from the fxp(4). This type of problem is probably lurking in other drivers. Unfortunately the ste(4) driver siliently failed and sent out truncated packets before the fix. When I instrumented the code while the system was hosting a CVS pserver checkout I saw the frag count go up to 10. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Sep 25 12:48:43 2002 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 2ABC537B401; Wed, 25 Sep 2002 12:48:42 -0700 (PDT) Received: from iguana.icir.org (iguana.icir.org [192.150.187.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDA3F43E4A; Wed, 25 Sep 2002 12:48:41 -0700 (PDT) (envelope-from rizzo@iguana.icir.org) Received: from iguana.icir.org (localhost [127.0.0.1]) by iguana.icir.org (8.12.3/8.11.3) with ESMTP id g8PJmAIb050357; Wed, 25 Sep 2002 12:48:10 -0700 (PDT) (envelope-from rizzo@iguana.icir.org) Received: (from rizzo@localhost) by iguana.icir.org (8.12.3/8.12.3/Submit) id g8PJmAPd050356; Wed, 25 Sep 2002 12:48:10 -0700 (PDT) (envelope-from rizzo) Date: Wed, 25 Sep 2002 12:48:10 -0700 From: Luigi Rizzo To: Doug Ambrisko Cc: Prafulla Deuskar , freebsd-net@FreeBSD.ORG Subject: Re: Fwd: mbuf chain Message-ID: <20020925124810.B50200@iguana.icir.org> References: <20020924212719.A42295@iguana.icir.org> <200209251939.g8PJdjr10039@ambrisko.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200209251939.g8PJdjr10039@ambrisko.com>; from ambrisko@ambrisko.com on Wed, Sep 25, 2002 at 12:39:45PM -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Sep 25, 2002 at 12:39:45PM -0700, Doug Ambrisko wrote: ... > Various drivers have code to deal with this when the structure > it is putting the frags into runs out :-( See a recent bug fix to > the ste(4) gleaned from the fxp(4). This type of problem is probably > lurking in other drivers. Unfortunately the ste(4) driver siliently which suggests that we should definitely try to modify sbappend() and/or possibly sbcompress to reduce the fragment count to reasonably small values even in presence of very small writes. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Sep 25 13: 1:32 2002 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 CAF3337B401; Wed, 25 Sep 2002 13:01:31 -0700 (PDT) Received: from ambrisko.com (adsl-64-174-51-42.dsl.snfc21.pacbell.net [64.174.51.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 442AA43E6E; Wed, 25 Sep 2002 13:01:31 -0700 (PDT) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.11.6/8.11.6) id g8PK0Z610725; Wed, 25 Sep 2002 13:00:35 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200209252000.g8PK0Z610725@ambrisko.com> Subject: Re: Fwd: mbuf chain In-Reply-To: <20020925124810.B50200@iguana.icir.org> To: Luigi Rizzo Date: Wed, 25 Sep 2002 13:00:35 -0700 (PDT) Cc: Doug Ambrisko , Prafulla Deuskar , freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Luigi Rizzo writes: | On Wed, Sep 25, 2002 at 12:39:45PM -0700, Doug Ambrisko wrote: | ... | > Various drivers have code to deal with this when the structure | > it is putting the frags into runs out :-( See a recent bug fix to | > the ste(4) gleaned from the fxp(4). This type of problem is probably | > lurking in other drivers. Unfortunately the ste(4) driver siliently | | which suggests that we should definitely try to modify sbappend() | and/or possibly sbcompress to reduce the fragment count to reasonably | small values even in presence of very small writes. Sounds good to me. BTW a simple test is to do a "dd" of small writes over rsh/ssh. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Sep 26 1: 1:14 2002 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 7E49237B401 for ; Thu, 26 Sep 2002 01:01:13 -0700 (PDT) Received: from out5.mx.nwbl.wi.voyager.net (out5.mx.nwbl.wi.voyager.net [169.207.3.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCE9343E42 for ; Thu, 26 Sep 2002 01:01:12 -0700 (PDT) (envelope-from silby@silby.com) Received: from pop5.nwbl.wi.voyager.net (pop5.nwbl.wi.voyager.net [169.207.3.83]) by out5.mx.nwbl.wi.voyager.net (Postfix) with ESMTP id 18BECC6B5D; Thu, 26 Sep 2002 03:00:29 -0500 (CDT) Received: from [10.1.1.6] (d34.as6.nwbl0.wi.voyager.net [169.207.128.34]) by pop5.nwbl.wi.voyager.net (8.10.2/8.10.2) with ESMTP id g8Q80Ru87369; Thu, 26 Sep 2002 03:00:27 -0500 (CDT) Date: Thu, 26 Sep 2002 03:04:37 -0500 (CDT) From: Mike Silbersack To: Giorgos Keramidas Cc: freebsd-net@freebsd.org Subject: Re: mbuf chain In-Reply-To: <20020925090309.GC597@hades.hell.gr> Message-ID: <20020926025730.J6503-100000@patrocles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 25 Sep 2002, Giorgos Keramidas wrote: > On 2002-09-24 13:57, Prafulla Deuskar wrote: > > All, > > > > Is there a pre-set limit on maximum number of fragments in a > > mbuf chain ? > > Not as a limit of the mbuf chain code, but as a limit of the IP packet > input code. Look at the description of the ip_maxfragpackets sysctl > value in src/sys/netinet/ip_input.c > > It is initialized by default to (nmbclusters / 4) in ip_init(). > > The relevant code, that enforces the limit, is near the beginning of > the ip_reass() function in the same file. > > Giorgos. I don't believe that mbuf fragments have any relationship to IP fragmentation. And while you mention it, the IP fragmentation handling code is another place where we need to add mbuf merging/chaining. I've been thinking about this, actually. How many IP fragments will a packet ever truly have? If you assume a 1500 byte ethernet packet broken into 200 byte chunks, that's < 8. If you break a jumbo frame into 1500 byte packets, that's < 7. Can there be any normal use of fragmentation that would produce more than 10 or so fragments? Also, will overlapping fragments really ever be seen, or can we just assume that's a sign of abuse? Sorry for the sudden change of direction for this thread, I've been pondering how to improve our resistance to mbuf exhaustion through ip frags. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Sep 26 3: 8:33 2002 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 C0EF737B401 for ; Thu, 26 Sep 2002 03:08:32 -0700 (PDT) Received: from relay1.macomnet.ru (relay1.macomnet.ru [195.128.64.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75A0843E42 for ; Thu, 26 Sep 2002 03:08:31 -0700 (PDT) (envelope-from maxim@macomnet.ru) Received: from news1.macomnet.ru (news1.macomnet.ru [195.128.64.14]) by relay1.macomnet.ru (8.11.6/8.11.6) with ESMTP id g8QA6vw602436; Thu, 26 Sep 2002 14:06:57 +0400 (MSD) Date: Thu, 26 Sep 2002 14:06:56 +0400 (MSD) From: Maxim Konovalov To: Mike Silbersack Cc: Giorgos Keramidas , Subject: Re: mbuf chain In-Reply-To: <20020926025730.J6503-100000@patrocles.silby.com> Message-ID: <20020926140529.P64981-100000@news1.macomnet.ru> References: <20020926025730.J6503-100000@patrocles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org [...] > I don't believe that mbuf fragments have any relationship to IP > fragmentation. > > And while you mention it, the IP fragmentation handling code is another > place where we need to add mbuf merging/chaining. > > I've been thinking about this, actually. How many IP fragments will a > packet ever truly have? If you assume a 1500 byte ethernet packet broken > into 200 byte chunks, that's < 8. If you break a jumbo frame into 1500 > byte packets, that's < 7. Can there be any normal use of fragmentation > that would produce more than 10 or so fragments? Also, will overlapping > fragments really ever be seen, or can we just assume that's a sign of > abuse? > > Sorry for the sudden change of direction for this thread, I've been > pondering how to improve our resistance to mbuf exhaustion through ip > frags. There is net.inet.ip.maxfragpackets but IMHO net.inet.ip.maxfragperpacket will be useful too. -- Maxim Konovalov, MAcomnet, Internet Dept., system engineer phone: +7 (095) 796-9079, mailto:maxim@macomnet.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Sep 26 7:31:10 2002 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 255F637B401 for ; Thu, 26 Sep 2002 07:31:10 -0700 (PDT) Received: from insomnia.spc.org (insomnia.spc.org [195.224.94.183]) by mx1.FreeBSD.org (Postfix) with SMTP id D5A7043E6E for ; Thu, 26 Sep 2002 07:31:08 -0700 (PDT) (envelope-from bms@insomnia.spc.org) Received: (qmail 1059 invoked by uid 1031); 26 Sep 2002 14:27:24 -0000 Date: Thu, 26 Sep 2002 15:27:23 +0100 From: Bruce M Simpson To: "Louis A. Mamakos" Cc: freebsd-net Subject: Re: Routed Log Message-ID: <20020926142723.GD17186@spc.org> Mail-Followup-To: Bruce M Simpson , "Louis A. Mamakos" , freebsd-net References: <20020925185114.GA51787@blossom.cjclark.org> <200209251915.g8PJFmkM029716@whizzo.transsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200209251915.g8PJFmkM029716@whizzo.transsys.com> User-Agent: Mutt/1.3.28i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Sep 25, 2002 at 03:15:48PM -0400, Louis A. Mamakos wrote: > > > I do not permit any ICMP packages... > Sigh, and this is why Path MTU discovery is broken on the Internet. 'Packages' sounds awfully Checkpoint-ish. There's a lot of it about these days. :-( BMS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Sep 26 8: 0:57 2002 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 CEDAC37B401; Thu, 26 Sep 2002 08:00:55 -0700 (PDT) Received: from hotmail.com (f7.law9.hotmail.com [64.4.9.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92BC343E75; Thu, 26 Sep 2002 08:00:55 -0700 (PDT) (envelope-from soheil_h_y@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 26 Sep 2002 08:00:55 -0700 Received: from 62.217.118.102 by lw9fd.law9.hotmail.msn.com with HTTP; Thu, 26 Sep 2002 15:00:54 GMT X-Originating-IP: [62.217.118.102] From: "soheil h" To: freebsd-net@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: UNKNOWN IP OPTION emergency Date: Thu, 26 Sep 2002 18:30:54 +0330 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 26 Sep 2002 15:00:55.0232 (UTC) FILETIME=[83875400:01C2656D] Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Dear All as in stevens' Tcp/Ip illustrated says when a router see an unknown option it must silently ignore it but when i put an option by type 253 len 12 and 10 byte of data some router on my path drop it how can i set an option an put 2 ip address in it that no router delete my data thanx _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Sep 26 8: 9:18 2002 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 5971237B404; Thu, 26 Sep 2002 08:09:17 -0700 (PDT) Received: from tp.databus.com (p70-227.acedsl.com [66.114.70.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8582343E77; Thu, 26 Sep 2002 08:09:16 -0700 (PDT) (envelope-from barney@tp.databus.com) Received: from tp.databus.com (localhost.databus.com [127.0.0.1]) by tp.databus.com (8.12.6/8.12.6) with ESMTP id g8QF9FE0020043; Thu, 26 Sep 2002 11:09:15 -0400 (EDT) (envelope-from barney@tp.databus.com) Received: (from barney@localhost) by tp.databus.com (8.12.6/8.12.6/Submit) id g8QF9FLZ020042; Thu, 26 Sep 2002 11:09:15 -0400 (EDT) Date: Thu, 26 Sep 2002 11:09:15 -0400 From: Barney Wolff To: soheil h Cc: freebsd-net@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: UNKNOWN IP OPTION emergency Message-ID: <20020926150915.GA19976@tp.databus.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-Scanned-By: MIMEDefang 2.21 (www . roaringpenguin . com / mimedefang) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org You can't. Some networks have firewalls or routers that drop any packet with IP options, as a security measure. You will not be able to persuade them otherwise. On Thu, Sep 26, 2002 at 06:30:54PM +0330, soheil h wrote: > some router on my path drop it > how can i set an option an put 2 ip address in it that no router delete my > data -- Barney Wolff I'm available by contract or FT: http://www.databus.com/bwresume.pdf To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Sep 26 8:12:56 2002 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 D5D5037B401 for ; Thu, 26 Sep 2002 08:12:55 -0700 (PDT) Received: from relay1.macomnet.ru (relay1.macomnet.ru [195.128.64.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id A469543E4A for ; Thu, 26 Sep 2002 08:12:54 -0700 (PDT) (envelope-from maxim@macomnet.ru) Received: from news1.macomnet.ru (news1.macomnet.ru [195.128.64.14]) by relay1.macomnet.ru (8.11.6/8.11.6) with ESMTP id g8QFCow626352; Thu, 26 Sep 2002 19:12:50 +0400 (MSD) Date: Thu, 26 Sep 2002 19:12:50 +0400 (MSD) From: Maxim Konovalov To: soheil h Cc: freebsd-net@FreeBSD.ORG Subject: Re: UNKNOWN IP OPTION emergency In-Reply-To: Message-ID: <20020926191050.A32610-100000@news1.macomnet.ru> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 19:00+0400, Sep 26, 2002, soheil h wrote: > > Dear All > > as in stevens' Tcp/Ip illustrated says when a router see an unknown option > it must silently ignore it but when i put an option by type 253 len 12 and > 10 byte of data > some router on my path drop it Do Not Crosspost (r) and Show Your Code (tm) -- Maxim Konovalov, MAcomnet, Internet Dept., system engineer phone: +7 (095) 796-9079, mailto:maxim@macomnet.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Sep 26 9:46:44 2002 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 12CCB37B401; Thu, 26 Sep 2002 09:46:42 -0700 (PDT) Received: from mail.zimmer-medienhaus.de (roosevelt.zimmer-medienhaus.de [212.88.130.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84D5943E4A; Thu, 26 Sep 2002 09:46:40 -0700 (PDT) (envelope-from david.zimmer@zimmer-medienhaus.de) Message-id: Date: Thu, 26 Sep 2002 18:33:18 +0200 Subject: Forwarding selected broadcasts with ipfw To: freebsd-ipfw@freebsd.org, freebsd-net@freebsd.org Cc: dominik.brettnacher@zimmer-medienhaus.de From: "David Zimmer" MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, we are using ipfw on FreeBSD 4.7 PRERELEASE as our main firewall. The box has 5 ethernet segments connected to it that serve - DMZ - DMZ Cisco CallManager - private LAN, Workstations - private LAN, Cisco IP Phones - public LAN, Internet Due to a new application that we are introducing we need to forward broadcast from the private LAN, Workstations into the DMZ. This is necessary for the clients to autoconnect to the server. I thought the forward action in the ipfw rule body could do this but I cannot get it to work. Here is what I did 1. I introduced a rule that should forward the packets, this rule looks like fwd 212.88.130.135 udp from any to 255.255.255.255 19813 2. The incoming packets match this rule according to the output of ipfw show 3. The forwarded packet never gets out onto any interface though, according to tcpdump My questions now are: a) What happens to the disapperaring packets b) is there a way to debug what happens to the packet after the above rule (#1) matches c) what other configuration might solve our problem Before we installed ipfw we just had a Cisco 3640 with several VLANs and appropriate access lists. Cisco offers the option of a so called "ip helper address" to forward selected broadcasts. Thanks for any help, David Zimmer ================================================================ David A. Zimmer Zimmer Medienhaus AG mailto: dz@zimmer-medienhaus.de Trierer Strasse 223-225 http://www.zimmer-medienhaus.de 66663 Merzig, Germany Phone: +49 6861 9312-0 Fax: +49 6861 9312-13 -- all kind of spam to this email address forbidden/keine Werbemails -- ================================================================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Sep 26 9:49:15 2002 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 4419937B401; Thu, 26 Sep 2002 09:49:12 -0700 (PDT) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id A404143E6E; Thu, 26 Sep 2002 09:49:11 -0700 (PDT) (envelope-from larse@ISI.EDU) Received: from isi.edu (iga0vwbiz3ogk53i@nik.isi.edu [128.9.168.58]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g8QGn4C07623; Thu, 26 Sep 2002 09:49:04 -0700 (PDT) Message-ID: <3D933A80.7070208@isi.edu> Date: Thu, 26 Sep 2002 09:49:04 -0700 From: Lars Eggert User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, de-de MIME-Version: 1.0 To: David Zimmer Cc: freebsd-ipfw@freebsd.org, freebsd-net@freebsd.org, dominik.brettnacher@zimmer-medienhaus.de Subject: Re: Forwarding selected broadcasts with ipfw References: Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms000801050701030508060001" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This is a cryptographically signed message in MIME format. --------------ms000801050701030508060001 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit David Zimmer wrote: > 1. I introduced a rule that should forward the packets, this rule looks > like > > fwd 212.88.130.135 udp from any to 255.255.255.255 19813 > > 2. The incoming packets match this rule according to the output of ipfw > show > > 3. The forwarded packet never gets out onto any interface though, > according to tcpdump What's the TTL on the broadcast packets? Lars -- Lars Eggert USC Information Sciences Institute --------------ms000801050701030508060001 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJtjCC AzgwggKhoAMCAQICEGZFcrfMdPXPY3ZFhNAukQEwDQYJKoZIhvcNAQEEBQAwgdExCzAJBgNV BAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgG A1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2Vydmlj ZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkG CSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMDA4MzAwMDAw MDBaFw0wNDA4MjcyMzU5NTlaMIGSMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBD YXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xDzANBgNVBAoTBlRoYXd0ZTEdMBsGA1UECxMUQ2Vy dGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNvbmFsIEZyZWVtYWlsIFJTQSAyMDAw LjguMzAwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAN4zMqZjxwklRT7SbngnZ4HF2ogZ gpcO40QpimM1Km1wPPrcrvfudG8wvDOQf/k0caCjbZjxw0+iZdsN+kvx1t1hpfmFzVWaNRqd knWoJ67Ycvm6AvbXsJHeHOmr4BgDqHxDQlBRh4M88Dm0m1SKE4f/s5udSWYALQmJ7JRr6aFp AgMBAAGjTjBMMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQDExFQcml2YXRlTGFiZWwxLTI5NzAS BgNVHRMBAf8ECDAGAQH/AgEAMAsGA1UdDwQEAwIBBjANBgkqhkiG9w0BAQQFAAOBgQAxsUtH XfkBceX1U2xdedY9mMAmE2KBIqcS+CKV6BtJtyd7BDm6/ObyJOuR+r3sDSo491BVqGz3Da1M G7wD9LXrokefbKIMWI0xQgkRbLAaadErErJAXWr5edDqLiXdiuT82w0fnQLzWtvKPPZE6iZp h39Ins6ln+eE2MliYq0FxjCCAzkwggKioAMCAQICAwglQTANBgkqhkiG9w0BAQQFADCBkjEL MAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3du MQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNVBAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYD VQQDEx9QZXJzb25hbCBGcmVlbWFpbCBSU0EgMjAwMC44LjMwMB4XDTAyMDgyNDE4NTMzOVoX DTAzMDgyNDE4NTMzOVowVDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYD VQQDEwtMYXJzIEVnZ2VydDEcMBoGCSqGSIb3DQEJARYNbGFyc2VAaXNpLmVkdTCCASIwDQYJ KoZIhvcNAQEBBQADggEPADCCAQoCggEBANI2Rrt4ggaQ/IrOsDeOm2H4/R5FRIL6JjDY3StE aogp1r23WKniQ1Vj98Nu5WxlaZ3Iam3Jen5T66H8u7rtMNpK4qAeAGoBsVeyVr1+CTFeuv+m xCh7BvBJwhLdm0zDaoDT05YKYZaqtsT+F286FWJQg31Xtf+vTKLVVrHcsafnteyal2NEt7Ac yZZfjsVLwxp2Lq3cwYfRQRoo7/yCVzS7HsgM6jmbO4taEMo4yC2rpnUbWEUCDTaCYgpAXzAl oiNk7GDh0wz2s5ZSnHRvNSBMAjCmpNtSYHfXFI1ANwrrrHIJ7Ei83+XN32PWY4OPzO3iown9 VR+vM+8lNx9OX28CAwEAAaNWMFQwKgYFK2UBBAEEITAfAgEAMBowGAIBBAQTTDJ1TXlmZkJO VWJOSkpjZFoyczAYBgNVHREEETAPgQ1sYXJzZUBpc2kuZWR1MAwGA1UdEwEB/wQCMAAwDQYJ KoZIhvcNAQEEBQADgYEAXcrIlKmPLM/r8r3oz2ZLPLaT1AyMjYTZY2qq/R7SUtFa9BNlTIFh DG78QKfJ9lo2LMzTPQqMZgNLmj95GbNPI8P8OIq2K6MeCZWz08ROackqTFP6xWbIFIfXcBVR 1dZnDDyDKBBh05KkvyTPawSQyOBUeNBfQUyO4TE+3o58U8UwggM5MIICoqADAgECAgMIJUEw DQYJKoZIhvcNAQEEBQAwgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUx EjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZp Y2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4z MDAeFw0wMjA4MjQxODUzMzlaFw0wMzA4MjQxODUzMzlaMFQxDzANBgNVBAQTBkVnZ2VydDEN MAsGA1UEKhMETGFyczEUMBIGA1UEAxMLTGFycyBFZ2dlcnQxHDAaBgkqhkiG9w0BCQEWDWxh cnNlQGlzaS5lZHUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDSNka7eIIGkPyK zrA3jpth+P0eRUSC+iYw2N0rRGqIKda9t1ip4kNVY/fDbuVsZWmdyGptyXp+U+uh/Lu67TDa SuKgHgBqAbFXsla9fgkxXrr/psQoewbwScIS3ZtMw2qA09OWCmGWqrbE/hdvOhViUIN9V7X/ r0yi1Vax3LGn57XsmpdjRLewHMmWX47FS8Madi6t3MGH0UEaKO/8glc0ux7IDOo5mzuLWhDK OMgtq6Z1G1hFAg02gmIKQF8wJaIjZOxg4dMM9rOWUpx0bzUgTAIwpqTbUmB31xSNQDcK66xy CexIvN/lzd9j1mODj8zt4qMJ/VUfrzPvJTcfTl9vAgMBAAGjVjBUMCoGBStlAQQBBCEwHwIB ADAaMBgCAQQEE0wydU15ZmZCTlViTkpKY2RaMnMwGAYDVR0RBBEwD4ENbGFyc2VAaXNpLmVk dTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUAA4GBAF3KyJSpjyzP6/K96M9mSzy2k9QM jI2E2WNqqv0e0lLRWvQTZUyBYQxu/ECnyfZaNizM0z0KjGYDS5o/eRmzTyPD/DiKtiujHgmV s9PETmnJKkxT+sVmyBSH13AVUdXWZww8gygQYdOSpL8kz2sEkMjgVHjQX0FMjuExPt6OfFPF MYIDJzCCAyMCAQEwgZowgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUx EjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZp Y2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4z MAIDCCVBMAkGBSsOAwIaBQCgggFhMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZI hvcNAQkFMQ8XDTAyMDkyNjE2NDkwNFowIwYJKoZIhvcNAQkEMRYEFDIpA3qDIRKgMlN69VY5 9EmPnoU2MFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0G CCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGtBgsqhkiG9w0BCRACCzGB naCBmjCBkjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJ Q2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNVBAsTFENlcnRpZmljYXRlIFNlcnZp Y2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFpbCBSU0EgMjAwMC44LjMwAgMIJUEwDQYJ KoZIhvcNAQEBBQAEggEAq6XldKOs6OZSQFk3LcqfZzojvyGeOKjE+SPhELMzY9CQgcEJ6uur sZlafKlTw0wy/zn2Qdnekn2vZImznNhfm67RS4F6tdFVPhcpNt/obob7cIBuvH2WPiOetvUv /VE5hHJbe4gU9RUXRRrP/a6tylJRC0F8tSrz1b6Kl47mQCOEPpKhCYe14Y1gy58lQ2zXwxK8 SJauIuQYA6bt+zb9Mhfu5OaMHsvlsUZqdHHwEiyV5bgkBeV8oHkuR4DueZpCa33MOWMfZEUB mx4UweIYh5CBliQ4U5Qb2SoD7bhC+LXRX7ZjrMhPUUdBt01j/Z9vVWs8RYZnWIcYGXoHNufc WgAAAAAAAA== --------------ms000801050701030508060001-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Sep 26 10: 8:53 2002 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 6A4AC37B401; Thu, 26 Sep 2002 10:08:52 -0700 (PDT) Received: from flamingo.mail.pas.earthlink.net (flamingo.mail.pas.earthlink.net [207.217.120.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id 121F543E4A; Thu, 26 Sep 2002 10:08:52 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0400.cvx40-bradley.dialup.earthlink.net ([216.244.43.145] helo=mindspring.com) by flamingo.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17uc87-0007e1-00; Thu, 26 Sep 2002 10:08:47 -0700 Message-ID: <3D933EDD.21AEC91E@mindspring.com> Date: Thu, 26 Sep 2002 10:07:41 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: soheil h Cc: freebsd-net@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: UNKNOWN IP OPTION emergency References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org soheil h wrote: > as in stevens' Tcp/Ip illustrated says when a router see an unknown option > it must silently ignore it but when i put an option by type 253 len 12 and > 10 byte of data > some router on my path drop it > how can i set an option an put 2 ip address in it that no router delete my > data Send a known option, instead? Ignore := pass | drop Normally, it means "drop", because unknown options are assumed to be hop-to-hop, meaning it's illegal for them to come from a router that did not originate them (i.e. a router that doesn't recognize the option forwarding it to one that does). If you want a covert data channel, you aren't going to be able to do it with router options. 8-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Sep 26 20:57:56 2002 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 407C937B401; Thu, 26 Sep 2002 20:57:55 -0700 (PDT) Received: from hotmail.com (f175.law9.hotmail.com [64.4.9.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0294F43E42; Thu, 26 Sep 2002 20:57:55 -0700 (PDT) (envelope-from soheil_h_y@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 26 Sep 2002 20:57:54 -0700 Received: from 217.218.30.73 by lw9fd.law9.hotmail.msn.com with HTTP; Fri, 27 Sep 2002 03:57:54 GMT X-Originating-IP: [217.218.30.73] From: "soheil h" To: tlambert2@mindspring.com, freebsd-net@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: UNKNOWN IP OPTION emergency Date: Fri, 27 Sep 2002 07:27:54 +0330 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 27 Sep 2002 03:57:54.0877 (UTC) FILETIME=[0F009ED0:01C265DA] Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi but the tunnel_send() for multicast tunnel do this with LSRR option is the tunnel_send() a standard tunnel ?????? that anyone understand it ? or not ??? Thanx >From: Terry Lambert >To: soheil h >CC: freebsd-net@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG >Subject: Re: UNKNOWN IP OPTION emergency >Date: Thu, 26 Sep 2002 10:07:41 -0700 > >soheil h wrote: > > as in stevens' Tcp/Ip illustrated says when a router see an unknown >option > > it must silently ignore it but when i put an option by type 253 len 12 >and > > 10 byte of data > > some router on my path drop it > > how can i set an option an put 2 ip address in it that no router delete >my > > data > >Send a known option, instead? > >Ignore := pass | drop > >Normally, it means "drop", because unknown options are assumed to >be hop-to-hop, meaning it's illegal for them to come from a router >that did not originate them (i.e. a router that doesn't recognize >the option forwarding it to one that does). > >If you want a covert data channel, you aren't going to be able to >do it with router options. 8-). > >-- Terry _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Sep 26 21:25: 3 2002 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 BF64537B401; Thu, 26 Sep 2002 21:25:02 -0700 (PDT) Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E07A43E42; Thu, 26 Sep 2002 21:25:02 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0362.cvx21-bradley.dialup.earthlink.net ([209.179.193.107] helo=mindspring.com) by gull.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17umgO-0000UU-00; Thu, 26 Sep 2002 21:24:53 -0700 Message-ID: <3D93DD53.7C653C80@mindspring.com> Date: Thu, 26 Sep 2002 21:23:47 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: soheil h Cc: freebsd-net@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: UNKNOWN IP OPTION emergency References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org soheil h wrote: > Hi > but the tunnel_send() for multicast tunnel do this with LSRR option > is the tunnel_send() a standard tunnel ?????? that anyone understand it ? or > not ??? Thanx Sorry; I couldn't find a tunnel_send() function to check this against in the FreeBSD kernel sources. So I can't rcomment.eally -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 27 2:59:39 2002 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 A62CB37B404 for ; Fri, 27 Sep 2002 02:59:37 -0700 (PDT) Received: from chicken.orbitel.bg (chicken100.orbitel.bg [195.24.32.21]) by mx1.FreeBSD.org (Postfix) with SMTP id B588443E75 for ; Fri, 27 Sep 2002 02:59:35 -0700 (PDT) (envelope-from i.tanusheff@procreditbank.com) Received: (qmail 6834 invoked from network); 27 Sep 2002 09:59:33 -0000 Received: from unknown (HELO procreditbank.com) (212.95.179.198) by chicken.orbitel.bg with SMTP; 27 Sep 2002 09:59:33 -0000 Received: from itaush [172.16.248.250] by Proxy+; Fri, 27 Sep 2002 12:42:10 +0300 for multiple recipients From: "Ivailo Tanusheff" To: "FreeBSD Questions" , "FreeBSD Security" , "FreeBSD Net" Subject: PKI Date: Fri, 27 Sep 2002 12:42:10 +0300 Message-ID: <02f001c2660a$26e197e0$faf810ac@sof.procreditbank.bg> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, Do you know if there is any Certificate server available for FreeBSD? I need to issue certificates to our customers. Thank you in advantage,=A0 Ivailo Tanusheff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 27 6:16:30 2002 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 7691137B407 for ; Fri, 27 Sep 2002 06:16:29 -0700 (PDT) Received: from insomnia.spc.org (insomnia.spc.org [195.224.94.183]) by mx1.FreeBSD.org (Postfix) with SMTP id 8CE5343E77 for ; Fri, 27 Sep 2002 06:16:27 -0700 (PDT) (envelope-from bms@insomnia.spc.org) Received: (qmail 4967 invoked by uid 1031); 27 Sep 2002 13:12:35 -0000 Date: Fri, 27 Sep 2002 14:12:35 +0100 From: Bruce M Simpson To: Ivailo Tanusheff Cc: FreeBSD Questions , FreeBSD Security , FreeBSD Net Subject: Re: PKI Message-ID: <20020927131234.GE26352@spc.org> Mail-Followup-To: Bruce M Simpson , Ivailo Tanusheff , FreeBSD Questions , FreeBSD Security , FreeBSD Net References: <02f001c2660a$26e197e0$faf810ac@sof.procreditbank.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <02f001c2660a$26e197e0$faf810ac@sof.procreditbank.bg> User-Agent: Mutt/1.3.28i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I'm working on a port of OpenCA which is almost ready. Hopefully within the next week (I'm ill at the moment.) :( www.openca.org BMS On Fri, Sep 27, 2002 at 12:42:10PM +0300, Ivailo Tanusheff wrote: > Do you know if there is any Certificate server available for FreeBSD? I > need to issue certificates to our customers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 27 7:14:24 2002 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 1977937B401; Fri, 27 Sep 2002 07:14:23 -0700 (PDT) Received: from hotmail.com (f32.law9.hotmail.com [64.4.9.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7936443E8A; Fri, 27 Sep 2002 07:14:21 -0700 (PDT) (envelope-from soheil_h_y@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 27 Sep 2002 07:14:20 -0700 Received: from 217.218.30.68 by lw9fd.law9.hotmail.msn.com with HTTP; Fri, 27 Sep 2002 14:14:19 GMT X-Originating-IP: [217.218.30.68] From: "soheil h" To: tlambert2@mindspring.com, freebsd-net@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: UNKNOWN IP OPTION emergency Date: Fri, 27 Sep 2002 17:44:19 +0330 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 27 Sep 2002 14:14:20.0392 (UTC) FILETIME=[2C165680:01C26630] Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I see on the TCP/IP illustrated it puts an LSRR option and record the ip addresses into it and make the off 12 !!! to say all the things are done i run this command .... the x.x.x.x is my default gw. but it takes the source route error !!!!!!!!! why this happend? #traceroute -n -g x.x.x.x yahoo.com raceroute to yahoo.com (66.218.71.198), 64 hops max, 48 byte packets 1 x.x.x.x 0.427 ms 0.545 ms 0.399 ms 2 y.y.y.y 0.922 ms 0.484 ms 0.473 ms 3 * * * 4 64.159.0.61 0.872 ms !S 0.663 ms !S 0.715 ms !S >From: Terry Lambert >To: soheil h >CC: freebsd-net@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG >Subject: Re: UNKNOWN IP OPTION emergency >Date: Thu, 26 Sep 2002 21:23:47 -0700 > >soheil h wrote: > > Hi > > but the tunnel_send() for multicast tunnel do this with LSRR option > > is the tunnel_send() a standard tunnel ?????? that anyone understand it >? or > > not ??? Thanx > > >Sorry; I couldn't find a tunnel_send() function to check this >against in the FreeBSD kernel sources. So I can't rcomment.eally > >-- Terry > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-net" in the body of the message _________________________________________________________________ Join the world’s largest e-mail service with MSN Hotmail. http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 27 7:18:15 2002 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 9911737B401 for ; Fri, 27 Sep 2002 07:18:14 -0700 (PDT) Received: from silver.he.iki.fi (silver.he.iki.fi [193.64.42.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82B7E43E75 for ; Fri, 27 Sep 2002 07:18:13 -0700 (PDT) (envelope-from pete@he.iki.fi) Received: from PHE (silver.he.iki.fi [193.64.42.241]) by silver.he.iki.fi (8.12.6/8.11.4) with SMTP id g8REI5UW046378 for ; Fri, 27 Sep 2002 17:18:07 +0300 (EEST) (envelope-from pete@he.iki.fi) Message-ID: <09ce01c26630$ba177cc0$8c2a40c1@PHE> From: "Petri Helenius" To: Subject: SO_TIMESTAMP Date: Fri, 27 Sep 2002 17:18:17 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Is there a reason why SO_TIMESTAMP does not work with TCP sockets but only with RAW and UDP ? Pete To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 27 9:30:32 2002 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 036B437B404; Fri, 27 Sep 2002 09:30:29 -0700 (PDT) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5EB2E43E42; Fri, 27 Sep 2002 09:30:28 -0700 (PDT) (envelope-from larse@ISI.EDU) Received: from isi.edu (c1-vpn3.isi.edu [128.9.176.29]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g8RFp6C00771; Fri, 27 Sep 2002 08:51:06 -0700 (PDT) Message-ID: <3D947E6A.1030406@isi.edu> Date: Fri, 27 Sep 2002 08:51:06 -0700 From: Lars Eggert Organization: USC Information Sciences Institute User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2a) Gecko/20020910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: soheil h Cc: tlambert2@mindspring.com, freebsd-net@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: UNKNOWN IP OPTION emergency References: Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms010100010402000000090007" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This is a cryptographically signed message in MIME format. --------------ms010100010402000000090007 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit soheil h wrote: > > I see on the TCP/IP illustrated it puts an LSRR option and record the ip > addresses into it and make the off 12 !!! to say all the things are done > i run this command .... the x.x.x.x is my default gw. but it takes the > source route error > !!!!!!!!! > why this happend? Many reasons, all of which people can only speculate on until they see your code, a description of your setup and experimental procedure, and a commented packet dump. Lars -- Lars Eggert USC Information Sciences Institute --------------ms010100010402000000090007 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJtjCC AzgwggKhoAMCAQICEGZFcrfMdPXPY3ZFhNAukQEwDQYJKoZIhvcNAQEEBQAwgdExCzAJBgNV BAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgG A1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2Vydmlj ZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkG CSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMDA4MzAwMDAw MDBaFw0wNDA4MjcyMzU5NTlaMIGSMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBD YXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xDzANBgNVBAoTBlRoYXd0ZTEdMBsGA1UECxMUQ2Vy dGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNvbmFsIEZyZWVtYWlsIFJTQSAyMDAw LjguMzAwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAN4zMqZjxwklRT7SbngnZ4HF2ogZ gpcO40QpimM1Km1wPPrcrvfudG8wvDOQf/k0caCjbZjxw0+iZdsN+kvx1t1hpfmFzVWaNRqd knWoJ67Ycvm6AvbXsJHeHOmr4BgDqHxDQlBRh4M88Dm0m1SKE4f/s5udSWYALQmJ7JRr6aFp AgMBAAGjTjBMMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQDExFQcml2YXRlTGFiZWwxLTI5NzAS BgNVHRMBAf8ECDAGAQH/AgEAMAsGA1UdDwQEAwIBBjANBgkqhkiG9w0BAQQFAAOBgQAxsUtH XfkBceX1U2xdedY9mMAmE2KBIqcS+CKV6BtJtyd7BDm6/ObyJOuR+r3sDSo491BVqGz3Da1M G7wD9LXrokefbKIMWI0xQgkRbLAaadErErJAXWr5edDqLiXdiuT82w0fnQLzWtvKPPZE6iZp h39Ins6ln+eE2MliYq0FxjCCAzkwggKioAMCAQICAwglQTANBgkqhkiG9w0BAQQFADCBkjEL MAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3du MQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNVBAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYD VQQDEx9QZXJzb25hbCBGcmVlbWFpbCBSU0EgMjAwMC44LjMwMB4XDTAyMDgyNDE4NTMzOVoX DTAzMDgyNDE4NTMzOVowVDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYD VQQDEwtMYXJzIEVnZ2VydDEcMBoGCSqGSIb3DQEJARYNbGFyc2VAaXNpLmVkdTCCASIwDQYJ KoZIhvcNAQEBBQADggEPADCCAQoCggEBANI2Rrt4ggaQ/IrOsDeOm2H4/R5FRIL6JjDY3StE aogp1r23WKniQ1Vj98Nu5WxlaZ3Iam3Jen5T66H8u7rtMNpK4qAeAGoBsVeyVr1+CTFeuv+m xCh7BvBJwhLdm0zDaoDT05YKYZaqtsT+F286FWJQg31Xtf+vTKLVVrHcsafnteyal2NEt7Ac yZZfjsVLwxp2Lq3cwYfRQRoo7/yCVzS7HsgM6jmbO4taEMo4yC2rpnUbWEUCDTaCYgpAXzAl oiNk7GDh0wz2s5ZSnHRvNSBMAjCmpNtSYHfXFI1ANwrrrHIJ7Ei83+XN32PWY4OPzO3iown9 VR+vM+8lNx9OX28CAwEAAaNWMFQwKgYFK2UBBAEEITAfAgEAMBowGAIBBAQTTDJ1TXlmZkJO VWJOSkpjZFoyczAYBgNVHREEETAPgQ1sYXJzZUBpc2kuZWR1MAwGA1UdEwEB/wQCMAAwDQYJ KoZIhvcNAQEEBQADgYEAXcrIlKmPLM/r8r3oz2ZLPLaT1AyMjYTZY2qq/R7SUtFa9BNlTIFh DG78QKfJ9lo2LMzTPQqMZgNLmj95GbNPI8P8OIq2K6MeCZWz08ROackqTFP6xWbIFIfXcBVR 1dZnDDyDKBBh05KkvyTPawSQyOBUeNBfQUyO4TE+3o58U8UwggM5MIICoqADAgECAgMIJUEw DQYJKoZIhvcNAQEEBQAwgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUx EjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZp Y2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4z MDAeFw0wMjA4MjQxODUzMzlaFw0wMzA4MjQxODUzMzlaMFQxDzANBgNVBAQTBkVnZ2VydDEN MAsGA1UEKhMETGFyczEUMBIGA1UEAxMLTGFycyBFZ2dlcnQxHDAaBgkqhkiG9w0BCQEWDWxh cnNlQGlzaS5lZHUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDSNka7eIIGkPyK zrA3jpth+P0eRUSC+iYw2N0rRGqIKda9t1ip4kNVY/fDbuVsZWmdyGptyXp+U+uh/Lu67TDa SuKgHgBqAbFXsla9fgkxXrr/psQoewbwScIS3ZtMw2qA09OWCmGWqrbE/hdvOhViUIN9V7X/ r0yi1Vax3LGn57XsmpdjRLewHMmWX47FS8Madi6t3MGH0UEaKO/8glc0ux7IDOo5mzuLWhDK OMgtq6Z1G1hFAg02gmIKQF8wJaIjZOxg4dMM9rOWUpx0bzUgTAIwpqTbUmB31xSNQDcK66xy CexIvN/lzd9j1mODj8zt4qMJ/VUfrzPvJTcfTl9vAgMBAAGjVjBUMCoGBStlAQQBBCEwHwIB ADAaMBgCAQQEE0wydU15ZmZCTlViTkpKY2RaMnMwGAYDVR0RBBEwD4ENbGFyc2VAaXNpLmVk dTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUAA4GBAF3KyJSpjyzP6/K96M9mSzy2k9QM jI2E2WNqqv0e0lLRWvQTZUyBYQxu/ECnyfZaNizM0z0KjGYDS5o/eRmzTyPD/DiKtiujHgmV s9PETmnJKkxT+sVmyBSH13AVUdXWZww8gygQYdOSpL8kz2sEkMjgVHjQX0FMjuExPt6OfFPF MYIDJzCCAyMCAQEwgZowgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUx EjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZp Y2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4z MAIDCCVBMAkGBSsOAwIaBQCgggFhMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZI hvcNAQkFMQ8XDTAyMDkyNzE1NTEwNlowIwYJKoZIhvcNAQkEMRYEFD1WjtXxpaGtAkP468G3 Y6GT+wkTMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0G CCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGtBgsqhkiG9w0BCRACCzGB naCBmjCBkjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJ Q2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNVBAsTFENlcnRpZmljYXRlIFNlcnZp Y2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFpbCBSU0EgMjAwMC44LjMwAgMIJUEwDQYJ KoZIhvcNAQEBBQAEggEATqUjKkGi2ftGMLiuXqOt5o4sl7f1627/Mc6JfNAr5lYpzTZT91Be N5B3L+uF6qfqmzYlIiS+FtC+mlhJTAcSE2J1W8FoLBJYKI1b3L3Kmh/uP5FKHqLTrQMoPqd6 CJy7TNYItDRuTGd/olFrwYBUtemG3KEB9VYO5JGUSV0RS3b3Gp3lZ5oLWmcwVMdh1HLB14fs kK2WiedVQeIXkT7mFeSlJzLujG2buwe+cYVLm6aCgcg7goU9Uy0GgwW2AKmqAbfP5ygBKxYg WiAukbHZHVlMa3BnJjemu0hKH88pa1Gvg/Kpv9oDjkSLHBYc7XAj8CookXYszc9VFQfxBxI9 LAAAAAAAAA== --------------ms010100010402000000090007-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 27 10:43:42 2002 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 3EF6E37B401 for ; Fri, 27 Sep 2002 10:43:41 -0700 (PDT) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BFCB43E42 for ; Fri, 27 Sep 2002 10:43:40 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: from khavrinen.lcs.mit.edu (localhost [IPv6:::1]) by khavrinen.lcs.mit.edu (8.12.3/8.12.5) with ESMTP id g8RHhdVo011910 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Fri, 27 Sep 2002 13:43:40 -0400 (EDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.12.3/8.12.5/Submit) id g8RHhbu6011907; Fri, 27 Sep 2002 13:43:37 -0400 (EDT) (envelope-from wollman) Date: Fri, 27 Sep 2002 13:43:37 -0400 (EDT) From: Garrett Wollman Message-Id: <200209271743.g8RHhbu6011907@khavrinen.lcs.mit.edu> To: "Petri Helenius" Cc: Subject: SO_TIMESTAMP In-Reply-To: <09ce01c26630$ba177cc0$8c2a40c1@PHE> References: <09ce01c26630$ba177cc0$8c2a40c1@PHE> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org < said: > Is there a reason why SO_TIMESTAMP does not work with TCP sockets > but only with RAW and UDP ? Because it doesn't really make sense? Since the TCP stream may be arbitrarily re-ordered, knowing when a packet arrived is not particularly useful to an application. If you really care, you should probably use BPF instead. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 27 11:38:59 2002 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 0A63537B401 for ; Fri, 27 Sep 2002 11:38:58 -0700 (PDT) Received: from silver.he.iki.fi (silver.he.iki.fi [193.64.42.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABA6743E42 for ; Fri, 27 Sep 2002 11:38:55 -0700 (PDT) (envelope-from pete@he.iki.fi) Received: from PHE (silver.he.iki.fi [193.64.42.241]) by silver.he.iki.fi (8.12.6/8.11.4) with SMTP id g8RIcSUW047589; Fri, 27 Sep 2002 21:38:50 +0300 (EEST) (envelope-from pete@he.iki.fi) Message-ID: <0a2301c26655$22c4eea0$8c2a40c1@PHE> From: "Petri Helenius" To: "Garrett Wollman" Cc: References: <09ce01c26630$ba177cc0$8c2a40c1@PHE> <200209271743.g8RHhbu6011907@khavrinen.lcs.mit.edu> Subject: Re: SO_TIMESTAMP Date: Fri, 27 Sep 2002 21:38:39 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > Is there a reason why SO_TIMESTAMP does not work with TCP sockets > > but only with RAW and UDP ? > > Because it doesn't really make sense? But it would. It would let me know how long it took the process to get to the data I´m currently reading from the socket. (and notify operator to buy more hardware if it took too long) > > Since the TCP stream may be arbitrarily re-ordered, knowing when a > packet arrived is not particularly useful to an application. If you > really care, you should probably use BPF instead. > Are you suggesting to reimplement TCP sockets in userland? Pete To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 27 12:11:27 2002 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 7F5BB37B401 for ; Fri, 27 Sep 2002 12:11:26 -0700 (PDT) Received: from mercury.dgim.crc.ca (mercury.dgim.crc.ca [142.92.39.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0041A43E65 for ; Fri, 27 Sep 2002 12:11:26 -0700 (PDT) (envelope-from frederic.massicotte@crc.ca) Received: from hercules (hercules.dgrc.crc.ca [142.92.34.186]) by mercury.dgim.crc.ca (8.12.6/8.12.6) with SMTP id g8RJBGHT004850 for ; Fri, 27 Sep 2002 15:11:16 -0400 Message-Id: <200209271911.g8RJBGHT004850@mercury.dgim.crc.ca> X-Sender: fmassico@mail.crc.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Fri, 27 Sep 2002 15:34:46 -0400 To: freebsd-net@FreeBSD.ORG From: Frederic Massicotte Subject: FreeBSD 2.x Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, I dot know the correct group I should send this message. Thanks for your help. we are a research centre in communications and for our research we need to use FreeBSD version 2.x on VMWare. For version 2.2.8 everything is working fine the operating system have no problem to be installed and the network behave well no device time out and the operating system find the emulated PCI ADM PCNET II ethernet card. So for FreeBSD 2.2.8 we have the following log for the Lance driver. ... vga0 rev 0 on pci 0:15:0 lnc1 rev 16 int a irq 9 on pci 0:16:0 lnc1: PCNet - PCI II address 00:50:56:a6:20:83 Probing for devices on ISA bus : ... In the case of FreeBSD 2.2.7 is not able to find the address of the card and the type of the card but it is just able to find the PCI card. So for FreeBSD 2.2.7 we have the following log for the Lance driver. ... vga0 rev 0 on pci 0:15:0 lnc1 rev 16 int a irq 9 on pci 0:16:0 Probing for devices on ISA bus : ... In the case of FreeBSD 2.2.5 is not able to find the correct card. It find a NE2100 card like lnc1: NE2100 (C-LANCE) address 00:50:56:a6:20:83 and when we configure the card we got the device timeout message. We this situation we are not able to get the network card up and running. If someone have a suggestion we will be very happy because we need to install various version of FreeBSD from the version 2.0.5 to 2.2.8 and we were just able to get one version working with the network. In fact, we have install all version of FreeBSD from 3.0 to 4.6.2 and we were able to get them working and send packet on the network in a VMWare environment. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 27 12:21:56 2002 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 BDD5437B401 for ; Fri, 27 Sep 2002 12:21:54 -0700 (PDT) Received: from newnet.co.uk (newnet.co.uk [212.87.80.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 069F943E3B for ; Fri, 27 Sep 2002 12:21:54 -0700 (PDT) (envelope-from peter@newnet.co.uk) Received: from newnet.co.uk (peter.port [212.87.87.37]) by newnet.co.uk (8.12.3/8.12.3) with ESMTP id g8RJLVNE043203; Fri, 27 Sep 2002 20:21:31 +0100 (BST) (envelope-from peter@newnet.co.uk) Message-ID: <3D94AFA7.3030308@newnet.co.uk> Date: Fri, 27 Sep 2002 20:21:11 +0100 From: Peter V Coates-Buglear User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en MIME-Version: 1.0 To: Frederic Massicotte Cc: freebsd-net@FreeBSD.ORG Subject: Re: FreeBSD 2.x References: <200209271911.g8RJBGHT004850@mercury.dgim.crc.ca> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Newnet-MailScanner: Found to be clean Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Frederic Massicotte wrote: > Hello, > > I dot know the correct group I should send this message. Thanks for your > help. > > we are a research centre in communications and for our research we need to > use FreeBSD version 2.x on VMWare. For version 2.2.8 everything is working > fine the operating system have no problem to be installed and the network > behave well no device time out and the operating system find the emulated > PCI ADM PCNET II ethernet card. So for FreeBSD 2.2.8 we have the following > log for the Lance driver. > > ... > vga0 rev 0 on pci 0:15:0 > lnc1 rev 16 int a irq 9 on pci 0:16:0 > lnc1: PCNet - PCI II address 00:50:56:a6:20:83 > Probing for devices on ISA bus : > ... > > In the case of FreeBSD 2.2.7 is not able to find the address of the card > and the type of the card but it is just able to find the PCI card. So for > FreeBSD 2.2.7 we have the following log for the Lance driver. > > ... > vga0 rev 0 on pci 0:15:0 > lnc1 rev 16 int a irq 9 on pci 0:16:0 > Probing for devices on ISA bus : > ... > > In the case of FreeBSD 2.2.5 is not able to find the correct card. It find > a NE2100 card like > lnc1: NE2100 (C-LANCE) address 00:50:56:a6:20:83 and when we configure the > card we got the device timeout message. > > We this situation we are not able to get the network card up and running. > If someone have a suggestion we will be very happy because we need to > install various version of FreeBSD from the version 2.0.5 to 2.2.8 and we > were just able to get one version working with the network. Hi, For an o/s 4 years old you'll need to use a network card that was current at the time. Something like the original Intel Pro 100B NIC card should be fine. Try e-bay or some such if you don't carry any old spares. Peter NewNet plc UK -- ____________________________________________________ Message scanned for viruses and dangerous content by and believed to be clean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Sep 27 15: 6:21 2002 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 B6C6837B401 for ; Fri, 27 Sep 2002 15:06:19 -0700 (PDT) Received: from scout.networkphysics.com (fw.networkphysics.com [205.158.104.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26DAD43E42 for ; Fri, 27 Sep 2002 15:06:19 -0700 (PDT) (envelope-from pavel@networkphysics.com) Received: from NetworkPhysics.COM (gt500.fractal.networkphysics.com [10.10.0.192]) by scout.networkphysics.com (8.11.5/8.11.5) with ESMTP id g8RM6IR43626 for ; Fri, 27 Sep 2002 15:06:18 -0700 (PDT) Message-Id: <200209272206.g8RM6IR43626@scout.networkphysics.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: freebsd-net@freebsd.org Subject: Question about mbuf allocation and VM routines Reply-To: pavel@alum.mit.edu X-Face: 3Y45fK2P',OZ{p{%jFQfsYLQA)-,d1K+cx@v"K(1.9^"Cx-J*93m!X9nsl*8C\'.tt} ;X+GO]HCw8n=+Dn Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I'm working on tracking down a crash in a 4.x system that showed up as a corruption of the kmapentzone zalloc() zone. I'm not sure what all is unusual about my system, but I suspect one key element is that it is using a lot more mbufs than a typical box. Anyway, all this leads me to ask about the following code. When all of the initial NMB_INIT mbufs are used up, the m_mballoc() routine will add more pages to mb_map, up the limit of nmbufs. Now, all of the MGET() and related routes set splimp, so they should serialize access correctly between ethernet drivers and the network stack code, for example. int m_mballoc(nmb, how) register int nmb; int how; { register caddr_t p; register int i; int nbytes; ... nbytes = round_page(nmb * MSIZE); p = (caddr_t)kmem_malloc(mb_map, nbytes, M_NOWAIT); if (p == 0 && how == M_WAIT) { mbstat.m_wait++; p = (caddr_t)kmem_malloc(mb_map, nbytes, M_WAITOK); } However, as shown in this excerpt m_mballoc() calls kmem_malloc(), which from its comments expects to be called at splhigh (or perhaps splvm?). Ultimately, my call chain leads me to vm_map_entry_create(mb_map), and I fear that the resulting zalloc()/zfree() is interrupted by something else at splvm, and thereby corrupts the kmapentzone free list. That would be consistent with the crash I've seen. So, my question is whether the above analysis makes sense, and whether the kmem_malloc(M_NOWAIT) call in m_mballoc() should be wrapped in splvm. I assume the M_WAITOK call should not be wrapped, but I haven't thought that one through. Any other insights about this? Many thanks, Tom Pavel Network Physics pavel@networkphysics.com / pavel@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Sep 28 8:30:32 2002 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 7587037B401 for ; Sat, 28 Sep 2002 08:30:27 -0700 (PDT) Received: from www.example.org (ANice-103-1-4-64.abo.wanadoo.fr [80.13.156.64]) by mx1.FreeBSD.org (Postfix) with SMTP id 9855B43E6A for ; Sat, 28 Sep 2002 08:30:25 -0700 (PDT) (envelope-from molter@tin.it) Received: (qmail 6030 invoked by uid 1000); 28 Sep 2002 15:30:21 -0000 Message-ID: <20020928153021.6029.qmail@cobweb.example.org> Date: Sat, 28 Sep 2002 17:30:20 +0200 From: Marco Molteni To: freebsd-mobile@freebsd.org Cc: freebsd-net@freebsd.org Subject: Fw: Link Triggers on Linux X-Mailer: Sylpheed version 0.8.2 (GTK+ 1.2.10; i386-portbld-freebsd4.6) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org FYI. Very interesting for people working on mobility and wireless networks like 802.11. Anybody interested in doing something similar for FreeBSD? Marco ----- Forwarded message from "Jean Tourrilhes" ----- To: pilc@ietf.org From: "Jean Tourrilhes" Subject: [pilc] On Link Triggers (implementation) Date: Tue, 24 Sep 2002 15:57:29 -0700 Hi, I quickly scanned through the Link Trigger discussion on the mailing list (don't have time to read all that). Maybe I should add a few comments (and sorry if I re-ignite a flame war). I've recently wrote a little protocol call P-Handoff. It is totally off topic, apart from the fact that to implement this protocol, I needed Link Triggers, which of course I also implemented (my bad habit of implementing before talking about it). So, maybe my practical experience can be of some use to some of you (or maybe not)... 1) Implementation status ------------------------ All implementation done on Linux only. Implemented for Wireless LANs (802.11, ...) through the Wireless Extensions (Wireless Events) since early 2002. Standard in Linux kernel 2.4.20-pre2 and higher. Not all WLAN driver do support it (See my web pages for more details). Implemented for IrDA (IrNET) through the IrNET control channel since early 2001. Standard in most 2.4.X kernel. 2) Mechanisms ------------- I fully agree with few people, the mechansisms to deliver those trigger are totally OS specific. For example, under Linux I use the RtNetLink socket, which is also used for most management messages (new/del routes, interface up/down, ...). I expect that other OSes would have more appropriate mechanisms. I also use different mechanisms for different link layers, but that's mostly an accident ;-) 3) Semantic ----------- My personal belief is that the semantic of those events is link specific, therefore I believe that it won't be possible to standardise them across all link layers. I'm not talking about the small stuff, such as the fact the WLAN events carry a IEEE 48 bit address while IrDA events carry a random 32 bit address. Most often the meaning of the event as well as the action to take on it is different. I guess I'll have to go through an example on that one ;-) These are the "failure" events that I've defined and could be used to trigger Vertical-Handoff. WLAN events : o SIOCGIWAP(addr) : Successfully registered to Access Point with address 'addr'. If 'addr' is NULL, it means that we could not find any Access Point suitable (out of range). This is generated at the end of the link layer handoff. o IWEVTXDROP(addr) : Packet sent to 'addr' was dropped due to excessive retries. o SNR : this is not an event, but you can poll the SNR for each peer through iwspy (updated on Rx'd packets). IrNET events : o Disconnected(addr) : IrDA stack closed the link connection to peer 'addr'. May be due to link failure (12s timeout) or explicit disconnection from one end. At this point, the IP interface is going to be destroyed. o Link-Blocked(addr) : Peer 'addr' failed to turnaround the link layer. We have not heard from the peer for one second (max link turn around time in IrDA is 500ms). However, the connection to the peer still has not timed out. As you can see, the semantic of those events are very different, and you really need to understand in which cisconstance they are generated to make good use of them. For example, if you want to trigger vertical handoff on the "Link-Blocked" event on IrNET, you have to remember that you need to explicitely disconnect the IrNET connection. On the other hand, you may want to accumulate a few IWEVTXDROP events before doing anything to avoid false positive due to long fade on the wireless channel, especially if your number of link level retry is small. For example, you may want to only start pre-allocating the backup path on the first event, and to really switch only after 3 or 4 events. But, you also need a fallback to IWEVTXDROP, because it will be generated only if there is outgoing traffic (as opposed to other events that will be generated in absence of traffic). And don't expect any SNR on IrDA ;-) Yeah, you could probably defined some meta-events abstracting and encapsulating the link layer events in some form (like "something bad happen on the link"). Actually, nobody prevent you to define your own set of standard events on the low level events I've defined. But in that case you would loose the benefit of the approach, which is to have a precise and dependable status of the link layer (which is needed to know exactly what's happening). 4) Timing --------- Those events don't have to be fast, but they have to be precise. None of the events I've defined is really fast, apart from IWEVTXDROP. For example, SIOCGIWAP occur *after* L2 handover. Most L2 handover on 802.11b take in the order of one second. On the other hand, the L2 state after this event is stable, and you don't run the risk of having L2 handoff and vertical handoff happening in parallel. Same for the IrNET events. By design, the link layer is not going to give you anything faster than that. Most wireless links need to average bad channel and fading on relatively slow time (order of 1 second) through the use of ARQ/FEC/interleaving/diversity, so you need wait patiently while the link do its job. I personally believe it's more important to make the decision right than to make it fast. 5) Where do events go --------------------- Some people have suggested that those events should go up the IP stack. I personally don't think that this is the best approach, because this is not where those events are needed. And also I don't want to polute the TCP/IP higher layer interfaces with link specific stuff (this is about layer separation). Another way to look at this : TCP/IP connections are mapped on links through the IP routing table. Not all links may have a route configured on them. A TCP connection may be migrated from one link to another, or even "bonded" on two of them. I don't see how you could get any way to map link information to TCP connections in any meaningfull way. For me, the events go sideway, directly into the management plane (so, staying within layer 2, and not going to layer 3). Very similar to the link layer configuration (ESSID, WEP) that is done totally outside the TCP/IP stack (so, it's not a surprise that I implemented those events in the link management channel). TCP/IP doesn't have to know about those events, they are purely a link API issue. I would expect that the main use of those events would be for user feedback ("your battery is flat and your connectivity shaky") and other things that are totally unrelated to TCP/IP. On top of that, the MobileIP manager or the AODV manager could connect directly to the link interface to get those events and would manipulate the routing table according to those (most OSes have well defined APIs to manipulate routing table). So, I guess that people interested in Link Triggers just need to download their favorite Linux distribution, get a 802.11 card and and start playing with it and making their own informed opinion ;-) Have fun... Jean _______________________________________________ pilc mailing list pilc@ietf.org ----- End forwarded message ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Sep 28 9: 3:45 2002 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 512E037B401 for ; Sat, 28 Sep 2002 09:03:43 -0700 (PDT) Received: from mail020.syd.optusnet.com.au (mail020.syd.optusnet.com.au [210.49.20.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 445FE43E81 for ; Sat, 28 Sep 2002 09:03:42 -0700 (PDT) (envelope-from david.burns@dugeem.net) Received: from dugeem.net (c19426.carlnfd1.nsw.optusnet.com.au [211.28.175.9]) by mail020.syd.optusnet.com.au (8.11.1/8.11.1) with ESMTP id g8SG3bQ30893; Sun, 29 Sep 2002 02:03:37 +1000 Message-ID: <3D95D34E.8020200@dugeem.net> Date: Sun, 29 Sep 2002 02:05:34 +1000 From: David Burns User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Frederic Massicotte Cc: freebsd-net@FreeBSD.ORG Subject: Re: FreeBSD 2.x References: <200209271911.g8RJBGHT004850@mercury.dgim.crc.ca> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Frederic Massicotte wrote: > Hello, > > I dot know the correct group I should send this message. Thanks for your > help. > > we are a research centre in communications and for our research we need to > use FreeBSD version 2.x on VMWare. For version 2.2.8 everything is working > fine the operating system have no problem to be installed and the network > behave well no device time out and the operating system find the emulated > PCI ADM PCNET II ethernet card. So for FreeBSD 2.2.8 we have the following > log for the Lance driver. > > ... > vga0 rev 0 on pci 0:15:0 > lnc1 rev 16 int a irq 9 on pci 0:16:0 > lnc1: PCNet - PCI II address 00:50:56:a6:20:83 > Probing for devices on ISA bus : > ... > > In the case of FreeBSD 2.2.7 is not able to find the address of the card > and the type of the card but it is just able to find the PCI card. So for > FreeBSD 2.2.7 we have the following log for the Lance driver. > > ... > vga0 rev 0 on pci 0:15:0 > lnc1 rev 16 int a irq 9 on pci 0:16:0 > Probing for devices on ISA bus : > ... > > In the case of FreeBSD 2.2.5 is not able to find the correct card. It find > a NE2100 card like > lnc1: NE2100 (C-LANCE) address 00:50:56:a6:20:83 and when we configure the > card we got the device timeout message. > > We this situation we are not able to get the network card up and running. > If someone have a suggestion we will be very happy because we need to > install various version of FreeBSD from the version 2.0.5 to 2.2.8 and we > were just able to get one version working with the network. IIRC VMware up to v3.1 only ever supported FreeBSD v2.2.7 and later. Current VMware releases v3.1 and later only supports FreeBSD v3.1 and later. For FreeBSD prior to v2.2.7 you're out of luck - due to lnc driver changes. You could consider patching the lnc driver but given the changes required (eg. ISA<->PCI bus driver hacks) I'm not sure that this would be practical. The only other solution I can think of (obviously suitable only for low bandwidth network connectivity) is to run PPP/SLIP through a virtual serial port! > > In fact, we have install all version of FreeBSD from 3.0 to 4.6.2 and we > were able to get them working and send packet on the network in a VMWare > environment. > Nice one! pyro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message