From owner-freebsd-net Sun Jan 21 9:29: 9 2001 Delivered-To: freebsd-net@freebsd.org Received: from falcon.prod.itd.earthlink.net (falcon.prod.itd.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id AA5EF37B401 for ; Sun, 21 Jan 2001 09:28:51 -0800 (PST) Received: from godfather (ip192.schiller-park9.il.pub-ip.psi.net [38.31.126.192]) by falcon.prod.itd.earthlink.net (EL-8_9_3_3/8.9.3) with SMTP id JAA09342 for ; Sun, 21 Jan 2001 09:28:50 -0800 (PST) Message-ID: <004601c083cf$9e3d2490$050101c0@godfather> From: "Sean" To: "BSD" Subject: Logging to a file Date: Sun, 21 Jan 2001 11:28:48 -0600 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 5.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I am making some modifications to the Ethernet code and I need to log some custom debug info to a file. So far I was using printf but there is too much info to dump on the display. I tried using fopen() fprintf() & fclose() however it gave me a linker error saying undefined reference to fopen etc. Any ideas? Thanks in advance! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Jan 21 11:16:41 2001 Delivered-To: freebsd-net@freebsd.org Received: from mink01.tirloni.co.uk (200-191-83-228-as.acessonet.com.br [200.191.83.228]) by hub.freebsd.org (Postfix) with ESMTP id E10AC37B400 for ; Sun, 21 Jan 2001 11:16:21 -0800 (PST) Received: from mink01 (mink01 [127.0.0.1]) by mink01.tirloni.co.uk (8.11.1/8.9.3) with ESMTP id f0LJ0vR00502; Sun, 21 Jan 2001 17:01:03 -0200 (BRST) (envelope-from tirloni@techie.com) Date: Sun, 21 Jan 2001 17:00:57 -0200 (BRST) From: "Giovanni P. Tirloni" X-Sender: tirloni@mink01.tirloni.co.uk To: freebsd-net@freebsd.org Cc: vev@michvhf.com Subject: Re: icmp-response bandwidth limit? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 20 Jan 2001, Vince Vielhaber wrote: > Jan 20 18:44:48 chives /kernel: icmp-response bandwidth limit 230/200 pps > > Is someone trying to pingflood me or something? Someone is sending too many icmp requests to your machine and the kernel isn't answering that cause you've ICMP_BANDLIM enabled in your kernel. This option tells the system not to reply to such requests when it reaches the limit (which is, by default, 200 packets per second). To change it just set the proper variable with sysctl(8), like this: [root@ttyp2:~]# sysctl net.inet.icmp.icmplim net.inet.icmp.icmplim: 200 [root@ttyp2:~]# sysctl -w net.inet.icmp.icmplim=300 net.inet.icmp.icmplim: 200 -> 300 or disable that option in the kernel (which isn't good, BTW). Hope it helps, Giovanni P. Tirloni tirloni@techie.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Jan 21 20:12:42 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail.nusa.or.id (unknown [202.152.14.98]) by hub.freebsd.org (Postfix) with SMTP id 3790037B400 for ; Sun, 21 Jan 2001 20:12:21 -0800 (PST) Received: (qmail 13404 invoked from network); 22 Jan 2001 04:19:06 -0000 Received: from unknown (HELO ntserver) (192.168.29.250) by intern.pub.nusa.or.id with SMTP; 22 Jan 2001 04:19:06 -0000 Reply-To: From: "Yudhiansyah Ahmadin" To: Subject: /kernel: arp: error :( Date: Mon, 22 Jan 2001 11:11:52 +0700 Message-ID: <000001c08429$73b87d50$fa1da8c0@nusa.or.id> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org heloo freebsd user .. i 'm new in freebsd i have some problem here, why my box always show this error messeges " ..... freebsd 202.xxx.xxx.xxx is on xl0 but got reply from 00:50:da:7c:c1:77 on xl1"dan " ..... freebsd /kernel: arp: 192.168.xxx.xxx is on xl1 but got reply from 00:50:ba:e2:fa:a0 on xl0" its annoy me......, these error always occur in 2-3 minute and my squid already up freebsd# ps -ax | grep squid 201 ?? S 0:36.19 squid -NsY any body could help me ... how to set my ethernet card ? -yudhi- and heres for some reference ************************************************************* freebsd# netstat -nr Routing tables Internet: Destination Gateway Flags Netif Expire default 202.xxx.xxx.xxx UGSc xl0 127.0.0.1 127.0.0.1 UH lo0 192.168.xx link#2 UC xl1 => 192.168.xx.x 0:1:2:be:36:91 UHLW xl1 647 192.168.xx.xx 0:50:4:67:b2:96 UHLW xl1 1170 192.168.xx.xxx 0:50:ba:e2:fa:a0 UHLW xl1 1157 202.xxx.xx.xx/28 link#1 UC xl0 => 202.xxx.xx.xx 0:30:80:f2:55:f1 UHLW xl0 1197 202.xxx.xx.xx 0:50:da:7c:c1:77 UHLW xl0 1096 202.xxx.xx.xxx 0:60:97:28:2:e0 UHLW lo0 freebsd# ifconfig -a xl0: flags=8843 mtu 1500 inet 202.xxx.xx.xxx netmask 0xfffffff0 broadcast 202.xxx.xx.xxx inet6 fe80::260:97ff:fe28:2e0%xl0 prefixlen 64 scopeid 0x1 ether 00:60:97:28:02:e0 media: 10baseT/UTP (10baseT/UTP ) supported media: 10base5/AUI 10baseT/UTP 10baseT/UTP mtu 1500 inet 192.168.xx.xxx netmask 0xffffff00 broadcast 192.168.xx.xxx inet6 fe80::260:97ff:fe28:2c2%xl1 prefixlen 64 scopeid 0x2 ether 00:60:97:28:02:c2 media: 10baseT/UTP (10baseT/UTP ) supported media: 10base5/AUI 10baseT/UTP 10baseT/UTP mtu 552 ppp0: flags=8010 mtu 1500 lo0: flags=8049 mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 **************************************************************************** ************ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Jan 21 20:21:32 2001 Delivered-To: freebsd-net@freebsd.org Received: from barabas.bitstream.net (barabas.bitstream.net [216.243.128.159]) by hub.freebsd.org (Postfix) with SMTP id 5736837B401 for ; Sun, 21 Jan 2001 20:21:11 -0800 (PST) Received: (qmail 31239 invoked from network); 22 Jan 2001 04:21:06 -0000 Received: from unknown (HELO dmitri.bitstream.net) (216.243.132.33) by barabas with SMTP; 22 Jan 2001 04:21:06 -0000 Date: Sun, 21 Jan 2001 22:16:02 -0600 (CST) From: Dan Debertin To: Yudhiansyah Ahmadin Cc: Subject: Re: /kernel: arp: error :( In-Reply-To: <000001c08429$73b87d50$fa1da8c0@nusa.or.id> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It has nothing to do with squid. You have a machine on the 202.x network that is on the same switch/hub as your 192.168.x network, so your kernel is getting confused. Make sure that your xl0 and xl1 interfaces are on diferent switches/hubs, or different VLANs on the same switch. ~Dan D. -- ++ Unix is the worst operating system, except for all others. ++ Dan Debertin ++ Senior Systems Administrator ++ Bitstream Underground, LLC ++ airboss@bitstream.net ++ (612)321-9290 x108 ++ GPG Fingerprint: 0BC5 F4D6 649F D0C8 D1A7 CAE4 BEF4 0A5C 300D 2387 On Mon, 22 Jan 2001, Yudhiansyah Ahmadin wrote: > heloo freebsd user .. > > i 'm new in freebsd > i have some problem here, why my box always show this error messeges > > " ..... freebsd 202.xxx.xxx.xxx is on xl0 but got reply > from 00:50:da:7c:c1:77 on xl1"dan > " ..... freebsd /kernel: arp: 192.168.xxx.xxx is on xl1 but got reply > from 00:50:ba:e2:fa:a0 on xl0" > > its annoy me......, these error always occur in 2-3 minute > and my squid already up > > freebsd# ps -ax | grep squid > 201 ?? S 0:36.19 squid -NsY > > any body could help me ... how to set my ethernet card ? > > -yudhi- > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Jan 21 20:53:21 2001 Delivered-To: freebsd-net@freebsd.org Received: from tinuviel.compendium.net.ar (usat2-00222.usateleport.com [208.248.183.222]) by hub.freebsd.org (Postfix) with ESMTP id A0DD037B402 for ; Sun, 21 Jan 2001 20:53:04 -0800 (PST) Received: by tinuviel.compendium.net.ar (Postfix, from userid 1000) id 52D4B196955; Mon, 22 Jan 2001 01:52:40 -0300 (ART) Date: Mon, 22 Jan 2001 01:52:39 -0300 To: freebsd-net@freebsd.org Subject: GRE tunnel ipv6 aware? Message-ID: <20010122015238.B12042@tinuviel.compendium.net.ar> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Mutt/1.3.12i x-attribution: HoraPe From: horape@tinuviel.compendium.net.ar Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org =A1Hola! I need to set a GRE tunnel to send ipv6 traffic. Can I with fbsd? I've tried with gre-tun, but it says that ipv6 socket family isn't supported. Thanks, HoraPe --- Horacio J. Pe=F1a horape@compendium.com.ar horape@uninet.edu bofh@puntoar.net.ar horape@hcdn.gov.ar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Jan 21 20:58:47 2001 Delivered-To: freebsd-net@freebsd.org Received: from hetnet.nl (unknown [194.151.104.184]) by hub.freebsd.org (Postfix) with ESMTP id 25E6F37B400 for ; Sun, 21 Jan 2001 20:58:30 -0800 (PST) Received: from wilbertd ([63.203.204.87]) by hetnet.nl with Microsoft SMTPSVC(5.5.1877.537.53); Mon, 22 Jan 2001 05:57:18 +0100 Message-ID: <006901c0842f$8c6480a0$57cccb3f@wilbertd> From: "Wilbert de Graaf" To: Cc: References: <000001c08429$73b87d50$fa1da8c0@nusa.or.id> Subject: Re: /kernel: arp: error :( Date: Sun, 21 Jan 2001 20:55:29 -0800 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 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Yudhiansyah Ahmadin wrote: > i 'm new in freebsd > i have some problem here, why my box always show this error messeges > > " ..... freebsd 202.xxx.xxx.xxx is on xl0 but got reply > from 00:50:da:7c:c1:77 on xl1"dan > " ..... freebsd /kernel: arp: 192.168.xxx.xxx is on xl1 but got reply > from 00:50:ba:e2:fa:a0 on xl0" There is a message from Guy Helmer in the arcvive about this: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=58150+0+archive/2000/freebsd-ne t/20001119.freebsd-net It includes a patch that should get rid of this message. Wilbert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jan 22 2:38:59 2001 Delivered-To: freebsd-net@freebsd.org Received: from tao.org.uk (genesis.tao.org.uk [194.242.131.94]) by hub.freebsd.org (Postfix) with ESMTP id 9EBB637B401 for ; Mon, 22 Jan 2001 02:38:40 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id 01DC93223; Mon, 22 Jan 2001 10:38:38 +0000 (GMT) Date: Mon, 22 Jan 2001 10:38:37 +0000 From: Josef Karthauser To: horape@tinuviel.compendium.net.ar Cc: freebsd-net@FreeBSD.ORG Subject: Re: GRE tunnel ipv6 aware? Message-ID: <20010122103837.B36298@tao.org.uk> References: <20010122015238.B12042@tinuviel.compendium.net.ar> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="oC1+HKm2/end4ao3" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010122015238.B12042@tinuviel.compendium.net.ar>; from horape@tinuviel.compendium.net.ar on Mon, Jan 22, 2001 at 01:52:39AM -0300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --oC1+HKm2/end4ao3 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 22, 2001 at 01:52:39AM -0300, horape@tinuviel.compendium.net.ar= wrote: > =A1Hola! >=20 > I need to set a GRE tunnel to send ipv6 traffic. Can I with fbsd? >=20 > I've tried with gre-tun, but it says that ipv6 socket family isn't > supported. >=20 Does it need to be GRE? If you're happy using IP-ENCAP instead then check out the gif(4) man page. Joe --oC1+HKm2/end4ao3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjpsDa0ACgkQXVIcjOaxUBbd9ACfegpXfde+i4yoO1+Rf9MQO6qI sZAAniZs0HUt/UFyC+F9d5H/TtqI7jYX =h+JR -----END PGP SIGNATURE----- --oC1+HKm2/end4ao3-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jan 22 6: 1:12 2001 Delivered-To: freebsd-net@freebsd.org Received: from tinuviel.compendium.net.ar (usat2-00222.usateleport.com [208.248.183.222]) by hub.freebsd.org (Postfix) with ESMTP id 121BD37B400 for ; Mon, 22 Jan 2001 06:00:55 -0800 (PST) Received: by tinuviel.compendium.net.ar (Postfix, from userid 1000) id 61B8A196970; Mon, 22 Jan 2001 10:58:22 -0300 (ART) Date: Mon, 22 Jan 2001 10:58:22 -0300 To: Josef Karthauser Cc: freebsd-net@FreeBSD.ORG Subject: Re: GRE tunnel ipv6 aware? Message-ID: <20010122105822.A20037@tinuviel.compendium.net.ar> References: <20010122015238.B12042@tinuviel.compendium.net.ar> <20010122103837.B36298@tao.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Mutt/1.3.12i In-Reply-To: <20010122103837.B36298@tao.org.uk>; from joe@tao.org.uk on Mon, Jan 22, 2001 at 10:38:37AM +0000 x-attribution: HoraPe From: horape@tinuviel.compendium.net.ar Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hola! > > I need to set a GRE tunnel to send ipv6 traffic. Can I with fbsd? > > I've tried with gre-tun, but it says that ipv6 socket family isn't > > supported. > Does it need to be GRE? If you're happy using IP-ENCAP instead then > check out the gif(4) man page. Yes, i've to make the link via an adsl router that only let me pass traffic to the internal boxes if it is tcp, udp or gre. > Joe Thanks, HoraPe --- Horacio J. Pe=F1a horape@compendium.com.ar horape@uninet.edu bofh@puntoar.net.ar horape@hcdn.gov.ar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jan 22 10:45:57 2001 Delivered-To: freebsd-net@freebsd.org Received: from excalibur.dotcom.fr (ns.dotcom.fr [195.154.74.11]) by hub.freebsd.org (Postfix) with ESMTP id 14D9137B401; Mon, 22 Jan 2001 10:45:38 -0800 (PST) Received: from IPricot.com (pc181.fr.ipricot.com [192.168.31.181]) by excalibur.dotcom.fr (8.9.1/8.9.1) with ESMTP id SAA20147; Mon, 22 Jan 2001 18:45:36 GMT Message-ID: <3A6C7FD0.7E2ABD65@IPricot.com> Date: Mon, 22 Jan 2001 19:45:36 +0100 From: Roman Le Houelleur Organization: dotcom X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-20000912-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-ipfw Cc: freebsd-net Subject: bandwidth analyser Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hi, I use FreeBSD 4.2 stable + bridge + dummynet + ipfw. I would like to calculate the bandwidth of each authorized IP source flowing through the bridge from a user program. As this bandwidth calculation should be done very often (10 to 20 times per second) I first tried to use the if_data structure from sysctl. But it seems the packet counter is only incremented for packets destinated to the specified interface, and moreover I wouldn't be able to separate the incoming flows depending on their source addresses. Anybody has an advice on the best way to achieve this calculation ? what about the counter capabilities of ipfw ? Moreover, concerning the bridge, I was wondering if there is a way not to put a third interface in promiscous mode. As this third nic exists only for management purposes I don't want it to participate to the bridge in any way. Thanks, Roman. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jan 22 10:55:49 2001 Delivered-To: freebsd-net@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id D784D37B401; Mon, 22 Jan 2001 10:55:29 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.1/8.11.1) id f0MItLq39152; Mon, 22 Jan 2001 10:55:21 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200101221855.f0MItLq39152@iguana.aciri.org> Subject: Re: bandwidth analyser In-Reply-To: <3A6C7FD0.7E2ABD65@IPricot.com> from Roman Le Houelleur at "Jan 22, 2001 7:45:36 pm" To: roman@IPricot.com (Roman Le Houelleur) Date: Mon, 22 Jan 2001 10:55:21 -0800 (PST) Cc: freebsd-ipfw@FreeBSD.ORG, freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > hi, > > I use FreeBSD 4.2 stable + bridge + dummynet + ipfw. > I would like to calculate the bandwidth of each > authorized IP source flowing through the bridge from a > user program. > As this bandwidth calculation should be done very often > (10 to 20 times per second) I first tried to use the if_data ... > Anybody has an advice on the best way to achieve this > calculation ? what about the counter capabilities of ipfw ? i think the ipfw interface to access this info is not very well suited to this kind of task, at least not as often as 20 times per second. > Moreover, concerning the bridge, I was wondering if > there is a way not to put a third interface in promiscous yes, there is asysctl interface (net.link.ether.bridge_cfg) see the manpages. cheers luigi ----------------------------------+----------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone: (510) 666 2927 ----------------------------------+----------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jan 22 11:10:53 2001 Delivered-To: freebsd-net@freebsd.org Received: from excalibur.dotcom.fr (ns.dotcom.fr [195.154.74.11]) by hub.freebsd.org (Postfix) with ESMTP id D985D37B404; Mon, 22 Jan 2001 11:10:32 -0800 (PST) Received: from IPricot.com (pc181.fr.ipricot.com [192.168.31.181]) by excalibur.dotcom.fr (8.9.1/8.9.1) with ESMTP id TAA20646; Mon, 22 Jan 2001 19:10:28 GMT Message-ID: <3A6C85A3.9A115BB4@IPricot.com> Date: Mon, 22 Jan 2001 20:10:27 +0100 From: Roman Le Houelleur Organization: dotcom X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-20000912-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-ipfw@FreeBSD.ORG Cc: freebsd-net@FreeBSD.ORG Subject: Re: bandwidth analyser References: <200101221855.f0MItLq39152@iguana.aciri.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Luigi Rizzo wrote: > > > > Moreover, concerning the bridge, I was wondering if > > there is a way not to put a third interface in promiscous > > yes, there is asysctl interface (net.link.ether.bridge_cfg) > > see the manpages. actually that's what I did, but I'm still not able to have my third nic out of the bridge. If I use net.link.ether.bridge_cfg: rl0:0,rl1:1,rl2:1 rl0 is on a separate cluster, so it's useable, but still rl0 is in promiscous mode. If I use something like net.link.ether.bridge_cfg: rl1:1,rl2:1 then rl0 will by default be part of the same "cluster" as rl1 and rl2. Have I missed something ? Roman. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jan 22 11:45:37 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id BDAF237B404; Mon, 22 Jan 2001 11:45:16 -0800 (PST) Received: from husten.security.at12.de (dial-195-14-233-8.netcologne.de [195.14.233.8]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id UAA04373; Mon, 22 Jan 2001 20:45:14 +0100 (MET) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by husten.security.at12.de (8.11.1/8.11.1) with ESMTP id f0MJj8W15298; Mon, 22 Jan 2001 20:45:08 +0100 (CET) (envelope-from pherman@frenchfries.net) Date: Mon, 22 Jan 2001 20:45:08 +0100 (CET) From: Paul Herman To: Roman Le Houelleur Cc: freebsd-ipfw , freebsd-net Subject: Re: bandwidth analyser In-Reply-To: <3A6C7FD0.7E2ABD65@IPricot.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello Roman, On Mon, 22 Jan 2001, Roman Le Houelleur wrote: > I use FreeBSD 4.2 stable + bridge + dummynet + ipfw. I would like > to calculate the bandwidth of each authorized IP source flowing > through the bridge from a user program. > > As this bandwidth calculation should be done very often (10 to 20 > times per second) I first tried to use the if_data structure from > sysctl. I think /usr/ports/net/argus does some analysis (however I don't think in real time.) Otherwise (shameless plug) try tcpstat: http://www.frenchfries.net/paul/tcpstat/index.html It's like a vmstat for networks (pcap filters and all), and sounds like what you are describing. -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jan 22 11:51:58 2001 Delivered-To: freebsd-net@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 9378A37B69C; Mon, 22 Jan 2001 11:51:37 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.1/8.11.1) id f0MJpZF39525; Mon, 22 Jan 2001 11:51:35 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200101221951.f0MJpZF39525@iguana.aciri.org> Subject: Re: bandwidth analyser In-Reply-To: <3A6C85A3.9A115BB4@IPricot.com> from Roman Le Houelleur at "Jan 22, 2001 8:10:27 pm" To: roman@IPricot.com (Roman Le Houelleur) Date: Mon, 22 Jan 2001 11:51:35 -0800 (PST) Cc: freebsd-ipfw@FreeBSD.ORG, freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > actually that's what I did, but I'm still not able to have > my third nic out of the bridge. > If I use net.link.ether.bridge_cfg: rl0:0,rl1:1,rl2:1 > rl0 is on a separate cluster, so it's useable, but still > rl0 is in promiscous mode. > If I use something like net.link.ether.bridge_cfg: rl1:1,rl2:1 > then rl0 will by default be part of the same "cluster" as > rl1 and rl2. > > Have I missed something ? well, you are hitting a bug or two in bridge.c :) The quick fix is to use something like sysctl -w net.link.ether.bridge_cfg="rl1:6,rl2:6," (note the different cluster-id and the trailing character). The main bug in bridge.c is that the code mistakes the NUL as a separator after the last config. The second bug in that when one interface is disabled, its name is not removed from the list in bdg_stats, so userland utilities still see its name and believe it is still active. Will have a look at fixing these bugs soon. cheers luigi ----------------------------------+----------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone: (510) 666 2927 ----------------------------------+----------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jan 22 12:15:54 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 225A837B6A7; Mon, 22 Jan 2001 12:15:34 -0800 (PST) Received: from casablanca-14.budapest.interware.hu ([195.70.53.14] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 14KnMy-000624-00; Mon, 22 Jan 2001 21:15:16 +0100 Message-ID: <3A6C94D2.8D41FC4D@elischer.org> Date: Mon, 22 Jan 2001 12:15:14 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Roman Le Houelleur Cc: freebsd-ipfw@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: bandwidth analyser References: <200101221855.f0MItLq39152@iguana.aciri.org> <3A6C85A3.9A115BB4@IPricot.com> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Roman Le Houelleur wrote: > > Luigi Rizzo wrote: > > > > > > > Moreover, concerning the bridge, I was wondering if > > > there is a way not to put a third interface in promiscous > > > > yes, there is asysctl interface (net.link.ether.bridge_cfg) > > > > see the manpages. > > actually that's what I did, but I'm still not able to have > my third nic out of the bridge. > If I use net.link.ether.bridge_cfg: rl0:0,rl1:1,rl2:1 > rl0 is on a separate cluster, so it's useable, but still > rl0 is in promiscous mode. > If I use something like net.link.ether.bridge_cfg: rl1:1,rl2:1 > then rl0 will by default be part of the same "cluster" as > rl1 and rl2. > > Have I missed something ? try using netgraph bridging. it give you better control. > > Roman. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ from Perth, presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jan 23 1:28: 3 2001 Delivered-To: freebsd-net@freebsd.org Received: from euitt.upm.es (haddock.euitt.upm.es [138.100.52.102]) by hub.freebsd.org (Postfix) with ESMTP id 9DEBF37B400 for ; Tue, 23 Jan 2001 01:27:45 -0800 (PST) Received: from deneb.euitt.upm.es (deneb.euitt.upm.es [138.100.52.12]) by euitt.upm.es (8.9.3/8.9.3) with ESMTP id KAA20128; Tue, 23 Jan 2001 10:27:23 +0100 (MET) Date: Tue, 23 Jan 2001 10:27:23 +0100 (CET) From: "Pedro J. Lobo" To: Garrett Wollman Cc: Subject: Re: Updated fxp VLAN patch for 4.2-RELEASE In-Reply-To: <200101051611.LAA70969@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 5 Jan 2001, Garrett Wollman wrote: > > - It doesn't modify if_vlan.c anymore. Instead, it uses ifi_hdrlen to tell > > if_vlan.c that it supports long frames. > > This looks good -- but I'm a bit confused by this segment of code: > > + #if NVLAN > 0 > + ifp->if_data.ifi_hdrlen = sizeof(struct ether_vlan_header); > + #else > + if (sc->not_82557) { > + ifp->if_data.ifi_hdrlen = sizeof(struct ether_vlan_header); > + } > + #endif > > Can you explain the logic here? (This seems to interfere with the > loadability of this module.) First of all, I'm sorry for the late answer. I've been travelling for a couple of days. As for your question: the 82557 doesn't support long frames directly, and they are handled as bad frames. If you want to see them, you must tell the controller to pass all frames (including errors) to the driver, as when the card is in promiscuous mode. Then, the driver must check that the received frames are correct (i.e., doesn't have CRC errors, etc.) before processing them. With the 558 and 559 controllers, there is a bit of support, as you can tell them to accept long frames as valid, and I enable this always (as does OpenBSD, which is where I got the code from). The point is that I'm hesitant to enable the 557 hack always, so I enable it only if the vlan pseudo-device is included in the kernel config file. You have no way of knowing this when compiling a loadable module, of course, because there is no kernel config file, so vlans are not supported by the lkm when using 557-based NICs. In 558- and 559-based NICs, the lkm does support vlans. To put it shortly: if you want to use vlans with a 557-based NIC, you must include the driver in the kernel, as the lkm won't support long frames. This is hardly a problem, because you have to build a custom kernel to enable vlans, anyway. With 558- and 559-based NICs there is no restriction, and the lkm has exactly the same functionality as the in-kernel driver. Cheers, Pedro. -- -------------------------------------------------------------------- Pedro José Lobo Perea Tel: +34 913367819 / Fax: +34 913319229 Centro de Cálculo e-mail: pjlobo@euitt.upm.es E.U.I.T. Telecomunicación Universidad Politécnica de Madrid Ctra. de Valencia, Km. 7 E-28031 Madrid - España / Spain To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jan 23 14:42:46 2001 Delivered-To: freebsd-net@freebsd.org Received: from modemcable101.200-201-24.mtl.mc.videotron.ca (modemcable140.61-201-24.mtl.mc.videotron.ca [24.201.61.140]) by hub.freebsd.org (Postfix) with SMTP id 1BA2637B400 for ; Tue, 23 Jan 2001 14:42:29 -0800 (PST) Received: (qmail 6688 invoked from network); 23 Jan 2001 22:42:28 -0000 Received: from cognac.local.mindstep.com (HELO cognac) (192.168.10.9) by jacuzzi.local.mindstep.com with SMTP; 23 Jan 2001 22:42:28 -0000 From: "Patrick Bihan-Faou" To: Subject: How to send arp request with no other traffic Date: Tue, 23 Jan 2001 17:43:50 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, How could I perform a arp resolution without attempting to send traffic to the IP address I am looking up ? To rephrase my question, if I use arp(8), to obtain the mac address associated with a specific IP address and that information is not yet in the arp cache, arp(8) returns: bash-2.03$ arp 192.168.10.208 192.168.10.208 (192.168.10.208) -- no entry so to obtain the information I want, I need to first do a ping: bash-2.03$ ping -c 1 192.168.10.208 PING 192.168.10.208 (192.168.10.208): 56 data bytes 64 bytes from 192.168.10.208: icmp_seq=0 ttl=255 time=0.355 ms --- 192.168.10.208 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.355/0.355/0.355/0.000 ms bash-2.03$ arp 192.168.10.208 ? (192.168.10.208) at 0:90:27:a7:6a:e0 [ethernet] While this is not a major concern, it would be nice if it was possible to trigger the arp lookup directly without using another command. Maybe with a special switch to the arp(8) command: bash-2.03$ arp -q 192.168.10.208 ? (192.168.10.208) at 0:90:27:a7:6a:e0 [ethernet] Can anybody give me a hint on how I could implement that option ? Patrick. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jan 23 15:10:28 2001 Delivered-To: freebsd-net@freebsd.org Received: from mercury.ccmr.cornell.edu (mercury.ccmr.cornell.edu [128.84.231.97]) by hub.freebsd.org (Postfix) with ESMTP id 6991537B400 for ; Tue, 23 Jan 2001 15:10:02 -0800 (PST) Received: from ruby.ccmr.cornell.edu (IDENT:0@ruby.ccmr.cornell.edu [128.84.231.115]) by mercury.ccmr.cornell.edu (8.9.3/8.9.3) with ESMTP id SAA08359; Tue, 23 Jan 2001 18:09:55 -0500 Received: from localhost (mitch@localhost) by ruby.ccmr.cornell.edu (8.9.3/8.9.3) with ESMTP id SAA15532; Tue, 23 Jan 2001 18:09:53 -0500 X-Authentication-Warning: ruby.ccmr.cornell.edu: mitch owned process doing -bs Date: Tue, 23 Jan 2001 18:09:53 -0500 (EST) From: Mitch Collinsworth To: Patrick Bihan-Faou Cc: freebsd-net@FreeBSD.ORG Subject: Re: How to send arp request with no other traffic In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org You've asked two different questions here, with differing answers: 1) How to do an arp resolution without sending traffic to the IP, and 2) Is it possible to do it all in one command. The answer to 2) is: of course. The answer to 1) goes something like this: arp doesn't send traffic to the IP. It sends an arp query to the ethernet broadcast address asking "What is the MAC address for this IP?" Anyone who has the answer, normally just the system with that IP, but sometimes another system configured to answer for it, responds with an answer. At that point the originating system then has the MAC address to use for that IP and it can begin sending packets to that MAC address (or not). At the physical layer you don't send to an IP, you send to a MAC. So yes, you can resolve an arp without ever sending a directed packet to the IP or MAC in question. But you will (normally) trigger the system in question to send a packet to you. -Mitch On Tue, 23 Jan 2001, Patrick Bihan-Faou wrote: > Hi, > > How could I perform a arp resolution without attempting to send traffic to > the IP address I am looking up ? > > To rephrase my question, if I use arp(8), to obtain the mac address > associated with a specific IP address and that information is not yet in the > arp cache, arp(8) returns: > > bash-2.03$ arp 192.168.10.208 > 192.168.10.208 (192.168.10.208) -- no entry > > > so to obtain the information I want, I need to first do a ping: > > bash-2.03$ ping -c 1 192.168.10.208 > PING 192.168.10.208 (192.168.10.208): 56 data bytes > 64 bytes from 192.168.10.208: icmp_seq=0 ttl=255 time=0.355 ms > > --- 192.168.10.208 ping statistics --- > 1 packets transmitted, 1 packets received, 0% packet loss > round-trip min/avg/max/stddev = 0.355/0.355/0.355/0.000 ms > bash-2.03$ arp 192.168.10.208 > ? (192.168.10.208) at 0:90:27:a7:6a:e0 [ethernet] > > > While this is not a major concern, it would be nice if it was possible to > trigger the arp lookup directly without using another command. Maybe with a > special switch to the arp(8) command: > > bash-2.03$ arp -q 192.168.10.208 > ? (192.168.10.208) at 0:90:27:a7:6a:e0 [ethernet] > > > > Can anybody give me a hint on how I could implement that option ? > > > Patrick. > > > > 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 Jan 23 15:15:23 2001 Delivered-To: freebsd-net@freebsd.org Received: from modemcable101.200-201-24.mtl.mc.videotron.ca (modemcable140.61-201-24.mtl.mc.videotron.ca [24.201.61.140]) by hub.freebsd.org (Postfix) with SMTP id 24BE737B402 for ; Tue, 23 Jan 2001 15:15:06 -0800 (PST) Received: (qmail 8502 invoked from network); 23 Jan 2001 23:15:00 -0000 Received: from cognac.local.mindstep.com (HELO cognac) (192.168.10.9) by jacuzzi.local.mindstep.com with SMTP; 23 Jan 2001 23:15:00 -0000 From: "Patrick Bihan-Faou" To: "Mitch Collinsworth" Cc: Subject: RE: How to send arp request with no other traffic Date: Tue, 23 Jan 2001 18:16:22 -0500 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.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal In-Reply-To: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, > You've asked two different questions here, with differing answers: > > 1) How to do an arp resolution without sending traffic to the IP, and > 2) Is it possible to do it all in one command. > > The answer to 2) is: of course. Thanks for the nice explanation of the arp mechanism. This was not really my question (I already knew that much). My real question was "2: is is possible to do it all in one command" and more specifically HOW... The arp(8) command does not do it or at least does not seem to do it. After browsing through the FreeBSD source, the only way to trigger the arp resolution is to attempt to send traffic to a given IP. Patrick. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jan 23 15:33: 9 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id C751337B69F for ; Tue, 23 Jan 2001 15:32:51 -0800 (PST) Received: from pretoria-21.budapest.interware.hu ([195.70.53.85] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 14LCvd-0008Io-00; Wed, 24 Jan 2001 00:32:46 +0100 Message-ID: <3A6E1499.D9578008@elischer.org> Date: Tue, 23 Jan 2001 15:32:41 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Patrick Bihan-Faou Cc: Mitch Collinsworth , freebsd-net@FreeBSD.ORG Subject: Re: How to send arp request with no other traffic References: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Patrick Bihan-Faou wrote: > > Hi, > > > You've asked two different questions here, with differing answers: > > > > 1) How to do an arp resolution without sending traffic to the IP, and > > 2) Is it possible to do it all in one command. > > > > The answer to 2) is: of course. > > Thanks for the nice explanation of the arp mechanism. This was not really my > question (I already knew that much). My real question was "2: is is possible > to do it all in one command" and more specifically HOW... > > The arp(8) command does not do it or at least does not seem to do it. After > browsing through the FreeBSD source, the only way to trigger the arp > resolution is to attempt to send traffic to a given IP. If you send a hand crafted arp packet, the response will be put into the arp table (whatever it is). Failing that you need to have a way of giving the arp code a way to know what to look up. At present the only way of doing that is to give it an unresolved IP packet. you could also ask the interface to take on the other address as an alias as that also causes an arp request but the retunr causes an error message when it clashes with the local alias. My best bet: send a hand crafted arp packet out through the nergraph hook on the interface and let the response be put in the table. > > Patrick. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ from Perth, presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jan 23 18:40:31 2001 Delivered-To: freebsd-net@freebsd.org Received: from ebola.biohz.net (ebola.biohz.net [206.80.1.35]) by hub.freebsd.org (Postfix) with ESMTP id 074DA37B400 for ; Tue, 23 Jan 2001 18:40:15 -0800 (PST) Received: from flu (localhost [127.0.0.1]) by ebola.biohz.net (Postfix) with SMTP id 8CBA13A282; Tue, 23 Jan 2001 18:40:14 -0800 (PST) Message-ID: <006901c085ae$fae9bd80$0402010a@biohz.net> From: "Renaud Waldura" To: "Patrick Bihan-Faou" Cc: References: Subject: Re: How to send arp request with no other traffic Date: Tue, 23 Jan 2001 18:40:14 -0800 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 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org An amusing trick to populate the ARP table is to ping the broadcast address. Even if hosts do not reply to your ping packet (typically, Windows machines), they are entered in the ARP table. You still have to send a single packet, but it does all the work. --Renaud To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jan 23 18:46: 8 2001 Delivered-To: freebsd-net@freebsd.org Received: from spider.pilosoft.com (p55-222.acedsl.com [160.79.55.222]) by hub.freebsd.org (Postfix) with ESMTP id 9A2E137B698 for ; Tue, 23 Jan 2001 18:45:50 -0800 (PST) Received: from localhost (alexmail@localhost) by spider.pilosoft.com (8.9.3/8.9.3) with ESMTP id VAA23180; Tue, 23 Jan 2001 21:47:40 -0500 (EST) Date: Tue, 23 Jan 2001 21:47:39 -0500 (EST) From: Alex Pilosov To: Renaud Waldura Cc: Patrick Bihan-Faou , freebsd-net@FreeBSD.ORG Subject: Re: How to send arp request with no other traffic In-Reply-To: <006901c085ae$fae9bd80$0402010a@biohz.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Actually answer to original question is here: http://synscan.nss.nu/programs.php I am not sure if it works on fbsd, last time I looked at it, it had a few linuxisms hardcoded... -alex On Tue, 23 Jan 2001, Renaud Waldura wrote: > An amusing trick to populate the ARP table is to ping the broadcast address. > Even if hosts do not reply to your ping packet (typically, Windows > machines), they are entered in the ARP table. > > You still have to send a single packet, but it does all the work. > > --Renaud > > > > > 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 Jan 23 19:47:31 2001 Delivered-To: freebsd-net@freebsd.org Received: from mx.cruzio.com (sa-165-227-138-17.cruzio.com [165.227.138.17]) by hub.freebsd.org (Postfix) with ESMTP id 736D437B698 for ; Tue, 23 Jan 2001 19:47:08 -0800 (PST) Received: (from brucem@localhost) by mx.cruzio.com (8.9.3/8.9.3) id TAA00860 for freebsd-net@FreeBSD.ORG; Tue, 23 Jan 2001 19:02:15 -0800 (PST) (envelope-from brucem) Date: Tue, 23 Jan 2001 19:02:15 -0800 (PST) From: "Bruce R. Montague Brucem" Message-Id: <200101240302.TAA00860@mx.cruzio.com> To: freebsd-net@FreeBSD.ORG Subject: virtual hypervisor clusters Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a speculative "freebsd-cluster" newbie type question. I hope "-net" is appropriate. A couple of us, over beer, were pondering clusters, virtual machines, VM/370 hypervisors/networks, emulators, JIT's, jails, dummynet, netgraph, etc.. Does anyone have a way to run multiple PC emulators, each running FreeBSD (of course) on a single FreeBSD machine? And then cluster the virtual machines using a virtual network driver/simulator? The intent here is to literally run multiple TCP/IP stacks (albeit at non-real-time simulation rates) and simulate a wide variety of media in the ``network'' virtual device on the real machine. That is, the typical network research problem (or VM wannabe). For this to actually work at any semi-realistic speed, the PC emulators would probably have to be truly `hypervisor-like', that is, basically run non-privileged code pretty much at regular instruction rates, and just take the emulation hit for non-privileged code/operations. The 32-bit x86 is still probably a good way from true virtualizability(?), but... Have any network research/simulation folks done such things using PC VMs? What is the best performance that has been achieved using PC emulators capable of running FreeBSD? Any relevant advice appreciated, however, only open source solutions are likely helpful, other than as existence proofs. Regards, - bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jan 23 19:49:12 2001 Delivered-To: freebsd-net@freebsd.org Received: from mx1.fujixerox.co.jp (mx1.fujixerox.co.jp [202.32.191.28]) by hub.freebsd.org (Postfix) with ESMTP id A5A7637B69C for ; Tue, 23 Jan 2001 19:48:53 -0800 (PST) Received: by mx1.fujixerox.co.jp; id MAA13589; Wed, 24 Jan 2001 12:48:51 +0900 (JST) Received: from ns1.fujixerox.co.jp(129.249.118.101) by mx1.fujixerox.co.jp via smap (3.2) id xma013347; Wed, 24 Jan 01 12:48:13 +0900 Received: from mail1.ksi.fujixerox.co.jp (mail1.ksi.fujixerox.co.jp [143.94.146.196]) by ns1.fujixerox.co.jp (8.9.3+3.2W/3.7W99122215) with ESMTP id MAA16996 for ; Wed, 24 Jan 2001 12:48:12 +0900 (JST) Received: from fxis.fujixerox.co.jp ([143.94.129.206]) by mail1.ksi.fujixerox.co.jp (8.9.3/3.7Wpl2-ksi) with ESMTP id MAA15516; Wed, 24 Jan 2001 12:48:12 +0900 (JST) Message-ID: <3A6E4F12.8FE12850@fxis.fujixerox.co.jp> Date: Wed, 24 Jan 2001 12:42:10 +0900 From: takaoka X-Mailer: Mozilla 4.51 [ja] (WinNT; I) X-Accept-Language: ja MIME-Version: 1.0 To: freebsd-net@FreeBSD.ORG, hajime.takaoka@fujixerox.co.jp Subject: AceNIC(1000base-TX) Driver for FreeBSD2.2.8 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org help me! looks for the driver of Alteon-AceNIC(1000base-TX) which operates by freeBSD2.2.8. Please teach if there is some information. #################################################### hajime takaoka Kansai System Technology Group/System Engineering Center/ Industry Solutions Company/Fuji Xerox Co.,Ltd Phone : +81-6-6263-4345 Fax : +81-6-6263-4349 Address: Midousuji-Honmachi Bldg.5F 5-7, Honmachi 3-Chome, Chuou-ku, Osaka-City, Osaka 541-0053 Japan. E-mail : hajime.takaoka@fujixerox.co.jp #################################################### To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jan 23 19:59:39 2001 Delivered-To: freebsd-net@freebsd.org Received: from ebola.biohz.net (ebola.biohz.net [206.80.1.35]) by hub.freebsd.org (Postfix) with ESMTP id A485C37B401 for ; Tue, 23 Jan 2001 19:59:21 -0800 (PST) Received: from flu (localhost [127.0.0.1]) by ebola.biohz.net (Postfix) with SMTP id 113B83A282; Tue, 23 Jan 2001 19:59:21 -0800 (PST) Message-ID: <008001c085ba$0813cae0$0402010a@biohz.net> From: "Renaud Waldura" To: "Alex Pilosov" , "Patrick Bihan-Faou" Cc: References: Subject: Re: How to send arp request with no other traffic Date: Tue, 23 Jan 2001 19:59:20 -0800 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 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Also known as /usr/ports/net/arping ! Very handy tool indeed. ----- Original Message ----- From: "Alex Pilosov" To: "Renaud Waldura" Cc: "Patrick Bihan-Faou" ; Sent: Tuesday, January 23, 2001 6:47 PM Subject: Re: How to send arp request with no other traffic > Actually answer to original question is here: > > http://synscan.nss.nu/programs.php > > I am not sure if it works on fbsd, last time I looked at it, it had a few > linuxisms hardcoded... > > > -alex > On Tue, 23 Jan 2001, Renaud Waldura wrote: > > > An amusing trick to populate the ARP table is to ping the broadcast address. > > Even if hosts do not reply to your ping packet (typically, Windows > > machines), they are entered in the ARP table. > > > > You still have to send a single packet, but it does all the work. > > > > --Renaud > > > > > > > > > > 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 Jan 23 21: 4:33 2001 Delivered-To: freebsd-net@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 4032937B400 for ; Tue, 23 Jan 2001 21:04:07 -0800 (PST) Received: by peorth.iteration.net (Postfix, from userid 1001) id 34A21575B7; Tue, 23 Jan 2001 23:04:29 -0600 (CST) Date: Tue, 23 Jan 2001 23:04:29 -0600 From: "Michael C . Wu" To: "Bruce R. Montague Brucem" Cc: freebsd-net@FreeBSD.ORG Subject: Re: virtual hypervisor clusters Message-ID: <20010123230429.C88688@peorth.iteration.net> Reply-To: "Michael C . Wu" Mail-Followup-To: "Michael C . Wu" , "Bruce R. Montague Brucem" , freebsd-net@FreeBSD.ORG References: <200101240302.TAA00860@mx.cruzio.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101240302.TAA00860@mx.cruzio.com>; from brucem@mx.cruzio.com on Tue, Jan 23, 2001 at 07:02:15PM -0800 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jan 23, 2001 at 07:02:15PM -0800, Bruce R. Montague Brucem scribbled: | This is a speculative "freebsd-cluster" newbie type | question. I hope "-net" is appropriate. | | A couple of us, over beer, were pondering clusters, | virtual machines, VM/370 hypervisors/networks, | emulators, JIT's, jails, dummynet, netgraph, etc.. You want the IBM virtual machine stuff... | Does anyone have a way to run multiple PC emulators, | each running FreeBSD (of course) on a single FreeBSD | machine? And then cluster the virtual machines using | a virtual network driver/simulator? The intent here | is to literally run multiple TCP/IP stacks (albeit | at non-real-time simulation rates) and simulate a ^^^^^^^^^^^^^Slower or faster? Look on merit.edu or IETF archives, they funded projects like this before. | wide variety of media in the ``network'' virtual | device on the real machine. That is, the typical | network research problem (or VM wannabe). You wish to emulate a real life network within one single computer. Having too many nodes would effectively forkbomb yourself. I have seen a course in TCP/IP protocol design that does this with their home grown code. I will ask them if they can allow the code to be released. | For this to actually work at any semi-realistic | speed, the PC emulators would probably have to be | truly `hypervisor-like', that is, basically run | non-privileged code pretty much at regular instruction | rates, and just take the emulation hit for non-privileged | code/operations. The 32-bit x86 is still probably | a good way from true virtualizability(?), but... You can improve jail enough to do this. Or you can implement many many netgraph nodes that does the basic TCP/IP protocols. | Have any network research/simulation folks done such | things using PC VMs? What is the best performance | that has been achieved using PC emulators capable | of running FreeBSD? Not with PC, I have only seen Sparc/MIPS/RISC/6000 platforms with high-end computing power. And the reason was stated earlier (re: forkbomb). | Any relevant advice appreciated, however, only open | source solutions are likely helpful, other than as | existence proofs. I know several commercial solutions exist, other than that, no can do. -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jan 23 21: 4:49 2001 Delivered-To: freebsd-net@freebsd.org Received: from spider.pilosoft.com (p55-222.acedsl.com [160.79.55.222]) by hub.freebsd.org (Postfix) with ESMTP id 108E537B6A6 for ; Tue, 23 Jan 2001 21:04:23 -0800 (PST) Received: from localhost (alexmail@localhost) by spider.pilosoft.com (8.9.3/8.9.3) with ESMTP id AAA20165; Wed, 24 Jan 2001 00:06:29 -0500 (EST) Date: Wed, 24 Jan 2001 00:06:29 -0500 (EST) From: Alex Pilosov To: "Bruce R. Montague Brucem" Cc: freebsd-net@FreeBSD.ORG Subject: Re: virtual hypervisor clusters In-Reply-To: <200101240302.TAA00860@mx.cruzio.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 23 Jan 2001, Bruce R. Montague Brucem wrote: > Does anyone have a way to run multiple PC emulators, > each running FreeBSD (of course) on a single FreeBSD > machine? And then cluster the virtual machines using > a virtual network driver/simulator? The intent here > is to literally run multiple TCP/IP stacks (albeit > at non-real-time simulation rates) and simulate a > wide variety of media in the ``network'' virtual > device on the real machine. That is, the typical > network research problem (or VM wannabe). Try following things: running freebsd under freebsd port of vmware running freebsd under freebsd port of plex86 Actually, you don't really need 'hypervisor'. It doesn't have to be "completely virtualized". Linux has something called 'user-mode linux', which is a complete kernel, however, instead of having real hardware drivers, it makes userlevel (filesystem,etc) calls to the 'top' kernel. You don't even need root to boot it. (which is why its called user-mode linux). FreeBSD doesn't have anything like that, to my knowledge. Also, I believe that this is a pretty nasty setup to simulate anything, since your main latency/slowdown will be in the context switching of 'top' virtual machine, and you will probably kill performance after 4th virtual machine (just a guess). More interesting research stuff is MOSIX, it has support for real clustering (global pids, process migration, etc). Their latest version is for linux, though previous one was for BSD/OS... -alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jan 23 21:39:59 2001 Delivered-To: freebsd-net@freebsd.org Received: from mario.zyan.com (mario.zyan.com [209.250.96.140]) by hub.freebsd.org (Postfix) with ESMTP id E2CF837B400 for ; Tue, 23 Jan 2001 21:39:41 -0800 (PST) Received: from dopey.weyrich.com (orville@node-64-249-12-250.dslspeed.zyan.com [64.249.12.250]) by mario.zyan.com (8.9.3/8.9.3) with ESMTP id VAA11821 for ; Tue, 23 Jan 2001 21:39:41 -0800 (PST) (envelope-from orville@weyrich.com) Received: from localhost (orville@localhost) by dopey.weyrich.com (8.9.3/8.6.9) with ESMTP id WAA17066; Tue, 23 Jan 2001 22:27:58 -0700 Date: Tue, 23 Jan 2001 22:27:58 -0700 (MST) From: "Orville R. Weyrich.Jr" To: Joe Schwartz Cc: freebsd-net@FreeBSD.ORG Subject: Re: streaming video In-Reply-To: <200101121634.KAA49904@sierrahill.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I also am seeking a way to serve streamed video. I can use FreeBSD or Linux, or in a pinch Solaris or SCO. I am wiling to spend SOME money, but I don't have a lot. Are there any inexpensive options out there? On Fri, 12 Jan 2001, Joe Schwartz wrote: > > Folks, > > I see that Entera does not provide the free streamer any > longer. Are there any other no cost alternatives to streaming > MPG video? > > Thanks, > > Joe > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > =================================================================== IF YOU WANT REFORM >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> VOTE REFORM ------------------------------------------------------------------- Orville R. Weyrich, Jr. Weyrich Computer Consulting mailto:orville@weyrich.com KD7HJV http://www.weyrich.com ------------------------------------------------------------------- Visit our online collection of book reviews: http://www.weyrich.com/book_reviews/ Ask about our world wide web services! ------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jan 23 22:54:55 2001 Delivered-To: freebsd-net@freebsd.org Received: from fork.computel.sk (fork.computel.sk [195.28.96.96]) by hub.freebsd.org (Postfix) with ESMTP id 5414337B404 for ; Tue, 23 Jan 2001 22:54:25 -0800 (PST) Received: from tempest.sk (t74.tempest.sk [195.28.100.74]) by fork.computel.sk with ESMTP id HAA08582; Wed, 24 Jan 2001 07:50:05 +0100 Message-ID: <3A6E7B1D.CDA921B9@tempest.sk> Date: Wed, 24 Jan 2001 07:50:05 +0100 From: Pavol Adamec Organization: Tempest X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Alex Pilosov Cc: "Bruce R. Montague Brucem" , freebsd-net@freebsd.org Subject: Re: virtual hypervisor clusters References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org There's a project to modify a FreeBSD kernel to be run as a userland process. Sorry, I can't find the link. Paul Alex Pilosov wrote: > > On Tue, 23 Jan 2001, Bruce R. Montague Brucem wrote: > > > Does anyone have a way to run multiple PC emulators, > > each running FreeBSD (of course) on a single FreeBSD > > machine? And then cluster the virtual machines using > > a virtual network driver/simulator? The intent here > > is to literally run multiple TCP/IP stacks (albeit > > at non-real-time simulation rates) and simulate a > > wide variety of media in the ``network'' virtual > > device on the real machine. That is, the typical > > network research problem (or VM wannabe). > > Try following things: > running freebsd under freebsd port of vmware > running freebsd under freebsd port of plex86 > > Actually, you don't really need 'hypervisor'. It doesn't have to be > "completely virtualized". Linux has something called 'user-mode linux', > which is a complete kernel, however, instead of having real > hardware drivers, it makes userlevel (filesystem,etc) calls to the 'top' > kernel. You don't even need root to boot it. (which is why its > called user-mode linux). FreeBSD doesn't have anything like that, to my > knowledge. > > Also, I believe that this is a pretty nasty setup to simulate anything, > since your main latency/slowdown will be in the context switching of 'top' > virtual machine, and you will probably kill performance after 4th virtual > machine (just a guess). > > More interesting research stuff is MOSIX, it has support for real > clustering (global pids, process migration, etc). Their latest version is > for linux, though previous one was for BSD/OS... > > -alex > > 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 Jan 23 22:54:56 2001 Delivered-To: freebsd-net@freebsd.org Received: from fork.computel.sk (fork.computel.sk [195.28.96.96]) by hub.freebsd.org (Postfix) with ESMTP id A9DD737B698 for ; Tue, 23 Jan 2001 22:54:25 -0800 (PST) Received: from tempest.sk (t74.tempest.sk [195.28.100.74]) by fork.computel.sk with ESMTP id HAA08698; Wed, 24 Jan 2001 07:53:09 +0100 Message-ID: <3A6E7BD4.96D56EE1@tempest.sk> Date: Wed, 24 Jan 2001 07:53:08 +0100 From: Pavol Adamec Organization: Tempest X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Alex Pilosov Cc: "Bruce R. Montague Brucem" , freebsd-net@freebsd.org Subject: Re: virtual hypervisor clusters References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As for my previous message: It is Alpine project (http://alpine.cs.washington.edu/). It runs (almost) unmodified TCP/IP stack in userland, not the kernel. Sorry for confusion. Paul ----- There's a project to modify a FreeBSD kernel to be run as a userland process. Sorry, I can't find the link. Paul Alex Pilosov wrote: > > On Tue, 23 Jan 2001, Bruce R. Montague Brucem wrote: > > > Does anyone have a way to run multiple PC emulators, > > each running FreeBSD (of course) on a single FreeBSD > > machine? And then cluster the virtual machines using > > a virtual network driver/simulator? The intent here > > is to literally run multiple TCP/IP stacks (albeit > > at non-real-time simulation rates) and simulate a > > wide variety of media in the ``network'' virtual > > device on the real machine. That is, the typical > > network research problem (or VM wannabe). > > Try following things: > running freebsd under freebsd port of vmware > running freebsd under freebsd port of plex86 > > Actually, you don't really need 'hypervisor'. It doesn't have to be > "completely virtualized". Linux has something called 'user-mode linux', > which is a complete kernel, however, instead of having real > hardware drivers, it makes userlevel (filesystem,etc) calls to the 'top' > kernel. You don't even need root to boot it. (which is why its > called user-mode linux). FreeBSD doesn't have anything like that, to my > knowledge. > > Also, I believe that this is a pretty nasty setup to simulate anything, > since your main latency/slowdown will be in the context switching of 'top' > virtual machine, and you will probably kill performance after 4th virtual > machine (just a guess). > > More interesting research stuff is MOSIX, it has support for real > clustering (global pids, process migration, etc). Their latest version is > for linux, though previous one was for BSD/OS... > > -alex > > 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 Jan 24 5: 7:18 2001 Delivered-To: freebsd-net@freebsd.org Received: from tomts5-srv.bellnexxia.net (tomts5.bellnexxia.net [209.226.175.25]) by hub.freebsd.org (Postfix) with ESMTP id 71E5637B698; Wed, 24 Jan 2001 05:06:54 -0800 (PST) Received: from johnny2k ([64.229.35.40]) by tomts5-srv.bellnexxia.net (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20010124130653.ITSH27935.tomts5-srv.bellnexxia.net@johnny2k>; Wed, 24 Jan 2001 08:06:53 -0500 Message-ID: <000a01c08606$9041efe0$2823e540@johnny2k> From: "John Telford" To: , Subject: IPFW modify the "simple" rule set 4.2 to allow ... Date: Wed, 24 Jan 2001 08:07:11 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01C085DC.A7368000" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-Mimeole: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0007_01C085DC.A7368000 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I'd like to get the settings in the right place so I'm asking the = experts. Freebsd 4.2 release with firewall type set to "simple".=20 It works but I'd like to allow 2 things through. SSH connections from the public side to the firewall. Connections to a Web server on the inside. Thanks in advance. John. ------=_NextPart_000_0007_01C085DC.A7368000 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I'd like to get the settings in the = right place so=20 I'm asking the experts. Freebsd 4.2 release with firewall type set to = "simple".=20
It works but I'd like to allow 2 things = through.
SSH connections from the public side to = the=20 firewall.
Connections to a Web server on the = inside.
 
Thanks in advance. = John.
------=_NextPart_000_0007_01C085DC.A7368000-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 5:14:23 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 0DC6337B400 for ; Wed, 24 Jan 2001 05:14:04 -0800 (PST) Received: from husten.security.at12.de (dial-213-168-64-251.netcologne.de [213.168.64.251]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id OAA21070 for ; Wed, 24 Jan 2001 14:14:01 +0100 (MET) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by husten.security.at12.de (8.11.1/8.11.1) with ESMTP id f0ODDsf75150 for ; Wed, 24 Jan 2001 14:13:54 +0100 (CET) (envelope-from pherman@frenchfries.net) Date: Wed, 24 Jan 2001 14:13:54 +0100 (CET) From: Paul Herman To: Subject: I have delayed ACK problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org A question for the TCP stack gurus... We were testing a FreeBSD 4.1 client with a Solaris 7 Oracle server. The FreeBSD client would take 10 times longer (60 sec) than a Linux client (~6 sec.) to complete an *identical* request. Configuration, client software and hardware problems have been ruled out. After comparing the tcpdump outputs, I found that the FreeBSD client was sending quite a few ACKs exactly 100ms later. Ah, delayed acks. sysctl -w net.inet.tcp.delayed_ack=0 "solves" the problem (or reducing the delack_timeout gives a corresponding performance win), and the FreeBSD client performs just as well as the Linux box, but I don't like this solution. Here's an example snippet from tcpdump where it trips up: 10:49:54.278268 192.168.111.16.1035 > 192.168.111.10.40438: P 4340:4420(80) ack 15362 win 17520 (DF) 10:49:54.279213 192.168.111.10.40438 > 192.168.111.16.1035: . 15362:16822(1460) ack 4420 win 8760 (DF) 10:49:54.279271 192.168.111.10.40438 > 192.168.111.16.1035: P 16822:17410(588) ack 4420 win 8760 (DF) 10:49:54.279387 192.168.111.10.40438 > 192.168.111.16.1035: . 17410:18870(1460) ack 4420 win 8760 (DF) 10:49:54.279443 192.168.111.10.40438 > 192.168.111.16.1035: P 18870:19433(563) ack 4420 win 8760 (DF) 10:49:54.279497 192.168.111.16.1035 > 192.168.111.10.40438: . ack 19433 win 17520 (DF) 10:49:54.279569 192.168.111.10.40438 > 192.168.111.16.1035: . 19433:20893(1460) ack 4420 win 8760 (DF) 10:49:54.279615 192.168.111.10.40438 > 192.168.111.16.1035: P 20893:21481(588) ack 4420 win 8760 (DF) 10:49:54.371025 192.168.111.16.1035 > 192.168.111.10.40438: . ack 21481 win 17520 (DF) 10:49:54.371223 192.168.111.10.40438 > 192.168.111.16.1035: P 21481:21752(271) ack 4420 win 8760 (DF) 192.168.111.10 Solaris Oracle Server 192.168.111.16 FreeBSD PHP client The four packets before get ACKed properly, but the next two don't. This happens a lot in this one connection, which slows it down by a factor of 10. I realize that in tcp_input() that the header prediction tries to decide if it is a "sender" or "receiver", and indeed this connection has a lot of small packets going back and forth before 192.168.111.10 starts a large data transfer, so I can understand that this might cause problems. We could live with just turning off delacks (it serves data more often than it receives), but I'd /really/ like to know what the problem is. My gut feeling is, it's not delack's problem, but a symtom of something else... This is a BIG performance hit in the default installation for FreeBSD, and I'm sure it isn't a rare occurance (Database connections, X11, etc. all do a little back & forth chat before a big file or pixmap is transfered...) What gets me is, at the end of the day is that FreeBSD can't, and Linux can (both implementing delayed ACKs) and management starts having their doubts. :( Environment: 100Mbit switched LAN, Intel fxp0 for FreeBSD, stock Sun E450 on the other side. Ideas? I'd appreciate any tips. Thanks, -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 5:54:39 2001 Delivered-To: freebsd-net@freebsd.org Received: from pop.univ-lyon1.fr (pop.univ-lyon1.fr [134.214.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 76E2037B400 for ; Wed, 24 Jan 2001 05:54:21 -0800 (PST) Received: by pop.univ-lyon1.fr (Postfix, from userid 3081) id 2557723D8F; Wed, 24 Jan 2001 14:54:18 +0100 (CET) Received: from eurinsa.insa-lyon.fr (eurinsa.insa-lyon.fr [134.214.81.32]) by pop.univ-lyon1.fr (Postfix) with ESMTP id 4A260BFA5 for ; Wed, 24 Jan 2001 14:54:14 +0100 (CET) Received: from EURINSA/SpoolDir by eurinsa.insa-lyon.fr (Mercury 1.40); 24 Jan 101 14:54:20 GMT+100 Received: from SpoolDir by EURINSA (Mercury 1.40); 24 Jan 101 14:53:57 GMT+100 Received: from arasid (134.214.170.96) by eurinsa.insa-lyon.fr (Mercury 1.40); 24 Jan 101 14:53:56 GMT+100 Message-ID: <002e01c0860c$adb454e0$0232a8c0@arasid> From: "Matus KICZKO" To: Subject: List of divert(4) connections Date: Wed, 24 Jan 2001 14:50:56 +0100 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 5.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-AntiVirus: scanned for viruses by AMaViS 0.2.1 (http://amavis.org/) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'd like to get a list of all tcp connections established between my internal network and internet throug divert(4) socket. Running natd with -verbose option does not start the daemon and display all packet alterations. Is there a way how to list connections handled by natd only something like netstat -M on linux)? Thanks Matus To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 7:35:50 2001 Delivered-To: freebsd-net@freebsd.org Received: from dustdevil.waterspout.com (unknown [64.64.82.228]) by hub.freebsd.org (Postfix) with ESMTP id 5CEAB37B400 for ; Wed, 24 Jan 2001 07:35:33 -0800 (PST) Received: (from csg@localhost) by dustdevil.waterspout.com (8.11.1/8.11.1) id f0O5X5E00291; Wed, 24 Jan 2001 00:33:05 -0500 (EST) (envelope-from csg) Date: Wed, 24 Jan 2001 00:33:05 -0500 From: "C. Stephen Gunn" To: Renaud Waldura Cc: Patrick Bihan-Faou , freebsd-net@FreeBSD.ORG Subject: Re: How to send arp request with no other traffic Message-ID: <20010124003305.B231@waterspout.com> References: <006901c085ae$fae9bd80$0402010a@biohz.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <006901c085ae$fae9bd80$0402010a@biohz.net>; from renaud@waldura.com on Tue, Jan 23, 2001 at 06:40:14PM -0800 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jan 23, 2001 at 06:40:14PM -0800, Renaud Waldura wrote: > An amusing trick to populate the ARP table is to ping the broadcast address. > Even if hosts do not reply to your ping packet (typically, Windows > machines), they are entered in the ARP table. > > You still have to send a single packet, but it does all the work. You can't really assume this will work. FreeBSD has a sysctl to disable responses to broadcast/multicast ICMP-echo requests. Exploitation of this "feature" is the basis for several denial of service attacks. Spoof the origin address to an layer-3 broadcast address and voila, amplified responses. :-( - Steve -- C. Stephen Gunn | Waterspout Communications, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 7:36:41 2001 Delivered-To: freebsd-net@freebsd.org Received: from dustdevil.waterspout.com (unknown [64.64.82.228]) by hub.freebsd.org (Postfix) with ESMTP id 6812737B402 for ; Wed, 24 Jan 2001 07:36:22 -0800 (PST) Received: (from csg@localhost) by dustdevil.waterspout.com (8.11.1/8.11.1) id f0O5UOm00280; Wed, 24 Jan 2001 00:30:24 -0500 (EST) (envelope-from csg) Date: Wed, 24 Jan 2001 00:30:24 -0500 From: "C. Stephen Gunn" To: Julian Elischer Cc: Patrick Bihan-Faou , Mitch Collinsworth , freebsd-net@FreeBSD.ORG Subject: Re: How to send arp request with no other traffic Message-ID: <20010124003024.A231@waterspout.com> References: <3A6E1499.D9578008@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A6E1499.D9578008@elischer.org>; from julian@elischer.org on Tue, Jan 23, 2001 at 03:32:41PM -0800 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jan 23, 2001 at 03:32:41PM -0800, Julian Elischer wrote: > send a hand crafted arp packet out through the nergraph > hook on the interface and let the response be put in the table. This is a side-effect of the ARP packet processing mechanism described in STD-0037. All inbound ARP packets are processed and inserted into the kernel table, before checking if a response is solicited or appropriate. The intention of the original designers of ARP was to use this mechanism to minimize the need for broadcasts on the network. I bring this up to say this is only a valid assumption on the ARP implementation in FreeBSD. I have not compared the STD-0037 recommendations with the implementation in NetBSD, and I am fairly certain that Linux _DOES_NOT_ note arp-updates from unsolicited packets. Sending spoofed ARP requests from the host in question will also require root, which inspecting the kernel routing and arp table currently doesn't. - Steve -- C. Stephen Gunn | Waterspout Communications, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 7:56:49 2001 Delivered-To: freebsd-net@freebsd.org Received: from ma4.justnet.ne.jp (ma4p.justnet.ne.jp [133.130.3.12]) by hub.freebsd.org (Postfix) with SMTP id 2EF2A37B401 for ; Wed, 24 Jan 2001 07:56:32 -0800 (PST) Received: (qmail 21980 invoked from network); Thu, 25 Jan 2001 00:56:29 +0900 Received: (ofmipd 133.1.17.145); Thu, 25 Jan 2001 00:56:29 +0900 Date: Thu, 25 Jan 2001 00:57:55 +0900 Message-Id: <3A6EFB83208.3FA9GENUINE@ma4.justnet.ne.jp> From: Tatsuhiko Terai To: freebsd-net@FreeBSD.ORG Cc: genuine@ma4.justnet.ne.jp Subject: estimation of RTT,RTO from tcpcb parameter MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver 1.26.02 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org (This mail is the multi-post to freebsd-net-jp. I'm sorry for the person who receives the duplicate mail.) I have a question about the estimation RTT, RTO using the information in tcpcb (t_srtt, t_rttvar). I'm trying to estimate network status at the kernel level using tcpcb information, obtain the estimation of RTT, RTO. I know that UNIX is not allowed floating point calculation in the kernel, so RTT estimator is implemented as using int. However, I don't know the method of calculation of the now RTT, RTO using t_srtt, t_rttvar in kernel tcpcb and so on. I hope that it is useful that I obtain the [ms]-order RTT,RTO >from that parameter. If there is an information about this, or anyone know the way of calculation, please teach me. Thanks. Tatsuhiko. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 8: 8:55 2001 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 8623C37B402 for ; Wed, 24 Jan 2001 08:08:37 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA61455; Wed, 24 Jan 2001 11:08:04 -0500 (EST) (envelope-from wollman) Date: Wed, 24 Jan 2001 11:08:04 -0500 (EST) From: Garrett Wollman Message-Id: <200101241608.LAA61455@khavrinen.lcs.mit.edu> To: Tatsuhiko Terai Cc: freebsd-net@FreeBSD.ORG Subject: estimation of RTT,RTO from tcpcb parameter In-Reply-To: <3A6EFB83208.3FA9GENUINE@ma4.justnet.ne.jp> References: <3A6EFB83208.3FA9GENUINE@ma4.justnet.ne.jp> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > I know that UNIX is not allowed floating point calculation > in the kernel, so RTT estimator is implemented as using int. > However, I don't know the method of calculation of the now RTT, RTO > using t_srtt, t_rttvar in kernel tcpcb and so on. See the function tcp_xmit_timer() in netinet/tcp_input.c. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 9:21:43 2001 Delivered-To: freebsd-net@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 996AB37B400 for ; Wed, 24 Jan 2001 09:21:22 -0800 (PST) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f0OHL2627523; Wed, 24 Jan 2001 11:21:02 -0600 (CST) (envelope-from jlemon) Date: Wed, 24 Jan 2001 11:21:02 -0600 (CST) From: Jonathan Lemon Message-Id: <200101241721.f0OHL2627523@prism.flugsvamp.com> To: pherman@frenchfries.net, net@freebsd.org Subject: Re: I have delayed ACK problems X-Newsgroups: local.mail.freebsd-net In-Reply-To: Organization: Cc: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you write: > >A question for the TCP stack gurus... > >We were testing a FreeBSD 4.1 client with a Solaris 7 Oracle server. >The FreeBSD client would take 10 times longer (60 sec) than a Linux >client (~6 sec.) to complete an *identical* request. Configuration, >client software and hardware problems have been ruled out. > >After comparing the tcpdump outputs, I found that the FreeBSD client >was sending quite a few ACKs exactly 100ms later. Ah, delayed acks. > > sysctl -w net.inet.tcp.delayed_ack=0 > >"solves" the problem (or reducing the delack_timeout gives a >corresponding performance win), and the FreeBSD client performs just >as well as the Linux box, but I don't like this solution. Here's an >example snippet from tcpdump where it trips up: >10:49:54.279497 16.1035 > 10.40438: . ack 19433 win 17520 (DF) >10:49:54.371025 16.1035 > 10.40438: . ack 21481 win 17520 (DF) Are you sure the trace has delayed ack turned off? The fact that the FreeBSD acks are about 100ms apart makes me think that the delayed ack mechanism is still running. >We could live with just turning off delacks (it serves data more often >than it receives), but I'd /really/ like to know what the problem is. >My gut feeling is, it's not delack's problem, but a symtom of >something else... > >This is a BIG performance hit in the default installation for FreeBSD, >and I'm sure it isn't a rare occurance (Database connections, X11, >etc. all do a little back & forth chat before a big file or pixmap is >transfered...) From the description above, it sounds like you are running into TCP's slow start effects. TCP will start slowly ramping up transmission to avoid overloading the network. Try bumping up net.inet.tcp.slowstart_flightsize, which specifies how many packets can be outstanding (unacked) at the beginning of a TCP connection. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 9:27: 1 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 27DB137B711 for ; Wed, 24 Jan 2001 09:26:42 -0800 (PST) Received: from portonovo-15.budapest.interware.hu ([195.70.60.79] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 14LTgm-0007yA-00; Wed, 24 Jan 2001 18:26:33 +0100 Message-ID: <3A6F1045.E3A39531@elischer.org> Date: Wed, 24 Jan 2001 09:26:29 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Matus KICZKO Cc: freebsd-net@freebsd.org Subject: Re: List of divert(4) connections References: <002e01c0860c$adb454e0$0232a8c0@arasid> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matus KICZKO wrote: > > I'd like to get a list of all tcp connections established between my > internal network and internet throug divert(4) socket. Running natd > with -verbose option does not start the daemon and display all packet > alterations. Is there a way how to list connections handled by natd only > something like netstat -M on linux)? you could copy the netgraph code in netstat and modify it to do divert.. (I think we had this once at Whistle when we wrote divert, but lost it) define "connections" if you mean active sessions being traced, I suggest that a SIGUSR1 to natd might be used to make it dump it's state somewhere) (patches to make it do this will be gladdy accpted :-) > Thanks > Matus > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ from Perth, presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 9:34:46 2001 Delivered-To: freebsd-net@freebsd.org Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by hub.freebsd.org (Postfix) with ESMTP id 3086137B404; Wed, 24 Jan 2001 09:34:28 -0800 (PST) Received: from localhost ([3ffe:501:100f:13ff::a]) by shuttle.wide.toshiba.co.jp (8.9.1+3.1W/8.9.1) with ESMTP id CAA06000; Thu, 25 Jan 2001 02:17:56 +0900 (JST) Date: Thu, 25 Jan 2001 02:00:24 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: freebsd-net@FreeBSD.ORG Cc: horape@tinuviel.compendium.net.ar, Kris Kennaway Subject: Re: Problem with gif tunnel: nd6_lookup: failed to add route for a neighbor In-Reply-To: In your message of "Wed, 17 Jan 2001 02:04:26 +0900" <14575.979664666@coconut.itojun.org> References: <20010116025802.A9040@tinuviel.compendium.net.ar> <14575.979664666@coconut.itojun.org> User-Agent: Wanderlust/2.3.0 (Roam) Emacs/21.0 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII X-Dispatcher: imput version 20000414(IM141) Lines: 35 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> On Wed, 17 Jan 2001 02:04:26 +0900, >>>>> itojun@iijlab.net said: >>> Your address prefix length is incorrect..can't remember what the >>> correct value should be off the top of my head, but it's come up >>> before so it should be in the archives upon closer examination. >> It looks like 128 is the "right" prefixlen. Problem is that my upstream >> provider (Sprint) wants to use 64 as prefixlen (IMHO FBSD is ok, but it >> seems to be the common practice to assign /64 to tunnels) > you need to configure like either: > # ifconfig gif0 3ffe:2900:000b:000d::1 3ffe:2900:000b:000d::2 \ > prefixlen 128 alias > # ifconfig gif0 3ffe:2900:000b:000d::1 prefixlen 64 alias > if you specify both your and peer's address, you need to set prefixlen > to 128. if you specify prefixlen to 64, the peer's address is not > necessary (it will get discovered automatically). > actually, the prefix length on p2p interface does not, and should not > really matter. (the separate problem is that there are multiple > interpretation of p2p in the world - major ones are gated > interpretation and cisco interpretation) > we (as KAME) will try to improve the behavior, like non-working ones > get rejected on ifconfig time or such. Just for your information: I've rewritten the KAME-current code using the stricter check. I believe (or hope) the latest code is much better than before. Please see the KAME's CHANGELOG for more details. 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 Wed Jan 24 9:35:18 2001 Delivered-To: freebsd-net@freebsd.org Received: from motgate2.mot.com (motgate2.mot.com [136.182.1.10]) by hub.freebsd.org (Postfix) with ESMTP id 8895537B698; Wed, 24 Jan 2001 09:34:55 -0800 (PST) Received: [from pobox2.mot.com (pobox2.mot.com [136.182.15.8]) by motgate2.mot.com (motgate2 2.1) with ESMTP id KAA13465; Wed, 24 Jan 2001 10:34:53 -0700 (MST)] Received: [from m-az33-r2.mot.com (m-az33-r2.mot.com [129.188.127.12]) by pobox2.mot.com (MOT-pobox2 2.0) with ESMTP id KAA24082; Wed, 24 Jan 2001 10:34:52 -0700 (MST)] Received: from pobox.cstl.labs.mot.com by m-az33-r2.mot.com with ESMTP; Wed, 24 Jan 2001 10:34:47 -0700 Received: from labs.mot.com ([173.23.93.6]) by pobox.cstl.labs.mot.com (Netscape Messaging Server 4.15) with ESMTP id G7OGU300.QZD; Wed, 24 Jan 2001 11:34:51 -0600 Message-Id: <3A6F123A.8C421122@labs.mot.com> Date: Wed, 24 Jan 2001 11:34:50 -0600 From: Joseph E Eggleston Reply-To: "Joe.Eggleston" Organization: Motorola Labs X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-1dac i686) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-net@FreeBSD.ORG" , freebsd-mozilla@freebsd.org Subject: mozilla ipv6 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, I'm trying to get mozilla working with ipv6. I've read that the linux mozilla is supposed to work with ipv6 by default. I tried installing the FreeBSD port of mozilla+ipv6-M18 but it seg faults immediately. The linux mozilla release .7 works with ipv4 under linux compatibility mode but doesn't seem to work with ipv6. Has anyone had any luck using mozilla as a v6 browser under freebsd? Any suggestions? thanks, Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 10: 8:57 2001 Delivered-To: freebsd-net@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 55EAF37B400; Wed, 24 Jan 2001 10:08:39 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.1/8.11.1) id f0OI8cb09586; Wed, 24 Jan 2001 10:08:38 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200101241808.f0OI8cb09586@iguana.aciri.org> Subject: dubious code in ip_output() ? To: net@freebsd.org Date: Wed, 24 Jan 2001 10:08:38 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, the change attached at the end was applied to ip_output() long ago -- it checks for room in the interface queue early in the delivery process -- but does this before passing the packet to the firewall. To me this seems incorrect because the firewall can drop the packet, divert it to a socket, maybe (not sure) change the output interface, pass it to a dummynet pipe, etc. Maybe none of these things were there at the time this code was committed, but it sounds like we should remove it now. (btw -- we also need to report up errors from dummynet and divert whenever this is possible... I will also look into this.) Opinions ? cheers luigi =================================================================== RCS file: /home/ncvs/src/sys/netinet/ip_output.c,v retrieving revision 1.2 retrieving revision 1.3 diff -u -p -r1.2 -r1.3 --- src/sys/netinet/ip_output.c 1994/05/25 09:11:33 1.2 +++ src/sys/netinet/ip_output.c 1994/08/01 12:01:45 1.3 @@ -255,6 +255,16 @@ ip_output(m0, opt, ro, flags, imo) ip->ip_src = IA_SIN(ia)->sin_addr; #endif /* + * Verify that we have any chance at all of being able to queue + * the packet or packet fragments + */ + if ((ifp->if_snd.ifq_len + ip->ip_len / ifp->if_mtu + 1) >= + ifp->if_snd.ifq_maxlen) { + error = ENOBUFS; + goto bad; + } + + /* * Look for broadcast address and * and verify user is allowed to send * such a packet. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 10:10:13 2001 Delivered-To: freebsd-net@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id 5EBA537B404; Wed, 24 Jan 2001 10:09:53 -0800 (PST) Received: from localhost (IDENT:9A0myyud679URa3eQ6qAzsS6XrNJ5BcxVwDKERM6ruThQF6YvcrH7TOPxAMua3nC@localhost [::1]) (authenticated) by peace.mahoroba.org (8.11.2/8.11.2/peace) with ESMTP/inet6 id f0OI5pa37023; Thu, 25 Jan 2001 03:05:51 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Thu, 25 Jan 2001 03:05:50 +0900 (JST) Message-Id: <20010125.030550.71093707.ume@mahoroba.org> To: Joe_Eggleston-CJE136@email.mot.com Cc: freebsd-net@freebsd.org, freebsd-mozilla@freebsd.org Subject: Re: mozilla ipv6 From: Hajimu UMEMOTO In-Reply-To: <3A6F123A.8C421122@labs.mot.com> References: <3A6F123A.8C421122@labs.mot.com> X-Mailer: xcite1.38> Mew version 1.95b97 on Emacs 20.7 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, >>>>> On Wed, 24 Jan 2001 11:34:50 -0600 >>>>> Joseph E Eggleston said: Joe> I'm trying to get mozilla working with ipv6. I've read that the linux Joe> mozilla is supposed to work with ipv6 by default. I tried installing the Joe> FreeBSD port of mozilla+ipv6-M18 but it seg faults immediately. The Joe> linux mozilla release .7 works with ipv4 under linux compatibility mode Joe> but doesn't seem to work with ipv6. Joe> Has anyone had any luck using mozilla as a v6 browser under freebsd? Any Joe> suggestions? It seems you are on 4.2-RELEASE. There was some problem in makeing thread application using C++. It was fixed in recent 4.2-STABLE. BTW, latest ports-current of mozilla+ipv6 is 0.7. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 10:30:25 2001 Delivered-To: freebsd-net@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id BBA8937B698 for ; Wed, 24 Jan 2001 10:30:06 -0800 (PST) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id KAA23133; Wed, 24 Jan 2001 10:21:14 -0800 (PST) Message-Id: <200101241821.KAA23133@implode.root.com> To: Luigi Rizzo Cc: net@FreeBSD.ORG Subject: Re: dubious code in ip_output() ? From: David Greenman Reply-To: dg@root.com Date: Wed, 24 Jan 2001 10:21:14 -0800 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >the change attached at the end was applied to ip_output() >long ago -- it checks for room in the interface queue early >in the delivery process -- but does this before passing the packet >to the firewall. > >To me this seems incorrect because the firewall can drop the packet, >divert it to a socket, maybe (not sure) change the output interface, >pass it to a dummynet pipe, etc. > >Maybe none of these things were there at the time this code >was committed, but it sounds like we should remove it now. > >(btw -- we also need to report up errors from dummynet >and divert whenever this is possible... I will also look >into this.) > >Opinions ? The original problem that was being solved is that the code would start queuing fragments of a large packet to the output queue and then notice that it was full and discard the remaining fragments. This resulted in completely useless packet fragments being output on the wire (fragments that would never form a complete packet). You can imagine the various problems that this causes. So the code can't be removed, but it could be moved a bit later, perhaps. It was at the correct location at the time that I wrote it, however. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 10:37:50 2001 Delivered-To: freebsd-net@freebsd.org Received: from ebola.biohz.net (ebola.biohz.net [206.80.1.35]) by hub.freebsd.org (Postfix) with ESMTP id C419E37B400 for ; Wed, 24 Jan 2001 10:37:32 -0800 (PST) Received: from flu (localhost [127.0.0.1]) by ebola.biohz.net (Postfix) with SMTP id 2B6063A282; Wed, 24 Jan 2001 10:37:32 -0800 (PST) Message-ID: <000d01c08634$b6702c80$0402010a@biohz.net> From: "Renaud Waldura" To: "C. Stephen Gunn" Cc: References: <006901c085ae$fae9bd80$0402010a@biohz.net> <20010124003305.B231@waterspout.com> Subject: Re: How to send arp request with no other traffic Date: Wed, 24 Jan 2001 10:37:31 -0800 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 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > You can't really assume this will work. FreeBSD has a sysctl > to disable responses to broadcast/multicast ICMP-echo requests. You know what, I tried it with Windows machines, that do not reply to broadcast ping either, and it worked anyway. What gives? ----- Original Message ----- From: "C. Stephen Gunn" To: "Renaud Waldura" Cc: "Patrick Bihan-Faou" ; Sent: Tuesday, January 23, 2001 9:33 PM Subject: Re: How to send arp request with no other traffic > > On Tue, Jan 23, 2001 at 06:40:14PM -0800, Renaud Waldura wrote: > > > An amusing trick to populate the ARP table is to ping the broadcast address. > > Even if hosts do not reply to your ping packet (typically, Windows > > machines), they are entered in the ARP table. > > > > You still have to send a single packet, but it does all the work. > > You can't really assume this will work. FreeBSD has a sysctl > to disable responses to broadcast/multicast ICMP-echo requests. > > Exploitation of this "feature" is the basis for several denial > of service attacks. Spoof the origin address to an layer-3 > broadcast address and voila, amplified responses. :-( > > - Steve > > -- > C. Stephen Gunn | Waterspout Communications, Inc. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 10:43:48 2001 Delivered-To: freebsd-net@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id A2A2537B69C for ; Wed, 24 Jan 2001 10:43:28 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.1/8.11.1) id f0OIhKQ09772; Wed, 24 Jan 2001 10:43:20 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200101241843.f0OIhKQ09772@iguana.aciri.org> Subject: Re: dubious code in ip_output() ? In-Reply-To: <200101241821.KAA23133@implode.root.com> from David Greenman at "Jan 24, 2001 10:21:14 am" To: dg@root.com Date: Wed, 24 Jan 2001 10:43:20 -0800 (PST) Cc: rizzo@aciri.org, net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org David, you are absolutely right that the code was correct at the time it was committed -- i think i tried to mention this. The question is where to move it now. Because it seems to be only necessary when we have fragmentation, perhaps the correct place is somewhere near the place where fragments are created (around line 830 in 4.2): len = (ifp->if_mtu - hlen) &~ 7; if (len < 8) { error = EMSGSIZE; goto bad; } ---> move check here <---- /* * if the interface will not calculate checksums on * fragmented packets, then do it here. */ so we get as much error reports as possible -- what do you think ? (as a side note -- ALTQ might have problem with code peeking at queue occupation, but that is not an easy problem to solve anyways... reminds me of some problems related to IP-over-ATM...) cheers luigi > >the change attached at the end was applied to ip_output() > >long ago -- it checks for room in the interface queue early ... > >Maybe none of these things were there at the time this code > >was committed, but it sounds like we should remove it now. ... > >Opinions ? > > The original problem that was being solved is that the code would start > queuing fragments of a large packet to the output queue and then notice that > it was full and discard the remaining fragments. This resulted in completely > useless packet fragments being output on the wire (fragments that would never > form a complete packet). You can imagine the various problems that this > causes. > So the code can't be removed, but it could be moved a bit later, perhaps. > It was at the correct location at the time that I wrote it, however. > > -DG ----------------------------------+----------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone: (510) 666 2927 ----------------------------------+----------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 10:59:35 2001 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 58B4837B402 for ; Wed, 24 Jan 2001 10:59:17 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id NAA62672; Wed, 24 Jan 2001 13:59:04 -0500 (EST) (envelope-from wollman) Date: Wed, 24 Jan 2001 13:59:04 -0500 (EST) From: Garrett Wollman Message-Id: <200101241859.NAA62672@khavrinen.lcs.mit.edu> To: Luigi Rizzo Cc: net@freebsd.org Subject: dubious code in ip_output() ? In-Reply-To: <200101241808.f0OI8cb09586@iguana.aciri.org> References: <200101241808.f0OI8cb09586@iguana.aciri.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > To me this seems incorrect because the firewall can drop the packet, > divert it to a socket, maybe (not sure) change the output interface, > pass it to a dummynet pipe, etc. It's completely bogus (I had that argument with it at the time). There is no predicting whether the interface queue will actually accept a packet until you try to enqueue it. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 11:27:45 2001 Delivered-To: freebsd-net@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 3BB4637B400 for ; Wed, 24 Jan 2001 11:27:25 -0800 (PST) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id LAA23469; Wed, 24 Jan 2001 11:18:50 -0800 (PST) Message-Id: <200101241918.LAA23469@implode.root.com> To: Luigi Rizzo Cc: net@FreeBSD.ORG Subject: Re: dubious code in ip_output() ? In-reply-to: Your message of "Wed, 24 Jan 2001 10:43:20 PST." <200101241843.f0OIhKQ09772@iguana.aciri.org> From: David Greenman Reply-To: dg@root.com Date: Wed, 24 Jan 2001 11:18:50 -0800 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >you are absolutely right that the code was correct at the time >it was committed -- i think i tried to mention this. > >The question is where to move it now. Because it seems to be only >necessary when we have fragmentation, perhaps the correct place is >somewhere near the place where fragments are created (around line >830 in 4.2): > > len = (ifp->if_mtu - hlen) &~ 7; > if (len < 8) { > error = EMSGSIZE; > goto bad; > } >---> move check here <---- > /* > * if the interface will not calculate checksums on > * fragmented packets, then do it here. > */ > >so we get as much error reports as possible -- what do you think ? If it works there, then that's fine by me. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 11:50:35 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 218E237B404 for ; Wed, 24 Jan 2001 11:50:16 -0800 (PST) Received: from husten.security.at12.de (dial-195-14-244-56.netcologne.de [195.14.244.56]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id UAA19178; Wed, 24 Jan 2001 20:50:14 +0100 (MET) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by husten.security.at12.de (8.11.1/8.11.1) with ESMTP id f0OJo6X15418; Wed, 24 Jan 2001 20:50:06 +0100 (CET) (envelope-from pherman@frenchfries.net) Date: Wed, 24 Jan 2001 20:50:06 +0100 (CET) From: Paul Herman To: Jonathan Lemon Cc: Subject: Re: I have delayed ACK problems In-Reply-To: <200101241721.f0OHL2627523@prism.flugsvamp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Jonathan, On Wed, 24 Jan 2001, Jonathan Lemon wrote: > >10:49:54.279497 16.1035 > 10.40438: . ack 19433 win 17520 (DF) > >10:49:54.371025 16.1035 > 10.40438: . ack 21481 win 17520 (DF) > > Are you sure the trace has delayed ack turned off? Sorry, wasn't clear there. Yes, this trace is with delayed acks turned ON, exhibiting the performance problems I was describing. > Try bumping up net.inet.tcp.slowstart_flightsize, which specifies > how many packets can be outstanding (unacked) at the beginning > of a TCP connection. Do you mean lower? Then it wouldn't wait for more segments to arrive and run up the delayed ack timer, correct? Thanks, I'll try it out (both ways, higher & lower values) but this unfortunately seems like a workaround rather than a solution. Something just doesn't sit well me. This shouldn't happen in a 100Mbit LAN. This seems like a plain vanilla network transaction, and FreeBSD is failing on something, where other OSes in the same environment don't. Time to dig through sys/netinet/tcp* ... -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 12: 7:14 2001 Delivered-To: freebsd-net@freebsd.org Received: from mrout1.yahoo.com (mrout1.yahoo.com [208.48.125.95]) by hub.freebsd.org (Postfix) with ESMTP id BD88737B6A0 for ; Wed, 24 Jan 2001 12:06:56 -0800 (PST) Received: from milk.yahoo.com (milk.yahoo.com [206.251.16.37]) by mrout1.yahoo.com (8.11.1/8.11.1/y.out) with ESMTP id f0OK6ss31962; Wed, 24 Jan 2001 12:06:54 -0800 (PST) Received: (from root@localhost) by milk.yahoo.com (8.11.0/8.11.0) id f0OK6rd66168; Wed, 24 Jan 2001 12:06:53 -0800 (PST) (envelope-from jayanth) Date: Wed, 24 Jan 2001 12:06:53 -0800 From: jayanth To: Paul Herman Cc: Jonathan Lemon , net@FreeBSD.ORG Subject: Re: I have delayed ACK problems Message-ID: <20010124120653.B65472@yahoo-inc.com> References: <200101241721.f0OHL2627523@prism.flugsvamp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from pherman@frenchfries.net on Wed, Jan 24, 2001 at 08:50:06PM +0100 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org it looks like the tcp code is not acking the data when the PUSH flag is set. It would be useful to generate an immediate ACK when the PUSH flag is set. it would be interesting to see if the other sends two full sized tcp segments if the freebsd stack will then immediately acknowledge the data. jayanth Paul Herman (pherman@frenchfries.net) wrote: > Hi Jonathan, > > On Wed, 24 Jan 2001, Jonathan Lemon wrote: > > > >10:49:54.279497 16.1035 > 10.40438: . ack 19433 win 17520 (DF) > > >10:49:54.371025 16.1035 > 10.40438: . ack 21481 win 17520 (DF) > > > > Are you sure the trace has delayed ack turned off? > > Sorry, wasn't clear there. Yes, this trace is with delayed acks > turned ON, exhibiting the performance problems I was describing. > > > Try bumping up net.inet.tcp.slowstart_flightsize, which specifies > > how many packets can be outstanding (unacked) at the beginning > > of a TCP connection. > > Do you mean lower? Then it wouldn't wait for more segments to arrive > and run up the delayed ack timer, correct? > > Thanks, I'll try it out (both ways, higher & lower values) but this > unfortunately seems like a workaround rather than a solution. > > Something just doesn't sit well me. This shouldn't happen in a > 100Mbit LAN. This seems like a plain vanilla network transaction, and > FreeBSD is failing on something, where other OSes in the same > environment don't. > > Time to dig through sys/netinet/tcp* ... > > -Paul. > > > > > > > > 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 Jan 24 12:23: 6 2001 Delivered-To: freebsd-net@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 14FB137B404 for ; Wed, 24 Jan 2001 12:22:48 -0800 (PST) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0OKMVt77399; Wed, 24 Jan 2001 12:22:31 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: Paul Herman Cc: Jonathan Lemon , net@FreeBSD.ORG Subject: Re: I have delayed ACK problems In-Reply-To: Message from Paul Herman of "Wed, 24 Jan 2001 20:50:06 +0100." Date: Wed, 24 Jan 2001 12:22:30 -0800 Message-ID: <77394.980367750@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Something just doesn't sit well me. This shouldn't happen in a > 100Mbit LAN. This seems like a plain vanilla network transaction, and > FreeBSD is failing on something, where other OSes in the same > environment don't. You're almost certainly correct that there's a misfeature lurking in there somewhere, I don't think anybody's arguing that particular point, it's just that you're also (sadly) in a much better position to diagnose this than [m]any of your readers since we don't have an active failure scenario to analyze like you do. :( - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 12:32:30 2001 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 0E12737B402 for ; Wed, 24 Jan 2001 12:32:13 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id PAA63576; Wed, 24 Jan 2001 15:32:09 -0500 (EST) (envelope-from wollman) Date: Wed, 24 Jan 2001 15:32:09 -0500 (EST) From: Garrett Wollman Message-Id: <200101242032.PAA63576@khavrinen.lcs.mit.edu> To: Paul Herman Cc: Subject: Re: I have delayed ACK problems In-Reply-To: References: <200101241721.f0OHL2627523@prism.flugsvamp.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > Something just doesn't sit well me. This shouldn't happen in a > 100Mbit LAN. This seems like a plain vanilla network transaction, and > FreeBSD is failing on something, where other OSes in the same > environment don't. Is your Solaris server attempting to do tinygram avoidance and getting it wrong? (There are some modes in which tinygram avoidance and delayed acks can combine to degrade TCP to lock-step mode. FreeBSD used to have a kluge to work around this.) That's the only think I can think of that would cause the sender-TCP to wait for an ack at the point demonstrated in your trace. Interactive protocols like X defeat tinygram avoidance by turning on TCP_NODELAY, but you'll probably have a hard time getting the Orrible server to do that. The first ACK gets sent quickly because your client application is blocked in read(); when the first data packet comes in, the application is awakened. The first four data packets arrive back-to-back, so the user process doesn't get scheduled until after the fourth. When that happens, it's already in the kernel (blocked in read() as I said) and immediately sucks all of the data out of the socket buffer. This causes the receive window to be updated, which forces the acknowledgement out immediately. For whatever reason, the next two packets are not being read immediately. Perhaps the client is off doing something else, or isn't getting scheduled, or perhaps it has set its wakeup threshold (SO_RCVLOWAT) too high. In any event, nothing takes place on the client side which would cause it to send an immediate ack, so nothing happens until the delayed-ack timer fires. This causes the other end to wake up and start sending again. In 4.3-Net/2 (FreeBSD 1.x) we had code in the header-prediction fast path which would automatically defeat delayed-ack when receiving short packets. (I don't have the 1.x CVS repository available here so I don't know whether this was introduced by David or came as a part of Net/2.) ISTR a recommendation from somewhere that TCP should ack no fewer than 1/2 of all received data segments. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 12:34:41 2001 Delivered-To: freebsd-net@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 6765337B401 for ; Wed, 24 Jan 2001 12:34:23 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.1/8.11.1) id f0OKYNP19344; Wed, 24 Jan 2001 12:34:23 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200101242034.f0OKYNP19344@iguana.aciri.org> Subject: suboptimal mbuf usage In-Reply-To: <200101241918.LAA23469@implode.root.com> from David Greenman at "Jan 24, 2001 11:18:50 am" To: net@freebsd.org Date: Wed, 24 Jan 2001 12:34:23 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, i have been looking at how often a packet which is sent to an ethernet driver is split over multiple mbufs, and it seems that this happens for the vast majority of packets -- basically everything above MHLEN goes into two mbufs, and MTU-sized TCP packets end up using 3 or more mbufs. This is on 4.2, and using ttcp to generate traffic, and ipfw which defaults to accept everything. I seem to remember that there was code at least in TCP which tries to leave room for the link and ip headers, but somehow this seems to fail... Has anyone else noticed this behaviour ? cheers luigi ----------------------------------+----------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone: (510) 666 2927 ----------------------------------+----------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 13:57:41 2001 Delivered-To: freebsd-net@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 1285537B400 for ; Wed, 24 Jan 2001 13:57:23 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id IAA26102; Thu, 25 Jan 2001 08:57:02 +1100 Date: Thu, 25 Jan 2001 08:56:54 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Jordan Hubbard Cc: Paul Herman , Jonathan Lemon , net@FreeBSD.ORG Subject: Re: I have delayed ACK problems In-Reply-To: <77394.980367750@winston.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 24 Jan 2001, Jordan Hubbard wrote: > > Something just doesn't sit well me. This shouldn't happen in a > > 100Mbit LAN. This seems like a plain vanilla network transaction, and > > FreeBSD is failing on something, where other OSes in the same > > environment don't. > > You're almost certainly correct that there's a misfeature lurking in > there somewhere, I don't think anybody's arguing that particular > point, it's just that you're also (sadly) in a much better position to > diagnose this than [m]any of your readers since we don't have an > active failure scenario to analyze like you do. :( I diagnosed similar problems in rmt(8) a few (?) months ago. Try: tar cf localhost:/tmp/foo /boot/kernel With the FreeBSD defaults, this crawls at almost precisely 100K/sec due to its protocol waiting for an ack after every 10K block and acks being delayed by 100 msec. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 14:18:42 2001 Delivered-To: freebsd-net@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 6BC6237B404 for ; Wed, 24 Jan 2001 14:18:24 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.1/8.11.1) id f0OMIOb19954; Wed, 24 Jan 2001 14:18:24 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200101242218.f0OMIOb19954@iguana.aciri.org> Subject: Re: suboptimal mbuf usage In-Reply-To: <200101242034.f0OKYNP19344@iguana.aciri.org> from Luigi Rizzo at "Jan 24, 2001 12:34:23 pm" To: rizzo@aciri.org (Luigi Rizzo) Date: Wed, 24 Jan 2001 14:18:24 -0800 (PST) Cc: net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org followup to my own message... the thing is easy to explain: For TCP, tcp_output() allocates one mbuf for the header, and then whenever the data does not fit into the remaining space in the mbuf, it typically references the data in the clusters stored in the socket queue. For an MSS-sized packet and 2KB clusters, there is a ~70% chance that the payload is in two different clusters, hence the reason for using 3 mbufs. For UDP, the mbuf chain passed to udp_output() is used directly. If the data block is small and fits into an mbuf, sosend() will leave room for the headers (check sys/kern/uipc_socket.c:sosend() near line 567), but it will not do this optimization for large blocks which need a cluster. cheers luigi > Hi, > > i have been looking at how often a packet which is sent to > an ethernet driver is split over multiple mbufs, and it > seems that this happens for the vast majority of > packets -- basically everything above MHLEN goes into > two mbufs, and MTU-sized TCP packets end up using 3 or > more mbufs. > > This is on 4.2, and using ttcp to generate traffic, and > ipfw which defaults to accept everything. > > I seem to remember that there was code at least in TCP which > tries to leave room for the link and ip headers, but > somehow this seems to fail... > > Has anyone else noticed this behaviour ? > > cheers > luigi > ----------------------------------+----------------------------------------- > Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) > http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 > Phone: (510) 666 2927 > ----------------------------------+----------------------------------------- > > > 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 Jan 24 15:35:50 2001 Delivered-To: freebsd-net@freebsd.org Received: from ma4.justnet.ne.jp (ma4p.justnet.ne.jp [133.130.3.12]) by hub.freebsd.org (Postfix) with SMTP id D08D737B401 for ; Wed, 24 Jan 2001 15:35:31 -0800 (PST) Received: (qmail 2610 invoked from network); Thu, 25 Jan 2001 08:35:27 +0900 Received: (ofmipd 133.1.17.145); Thu, 25 Jan 2001 08:35:27 +0900 Date: Thu, 25 Jan 2001 08:36:51 +0900 Message-Id: <3A6F67132EE.7B47GENUINE@ma4.justnet.ne.jp> From: Tatsuhiko Terai To: freebsd-net@FreeBSD.ORG Subject: Re: estimation of RTT,RTO from tcpcb parameter In-Reply-To: <3A6EFB83208.3FA9GENUINE@ma4.justnet.ne.jp> References: <3A6EFB83208.3FA9GENUINE@ma4.justnet.ne.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver 1.26.02 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thank you for your advise. >See the function tcp_xmit_timer() in netinet/tcp_input.c. Does this program mean that ? RTT = (tp)->t_srtt >> (TCP_RTT_SHIFT - TCP_DELTA_SHIFT) [ms] RTO = tp->t_rxtcur [ms] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 16: 9:46 2001 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id CD14437B401 for ; Wed, 24 Jan 2001 16:09:27 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id TAA73303; Wed, 24 Jan 2001 19:09:23 -0500 (EST) (envelope-from wollman) Date: Wed, 24 Jan 2001 19:09:23 -0500 (EST) From: Garrett Wollman Message-Id: <200101250009.TAA73303@khavrinen.lcs.mit.edu> To: Tatsuhiko Terai Cc: freebsd-net@FreeBSD.ORG Subject: Re: estimation of RTT,RTO from tcpcb parameter In-Reply-To: <3A6F67132EE.7B47GENUINE@ma4.justnet.ne.jp> References: <3A6EFB83208.3FA9GENUINE@ma4.justnet.ne.jp> <3A6F67132EE.7B47GENUINE@ma4.justnet.ne.jp> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > Does this program mean that ? > RTT = (tp)->t_srtt >> (TCP_RTT_SHIFT - TCP_DELTA_SHIFT) [ms] > RTO = tp->t_rxtcur [ms] No. Please take a look at W. Richard Stevens' _TCP/IP Illustrated_ series, particularly volume 2. Nothing inside the kernel is measured in milliseconds. TCP parameters are measured in timer ticks, the length of which depends on which version of FreeBSD you are running and (potentially) on what hardware platform. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 16:26:13 2001 Delivered-To: freebsd-net@freebsd.org Received: from ma4.justnet.ne.jp (ma4p.justnet.ne.jp [133.130.3.12]) by hub.freebsd.org (Postfix) with SMTP id C6A3237B400 for ; Wed, 24 Jan 2001 16:25:56 -0800 (PST) Received: (qmail 6721 invoked from network); Thu, 25 Jan 2001 09:25:52 +0900 Received: (ofmipd 133.1.17.145); Thu, 25 Jan 2001 09:25:52 +0900 Date: Thu, 25 Jan 2001 09:27:19 +0900 Message-Id: <3A6F72E71D6.7B48GENUINE@ma4.justnet.ne.jp> From: Tatsuhiko Terai To: Garrett Wollman Cc: freebsd-net@freebsd.org Subject: Re: estimation of RTT,RTO from tcpcb parameter In-Reply-To: <200101250009.TAA73303@khavrinen.lcs.mit.edu> References: <3A6F67132EE.7B47GENUINE@ma4.justnet.ne.jp> <200101250009.TAA73303@khavrinen.lcs.mit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver 1.26.02 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks for your advise. > No. Please take a look at W. Richard Stevens' _TCP/IP Illustrated_ > series, particularly volume 2. > I'll try. > Nothing inside the kernel is measured in milliseconds. TCP parameters > are measured in timer ticks, the length of which depends on which > version of FreeBSD you are running and (potentially) on what hardware > platform. By the way, my running machine is P-III 1GHz with i820 chip and FreeBSD-4.0-RELEASE. Is the length of time tick for this plathome invert of 1GHz? (1/10^-9 [s])? or 10 [ms] (I think it is the time ticks for FreeBSD)? RTT = (tp)->t_srtt >> (TCP_RTT_SHIFT - TCP_DELTA_SHIFT) shows sometimes rapidly increase to 40 between ti0 gigabit link. I think 40 * 10 [ms] is too longer for rtt, so I confused.. If there is some information, would you please like toteach ? Thanks- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 17:33:37 2001 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 6816637B401 for ; Wed, 24 Jan 2001 17:33:20 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id UAA73836; Wed, 24 Jan 2001 20:33:14 -0500 (EST) (envelope-from wollman) Date: Wed, 24 Jan 2001 20:33:14 -0500 (EST) From: Garrett Wollman Message-Id: <200101250133.UAA73836@khavrinen.lcs.mit.edu> To: Tatsuhiko Terai Cc: freebsd-net@freebsd.org Subject: Re: estimation of RTT,RTO from tcpcb parameter In-Reply-To: <3A6F72E71D6.7B48GENUINE@ma4.justnet.ne.jp> References: <3A6F67132EE.7B47GENUINE@ma4.justnet.ne.jp> <200101250009.TAA73303@khavrinen.lcs.mit.edu> <3A6F72E71D6.7B48GENUINE@ma4.justnet.ne.jp> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > By the way, my running machine is P-III 1GHz with i820 chip and > FreeBSD-4.0-RELEASE. > Is the length of time tick for this plathome invert of 1GHz? > (1/10^-9 [s])? or 10 [ms] (I think it is the time ticks for > FreeBSD)? The system timer ticks at a rate of 100 Hz on all IA32 processors. (I believe on Alphas it ticks at 1024 Hz but I may be imagining it.) Thus, the period is either 10 ms or 0.98 ms. In historic versions of FreeBSD, most TCP timers ticked at 2 Hz while the others ticked at 5 Hz. This was changed in advance of FreeBSD 4.0. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 18:35:40 2001 Delivered-To: freebsd-net@freebsd.org Received: from ma4.justnet.ne.jp (ma4p.justnet.ne.jp [133.130.3.12]) by hub.freebsd.org (Postfix) with SMTP id BF6F737B699 for ; Wed, 24 Jan 2001 18:35:19 -0800 (PST) Received: (qmail 11525 invoked from network); Thu, 25 Jan 2001 11:35:15 +0900 Received: (ofmipd 133.1.17.145); Thu, 25 Jan 2001 11:35:15 +0900 Date: Thu, 25 Jan 2001 11:36:42 +0900 Message-Id: <3A6F913A320.7B49GENUINE@ma4.justnet.ne.jp> From: Tatsuhiko Terai To: Garrett Wollman Cc: freebsd-net@freebsd.org Subject: Re: estimation of RTT,RTO from tcpcb parameter In-Reply-To: <200101250133.UAA73836@khavrinen.lcs.mit.edu> References: <3A6F72E71D6.7B48GENUINE@ma4.justnet.ne.jp> <200101250133.UAA73836@khavrinen.lcs.mit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver 1.26.02 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thank you very much for your kindly advise. >The system timer ticks at a rate of 100 Hz on all IA32 processors. (I >believe on Alphas it ticks at 1024 Hz but I may be imagining it.) >Thus, the period is either 10 ms or 0.98 ms. > >In historic versions of FreeBSD, most TCP timers ticked at 2 Hz while >the others ticked at 5 Hz. This was changed in advance of FreeBSD >4.0. I see. Anyway, it seems to be difficult that estimating RTT, RTO within a LAN envirounment (such as Gigabit connection). Of course, this time scale may be valid for general internet envirounment. I'll study more. Thanks - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 18:38:47 2001 Delivered-To: freebsd-net@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id B5CEB37B699 for ; Wed, 24 Jan 2001 18:38:29 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.1/8.11.1) id f0P2cTK33421; Wed, 24 Jan 2001 18:38:29 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200101250238.f0P2cTK33421@iguana.aciri.org> Subject: error return by RTM_GET To: net@freebsd.org Date: Wed, 24 Jan 2001 18:38:24 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, when you issue a RTM_GET request to the routing socket for a non-existing route, the write() to the socket fails with errno=3, ESRCH, which is printed by the "route" command as route: writing to routing socket: No such process The error message is kind of misleading, i wonder if we can replace the return value in sys/net/rtsock.c with ENOMSG /* No message of desired type */ ? Does any userland application depend on ESRCH ? cheers luigi ----------------------------------+----------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone: (510) 666 2927 ----------------------------------+----------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 19: 7:18 2001 Delivered-To: freebsd-net@freebsd.org Received: from hetnet.nl (unknown [194.151.104.183]) by hub.freebsd.org (Postfix) with ESMTP id 4EF7337B400 for ; Wed, 24 Jan 2001 19:07:01 -0800 (PST) Received: from hetnet.nl ([63.201.231.180]) by hetnet.nl with Microsoft SMTPSVC(5.5.1877.537.53); Thu, 25 Jan 2001 04:04:50 +0100 Message-ID: <3A6F9721.180528FE@hetnet.nl> Date: Wed, 24 Jan 2001 19:01:53 -0800 From: Wilbert de Graaf X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 Cc: net@freebsd.org Subject: Re: error return by RTM_GET References: <200101250238.f0P2cTK33421@iguana.aciri.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Luigi Rizzo wrote: > Does any userland application depend on ESRCH ? pimd does, but only to decide to generate some log: routesock.c: 207 if ((rlen = write(routing_socket, (char *)&m_rtmsg, l)) < 0) { IF_DEBUG(DEBUG_RPF | DEBUG_KERN) { if (errno == ESRCH) log(LOG_DEBUG, 0, "Writing to routing socket: no such route\n"); else log(LOG_DEBUG, 0, "Error writing to routing socket"); } Wilbert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 19:53:31 2001 Delivered-To: freebsd-net@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 8350237B401 for ; Wed, 24 Jan 2001 19:53:14 -0800 (PST) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f0P3qpV49010; Wed, 24 Jan 2001 21:52:51 -0600 (CST) (envelope-from jlemon) Date: Wed, 24 Jan 2001 21:52:51 -0600 (CST) From: Jonathan Lemon Message-Id: <200101250352.f0P3qpV49010@prism.flugsvamp.com> To: genuine@ma4.justnet.ne.jp, net@freebsd.org Subject: Re: estimation of RTT,RTO from tcpcb parameter X-Newsgroups: local.mail.freebsd-net In-Reply-To: References: Organization: Cc: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you write: >Thank you very much for your kindly advise. > >>The system timer ticks at a rate of 100 Hz on all IA32 processors. (I >>believe on Alphas it ticks at 1024 Hz but I may be imagining it.) >>Thus, the period is either 10 ms or 0.98 ms. >> >>In historic versions of FreeBSD, most TCP timers ticked at 2 Hz while >>the others ticked at 5 Hz. This was changed in advance of FreeBSD >>4.0. > >I see. >Anyway, it seems to be difficult that estimating RTT, RTO within a LAN >envirounment (such as Gigabit connection). >Of course, this time scale may be valid for general internet envirounment. >I'll study more. The math for RTT calculations is explained somewhere in Van Jacobsen's congestion avoidance & control paper, I believe. The equations have since been modified slightly since then, but give the basic idea. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 20:34: 2 2001 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 8F0F637B402 for ; Wed, 24 Jan 2001 20:33:44 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id XAA75280; Wed, 24 Jan 2001 23:33:42 -0500 (EST) (envelope-from wollman) Date: Wed, 24 Jan 2001 23:33:42 -0500 (EST) From: Garrett Wollman Message-Id: <200101250433.XAA75280@khavrinen.lcs.mit.edu> To: Luigi Rizzo Cc: net@FreeBSD.ORG Subject: error return by RTM_GET In-Reply-To: <200101250238.f0P2cTK33421@iguana.aciri.org> References: <200101250238.f0P2cTK33421@iguana.aciri.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > The error message is kind of misleading, i wonder if we can > replace the return value in sys/net/rtsock.c with > ENOMSG /* No message of desired type */ ? I think at one point it was returning ENOENT. There are no good error messages for this purpose; programs should do a better job of interpreting the error numbers that we have. If you want to propose a fix to route(8) I won't object. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 24 20:39: 7 2001 Delivered-To: freebsd-net@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 6793437B402 for ; Wed, 24 Jan 2001 20:38:50 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.1/8.11.1) id f0P4cmX35105; Wed, 24 Jan 2001 20:38:48 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200101250438.f0P4cmX35105@iguana.aciri.org> Subject: Re: error return by RTM_GET In-Reply-To: <200101250433.XAA75280@khavrinen.lcs.mit.edu> from Garrett Wollman at "Jan 24, 2001 11:33:42 pm" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Wed, 24 Jan 2001 20:38:48 -0800 (PST) Cc: rizzo@aciri.org, net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > The error message is kind of misleading, i wonder if we can > > replace the return value in sys/net/rtsock.c with > > ENOMSG /* No message of desired type */ ? > > I think at one point it was returning ENOENT. There are no good error > messages for this purpose; programs should do a better job of > interpreting the error numbers that we have. > > If you want to propose a fix to route(8) I won't object. yeah, this is probably the best way to avoid problems with userland apps. cheers luigi ----------------------------------+----------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone: (510) 666 2927 ----------------------------------+----------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 25 0:24:34 2001 Delivered-To: freebsd-net@freebsd.org Received: from web3004.mail.yahoo.com (web3004.mail.yahoo.com [204.71.202.167]) by hub.freebsd.org (Postfix) with SMTP id A755E37B402 for ; Thu, 25 Jan 2001 00:24:14 -0800 (PST) Received: (qmail 9312 invoked by uid 60001); 25 Jan 2001 08:24:04 -0000 Message-ID: <20010125082404.9311.qmail@web3004.mail.yahoo.com> Received: from [203.117.33.25] by web3004.mail.yahoo.com; Thu, 25 Jan 2001 00:24:04 PST Date: Thu, 25 Jan 2001 00:24:04 -0800 (PST) From: John Subject: problems compiling raw socket program To: freebsd-net@FreeBSD.ORG MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="0-197227092-980411044=:7396" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --0-197227092-980411044=:7396 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi Can anyone enlighten me on why I can't compile? I use gcc -o rawsocket rawsocket.c and I get: bash-2.03$ gcc -o rawsocket rawsocket.c In file included from rawsocket.c:7: /usr/include/netinet/ip.h:152: parse error before `n_long' /usr/include/netinet/ip.h:152: warning: no semicolon at end of struct or union /usr/include/netinet/ip.h:152: warning: no semicolon at end of struct or union /usr/include/netinet/ip.h:155: parse error before `n_long' /usr/include/netinet/ip.h:155: warning: no semicolon at end of struct or union /usr/include/netinet/ip.h:156: warning: data definition has no type or storage class /usr/include/netinet/ip.h:157: parse error before `}' /usr/include/netinet/ip.h:157: warning: data definition has no type or storage class /usr/include/netinet/ip.h:158: parse error before `}' bash-2.03$ thanks john __________________________________________________ Do You Yahoo!? Yahoo! Auctions - Buy the things you want at great prices. http://auctions.yahoo.com/ --0-197227092-980411044=:7396 Content-Type: text/plain; name="rawsocket.c" Content-Description: rawsocket.c Content-Disposition: inline; filename="rawsocket.c" #include #include #include #include #include #include #include #include #include #include #include #define PORTNUMBER 80 int main(void) { int n, s; char buf[4096]; char hostname[64]; //struct hostent *hp; struct sockaddr_in name; struct ip *iph = (struct ip *) buf; struct tcphdr *tcph = (struct tcphdr *) buf + sizeof (struct ip); memset (buf, 0, 4096); /* zero out the buffer */ /* we'll now fill in the ip/tcp header values, see above for explanations */ iph->ip_hl = 5; iph->ip_v = 4; iph->ip_tos = 0; iph->ip_len = sizeof (struct ip) + sizeof (struct tcphdr); /* no payload */ iph->ip_id = htonl (54321); /* the value doesn't matter here */ iph->ip_off = 0; iph->ip_ttl = 255; iph->ip_p = 6; iph->ip_sum = 0; /* set it to 0 before computing the actual checksum later */ iph->ip_src.s_addr = inet_addr ("1.2.3.4");/* SYN's can be blindly spoofed */ iph->ip_dst.s_addr = name.sin_addr.s_addr; tcph->th_sport = htons (1234); /* arbitrary port */ tcph->th_dport = htons (PORTNUMBER); tcph->th_seq = random ();/* in a SYN packet, the sequence is a random */ tcph->th_ack = 0;/* number, and the ack sequence is 0 in the 1st packet */ tcph->th_x2 = 0; tcph->th_off = 0; /* first and only tcp segment */ tcph->th_flags = TH_SYN; /* initial connection request */ tcph->th_win = htonl (65535); /* maximum allowed window size */ tcph->th_sum = 0;/* if you set a checksum to zero, your kernel's IP stack should fill in the correct checksum during transmission */ tcph->th_urp = 0; iph->ip_sum = csum ((unsigned short *) buf, iph->ip_len >> 1); if ((s = socket(AF_INET, SOCK_RAW, IPPROTO_UDP)) < 0) { perror("socket"); exit(1); } /* finally, it is very advisable to do a IP_HDRINCL call, to make sure that the kernel knows the header is included in the data, and doesn't insert its own header into the packet before our data */ { /* lets do it the ugly way.. */ int one = 1; const int *val = &one; if (setsockopt (s, IPPROTO_IP, IP_HDRINCL, val, sizeof (one)) < 0) printf ("Warning: Cannot set HDRINCL!\n"); } //create the address of the server, also local memset(&name, 0, sizeof(struct sockaddr_in)); name.sin_family = AF_INET; name.sin_port = htons(PORTNUMBER); name.sin_addr.s_addr = inet_addr ("127.0.0.1"); if (sendto (s, /* our socket */ buf, /* the buffer containing headers and data */ iph->ip_len, /* total length of our datagram */ 0, /* routing flags, normally always 0 */ (struct sockaddr *) &name, /* socket addr, just like in */ sizeof (name)) < 0) /* a normal send() */ printf ("error\n"); else printf ("."); close(s); exit(0); } --0-197227092-980411044=:7396-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 25 0:25:48 2001 Delivered-To: freebsd-net@freebsd.org Received: from mrout1.yahoo.com (mrout1.yahoo.com [208.48.125.95]) by hub.freebsd.org (Postfix) with ESMTP id 07FF537B401 for ; Thu, 25 Jan 2001 00:25:30 -0800 (PST) Received: from milk.yahoo.com (milk.yahoo.com [206.251.16.37]) by mrout1.yahoo.com (8.11.1/8.11.1/y.out) with ESMTP id f0P8PCs08729; Thu, 25 Jan 2001 00:25:12 -0800 (PST) Received: (from root@localhost) by milk.yahoo.com (8.11.0/8.11.0) id f0P8PAf77221; Thu, 25 Jan 2001 00:25:10 -0800 (PST) (envelope-from jayanth) Date: Thu, 25 Jan 2001 00:25:10 -0800 From: jayanth To: Bruce Evans Cc: Jordan Hubbard , Paul Herman , Jonathan Lemon , net@FreeBSD.ORG Subject: Re: I have delayed ACK problems Message-ID: <20010125002509.A77051@yahoo-inc.com> References: <77394.980367750@winston.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from bde@zeta.org.au on Thu, Jan 25, 2001 at 08:56:54AM +1100 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bruce, could you test this patch and compare the results. By generating an ACK for every segment with the TH_PSH flag set I found a significant increase in throughput. Index: tcp_input.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/tcp_input.c,v retrieving revision 1.122 diff -u -r1.122 tcp_input.c --- tcp_input.c 2001/01/24 16:25:36 1.122 +++ tcp_input.c 2001/01/25 08:08:36 @@ -966,7 +966,7 @@ m_adj(m, drop_hdrlen); /* delayed header drop */ sbappend(&so->so_rcv, m); sorwakeup(so); - if (tcp_delack_enabled) { + if ((tcp_delack_enabled) && !(th->th_flags & TH_PSH)){ callout_reset(tp->tt_delack, tcp_delacktime, tcp_timer_delack, tp); } else { jayanth Bruce Evans (bde@zeta.org.au) wrote: > On Wed, 24 Jan 2001, Jordan Hubbard wrote: > > > > Something just doesn't sit well me. This shouldn't happen in a > > > 100Mbit LAN. This seems like a plain vanilla network transaction, and > > > FreeBSD is failing on something, where other OSes in the same > > > environment don't. > > > > You're almost certainly correct that there's a misfeature lurking in > > there somewhere, I don't think anybody's arguing that particular > > point, it's just that you're also (sadly) in a much better position to > > diagnose this than [m]any of your readers since we don't have an > > active failure scenario to analyze like you do. :( > > I diagnosed similar problems in rmt(8) a few (?) months ago. Try: > > tar cf localhost:/tmp/foo /boot/kernel > > With the FreeBSD defaults, this crawls at almost precisely 100K/sec > due to its protocol waiting for an ack after every 10K block and acks > being delayed by 100 msec. > > Bruce > > > > 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 Thu Jan 25 1: 8:17 2001 Delivered-To: freebsd-net@freebsd.org Received: from hetnet.nl (net014s.hetnet.nl [194.151.104.154]) by hub.freebsd.org (Postfix) with ESMTP id AF50037B401 for ; Thu, 25 Jan 2001 01:08:00 -0800 (PST) Received: from wilbertd ([63.201.228.76]) by hetnet.nl with Microsoft SMTPSVC(5.5.1877.537.53); Thu, 25 Jan 2001 10:05:42 +0100 Message-ID: <00bd01c086ad$e51385e0$4ce4c93f@wilbertd> From: "Wilbert de Graaf" To: "John" Cc: References: <20010125082404.9311.qmail@web3004.mail.yahoo.com> Subject: Re: problems compiling raw socket program Date: Thu, 25 Jan 2001 01:04:57 -0800 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 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Can anyone enlighten me on why I can't compile? It tells you some types are missing so you need to add one or more headers. This will probably do it: #include Wilbert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 25 1:43:11 2001 Delivered-To: freebsd-net@freebsd.org Received: from web3005.mail.yahoo.com (web3005.mail.yahoo.com [204.71.202.168]) by hub.freebsd.org (Postfix) with SMTP id CD26037B699 for ; Thu, 25 Jan 2001 01:42:53 -0800 (PST) Received: (qmail 7043 invoked by uid 60001); 25 Jan 2001 09:42:43 -0000 Message-ID: <20010125094243.7042.qmail@web3005.mail.yahoo.com> Received: from [203.117.33.25] by web3005.mail.yahoo.com; Thu, 25 Jan 2001 01:42:43 PST Date: Thu, 25 Jan 2001 01:42:43 -0800 (PST) From: John Subject: Re: problems compiling raw socket program To: Wilbert de Graaf Cc: freebsd-net@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi I tried that as you had advised, but the error remains the same. bash-2.03$ gcc -o rawsocket rawsocket.c In file included from rawsocket.c:7: /usr/include/netinet/ip.h:152: parse error before `n_long' /usr/include/netinet/ip.h:152: warning: no semicolon at end of struct or union /usr/include/netinet/ip.h:152: warning: no semicolon at end of struct or union /usr/include/netinet/ip.h:155: parse error before `n_long' /usr/include/netinet/ip.h:155: warning: no semicolon at end of struct or union /usr/include/netinet/ip.h:156: warning: data definition has no type or storage class /usr/include/netinet/ip.h:157: parse error before `}' /usr/include/netinet/ip.h:157: warning: data definition has no type or storage class /usr/include/netinet/ip.h:158: parse error before `}' bash-2.03$ --- Wilbert de Graaf wrote: > > Can anyone enlighten me on why I can't compile? > > It tells you some types are missing so you need to > add one or more headers. > This will probably do it: #include > > > Wilbert > > __________________________________________________ Do You Yahoo!? Yahoo! Auctions - Buy the things you want at great prices. http://auctions.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 25 3: 6: 0 2001 Delivered-To: freebsd-net@freebsd.org Received: from samar.sasi.com (samar.sasken.com [164.164.56.2]) by hub.freebsd.org (Postfix) with ESMTP id 38C4237B698 for ; Thu, 25 Jan 2001 03:05:28 -0800 (PST) Received: from samar (samar.sasi.com [164.164.56.2]) by samar.sasi.com (8.9.3/8.9.3) with SMTP id QAA19724 for ; Thu, 25 Jan 2001 16:35:14 +0530 (IST) Received: from suns3.sasi.com ([10.0.36.3]) by samar.sasi.com; Thu, 25 Jan 2001 16:35:13 +0000 (IST) Received: from localhost (sseth@localhost) by suns3.sasi.com (8.9.3/8.9.3) with ESMTP id QAA29651 for ; Thu, 25 Jan 2001 16:35:12 +0530 (IST) Date: Thu, 25 Jan 2001 16:35:12 +0530 (IST) From: Satyajeet Seth To: Subject: Pseudo ethernet interface Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Is it possible to provide pseudo ethernet interfaces? Can we associate an IP and MAC address with a psuedo ethernet interface to facilitate data packet transmission & reception through that? If so, how does it work? Pointers to any documentation in this regard will be appreciated. This mail has also been posted to freebsd-hackers. Thanks, Satya To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 25 3:51:25 2001 Delivered-To: freebsd-net@freebsd.org Received: from paprika.michvhf.com (adsl-pool23-22.detroit.mi.ameritech.net [64.108.56.22]) by hub.freebsd.org (Postfix) with SMTP id AFEE437B400 for ; Thu, 25 Jan 2001 03:51:06 -0800 (PST) Received: (qmail 11282 invoked by uid 1001); 25 Jan 2001 11:51:06 -0000 Date: Thu, 25 Jan 2001 06:51:06 -0500 (EST) From: Vince Vielhaber To: John Cc: Subject: Re: problems compiling raw socket program In-Reply-To: <20010125094243.7042.qmail@web3005.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 25 Jan 2001, John wrote: > Hi > > I tried that as you had advised, but the error remains > the same. Rearrange your includes like this: #include #include #include #include #include #include #include #include #include #include #include #include and it'll compile, but the link fails with: undefined reference to `csum' missing library, but I didn't bother looking to see what. Vince. > > bash-2.03$ gcc -o rawsocket rawsocket.c > In file included from rawsocket.c:7: > /usr/include/netinet/ip.h:152: parse error before > `n_long' > /usr/include/netinet/ip.h:152: warning: no semicolon > at end of struct or union > /usr/include/netinet/ip.h:152: warning: no semicolon > at end of struct or union > /usr/include/netinet/ip.h:155: parse error before > `n_long' > /usr/include/netinet/ip.h:155: warning: no semicolon > at end of struct or union > /usr/include/netinet/ip.h:156: warning: data > definition has no type or storage class > /usr/include/netinet/ip.h:157: parse error before `}' > /usr/include/netinet/ip.h:157: warning: data > definition has no type or storage class > /usr/include/netinet/ip.h:158: parse error before `}' > bash-2.03$ > > > > --- Wilbert de Graaf wrote: > > > Can anyone enlighten me on why I can't compile? > > > > It tells you some types are missing so you need to > > add one or more headers. > > This will probably do it: #include > > > > > > Wilbert > > > > > > > __________________________________________________ > Do You Yahoo!? > Yahoo! Auctions - Buy the things you want at great prices. > http://auctions.yahoo.com/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com http://www.pop4.net 128K ISDN from $22.00/mo - 56K Dialup from $16.00/mo at Pop4 Networking Online Campground Directory http://www.camping-usa.com Online Giftshop Superstore http://www.cloudninegifts.com ========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 25 4: 6: 0 2001 Delivered-To: freebsd-net@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id A89CD37B400 for ; Thu, 25 Jan 2001 04:05:43 -0800 (PST) Received: from beagle (beagle [193.175.132.100]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id MAA18452; Thu, 25 Jan 2001 12:19:02 +0100 (MET) Date: Thu, 25 Jan 2001 12:19:02 +0100 (CET) From: Harti Brandt To: Satyajeet Seth Cc: freebsd-net@FreeBSD.ORG Subject: Re: Pseudo ethernet interface In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 25 Jan 2001, Satyajeet Seth wrote: > Hi, > > Is it possible to provide pseudo ethernet interfaces? > Can we associate an IP and MAC address with a psuedo ethernet interface > to facilitate data packet transmission & reception through that? > If so, how does it work? > Pointers to any documentation in this regard will be appreciated. > > This mail has also been posted to freebsd-hackers. > > Thanks, Satya man 4 tap harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.gmd.de, harti@begemot.org, lhbrandt@mail.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 25 5:52:34 2001 Delivered-To: freebsd-net@freebsd.org Received: from bart.esiee.fr (bart.esiee.fr [147.215.1.20]) by hub.freebsd.org (Postfix) with ESMTP id 43C3337B400 for ; Thu, 25 Jan 2001 05:52:17 -0800 (PST) Received: (from bonnetf@localhost) by bart.esiee.fr (8.11.1/8.11.1) id f0PDqFS13664 for freebsd-net@freebsd.org; Thu, 25 Jan 2001 14:52:15 +0100 (MET) From: Frank Bonnet Message-Id: <200101251352.f0PDqFS13664@bart.esiee.fr> Subject: sysctl: unknown oid 'net.link.ether.bridge' To: freebsd-net@freebsd.org Date: Thu, 25 Jan 2001 14:52:15 MET X-Mailer: Elm [revision: 212.5] Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi trying to setup bridging on a 4.2-RELEASE box I get this error message ... sysctl -w net.link.ether.bridge=1 sysctl: unknown oid 'net.link.ether.bridge' I've rebuild the kernel with following the http://www.freebsd.org/handbook/bridging.html instructions ... Any help welcome TIA -- Frank Bonnet Systemes et Reseaux UNIX Groupe ESIEE Paris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 25 8:19:24 2001 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 510FD37B6A8 for ; Thu, 25 Jan 2001 08:19:05 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA83006; Thu, 25 Jan 2001 11:17:51 -0500 (EST) (envelope-from wollman) Date: Thu, 25 Jan 2001 11:17:51 -0500 (EST) From: Garrett Wollman Message-Id: <200101251617.LAA83006@khavrinen.lcs.mit.edu> To: jayanth Cc: net@FreeBSD.ORG Subject: Re: I have delayed ACK problems In-Reply-To: <20010125002509.A77051@yahoo-inc.com> References: <77394.980367750@winston.osd.bsdi.com> <20010125002509.A77051@yahoo-inc.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > could you test this patch and compare the results. > By generating an ACK for every segment with the TH_PSH flag set > I found a significant increase in throughput. I don't think this is right. I think what we want to do is: if (callout_pending(tp->tt_delack)) { callout_stop(tp->tt_delack); tp->t_flags |= TF_ACKNOW; } else callout_reset(...) This has the effect of ACKing every other packet. This should probably be encapsulated in a macro: #define MAYBE_DELAYED_ACK(tp) \ do { \ if (tcp_delack_enabled) { \ if (callout_pending(tp->tt_delack)) { \ callout_stop(tp->tt_delack); \ tp->t_flags |= TF_ACKNOW; \ } else \ callout_reset(tp->tt_delack, \ tcp_delacktime, \ tcp_timer_delack, tp); \ } else \ tp->t_flags |= TF_ACKNOW; \ while (0) (It may be possible to eliminate the callout_stop() call and one of the `if' statements.) -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 25 8:53:48 2001 Delivered-To: freebsd-net@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 08D1537B401 for ; Thu, 25 Jan 2001 08:53:29 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.1/8.11.1) id f0PGrMU40657; Thu, 25 Jan 2001 08:53:22 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200101251653.f0PGrMU40657@iguana.aciri.org> Subject: Re: sysctl: unknown oid 'net.link.ether.bridge' In-Reply-To: <200101251352.f0PDqFS13664@bart.esiee.fr> from Frank Bonnet at "Jan 25, 2001 2:52:15 pm" To: bonnetf@bart.esiee.fr (Frank Bonnet) Date: Thu, 25 Jan 2001 08:53:22 -0800 (PST) Cc: freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org did you have "options BRIDGE" in your kernel config ? cheers luigi > Hi > trying to setup bridging on a 4.2-RELEASE box > I get this error message ... > > sysctl -w net.link.ether.bridge=1 > sysctl: unknown oid 'net.link.ether.bridge' > > > I've rebuild the kernel with following the > http://www.freebsd.org/handbook/bridging.html > instructions ... > > Any help welcome > TIA > -- > Frank Bonnet > Systemes et Reseaux UNIX > Groupe ESIEE Paris > > > 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 Thu Jan 25 9:14:50 2001 Delivered-To: freebsd-net@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id C8A4337B402; Thu, 25 Jan 2001 09:14:30 -0800 (PST) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f0PHE3L73868; Thu, 25 Jan 2001 11:14:03 -0600 (CST) (envelope-from jlemon) Date: Thu, 25 Jan 2001 11:14:03 -0600 (CST) From: Jonathan Lemon Message-Id: <200101251714.f0PHE3L73868@prism.flugsvamp.com> To: wollman@khavrinen.lcs.mit.edu, net@freebsd.org, jayanth@freebsd.org Subject: Re: I have delayed ACK problems X-Newsgroups: local.mail.freebsd-net In-Reply-To: References: Organization: Cc: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you write: >< said: > >> could you test this patch and compare the results. >> By generating an ACK for every segment with the TH_PSH flag set >> I found a significant increase in throughput. > >I don't think this is right. > >I think what we want to do is: > > if (callout_pending(tp->tt_delack)) { > callout_stop(tp->tt_delack); > tp->t_flags |= TF_ACKNOW; > } else > callout_reset(...) I'm not sure this is required. Expanding the context of the area in question: /* * Add data to socket buffer. */ m_adj(m, drop_hdrlen); /* delayed header drop */ sbappend(&so->so_rcv, m); sorwakeup(so); if (tcp_delack_enabled) { callout_reset(tp->tt_delack, tcp_delacktime, tcp_timer_delack, tp); } else { tp->t_flags |= TF_ACKNOW; tcp_output(tp); } return; From the bottom portion of tcp_output(): tp->last_ack_sent = tp->rcv_nxt; tp->t_flags &= ~TF_ACKNOW; if (tcp_delack_enabled) callout_stop(tp->tt_delack); So simply setting TF_ACKNOW and calling tcp_output should be sufficient; if there is a pending delack timer it will get turned off when the ACK is actually sent. I think that jayanth's patch is correct, although I slightly dislike tying it to the PSH flag - not all implementations actually set this. However, it is better than the lower bound of acking every incoming data packet. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 25 9:41:24 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 2F86C37B400 for ; Thu, 25 Jan 2001 09:41:05 -0800 (PST) Received: from husten.security.at12.de (dial-213-168-64-19.netcologne.de [213.168.64.19]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id SAA10710; Thu, 25 Jan 2001 18:41:02 +0100 (MET) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by husten.security.at12.de (8.11.1/8.11.1) with ESMTP id f0PHdO038879; Thu, 25 Jan 2001 18:39:24 +0100 (CET) (envelope-from pherman@frenchfries.net) Date: Thu, 25 Jan 2001 18:39:24 +0100 (CET) From: Paul Herman To: Garrett Wollman Cc: jayanth , Subject: Re: I have delayed ACK problems In-Reply-To: <200101251617.LAA83006@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1724782094-980443456=:11792" Content-ID: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1724782094-980443456=:11792 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: On Thu, 25 Jan 2001, Garrett Wollman wrote: > < said: > > > could you test this patch and compare the results. > > By generating an ACK for every segment with the TH_PSH flag set > > I found a significant increase in throughput. > > I don't think this is right. I don't think it is either -- trying it with the rmt(8) results in each mss packet geting it's own ACK, which is the same behaviour as turning of delayed acks all together. This morning I came up with this patch, which *seems* to have solved both problems: 1) the rmt(8) problem Bruce wrote about and 2) my problem with the Solaris <-> FreeBSD problem I was experiencing. Thing is, I'm no TCP expert, and I am way out of my league on this. In fact, I'm certain it breaks something (for one the delayed ack counter no longer runs up, hmmm, and a few connections will stall), but maybe it's a start. Whatever happened to TF_DELACK anyway? -Paul. --0-1724782094-980443456=:11792 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="delack-current.patch" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="delack-current.patch" SW5kZXg6IHRjcF9pbnB1dC5jDQo9PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09DQpS Q1MgZmlsZTogL2hvbWUvbmN2cy9zcmMvc3lzL25ldGluZXQvdGNwX2lucHV0 LmMsdg0KcmV0cmlldmluZyByZXZpc2lvbiAxLjEyMQ0KZGlmZiAtdSAtcjEu MTIxIHRjcF9pbnB1dC5jDQotLS0gdGNwX2lucHV0LmMJMjAwMC8xMi8xNSAy MTo0NTo0OQkxLjEyMQ0KKysrIHRjcF9pbnB1dC5jCTIwMDEvMDEvMjUgMTc6 MzY6MjENCkBAIC0xNzgsOSArMTc4LDE0IEBADQogCWlmICgodGgpLT50aF9z ZXEgPT0gKHRwKS0+cmN2X254dCAmJiBcDQogCSAgICBMSVNUX0VNUFRZKCYo dHApLT50X3NlZ3EpICYmIFwNCiAJICAgICh0cCktPnRfc3RhdGUgPT0gVENQ U19FU1RBQkxJU0hFRCkgeyBcDQotCQlpZiAodGNwX2RlbGFja19lbmFibGVk KSBcDQotCQkJY2FsbG91dF9yZXNldCh0cC0+dHRfZGVsYWNrLCB0Y3BfZGVs YWNrdGltZSwgXA0KLQkJCSAgICB0Y3BfdGltZXJfZGVsYWNrLCB0cCk7IFwN CisJCWlmICh0Y3BfZGVsYWNrX2VuYWJsZWQpIHsgXA0KKwkJCWlmICh0aC0+ dGhfZmxhZ3MgJiBUSF9QVVNIKSB7IFwNCisJCQkJdHAtPnRfZmxhZ3MgfD0g VEZfQUNLTk9XOyBcDQorCQkJCWNhbGxvdXRfcmVzZXQodHAtPnR0X2RlbGFj aywgdGNwX2RlbGFja3RpbWUsIHRjcF90aW1lcl9kZWxhY2ssIHRwKTsgXA0K KwkJCX0gXA0KKwkJCWVsc2UgXA0KKwkJCQl0cC0+dF9mbGFncyB8PSBURl9E RUxBQ0s7IFwNCisJCX0gXA0KIAkJZWxzZSBcDQogCQkJdHAtPnRfZmxhZ3Mg fD0gVEZfQUNLTk9XOyBcDQogCQkodHApLT5yY3Zfbnh0ICs9ICoodGxlbnAp OyBcDQpAQCAtOTY3LDggKzk3MiwxMyBAQA0KIAkJCXNiYXBwZW5kKCZzby0+ c29fcmN2LCBtKTsNCiAJCQlzb3J3YWtldXAoc28pOw0KIAkJCWlmICh0Y3Bf ZGVsYWNrX2VuYWJsZWQpIHsNCi0JICAgICAgICAgICAgICAgICAgICAgICAg Y2FsbG91dF9yZXNldCh0cC0+dHRfZGVsYWNrLCB0Y3BfZGVsYWNrdGltZSwN Ci0JICAgICAgICAgICAgICAgICAgICAgICAgICAgIHRjcF90aW1lcl9kZWxh Y2ssIHRwKTsNCisJCQkJaWYgKHRoLT50aF9mbGFncyAmIFRIX1BVU0gpIHsN CisJCQkJCXRwLT50X2ZsYWdzIHw9IFRGX0FDS05PVzsNCisJCSAgICAgICAg ICAgICAgICAgICAgICAgIGNhbGxvdXRfcmVzZXQodHAtPnR0X2RlbGFjaywg dGNwX2RlbGFja3RpbWUsDQorCQkgICAgICAgICAgICAgICAgICAgICAgICAg ICAgdGNwX3RpbWVyX2RlbGFjaywgdHApOw0KKwkJCQl9DQorCQkJCWVsc2UN CisJCQkJCXRwLT50X2ZsYWdzIHw9IFRGX0RFTEFDSzsNCiAJCQl9IGVsc2Ug ew0KIAkJCQl0cC0+dF9mbGFncyB8PSBURl9BQ0tOT1c7DQogCQkJCXRjcF9v dXRwdXQodHApOw0KSW5kZXg6IHRjcF9vdXRwdXQuYw0KPT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PQ0KUkNTIGZpbGU6IC9ob21lL25jdnMvc3JjL3N5cy9uZXRp bmV0L3RjcF9vdXRwdXQuYyx2DQpyZXRyaWV2aW5nIHJldmlzaW9uIDEuNDgN CmRpZmYgLXUgLXIxLjQ4IHRjcF9vdXRwdXQuYw0KLS0tIHRjcF9vdXRwdXQu YwkyMDAwLzEwLzI3IDExOjQ1OjQxCTEuNDgNCisrKyB0Y3Bfb3V0cHV0LmMJ MjAwMS8wMS8yNSAxNzozNjoyMQ0KQEAgLTkxMyw3ICs5MTMsNyBAQA0KIAlp ZiAod2luID4gMCAmJiBTRVFfR1QodHAtPnJjdl9ueHQrd2luLCB0cC0+cmN2 X2FkdikpDQogCQl0cC0+cmN2X2FkdiA9IHRwLT5yY3Zfbnh0ICsgd2luOw0K IAl0cC0+bGFzdF9hY2tfc2VudCA9IHRwLT5yY3Zfbnh0Ow0KLQl0cC0+dF9m bGFncyAmPSB+VEZfQUNLTk9XOw0KKwl0cC0+dF9mbGFncyAmPSB+KFRGX0FD S05PV3xURl9ERUxBQ0spOw0KIAlpZiAodGNwX2RlbGFja19lbmFibGVkKQ0K IAkJY2FsbG91dF9zdG9wKHRwLT50dF9kZWxhY2spOw0KIAlpZiAoc2VuZGFs b3QgJiYgKCF0Y3BfZG9fbmV3cmVubyB8fCAtLW1heGJ1cnN0KSkNCkluZGV4 OiB0Y3BfdGltZXIuYw0KPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQ0KUkNTIGZp bGU6IC9ob21lL25jdnMvc3JjL3N5cy9uZXRpbmV0L3RjcF90aW1lci5jLHYN CnJldHJpZXZpbmcgcmV2aXNpb24gMS4zOQ0KZGlmZiAtdSAtcjEuMzkgdGNw X3RpbWVyLmMNCi0tLSB0Y3BfdGltZXIuYwkyMDAwLzEwLzAyIDE1OjAwOjEz CTEuMzkNCisrKyB0Y3BfdGltZXIuYwkyMDAxLzAxLzI1IDE3OjM2OjIxDQpA QCAtMTczLDExICsxNzMsMTMgQEANCiAJCXNwbHgocyk7DQogCQlyZXR1cm47 DQogCX0NCi0JY2FsbG91dF9kZWFjdGl2YXRlKHRwLT50dF9kZWxhY2spOw0K LQ0KLQl0cC0+dF9mbGFncyB8PSBURl9BQ0tOT1c7DQotCXRjcHN0YXQudGNw c19kZWxhY2srKzsNCi0JKHZvaWQpIHRjcF9vdXRwdXQodHApOw0KKwlpZiAo dHAtPnRfZmxhZ3MgJiBURl9ERUxBQ0spIHsNCisJCWNhbGxvdXRfZGVhY3Rp dmF0ZSh0cC0+dHRfZGVsYWNrKTsNCisJCXRwLT50X2ZsYWdzICY9IH5URl9E RUxBQ0s7DQorCQl0cC0+dF9mbGFncyB8PSBURl9BQ0tOT1c7DQorCQl0Y3Bz dGF0LnRjcHNfZGVsYWNrKys7DQorCQkodm9pZCkgdGNwX291dHB1dCh0cCk7 DQorCQl9DQogCXNwbHgocyk7DQogfQ0KIA0K --0-1724782094-980443456=:11792-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 25 9:51:42 2001 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 581C937B69F for ; Thu, 25 Jan 2001 09:51:25 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id MAA83819; Thu, 25 Jan 2001 12:51:14 -0500 (EST) (envelope-from wollman) Date: Thu, 25 Jan 2001 12:51:14 -0500 (EST) From: Garrett Wollman Message-Id: <200101251751.MAA83819@khavrinen.lcs.mit.edu> To: Jonathan Lemon Cc: net@freebsd.org Subject: Re: I have delayed ACK problems In-Reply-To: <200101251714.f0PHE3L73868@prism.flugsvamp.com> References: <200101251714.f0PHE3L73868@prism.flugsvamp.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > I'm not sure this is required. Expanding the context of the area in > question: The important part was the if (callout_pending(tp->tt_delack)) { ... tp->t_flags |= TF_ACKNOW; } bit. This causes us to ack immediately where previously we would just delay an already-schedule delayed ack. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 25 9:55:34 2001 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id F30AE37B6A2 for ; Thu, 25 Jan 2001 09:55:14 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id MAA83840; Thu, 25 Jan 2001 12:55:07 -0500 (EST) (envelope-from wollman) Date: Thu, 25 Jan 2001 12:55:07 -0500 (EST) From: Garrett Wollman Message-Id: <200101251755.MAA83840@khavrinen.lcs.mit.edu> To: Paul Herman Cc: net@FreeBSD.ORG Subject: Re: I have delayed ACK problems In-Reply-To: References: <200101251617.LAA83006@khavrinen.lcs.mit.edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > Whatever happened to TF_DELACK anyway? It was removed since it is no longer necessary. The same information can be gleaned from callout_pending(tp->tt_delack). > SW5kZXg6IHRjcF9pbnB1dC5jDQo9PT09PT09PT09PT09PT09PT09PT09PT09 > PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09DQpS Please do not MIME-encrypt patches; it makes them much more difficult to read. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 25 10:51:30 2001 Delivered-To: freebsd-net@freebsd.org Received: from mailman.packetdesign.com (dns.PACKETDESIGN.NET [216.15.46.10]) by hub.freebsd.org (Postfix) with ESMTP id 6749537B6A7; Thu, 25 Jan 2001 10:50:56 -0800 (PST) Received: from bubba.packetdesign.com (bubba.packetdesign.com [192.168.0.223]) by mailman.packetdesign.com (8.11.0/8.11.0) with ESMTP id f0PIosI77362; Thu, 25 Jan 2001 10:50:54 -0800 (PST) (envelope-from archie@packetdesign.com) Received: (from archie@localhost) by bubba.packetdesign.com (8.11.1/8.11.1) id f0PIoUw67420; Thu, 25 Jan 2001 10:50:30 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200101251850.f0PIoUw67420@bubba.packetdesign.com> Subject: sf driver problem? To: freebsd-net@freebsd.org, freebsd-hackers@freebsd.org Date: Thu, 25 Jan 2001 10:50:30 -0800 (PST) Cc: wpaul@freebsd.org X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Has anyone had any luck in figuring out why the Adaptec ANA four-port Ethernet cards dramatically slow down the machine when all four ports are in use? http://www.freebsd.org/cgi/query-pr.cgi?pr=22624 (nevermind the video interrupt conflict theory, that doesn't seem to have anything to do with it) Thanks, -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 25 14:20: 3 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 8E1DB37B400 for ; Thu, 25 Jan 2001 14:19:44 -0800 (PST) Received: from husten.security.at12.de (dial-213-168-89-127.netcologne.de [213.168.89.127] (may be forged)) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id XAA06836; Thu, 25 Jan 2001 23:19:37 +0100 (MET) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by husten.security.at12.de (8.11.1/8.11.1) with ESMTP id f0PMJQA20260; Thu, 25 Jan 2001 23:19:26 +0100 (CET) (envelope-from pherman@frenchfries.net) Date: Thu, 25 Jan 2001 23:19:25 +0100 (CET) From: Paul Herman To: Garrett Wollman Cc: Jonathan Lemon , Subject: Re: I have delayed ACK problems In-Reply-To: <200101251751.MAA83819@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 25 Jan 2001, Garrett Wollman wrote: > < said: > > The important part was the > if (callout_pending(tp->tt_delack)) { > ... > tp->t_flags |= TF_ACKNOW; > } > > bit. This causes us to ack immediately where previously we would just > delay an already-schedule delayed ack. Yep, that does it. Simple. Elegant. I see now why my (bloated unintelligible) patch worked, it also didn't reset the timer when a delayed ack might have already been pending. OK, there are other parts of the code that do the same thing (TCP_REASS, SYN was ACKed, et. al.) but if no one objects, I'll send-pr the patch to be commited. Thanks everybody!! -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 25 17:25:59 2001 Delivered-To: freebsd-net@freebsd.org Received: from virtual.sysadmin-inc.com (lists.sysadmin-inc.com [209.16.228.140]) by hub.freebsd.org (Postfix) with ESMTP id 34D6F37B400 for ; Thu, 25 Jan 2001 17:25:41 -0800 (PST) Received: from wkst (virtual2.sysadmin-inc.com [209.16.228.145]) by virtual.sysadmin-inc.com (8.9.1/8.9.1) with SMTP id UAA04934 for ; Thu, 25 Jan 2001 20:25:40 -0500 Reply-To: From: "Peter Brezny" To: Subject: ipfw not allowing udp? Date: Thu, 25 Jan 2001 20:24:46 -0800 Message-ID: <003601c0874f$ea8932c0$46010a0a@sysadmininc.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a line in my firewall config like this: ipfw add allow udp from any 53 to my.ns.ip.here 53 and was dissappointed to find that when i configured a secondary name server to use the primary behind the firewall, it was unable to make the zone transfers... have i missed something big and zone transfers require more than just port 53? TIA Peter Brezny SysAdmin Services Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 25 17:33:23 2001 Delivered-To: freebsd-net@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id E683237B401 for ; Thu, 25 Jan 2001 17:33:06 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.1/8.11.1) id f0Q1X1d61734; Thu, 25 Jan 2001 17:33:01 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200101260133.f0Q1X1d61734@iguana.aciri.org> Subject: Re: ipfw not allowing udp? In-Reply-To: <003601c0874f$ea8932c0$46010a0a@sysadmininc.com> from Peter Brezny at "Jan 25, 2001 8:24:46 pm" To: peter@sysadmin-inc.com Date: Thu, 25 Jan 2001 17:33:00 -0800 (PST) Cc: freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I have a line in my firewall config like this: > > ipfw add allow udp from any 53 to my.ns.ip.here 53 > > and was dissappointed to find that when i configured a secondary name server > to use the primary behind the firewall, it was unable to make the zone > transfers... > > have i missed something big and zone transfers require more than just port > 53? don't they use tcp as well ? luigi > TIA > > Peter Brezny > SysAdmin Services Inc. > > > > 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 Thu Jan 25 18: 5: 3 2001 Delivered-To: freebsd-net@freebsd.org Received: from ceasefire.bitstream.net (ceasefire.bitstream.net [216.243.128.220]) by hub.freebsd.org (Postfix) with SMTP id 5672A37B400 for ; Thu, 25 Jan 2001 18:04:44 -0800 (PST) Received: (qmail 35539 invoked from network); 26 Jan 2001 02:04:43 -0000 Received: from unknown (HELO dmitri.bitstream.net) (216.243.132.33) by ceasefire with SMTP; 26 Jan 2001 02:04:43 -0000 Date: Thu, 25 Jan 2001 19:59:09 -0600 (CST) From: Dan Debertin To: Peter Brezny Cc: Subject: Re: ipfw not allowing udp? In-Reply-To: <003601c0874f$ea8932c0$46010a0a@sysadmininc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 25 Jan 2001, Peter Brezny wrote: > have i missed something big and zone transfers require more than just port > 53? Zone transfers (and any DNS transaction that requires packet sizes larger than 512 bytes) use TCP port 53. ~Dan D. -- ++ Unix is the worst operating system, except for all others. ++ Dan Debertin ++ Senior Systems Administrator ++ Bitstream Underground, LLC ++ airboss@bitstream.net ++ (612)321-9290 x108 ++ GPG Fingerprint: 0BC5 F4D6 649F D0C8 D1A7 CAE4 BEF4 0A5C 300D 2387 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 25 18:21:37 2001 Delivered-To: freebsd-net@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id 86FD237B404 for ; Thu, 25 Jan 2001 18:21:19 -0800 (PST) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id TAA13806; Thu, 25 Jan 2001 19:21:10 -0700 (MST) Date: Thu, 25 Jan 2001 19:21:10 -0700 (MST) From: Nick Rogness To: Peter Brezny Cc: freebsd-net@freebsd.org Subject: Re: ipfw not allowing udp? In-Reply-To: <003601c0874f$ea8932c0$46010a0a@sysadmininc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 25 Jan 2001, Peter Brezny wrote: > I have a line in my firewall config like this: > > ipfw add allow udp from any 53 to my.ns.ip.here 53 > > and was dissappointed to find that when i configured a secondary name server > to use the primary behind the firewall, it was unable to make the zone > transfers... > > have i missed something big and zone transfers require more than just port > 53? Zone transfer work on port 53 TCP. Nick Rogness - Keep on routing in a Free World... "FreeBSD: The Power to Serve " To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 25 22:20:13 2001 Delivered-To: freebsd-net@freebsd.org Received: from blackstar.krsu.edu.kg (unknown [195.254.160.132]) by hub.freebsd.org (Postfix) with ESMTP id 1A21637B400 for ; Thu, 25 Jan 2001 22:19:51 -0800 (PST) Received: from krsu.edu.kg (krsu.edu.kg [195.254.164.3]) by blackstar.krsu.edu.kg (8.9.1a/8.9.1) with ESMTP id MAA25766 for ; Mon, 4 Dec 2000 12:37:18 +0500 (KGT) Received: from localhost (ildar@localhost) by krsu.edu.kg (8.9.3/8.9.3) with ESMTP id LAA56522 for ; Fri, 26 Jan 2001 11:26:17 +0500 (KGT) (envelope-from ildar@krsu.edu.kg) Date: Fri, 26 Jan 2001 11:26:17 +0500 (KGT) From: -Digger To: freebsd-net@FreeBSD.ORG Subject: What for messages? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hi all, what for messages and what daemon or process can make it? file /var/log/messages: ---cut--- host /kernel: Connection attempt to TCP 127.0.0.1:199 from 127.0.0.1035 host /kernel: Connection attempt to TCP 127.0.0.1:199 from 127.0.0.1036 host /kernel: Connection attempt to TCP 127.0.0.1:199 from 127.0.0.1037 host /kernel: Connection attempt to TCP 127.0.0.1:199 from 127.0.0.1038 ---cut--- In a file /etc/services I have not found description of this port. Thank's P.S. Sorry for my bAd english --- -Digger, BOFH ;) Telecommunication Centre of KRSU ICQ# 48385535 SOAP: ildar@krsu.edu.kg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 25 22:32: 7 2001 Delivered-To: freebsd-net@freebsd.org Received: from bilver.wjv.com (dhcp-1-33.n01.orldfl01.us.ra.verio.net [157.238.210.33]) by hub.freebsd.org (Postfix) with ESMTP id BF63B37B400 for ; Thu, 25 Jan 2001 22:31:43 -0800 (PST) Received: (from bill@localhost) by bilver.wjv.com (8.9.3/8.9.3) id BAA03603 for freebsd-net@freebsd.org; Fri, 26 Jan 2001 01:31:42 -0500 (EST) (envelope-from bill) Date: Fri, 26 Jan 2001 01:31:40 -0500 From: Bill Vermillion To: freebsd-net@freebsd.org Subject: Re: What for messages? Message-ID: <20010126013140.C3452@wjv.com> Reply-To: bv@bilver.wjv.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from ildar@krsu.edu.kg on Fri, Jan 26, 2001 at 11:26:17AM +0500 Organization: W.J.Vermillion / Orlando - Winter Park Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jan 26, 2001 at 11:26:17AM +0500, -Digger thus spoke: > hi all, > what for messages and what daemon or process can make it? > > file /var/log/messages: > > ---cut--- > host /kernel: Connection attempt to TCP 127.0.0.1:199 from 127.0.0.1035 > host /kernel: Connection attempt to TCP 127.0.0.1:199 from 127.0.0.1036 > host /kernel: Connection attempt to TCP 127.0.0.1:199 from 127.0.0.1037 > host /kernel: Connection attempt to TCP 127.0.0.1:199 from 127.0.0.1038 > ---cut--- > > In a file /etc/services I have not found description of this port. > > Thank's > > P.S. Sorry for my bAd english > Do you have log_in_vain="YES" in your rc.conf. That what it looks like at first glance to me. Bill -- Bill Vermillion - bv @ wjv . com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 25 22:55:47 2001 Delivered-To: freebsd-net@freebsd.org Received: from blackstar.krsu.edu.kg (unknown [195.254.160.132]) by hub.freebsd.org (Postfix) with ESMTP id 4D97037B401 for ; Thu, 25 Jan 2001 22:55:20 -0800 (PST) Received: from krsu.edu.kg (krsu.edu.kg [195.254.164.3]) by blackstar.krsu.edu.kg (8.9.1a/8.9.1) with ESMTP id NAA00243; Mon, 4 Dec 2000 13:12:53 +0500 (KGT) Received: from localhost (ildar@localhost) by krsu.edu.kg (8.9.3/8.9.3) with ESMTP id MAA57261; Fri, 26 Jan 2001 12:01:50 +0500 (KGT) (envelope-from ildar@krsu.edu.kg) Date: Fri, 26 Jan 2001 12:01:50 +0500 (KGT) From: -Digger To: bv@wjv.com Cc: freebsd-net@FreeBSD.ORG Subject: Re: What for messages? In-Reply-To: <20010126013140.C3452@wjv.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 26 Jan 2001, Bill Vermillion wrote: > On Fri, Jan 26, 2001 at 11:26:17AM +0500, -Digger thus spoke: > > hi all, > > > what for messages and what daemon or process can make it? > > > > file /var/log/messages: > > > > ---cut--- > > host /kernel: Connection attempt to TCP 127.0.0.1:199 from 127.0.0.1035 > > host /kernel: Connection attempt to TCP 127.0.0.1:199 from 127.0.0.1036 > > host /kernel: Connection attempt to TCP 127.0.0.1:199 from 127.0.0.1037 > > host /kernel: Connection attempt to TCP 127.0.0.1:199 from 127.0.0.1038 > > ---cut--- > > > > In a file /etc/services I have not found description of this port. > > > > Thank's > > > > P.S. Sorry for my bAd english > > > > Do you have log_in_vain="YES" in your rc.conf. That what it > looks like at first glance to me. Yes, i have log_in_vain="YES" in rc.conf, well nevertheless what daemon makes it? > > Bill > -- > Bill Vermillion - bv @ wjv . com --- -Digger, BOFH ;) Telecommunication Centre of KRSU ICQ# 48385535 SOAP: ildar@krsu.edu.kg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 25 23: 8:32 2001 Delivered-To: freebsd-net@freebsd.org Received: from atro.pine.nl (atro.pine.nl [213.156.0.2]) by hub.freebsd.org (Postfix) with ESMTP id 823A037B400 for ; Thu, 25 Jan 2001 23:08:15 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by atro.pine.nl (8.11.1/8.11.1) with ESMTP id f0Q78Bn00373; Fri, 26 Jan 2001 08:08:12 +0100 (MET) Date: Fri, 26 Jan 2001 08:08:11 +0100 (MET) From: Mark Lastdrager To: Peter Brezny Cc: Subject: Re: ipfw not allowing udp? In-Reply-To: <003601c0874f$ea8932c0$46010a0a@sysadmininc.com> Message-ID: X-NCC-RegID: nl.pine MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At Thu, 25 Jan 2001, owner-freebsd-net@FreeBSD.ORG wrote: >I have a line in my firewall config like this: > >ipfw add allow udp from any 53 to my.ns.ip.here 53 > >and was dissappointed to find that when i configured a secondary name server >to use the primary behind the firewall, it was unable to make the zone >transfers... > >have i missed something big and zone transfers require more than just port >53? I think I don't have to repeat that zonetransfers use 53/tcp ;-) What could be helpful here is to insert a rule before the default deny rule: ipfw add deny log ip from any to any This way all denies are being logged so you can see what's wrong. Mark Lastdrager -- Pine Internet BV :: tel. +31-70-3111010 :: fax. +31-70-3111011 PGP 92BB81D1 fingerprint 0059 7D7B C02B 38D2 A853 2785 8C87 3AF1 Today's excuse: The rolling stones concert down the road caused a brown out To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jan 26 6: 5:42 2001 Delivered-To: freebsd-net@freebsd.org Received: from virtual.sysadmin-inc.com (lists.sysadmin-inc.com [209.16.228.140]) by hub.freebsd.org (Postfix) with ESMTP id B6E8F37B401 for ; Fri, 26 Jan 2001 06:05:24 -0800 (PST) Received: from wkst ([209.16.228.145]) by virtual.sysadmin-inc.com (8.9.1/8.9.1) with SMTP id JAA16890 for ; Fri, 26 Jan 2001 09:05:27 -0500 Reply-To: From: "Peter Brezny" To: Subject: dns; default primary zone files get hard coded origin's on secondary. Date: Fri, 26 Jan 2001 09:04:37 -0800 Message-ID: <002201c087ba$10c533c0$46010a0a@sysadmininc.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I recently revamped a lot of my zone files, consolidating several into generic files since many of our domains have mail, dns, and web hosting on the same servers. This works fine on the primary server, substituting an @ symbol in the zone file for the origin of the zone listed in the .conf file. However, on the secondary The origin in the zone file is being hard coded to what ever the server looked up first, which of course wrecks the information for any subsiquent zone that uses the same default zone file. example: on the primary @ in soa etc... in ns ns1.domain.com in a ip.of.domain.com mail in a ip.of.mail.com The secondary reports this: $ORIGIN org. in soa etc... in ns ns1.domain.com in a ip.of.domain.com $ORIGIN first.domain.that.got.looked.up mail in a ip.of.mail.com Is there a way to get around this? my primary server is running bind 8.2.3-T6b and the slave server is running bind 8.1.2 Thanks in advance for your help. Peter Brezny SysAdmin Services Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jan 26 8:44:22 2001 Delivered-To: freebsd-net@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id 4D09737B69B for ; Fri, 26 Jan 2001 08:44:04 -0800 (PST) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id JAA03787; Fri, 26 Jan 2001 09:44:02 -0700 (MST) Date: Fri, 26 Jan 2001 09:44:02 -0700 (MST) From: Nick Rogness To: Peter Brezny Cc: freebsd-net@freebsd.org Subject: Re: dns; default primary zone files get hard coded origin's on secondary. In-Reply-To: <002201c087ba$10c533c0$46010a0a@sysadmininc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 26 Jan 2001, Peter Brezny wrote: > I recently revamped a lot of my zone files, consolidating several into > generic files since many of our domains have mail, dns, and web hosting on > the same servers. This works fine on the primary server, substituting an @ > symbol in the zone file for the origin of the zone listed in the .conf file. > However, on the secondary The origin in the zone file is being hard coded > to what ever the server looked up first, which of course wrecks the > information for any subsiquent zone that uses the same default zone file. Let me see if I understand you correctly. In /etc/namedb/named.conf you have: zone "abc.com" { type master; file "generic_file.db"; } zone "bcd.com" { type master; file "generic_file.db"; } Am I correct in my assumption? Nick Rogness - Keep on routing in a Free World... "FreeBSD: The Power to Serve " To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jan 26 12:23:13 2001 Delivered-To: freebsd-net@freebsd.org Received: from blount.mail.mindspring.net (blount.mail.mindspring.net [207.69.200.226]) by hub.freebsd.org (Postfix) with ESMTP id 0103337B400; Fri, 26 Jan 2001 12:22:43 -0800 (PST) Received: from timothyr.net (user-vcaup29.dsl.mindspring.com [216.175.100.73]) by blount.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id PAA14210; Fri, 26 Jan 2001 15:22:41 -0500 (EST) Received: from sloth (sloth [192.168.1.5]) by timothyr.net (8.11.1/8.11.1) with ESMTP id f0QKMco24396; Fri, 26 Jan 2001 12:22:39 -0800 (PST) (envelope-from timothyr@timothyr.com) From: "Timothy L. Robertson" To: , Subject: PPPoE Connection Hangs Sometimes Date: Fri, 26 Jan 2001 12:22:30 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Everyone, I use PPPoE to connect to Mindspring over ADSL. Sometimes Mindspring drops the connection for whatever reason, so I have a script in ppp.linkup that pings several sites periodically, and if they all go down kills my ppp process and starts a new one. This works great most of the time, but sometimes when ppp tries to connect again it gets stuck. Here's what the log looks like: Jan 25 21:15:29 scarlet ppp[18006]: Phase: Using interface: tun0 Jan 25 21:15:29 scarlet ppp[18006]: Phase: deflink: Created in closed state Jan 25 21:15:29 scarlet ppp[18006]: tun0: Command: pppoe: set device PPPoE:xl0 Jan 25 21:15:29 scarlet ppp[18006]: tun0: Command: pppoe: set mru 2048 Jan 25 21:15:29 scarlet ppp[18006]: tun0: Command: pppoe: set mtu 1492 Jan 25 21:15:29 scarlet ppp[18006]: tun0: Command: pppoe: set speed sync Jan 25 21:15:29 scarlet ppp[18006]: tun0: Command: pppoe: set cd 5 Jan 25 21:15:29 scarlet ppp[18006]: tun0: Command: pppoe: set redial 0 0 Jan 25 21:15:29 scarlet ppp[18006]: tun0: Command: pppoe: set reconnect 10 99 Jan 25 21:15:29 scarlet ppp[18006]: tun0: Command: pppoe: set dial Jan 25 21:15:29 scarlet ppp[18006]: tun0: Command: pppoe: set login Jan 25 21:15:29 scarlet ppp[18006]: tun0: Command: pppoe: set authname tlrobertson@mindspring.com Jan 25 21:15:29 scarlet ppp[18006]: tun0: Command: pppoe: set authkey ******** Jan 25 21:15:29 scarlet ppp[18006]: tun0: Command: pppoe: set timeout 0 Jan 25 21:15:29 scarlet ppp[18006]: tun0: Command: pppoe: set ifaddr 0 0 255.255.255.255 255.255.255.255 Jan 25 21:15:29 scarlet ppp[18006]: tun0: Command: pppoe: delete ALL Jan 25 21:15:29 scarlet ppp[18006]: tun0: Command: pppoe: add 0 0 HISADDR Jan 25 21:15:29 scarlet ppp[18007]: tun0: Phase: PPP Started (ddial mode). Jan 25 21:15:29 scarlet ppp[18007]: tun0: Phase: bundle: Establish Jan 25 21:15:29 scarlet ppp[18007]: tun0: Phase: deflink: closed -> opening Jan 25 21:15:29 scarlet ppp[18007]: tun0: Warning: deflink: Reducing MRU to 1492 Jan 25 21:15:29 scarlet ppp[18007]: tun0: Phase: deflink: Connected! Jan 25 21:15:29 scarlet ppp[18007]: tun0: Phase: deflink: opening -> dial Jan 25 21:15:29 scarlet ppp[18007]: tun0: Phase: deflink: dial -> carrier Jan 25 21:15:34 scarlet ppp[18007]: tun0: Phase: deflink: Disconnected! Jan 25 21:15:34 scarlet ppp[18007]: tun0: Phase: deflink: carrier -> hangup Jan 25 21:15:34 scarlet ppp[18007]: tun0: Phase: deflink: Connect time: 5 secs: 0 octets in, 0 octets out Jan 25 21:15:34 scarlet ppp[18007]: tun0: Phase: deflink: : 0 packets in, 0 packets out Jan 25 21:15:34 scarlet ppp[18007]: tun0: Phase: total 0 bytes/sec, peak 0 bytes/sec on Thu Jan 25 21:15:34 2001 Jan 25 21:15:34 scarlet ppp[18007]: tun0: Phase: deflink: hangup -> opening and then nothing more. This usually happens when I'm away from my machiine, I come home, reconnect and everything works fine for a few days, until it happens again. How can i check for this condition and have ppp start over when it occurs, or even better avoid it all together? Any help appriciated. TIA, -Tim timothyr@timothyr.com Here are some other relevant files: scarlet:/etc/ppp 521$ more ppp.linkup MYADDR: !bg /etc/ppp/ppp.linkup.sh scarlet:/etc/ppp 522$ more ppp.linkup.sh #!/bin/sh ddup --host timothyr.dyndns.org /bin/sh /etc/snortstart.sh /usr/local/bin/fetchmail -f /etc/mail/fetchmail.rc -d 60 /etc/ppp/nettest.sh & scarlet:/etc/ppp 523$ more nettest.sh #! /usr/local/bin/bash count=1 while [ $count -ne 0 ]; do { sleep 30 count=0 [ -n "$(ping -c 1 -q mindspring.com | grep ", 0% packet loss")" ] && let count=$count+1 [ -n "$(ping -c 1 -q yahoo.com | grep ", 0% packet loss")" ] && let count=$count+1 [ -n "$(ping -c 1 -q salon.com | grep ", 0% packet loss")" ] && let count=$count+1 [ -n "$(ping -c 1 -q socrates.berkeley.edu | grep ", 0% packet loss")" ] && let count=$count+1 [ -n "$(ping -c 1 -q sgi.com | grep ", 0% packet loss")" ] && let count=$count+1 #echo $count }; done; /etc/ppp/reconnect.sh scarlet:/etc/ppp 524$ more reconnect.sh #!/usr/local/bin/bash kill -9 `cat /var/run/tun0.pid` /usr/sbin/ppp -quiet -ddial pppoe and here's a successful connection for reference: Jan 26 11:02:07 scarlet ppp[19109]: Phase: Using interface: tun0 Jan 26 11:02:07 scarlet ppp[19109]: Phase: deflink: Created in closed state Jan 26 11:02:07 scarlet ppp[19109]: tun0: Command: pppoe: set device PPPoE:xl0 Jan 26 11:02:07 scarlet ppp[19109]: tun0: Command: pppoe: set mru 2048 Jan 26 11:02:07 scarlet ppp[19109]: tun0: Command: pppoe: set mtu 1492 Jan 26 11:02:07 scarlet ppp[19109]: tun0: Command: pppoe: set speed sync Jan 26 11:02:07 scarlet ppp[19109]: tun0: Command: pppoe: set cd 5 Jan 26 11:02:07 scarlet ppp[19109]: tun0: Command: pppoe: set redial 0 0 Jan 26 11:02:07 scarlet ppp[19109]: tun0: Command: pppoe: set reconnect 10 99 Jan 26 11:02:07 scarlet ppp[19109]: tun0: Command: pppoe: set dial Jan 26 11:02:07 scarlet ppp[19109]: tun0: Command: pppoe: set login Jan 26 11:02:07 scarlet ppp[19109]: tun0: Command: pppoe: set authname tlrobertson@mindspring.com Jan 26 11:02:07 scarlet ppp[19109]: tun0: Command: pppoe: set authkey ******** Jan 26 11:02:07 scarlet ppp[19109]: tun0: Command: pppoe: set timeout 0 Jan 26 11:02:07 scarlet ppp[19109]: tun0: Command: pppoe: set ifaddr 0 0 255.255.255.255 255.255.255.255 Jan 26 11:02:07 scarlet ppp[19109]: tun0: Command: pppoe: delete ALL Jan 26 11:02:07 scarlet ppp[19109]: tun0: Command: pppoe: add 0 0 HISADDR Jan 26 11:02:07 scarlet ppp[19110]: tun0: Phase: PPP Started (ddial mode). Jan 26 11:02:07 scarlet ppp[19110]: tun0: Phase: bundle: Establish Jan 26 11:02:07 scarlet ppp[19110]: tun0: Phase: deflink: closed -> opening Jan 26 11:02:07 scarlet ppp[19110]: tun0: Warning: deflink: Reducing MRU to 1492 Jan 26 11:02:07 scarlet ppp[19110]: tun0: Phase: deflink: Connected! Jan 26 11:02:07 scarlet ppp[19110]: tun0: Phase: deflink: opening -> dial Jan 26 11:02:07 scarlet ppp[19110]: tun0: Phase: deflink: dial -> carrier Jan 26 11:02:09 scarlet ppp[19110]: tun0: Phase: Received NGM_PPPOE_SUCCESS (hook "tun0") Jan 26 11:02:09 scarlet ppp[19110]: tun0: Phase: deflink: carrier -> login Jan 26 11:02:09 scarlet ppp[19110]: tun0: Phase: deflink: login -> lcp Jan 26 11:02:09 scarlet ppp[19110]: tun0: LCP: FSM: Using "deflink" as a transport Jan 26 11:02:09 scarlet ppp[19110]: tun0: LCP: deflink: State change Initial --> Closed Jan 26 11:02:09 scarlet ppp[19110]: tun0: LCP: deflink: State change Closed --> Stopped Jan 26 11:02:09 scarlet ppp[19110]: tun0: LCP: deflink: RecvConfigReq(220) state = Stopped Jan 26 11:02:09 scarlet ppp[19110]: tun0: LCP: MRU[4] 1492 Jan 26 11:02:09 scarlet ppp[19110]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) Jan 26 11:02:09 scarlet ppp[19110]: tun0: LCP: MAGICNUM[6] 0x0027c326 Jan 26 11:02:09 scarlet ppp[19110]: tun0: LCP: deflink: SendConfigReq(1) state = Stopped Jan 26 11:02:09 scarlet ppp[19110]: tun0: LCP: MRU[4] 1492 Jan 26 11:02:09 scarlet ppp[19110]: tun0: LCP: MAGICNUM[6] 0x895630a7 Jan 26 11:02:09 scarlet ppp[19110]: tun0: LCP: deflink: SendConfigAck(220) state = Stopped Jan 26 11:02:09 scarlet ppp[19110]: tun0: LCP: MRU[4] 1492 Jan 26 11:02:09 scarlet ppp[19110]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) Jan 26 11:02:09 scarlet ppp[19110]: tun0: LCP: MAGICNUM[6] 0x0027c326 Jan 26 11:02:09 scarlet ppp[19110]: tun0: LCP: deflink: LayerStart Jan 26 11:02:09 scarlet ppp[19110]: tun0: LCP: deflink: State change Stopped --> Ack-Sent Jan 26 11:02:09 scarlet ppp[19110]: tun0: LCP: deflink: RecvConfigAck(1) state = Ack-Sent Jan 26 11:02:09 scarlet ppp[19110]: tun0: LCP: deflink: State change Ack-Sent --> Opened Jan 26 11:02:09 scarlet ppp[19110]: tun0: LCP: deflink: LayerUp Jan 26 11:02:09 scarlet ppp[19110]: tun0: Phase: bundle: Authenticate Jan 26 11:02:09 scarlet ppp[19110]: tun0: Phase: deflink: his = PAP, mine = none Jan 26 11:02:09 scarlet ppp[19110]: tun0: Phase: Pap Output: tlrobertson@mindspring.com ******** Jan 26 11:02:11 scarlet ppp[19110]: tun0: Phase: Pap Input: SUCCESS () Jan 26 11:02:11 scarlet ppp[19110]: tun0: IPCP: Using trigger address 255.255.255.255 Jan 26 11:02:11 scarlet ppp[19110]: tun0: CCP: FSM: Using "deflink" as a transport Jan 26 11:02:11 scarlet ppp[19110]: tun0: CCP: deflink: State change Initial --> Closed Jan 26 11:02:11 scarlet ppp[19110]: tun0: CCP: deflink: LayerStart. Jan 26 11:02:11 scarlet ppp[19110]: tun0: CCP: MPPE: InitOptsOutput Jan 26 11:02:11 scarlet ppp[19110]: tun0: CCP: MPPE: MasterKey is invalid, MPPE is capable only with CHAP81 authentication Jan 26 11:02:11 scarlet ppp[19110]: tun0: CCP: deflink: SendConfigReq(1) state = Closed Jan 26 11:02:11 scarlet ppp[19110]: tun0: CCP: DEFLATE[4] win 15 Jan 26 11:02:11 scarlet ppp[19110]: tun0: CCP: PRED1[2] Jan 26 11:02:11 scarlet ppp[19110]: tun0: CCP: MPPE[6] value 0x00000000 Jan 26 11:02:11 scarlet ppp[19110]: tun0: CCP: deflink: State change Closed --> Req-Sent Jan 26 11:02:11 scarlet ppp[19110]: tun0: Phase: deflink: lcp -> open Jan 26 11:02:11 scarlet ppp[19110]: tun0: Phase: bundle: Network Jan 26 11:02:11 scarlet ppp[19110]: tun0: IPCP: FSM: Using "deflink" as a transport Jan 26 11:02:11 scarlet ppp[19110]: tun0: IPCP: deflink: State change Initial --> Closed Jan 26 11:02:11 scarlet ppp[19110]: tun0: IPCP: deflink: LayerStart. Jan 26 11:02:11 scarlet ppp[19110]: tun0: IPCP: deflink: SendConfigReq(1) state = Closed Jan 26 11:02:11 scarlet ppp[19110]: tun0: IPCP: IPADDR[6] 255.255.255.255 Jan 26 11:02:11 scarlet ppp[19110]: tun0: IPCP: COMPPROTO[6] 16 VJ slots with slot compression Jan 26 11:02:11 scarlet ppp[19110]: tun0: IPCP: deflink: State change Closed --> Req-Sent Jan 26 11:02:11 scarlet ppp[19110]: tun0: LCP: deflink: RecvEchoRequest(0) state = Opened Jan 26 11:02:11 scarlet ppp[19110]: tun0: LCP: deflink: SendEchoReply(0) state = Opened Jan 26 11:02:11 scarlet ppp[19110]: tun0: IPCP: deflink: RecvConfigReq(24) state = Req-Sent Jan 26 11:02:11 scarlet ppp[19110]: tun0: IPCP: IPADDR[6] 216.175.101.1 Jan 26 11:02:11 scarlet ppp[19110]: tun0: IPCP: deflink: SendConfigAck(24) state = Req-Sent Jan 26 11:02:11 scarlet ppp[19110]: tun0: IPCP: IPADDR[6] 216.175.101.1 Jan 26 11:02:11 scarlet ppp[19110]: tun0: IPCP: deflink: State change Req-Sent --> Ack-Sent Jan 26 11:02:11 scarlet ppp[19110]: tun0: LCP: deflink: RecvProtocolRej(221) state = Opened Jan 26 11:02:11 scarlet ppp[19110]: tun0: LCP: deflink: -- Protocol 0x80fd (Compression Control Protocol) was rejected! Jan 26 11:02:11 scarlet ppp[19110]: tun0: CCP: deflink: State change Req-Sent --> Stopped Jan 26 11:02:11 scarlet ppp[19110]: tun0: IPCP: deflink: RecvConfigRej(1) state = Ack-Sent Jan 26 11:02:11 scarlet ppp[19110]: tun0: IPCP: COMPPROTO[6] 16 VJ slots with slot compression Jan 26 11:02:11 scarlet ppp[19110]: tun0: IPCP: deflink: SendConfigReq(2) state = Ack-Sent Jan 26 11:02:11 scarlet ppp[19110]: tun0: IPCP: IPADDR[6] 255.255.255.255 Jan 26 11:02:12 scarlet ppp[19110]: tun0: IPCP: deflink: RecvConfigNak(2) state = Ack-Sent Jan 26 11:02:12 scarlet ppp[19110]: tun0: IPCP: IPADDR[6] 216.175.101.156 Jan 26 11:02:12 scarlet ppp[19110]: tun0: IPCP: IPADDR[6] changing address: 255.255.255.255 --> 216.175.101.156 Jan 26 11:02:12 scarlet ppp[19110]: tun0: IPCP: deflink: SendConfigReq(3) state = Ack-Sent Jan 26 11:02:12 scarlet ppp[19110]: tun0: IPCP: IPADDR[6] 216.175.101.156 Jan 26 11:02:12 scarlet ppp[19110]: tun0: IPCP: deflink: RecvConfigAck(3) state = Ack-Sent Jan 26 11:02:12 scarlet ppp[19110]: tun0: IPCP: deflink: State change Ack-Sent --> Opened Jan 26 11:02:12 scarlet ppp[19110]: tun0: IPCP: deflink: LayerUp. Jan 26 11:02:12 scarlet ppp[19110]: tun0: IPCP: myaddr 216.175.101.156 hisaddr = 216.175.101.1 Jan 26 11:02:12 scarlet ppp[19110]: tun0: Command: MYADDR: !bg /etc/ppp/ppp.linkup.sh Jan 26 11:02:12 scarlet ppp[19110]: tun0: LCP: deflink: RecvEchoRequest(0) state = Opened Jan 26 11:02:12 scarlet ppp[19110]: tun0: LCP: deflink: SendEchoReply(0) state = Opened To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Jan 27 1: 2:44 2001 Delivered-To: freebsd-net@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id B850337B6B3 for ; Sat, 27 Jan 2001 01:02:26 -0800 (PST) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id CAA10085 for ; Sat, 27 Jan 2001 02:02:25 -0700 (MST) Date: Sat, 27 Jan 2001 02:02:25 -0700 (MST) From: Nick Rogness To: freebsd-net@freebsd.org Subject: ipfw fwd Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Couple of comments on ipfw fwd. After playing around with the forward feature of ipfw, I ran into a couple of interesting things. First let me give you my test lab environment diagram: Internet | xl0 | 192.168.10.1 ----ed1---FreeBSD | fxp0 | 192.168.20.0/24 After adding the command: ipfw add 100 fwd 192.168.10.1 tcp from any to any 80 in via fxp0 I see no packet arrive at host 192.168.10.1. Do forwarded packets re-enter the firewall for a given outgoing interface? In this case ed1 ? Or are they somehow skipped and just routed out the interface after a match is made? After changing the above ipfw command to 'out via xl0' I start seeing incoming packets on the 192.168.10.1 host. Do IPFW Forward rules only apply to outgoing style rules? Nick Rogness - Keep on routing in a Free World... "FreeBSD: The Power to Serve " To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Jan 27 23: 3:17 2001 Delivered-To: freebsd-net@freebsd.org Received: from anakin.jestec.com (unknown [216.218.200.104]) by hub.freebsd.org (Postfix) with ESMTP id 93C7C37B402 for ; Sat, 27 Jan 2001 23:02:59 -0800 (PST) Received: from twopimped (cc502667-a.catv1.md.home.com [24.9.158.2]) by anakin.jestec.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com for ; Sat, 27 Jan 2001 23:05:31 -0800 From: "G. Jason Middleton" To: Subject: no buffer space available Date: Sun, 28 Jan 2001 02:05:08 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" 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) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a problem. I can telnet into my bsd box from the net and after a while it will just not let me in. It just drops right off the face of the earth. So when i actually try to ping something from the box after this happens i get an error as follows: ping: sendto: no buffer space avaialble. when i reboot everything works like it should. Got any ideas? Regards, G. Jason Middleton University of Maryland Baltimore County To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Jan 27 23:12:18 2001 Delivered-To: freebsd-net@freebsd.org Received: from VL-MS-MR003.sc1.videotron.ca (relais.videotron.ca [24.201.245.36]) by hub.freebsd.org (Postfix) with ESMTP id 754DC37B402 for ; Sat, 27 Jan 2001 23:12:00 -0800 (PST) Received: from jehovah ([24.201.144.31]) by VL-MS-MR003.sc1.videotron.ca (Netscape Messaging Server 4.15) with SMTP id G7V2NZ00.T14; Sun, 28 Jan 2001 02:11:59 -0500 Message-ID: <000f01c088f9$db5c08d0$1f90c918@jehovah> From: "Bosko Milekic" To: "G. Jason Middleton" , References: Subject: Re: no buffer space available Date: Sun, 28 Jan 2001 02:13:47 -0500 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 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does this happen regularly? Check `netstat -m' on the machine (you'll probably have to do it from the console) when this is happening. If it happens regularly, does anything specific happen that "helps reproduce it?" What version of FreeBSD are you running? -Bosko G. Jason Middleton wrote: > I have a problem. > I can telnet into my bsd box from the net and after a while it will just not > let me in. It just drops right off the face of the earth. So when i > actually try to ping something from the box after this happens i get an > error as follows: > > ping: sendto: no buffer space avaialble. > > > when i reboot everything works like it should. > > Got any ideas? > > Regards, > > G. Jason Middleton > University of Maryland Baltimore County To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message