From owner-freebsd-net Mon Jun 22 01:26:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA17910 for freebsd-net-outgoing; Mon, 22 Jun 1998 01:26:51 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from muswell.demon.co.uk (muswell.demon.co.uk [158.152.10.120]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA17873; Mon, 22 Jun 1998 01:26:37 -0700 (PDT) (envelope-from ruth@muswell.demon.co.uk) Received: (from ruth@localhost) by muswell.demon.co.uk (8.8.7/8.6.12) id IAA05135; Mon, 22 Jun 1998 08:46:15 +0100 (BST) Date: Mon, 22 Jun 1998 08:46:15 +0100 (BST) Message-Id: <199806220746.IAA05135@muswell.demon.co.uk> From: ruth moulton MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Jeremy Shaffner Cc: ruth moulton , freebsd-questions@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: connecting NT and FBSD via tcp/ip over ethernet In-Reply-To: References: <199806190819.JAA01172@muswell.demon.co.uk> X-Mailer: VM 6.22 under 19.15 XEmacs Lucid Disposition-notification-to: ruth@muswell.demon.co.uk Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jeremy, thanks for your reply, I'll remake the kernel and try tcpdump. > > on FBSD, the ifconfig command is > > ifconfig ed0 192.168.0.2 broadcast 255.255.255.0, > > giving > > ed0: flags=8863 mtu 1500 > > inet 192.168.0.1 netmask 0xffffff00 broadcast 255.255.255.0 > > > That doesn't seem to make much sense. I assume you want FBSD to be .1 > since you want to use it as a router. this was a typo!! - (I thought I'd checked what I'd typed so carely), the command I use is ifconfig ed0 192.168.0.1 broadcast 255.255.255.0, hence the results of ifconfig -a above! - thanks for pointing this out ruth -- ================================================ Ruth Moulton ruth@muswell.demon.co.uk Consultant 65 Tetherdown, London N.10 1NH, UK Tel:+44 181 883 5823 -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jun 22 06:31:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA29968 for freebsd-net-outgoing; Mon, 22 Jun 1998 06:31:08 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from sierrahill.com (sierrahill.com [207.8.11.162]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA29915; Mon, 22 Jun 1998 06:30:55 -0700 (PDT) (envelope-from rjoe@sierrahill.com) Received: (from rjoe@localhost) by sierrahill.com (8.8.7/8.8.7) id IAA05713; Mon, 22 Jun 1998 08:26:11 -0500 (CDT) (envelope-from rjoe) From: Joe Schwartz Message-Id: <199806221326.IAA05713@sierrahill.com> Subject: routing issue To: freebsd-net@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Date: Mon, 22 Jun 1998 08:26:11 -0500 (CDT) X-Mailer: ELM [version 2.4 PL23] 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 Folks, I want to use a FreeBSD machine as an Internet host with 2 ethernet cards. One card on an Internet subnet and the other card to service the internal private network. I'm having trouble getting it to route between the 2 interfaces. I have 3 machines setup for a test. machine a: ---------- ifconfig -a ep0: flags=8843 mtu 1500 inet 207.8.11.165 netmask 0xfffffff8 broadcast 207.8.11.167 ether 00:a0:24:11:c7:19 machine b: ---------- ifconfig -a ep0: flags=8843 mtu 1500 inet 207.8.11.166 netmask 0xfffffff8 broadcast 207.8.11.167 ether 00:10:4b:29:aa:a7 ep1: flags=8843 mtu 1500 inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 ether 00:10:4b:20:94:3a machine c: ---------- ifconfig -a ep0: flags=8843 mtu 1500 inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255 ether 00:10:4b:29:ab:da machine a's default route is set to 207.8.11.166 machine c's default route is set to 192.168.1.1 machine b has a route between the 2 interfaces by issuing: (but doesn't work) route add -net 192.168.1.0 207.8.11.166 0 machine b can ping machine a and c machine a can ping: 207.8.11.166 and 192.168.1.1 but not 192.168.1.2 machine c can ping: 192.168.1.1 and 207.8.11.166 but not 207.8.11.165 ============================================================== In /etc/rc.conf I've got: gateway_enable="YES" router_enable="YES" Machine b ISN'T routing between the 2 interfaces. Any suggestions? ----- I have several machines set up like this for clients working perfectly under FreeBSD 2.1.x. Does FreeBSD 2.2.x expect a subtle difference somehow? Is my 'route add' command incorrect? HELP!! THANKS, Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jun 22 06:46:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA02545 for freebsd-net-outgoing; Mon, 22 Jun 1998 06:46:43 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from itesec.hsc.fr (root@itesec.hsc.fr [192.70.106.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA02316; Mon, 22 Jun 1998 06:43:15 -0700 (PDT) (envelope-from pb@hsc.fr) Received: from mars.hsc.fr (mars.hsc.fr [192.70.106.44]) by itesec.hsc.fr (8.8.8/8.8.5/itesec-1.12-nospam) with ESMTP id PAA25197; Mon, 22 Jun 1998 15:42:47 +0200 (MET DST) Received: (from pb@localhost) by mars.hsc.fr (8.8.8/8.8.8/pb-19980526) id PAA09519; Mon, 22 Jun 1998 15:42:46 +0200 (CEST) (envelope-from pb) Message-ID: <19980622154245.A9508@mars.hsc.fr> Date: Mon, 22 Jun 1998 15:42:45 +0200 From: Pierre Beyssac To: Joe Schwartz , freebsd-net@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: routing issue References: <199806221326.IAA05713@sierrahill.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.8i In-Reply-To: <199806221326.IAA05713@sierrahill.com>; from Joe Schwartz on Mon, Jun 22, 1998 at 08:26:11AM -0500 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Jun 22, 1998 at 08:26:11AM -0500, Joe Schwartz wrote: > route add -net 192.168.1.0 207.8.11.166 0 This is wrong. The use of metric as a trailing integer is deprecated, it's interpreted as a netmask instead. Try this instead: route add -net 192.168.1.0 207.8.11.166 -- Pierre.Beyssac@hsc.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jun 22 08:52:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA21601 for freebsd-net-outgoing; Mon, 22 Jun 1998 08:52:25 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from tera.bctel.net (tera.bctel.net [204.174.64.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA21592 for ; Mon, 22 Jun 1998 08:52:21 -0700 (PDT) (envelope-from jim_lemieux@bctel.com) Received: (from nobody@localhost) by tera.bctel.net (8.8.8/8.8.8) id IAA09685 for ; Mon, 22 Jun 1998 08:48:48 -0700 (PDT) Received: from gargoyle.bctel.com(192.197.174.178) by tera.bctel.net via smap (V2.0) id xma009650; Mon, 22 Jun 98 08:48:39 -0700 Received: from bctel.com ([142.174.51.12]) by gargoyle.bctel.com (Netscape Messaging Server 3.52) with ESMTP id AAA4E04 for ; Mon, 22 Jun 1998 08:46:23 -0700 Message-ID: <358E7D62.B47F5E53@bctel.com> Date: Mon, 22 Jun 1998 08:50:59 -0700 From: "Jim Lemieux" X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-net@FreeBSD.ORG Subject: FreeBSD X.25 support Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello: I'm looking for some sort of X.25 networking support in FreeBSD...I am currently running 2.2.6 and looking in the LINT file I see that some support was once avail...excerpt from /usr/src/sys/i386/conf/LINT... # These are currently broken and are no longer shipped due to lack # of interest. #options CCITT #X.25 network layer #options ISO #options TPIP #ISO TP class 4 over IP #options TPCONS #ISO TP class 0 over X.25 #options LLC #X.25 link layer for Ethernets #options HDLC #X.25 link layer for serial lines #options EON #ISO CLNP over IP #options NSIP #XNS over IP Does anybody know at what release this support and the associated files were last provided in? Thanks, Jim Lemieux To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jun 22 11:46:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA26011 for freebsd-net-outgoing; Mon, 22 Jun 1998 11:46:04 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25919 for ; Mon, 22 Jun 1998 11:45:36 -0700 (PDT) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id OAA02874; Mon, 22 Jun 1998 14:39:23 -0400 (EDT) Date: Mon, 22 Jun 1998 14:45:30 -0400 (EDT) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: Jim Lemieux cc: freebsd-net@FreeBSD.ORG Subject: Re: FreeBSD X.25 support In-Reply-To: <358E7D62.B47F5E53@bctel.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 Mon, 22 Jun 1998, Jim Lemieux wrote: > Does anybody know at what release this support and the associated > files were last provided in? I believe my 2.0-ALPHA CD has a working copy. Not that I ever tried them but I believe 2.0 was before the decision to rip them out due to bit rot. Chris -- "Linux... The choice of a GNUtered generation." ===================================| Open Systems Networking And Consulting. FreeBSD 2.2.6 is available now! | Phone: 316-326-6800 -----------------------------------| 1402 N. Washington, Wellington, KS-67152 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting-Network Engineering-Security ===================================| http://open-systems.net -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= =BBjp -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jun 22 12:19:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01879 for freebsd-net-outgoing; Mon, 22 Jun 1998 12:19:07 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from ns.webwizard.net.mx (mexcom.net.mx [207.249.162.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01835; Mon, 22 Jun 1998 12:18:54 -0700 (PDT) (envelope-from eculp@webwizard.org.mx) Received: from sunix (eculp@sunix.mexcom.net [206.103.64.3]) by ns.webwizard.net.mx (8.8.8/8.8.7) with SMTP id OAA03407; Mon, 22 Jun 1998 14:17:57 -0500 (CDT) Message-ID: <358EA148.6513CABD@webwizard.org.mx> Date: Mon, 22 Jun 1998 13:24:08 -0500 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.0.14 i586) MIME-Version: 1.0 To: Joe Schwartz CC: freebsd-net@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: [Fwd: Re: routing issue] Content-Type: multipart/mixed; boundary="------------14049ECB962959A7A7BB842" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. --------------14049ECB962959A7A7BB842 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I screwed up on my email configuration. Message never got out. sorry, Hope it's still useful. ed --------------14049ECB962959A7A7BB842 Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-ID: <358E65D7.7A926B2B@mexcom.net> Date: Mon, 22 Jun 1998 09:10:31 -0500 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.0.14 i586) MIME-Version: 1.0 To: Joe Schwartz CC: freebsd-net@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: routing issue References: <199806221326.IAA05713@sierrahill.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit think that you need natd and ipfw on the gateway machine. first in your kernel config file add something like: options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about options IPDIVERT #divert sockets options "IPFIREWALL_VERBOSE_LIMIT=100" #limit verbosity options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default recompile edit rc.conf something like this: firewall_enable="YES" # Set to YES to enable firewall functionality firewall_type="open" # Firewall type (see /etc/rc.firewall) firewall_quiet="NO" # Set to YES to suppress rule display natd_enable="YES" # Enable natd (if firewall_enable == YES). natd_interface="ep0" # Public interface to use with natd. natd_flags="-v -s -m -u " # Additional flags for natd. the up to date rc.firewall file seems to work fine I did move the natd inicialzation in rc.network to the begining of ipfw it may not have been necessary but since it works, I haven't fixed it. The problem was that natd didn't start. (Don't forget to comment out the orginal natd inicialization) You might want to do this if natd doesn't start after reboot. ps -ax|grep natd. You can start it manually if necessary and everything should work. # cut and paste from rc.network # Initialize IP filtering using ipfw echo -n "natd repositioned in rc.network" natd -v -s -m -u -n ep0 # test and fix. Next line is part of original file. /sbin/ipfw -q flush > /dev/null 2>&1 By this time you should be recompiled and ready for a reboot:-) Don't worry, if I forgot something your machine won't work :-) provecho ed Joe Schwartz wrote: > > Folks, > > I want to use a FreeBSD machine as an Internet host with 2 > ethernet cards. One card on an Internet subnet and the other > card to service the internal private network. > > I'm having trouble getting it to route between the 2 interfaces. > > I have 3 machines setup for a test. > > machine a: > ---------- > ifconfig -a > ep0: flags=8843 mtu 1500 > inet 207.8.11.165 netmask 0xfffffff8 broadcast 207.8.11.167 > ether 00:a0:24:11:c7:19 > > machine b: > ---------- > ifconfig -a > ep0: flags=8843 mtu 1500 > inet 207.8.11.166 netmask 0xfffffff8 broadcast 207.8.11.167 > ether 00:10:4b:29:aa:a7 > ep1: flags=8843 mtu 1500 > inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 > ether 00:10:4b:20:94:3a > > machine c: > ---------- > ifconfig -a > ep0: flags=8843 mtu 1500 > inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255 > ether 00:10:4b:29:ab:da > > machine a's default route is set to 207.8.11.166 > machine c's default route is set to 192.168.1.1 > > machine b has a route between the 2 interfaces by issuing: (but doesn't work) > > route add -net 192.168.1.0 207.8.11.166 0 > > machine b can ping machine a and c > > machine a can ping: > 207.8.11.166 and 192.168.1.1 but not 192.168.1.2 > > machine c can ping: > 192.168.1.1 and 207.8.11.166 but not 207.8.11.165 > > ============================================================== > > In /etc/rc.conf I've got: > > gateway_enable="YES" > router_enable="YES" > > Machine b ISN'T routing between the 2 interfaces. Any suggestions? > ----- > I have several machines set up like this for clients working perfectly > under FreeBSD 2.1.x. > > Does FreeBSD 2.2.x expect a subtle difference somehow? Is my 'route add' > command incorrect? > > HELP!! > THANKS, > > Joe > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message --------------14049ECB962959A7A7BB842-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jun 22 22:54:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02737 for freebsd-net-outgoing; Mon, 22 Jun 1998 22:54:28 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from ha1.rdc1.sdca.home.com (siteadm@ha1.rdc1.sdca.home.com [24.0.3.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02721; Mon, 22 Jun 1998 22:54:22 -0700 (PDT) (envelope-from kahn@home.com) Received: from ERIN.UNET.TM ([24.0.171.37]) by ha1.rdc1.sdca.home.com (Netscape Mail Server v2.02) with SMTP id AAA8311; Mon, 22 Jun 1998 22:45:52 -0700 Message-ID: <004201bd9e6a$73288800$4800a8c0@ERIN.UNET.TM> From: "Kahn" To: "Joe Schwartz" , , Subject: Re: routing issue Date: Mon, 22 Jun 1998 22:47:42 -0700 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 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org You cannot route the class B of 192.168.xxx.xxx, However you can use natd to run as an invisable proxie. The only problem is if you use a program like ICQ on one of the clients, you will have to add in a socks 5 proxie to. Erin ---------------------------------------------------------------------------- ------------ We are Intel. Division is futile. You will be approximated. ---------------------------------------------------------------------------- ------------ -----Original Message----- From: Joe Schwartz To: freebsd-net@freebsd.org ; freebsd-questions@freebsd.org Date: Monday, June 22, 1998 7:15 AM Subject: routing issue > >Folks, > >I want to use a FreeBSD machine as an Internet host with 2 >ethernet cards. One card on an Internet subnet and the other >card to service the internal private network. > >I'm having trouble getting it to route between the 2 interfaces. > > >I have 3 machines setup for a test. > >machine a: >---------- >ifconfig -a >ep0: flags=8843 mtu 1500 > inet 207.8.11.165 netmask 0xfffffff8 broadcast 207.8.11.167 > ether 00:a0:24:11:c7:19 > > >machine b: >---------- >ifconfig -a >ep0: flags=8843 mtu 1500 > inet 207.8.11.166 netmask 0xfffffff8 broadcast 207.8.11.167 > ether 00:10:4b:29:aa:a7 >ep1: flags=8843 mtu 1500 > inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 > ether 00:10:4b:20:94:3a > >machine c: >---------- >ifconfig -a >ep0: flags=8843 mtu 1500 > inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255 > ether 00:10:4b:29:ab:da > > > >machine a's default route is set to 207.8.11.166 >machine c's default route is set to 192.168.1.1 > >machine b has a route between the 2 interfaces by issuing: (but doesn't work) > >route add -net 192.168.1.0 207.8.11.166 0 > >machine b can ping machine a and c > >machine a can ping: >207.8.11.166 and 192.168.1.1 but not 192.168.1.2 > >machine c can ping: >192.168.1.1 and 207.8.11.166 but not 207.8.11.165 > >============================================================== > >In /etc/rc.conf I've got: > >gateway_enable="YES" >router_enable="YES" > >Machine b ISN'T routing between the 2 interfaces. Any suggestions? > ----- >I have several machines set up like this for clients working perfectly >under FreeBSD 2.1.x. > >Does FreeBSD 2.2.x expect a subtle difference somehow? Is my 'route add' >command incorrect? > >HELP!! >THANKS, > >Joe > >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 Jun 23 01:36:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA21548 for freebsd-net-outgoing; Tue, 23 Jun 1998 01:36:18 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from arthur.axion.bt.co.uk (arthur.axion.bt.co.uk [132.146.5.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA21533 for ; Tue, 23 Jun 1998 01:36:09 -0700 (PDT) (envelope-from graeme.brown@bt-sys.bt.co.uk) Received: from rambo (actually rambo.futures.bt.co.uk) by arthur.axion.bt.co.uk (PP) with SMTP; Tue, 23 Jun 1998 09:32:59 +0100 Received: from maczebedee (actually macsmtp) by rambo with SMTP (PP); Tue, 23 Jun 1998 09:33:09 +0100 Message-ID: Date: 23 Jun 1998 09:32:27 +0100 From: Graeme Brown Subject: RE: Looking for FreeBSD version of mrouted-3.8 (DVMRP) To: "Gregory P. Smith" Cc: "FreeBSD-Net (FreeBSD.Org) List" X-Mailer: Mail*Link SMTP for Quarterdeck Mail; Version 4.0.0 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greg thanks for info. I tried mrouted-3.8.2 on a FreeBSD box interworking to a CISCO router running PIM-SM but could not get mrouted-3.8.2 to prune even though I explicitly put "pruning on" in /etc/mrouted.conf. Graeme _______________________________________________________________________________ To: Graeme Brown From: Gregory P. Smith on Mon, Jun 22, 1998 6:59 pm Subject: Re: Looking for FreeBSD version of mrouted-3.8 (DVMRP) RFC Header:Received: by maczebedee with ADMIN;22 Jun 1998 18:58:48 +0100 Received: from dent.axion.bt.co.uk by rambo with SMTP (PP); Mon, 22 Jun 1998 19:00:32 +0100 Received: from ryouko.nas.nasa.gov by dent.axion.bt.co.uk (PP) with ESMTP; Mon, 22 Jun 1998 18:57:48 +0100 Received: from ryouko.nas.nasa.gov (localhost [127.0.0.1]) by ryouko.nas.nasa.gov (8.8.7/NAS8.8.7) with ESMTP id KAA14819 for ; Mon, 22 Jun 1998 10:57:31 -0700 (PDT) Message-Id: <199806221757.KAA14819@ryouko.nas.nasa.gov> To: Graeme Brown Subject: Re: Looking for FreeBSD version of mrouted-3.8 (DVMRP) In-reply-to: Your message of "19 Jun 1998 11:53:24 BST." Date: Mon, 22 Jun 1998 10:57:30 -0700 From: "Gregory P. Smith" > Dear List > > Where can I find a pruning version of DVMRP (mrouted) for FreeBSD 2.2.6 ? I > think this means I need mrouted-3.8 either binary or source distribution. ftp://ftp.parc.xerox.com/pub/net-research/ipmulti 3.9-beta3 (in the beta-test subdirectory) is the latest and has been working well for me. All current versions are kept on this site. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jun 23 05:41:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA04856 for freebsd-net-outgoing; Tue, 23 Jun 1998 05:41:22 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (billf@hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA04817; Tue, 23 Jun 1998 05:41:13 -0700 (PDT) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA038865667; Tue, 23 Jun 1998 08:41:07 -0400 Date: Tue, 23 Jun 1998 08:41:06 -0400 (EDT) From: Bill Fumerola Cc: freebsd-net@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: routing issue In-Reply-To: <004201bd9e6a$73288800$4800a8c0@ERIN.UNET.TM> 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 As I sit here on my Window(ugh) machine I am running ICQ without any problems. I run natd, and no other proxy. I've told it I sit behind an unknown firewall which may force it to use TCP. Regardless, it works for me. On Mon, 22 Jun 1998, Kahn wrote: > You cannot route the class B of 192.168.xxx.xxx, However you can use natd to > run as an invisable proxie. The only problem is if you use a program like > ICQ on one of the clients, you will have to add in a socks 5 proxie to. bill fumerola (root/billf)@chc-chimes.com computer horizons corp - www.computerhorizons.com ph:(248)641-1500 x107 / bill.fumerola@chc.fabrik.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jun 23 07:20:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA21087 for freebsd-net-outgoing; Tue, 23 Jun 1998 07:20:48 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from ha1.rdc1.sdca.home.com (siteadm@ha1.rdc1.sdca.home.com [24.0.3.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA21064; Tue, 23 Jun 1998 07:20:42 -0700 (PDT) (envelope-from kahn@home.com) Received: from ERIN.UNET.TM ([24.0.171.37]) by ha1.rdc1.sdca.home.com (Netscape Mail Server v2.02) with SMTP id AAA23781; Tue, 23 Jun 1998 07:20:34 -0700 Message-ID: <001c01bd9eb2$5b536040$4800a8c0@ERIN.UNET.TM> From: "Kahn" To: "Bill Fumerola" Cc: , Subject: Re: routing issue Date: Tue, 23 Jun 1998 07:20:45 -0700 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 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org But can people on the outside start a chat with you? Can you start one with them? Can they send you a message directly, with out going through the ICQ servers? These are all problems I've been having, But these are the only problems. Everything else works great, I only regret is not setting up the FreeBSD box sooner. Erin ---------------------------------------------------------------------------- ------------ We are Intel. Division is futile. You will be approximated. ---------------------------------------------------------------------------- ------------ -----Original Message----- From: Bill Fumerola Cc: freebsd-net@FreeBSD.ORG ; freebsd-questions@FreeBSD.ORG Date: Tuesday, June 23, 1998 7:07 AM Subject: Re: routing issue > >As I sit here on my Window(ugh) machine I am running ICQ without any >problems. I run natd, and no other proxy. I've told it I sit behind an >unknown firewall which may force it to use TCP. Regardless, it works for >me. > > > >On Mon, 22 Jun 1998, Kahn wrote: > >> You cannot route the class B of 192.168.xxx.xxx, However you can use natd to >> run as an invisable proxie. The only problem is if you use a program like >> ICQ on one of the clients, you will have to add in a socks 5 proxie to. > > > bill fumerola (root/billf)@chc-chimes.com > computer horizons corp - www.computerhorizons.com > ph:(248)641-1500 x107 / bill.fumerola@chc.fabrik.com > > >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 Jun 23 07:25:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22243 for freebsd-net-outgoing; Tue, 23 Jun 1998 07:25:52 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from ack.berkeley.edu (ack.Berkeley.EDU [128.32.206.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA22230 for ; Tue, 23 Jun 1998 07:25:50 -0700 (PDT) (envelope-from lindahl@ack.berkeley.edu) Received: (from lindahl@localhost) by ack.berkeley.edu (8.8.5/8.8.5) id HAA27759; Tue, 23 Jun 1998 07:25:43 -0700 (PDT) Date: Tue, 23 Jun 1998 07:25:43 -0700 (PDT) From: ken lindahl Message-Id: <199806231425.HAA27759@ack.berkeley.edu> To: graeme.brown@bt-sys.bt.co.uk Subject: RE: Looking for FreeBSD version of mrouted-3.8 (DVMRP) Cc: freebsd-net@FreeBSD.ORG Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hi, in most versions of IOS, ciscos do not maintain prune state when there are DVMRP neighbors present on a multi-access LAN. (i don't know if this description matches your instance, if not, please ignore my rantings.) i think this is related to the poison-reverse mechanism used in DVMRP to tell the upstream routers that there are downstream neighbors. ciscos don't maintain the DVMRP poison-reverse information, therefore they are not able to safely prune. (they may "cut off" downstream DVMRP neighbors that they've "forgotten" about.) so, ciscos won't prune in the presence of DVMRP neighbors on a multi-access LAN. i think i've been told that this has been fixed in 11.2(13) and later, also in 11.1CC(19) and later, though i haven't heard exactly how. i've seen the problem; i've not yet tested 11.2(13) to see if it is fixed. the one workaround that i know of is to tunnel between the cisco and the DVMRP router (mrouted or bay router, for example), making sure that the DVMRP router has disabled native (non-tunneled) multicast onto the shared LAN. ken lindahl uc berkeley On 23 Jun 1998 09:32:27, Graeme Brown wrote: >Greg > >thanks for info. I tried mrouted-3.8.2 on a FreeBSD box interworking to a >CISCO router running PIM-SM but could not get mrouted-3.8.2 to prune even >though >I explicitly put "pruning on" in /etc/mrouted.conf. > >Graeme To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jun 23 08:14:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01704 for freebsd-net-outgoing; Tue, 23 Jun 1998 08:14:02 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from tera.bctel.net (tera.bctel.net [204.174.64.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01685 for ; Tue, 23 Jun 1998 08:13:59 -0700 (PDT) (envelope-from jim_lemieux@bctel.com) Received: (from nobody@localhost) by tera.bctel.net (8.8.8/8.8.8) id IAA04006 for ; Tue, 23 Jun 1998 08:10:17 -0700 (PDT) Received: from gargoyle.bctel.com(192.197.174.178) by tera.bctel.net via smap (V2.0) id xma003908; Tue, 23 Jun 98 08:09:36 -0700 Received: from bctel.com ([142.174.51.12]) by gargoyle.bctel.com (Netscape Messaging Server 3.52) with ESMTP id AAAB1B for ; Tue, 23 Jun 1998 08:06:58 -0700 Message-ID: <358FC5B7.599DCA4A@bctel.com> Date: Tue, 23 Jun 1998 08:11:51 -0700 From: "Jim Lemieux" X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-net@FreeBSD.ORG Subject: Re: FreeBSD X.25 support References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org OK...does anybody know where I can find a copy of 2.0.x??? Open Systems Networking wrote: > On Mon, 22 Jun 1998, Jim Lemieux wrote: > > > Does anybody know at what release this support and the associated > > files were last provided in? > > I believe my 2.0-ALPHA CD has a working copy. Not that I ever tried them > but I believe 2.0 was before the decision to rip them out due to bit rot. > > Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jun 23 09:55:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19430 for freebsd-net-outgoing; Tue, 23 Jun 1998 09:55:56 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19410 for ; Tue, 23 Jun 1998 09:55:47 -0700 (PDT) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id MAA25985; Tue, 23 Jun 1998 12:49:13 -0400 (EDT) Date: Tue, 23 Jun 1998 12:55:19 -0400 (EDT) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: Jim Lemieux cc: freebsd-net@FreeBSD.ORG Subject: Re: FreeBSD X.25 support In-Reply-To: <358FC5B7.599DCA4A@bctel.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 Jun 1998, Jim Lemieux wrote: > OK...does anybody know where I can find a copy of 2.0.x??? You might install cvsup and use the stable-supfile but modify the "tag" line to read : tag=RELENG_2_0 instead of tag=RELENG_2_2 If that is a valid tag. If is and it works see if 2.0 has working x.25 if it does bump the tag to: RELENG_2_1_0 Ans see if 2.1 has x.25 support. I think 2.1 is about as far as it got with working support. I hope this helps and I hope those tags are valid. Chris -- "Linux... The choice of a GNUtered generation." ===================================| Open Systems Networking And Consulting. FreeBSD 2.2.6 is available now! | Phone: 316-326-6800 -----------------------------------| 1402 N. Washington, Wellington, KS-67152 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting-Network Engineering-Security ===================================| http://open-systems.net -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= =BBjp -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jun 23 13:04:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24876 for freebsd-net-outgoing; Tue, 23 Jun 1998 13:04:18 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from obie.softweyr.com ([204.68.178.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24810 for ; Tue, 23 Jun 1998 13:03:53 -0700 (PDT) (envelope-from wes@obie.softweyr.com) Received: (from wes@localhost) by obie.softweyr.com (8.8.8/8.8.8) id OAA10405; Tue, 23 Jun 1998 14:03:43 -0600 (MDT) (envelope-from wes) From: Wes Peters Message-Id: <199806232003.OAA10405@obie.softweyr.com> Subject: Re: routing issue In-Reply-To: <001c01bd9eb2$5b536040$4800a8c0@ERIN.UNET.TM> from Kahn at "Jun 23, 98 07:20:45 am" To: kahn@home.com (Kahn) Date: Tue, 23 Jun 1998 14:03:43 -0600 (MDT) Cc: net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (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 > But can people on the outside start a chat with you? Can you start one with > them? Can they send you a message directly, with out going through the ICQ > servers? These are all problems I've been having, But these are the only > problems. Everything else works great, I only regret is not setting up the > FreeBSD box sooner. No, but you just can't do that using a private network. If you really need this capability, you will have to give each of your users a publicly available IP address, or have them remain logged into a server that has a public interface. That is whatPRIVATE networks are fore - remaining private. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jun 23 21:31:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22641 for freebsd-net-outgoing; Tue, 23 Jun 1998 21:31:41 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from roma.coe.ufrj.br (jonny@roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA22629 for ; Tue, 23 Jun 1998 21:31:35 -0700 (PDT) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id BAA20677; Wed, 24 Jun 1998 01:31:24 -0300 (EST) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199806240431.BAA20677@roma.coe.ufrj.br> Subject: Re: Looking for FreeBSD version of mrouted-3.8 (DVMRP) In-Reply-To: from Graeme Brown at "Jun 23, 98 09:32:27 am" To: graeme.brown@bt-sys.bt.co.uk (Graeme Brown) Date: Wed, 24 Jun 1998 01:31:24 -0300 (EST) Cc: greg@nas.nasa.gov, freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (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 #define quoting(Graeme Brown) // thanks for info. I tried mrouted-3.8.2 on a FreeBSD box interworking to a // CISCO router running PIM-SM but could not get mrouted-3.8.2 to prune even // though // I explicitly put "pruning on" in /etc/mrouted.conf. Take a try at mrouted-3.9beta3. I've made a port of it recently, but it has not yet been commited. Search at the PR database for PRs with mrouted in it. 3.9 fixes lots of bugs. I don't know why it hasn't yet been integrated. Being beta is not an explanation. The whole MBone is beta. :) Maybe you need the SNMP version of mrouted. I'm sorry, but 3.9 does not have snmp. I would love to monitor the tunnels' traffic, but life isn't that easy. BTW: IIRC, "on" is the default state of "prunning". :) // > Where can I find a pruning version of DVMRP (mrouted) for FreeBSD 2.2.6 ? I // > think this means I need mrouted-3.8 either binary or source distribution. // // ftp://ftp.parc.xerox.com/pub/net-research/ipmulti // // 3.9-beta3 (in the beta-test subdirectory) is the latest and has been // working well for me. All current versions are kept on this site. // // Greg Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jun 23 21:59:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA26993 for freebsd-net-outgoing; Tue, 23 Jun 1998 21:59:29 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from roma.coe.ufrj.br (jonny@roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA26952 for ; Tue, 23 Jun 1998 21:59:13 -0700 (PDT) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id BAA21338; Wed, 24 Jun 1998 01:57:46 -0300 (EST) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199806240457.BAA21338@roma.coe.ufrj.br> Subject: Re: FreeBSD and default IP Multicast support In-Reply-To: <199806240339.UAA24668@rah.star-gate.com> from Amancio Hasty at "Jun 23, 98 08:39:14 pm" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Wed, 24 Jun 1998 01:57:46 -0300 (EST) Cc: mbone@ISI.EDU, net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (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 CC:ing to net@freebsd.org, where this discussion should probably continue. #define quoting(Amancio Hasty) // Got curious as to what was the latest as to why our default kernels // are not being compile with IP Multicast enabled. Because 99% or more of the FreeBSD user community does not need it ? IMHO, I think that to understand what the MBone is and to setup a well understood tunnel is not easier than compile a new FreeBSD kernel. // Fortunately, in FreeBSD land is very easy to compile a kernel or You get my point... // to build ip_mroute_mod loadable kernel module. I've never heard of a ip_mrouted_mod loadable kernel module. If it's possible to have mrouting capability as a LKM, this could be available by default. Why is it not ? To avoid lamers building tunnels wihtout understanding what they are doing ? :) Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jun 23 22:40:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04558 for freebsd-net-outgoing; Tue, 23 Jun 1998 22:40:45 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA04429 for ; Tue, 23 Jun 1998 22:40:02 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id WAA00648; Tue, 23 Jun 1998 22:39:52 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199806240539.WAA00648@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Joao Carlos Mendes Luis cc: mbone@ISI.EDU, net@FreeBSD.ORG Subject: Re: FreeBSD and default IP Multicast support In-reply-to: Your message of "Wed, 24 Jun 1998 01:57:46 -0300." <199806240457.BAA21338@roma.coe.ufrj.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Jun 1998 22:39:52 -0700 From: Amancio Hasty Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org {hasty} pwd /usr/src/lkm/ip_mroute_mod {hasty} vi Makefile # $Id: Makefile,v 1.3 1997/02/22 12:48:12 peter Exp $ .PATH: ${.CURDIR}/../../sys/netinet KMOD= ip_mroute_mod SRCS= ip_mroute.c NOMAN= CFLAGS+= -DMROUTE_LKM -DMROUTING .include ---------------------------------------------------- So yes, there is an ip_mroute_mod, however I have never used it whenever I have needed ip multicast routing in one of my systems I just recompiled the kernel. Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jun 23 23:01:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA08111 for freebsd-net-outgoing; Tue, 23 Jun 1998 23:01:20 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from alpha.xerox.com (omega.Xerox.COM [13.1.64.95]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA08089 for ; Tue, 23 Jun 1998 23:01:04 -0700 (PDT) (envelope-from fenner@parc.xerox.com) Received: from mango.parc.xerox.com ([13.1.102.232]) by alpha.xerox.com with SMTP id <40908(1)>; Tue, 23 Jun 1998 23:00:14 PDT Received: (from fenner@localhost) by mango.parc.xerox.com (8.8.8/8.8.8) id XAA05423; Tue, 23 Jun 1998 23:00:09 -0700 (PDT) (envelope-from fenner) Date: Tue, 23 Jun 1998 23:00:09 PDT From: Bill Fenner Message-Id: <199806240600.XAA05423@mango.parc.xerox.com> To: graeme.brown@bt-sys.bt.co.uk, jonny@jonny.eng.br Subject: Re: Looking for FreeBSD version of mrouted-3.8 (DVMRP) Cc: freebsd-net@FreeBSD.ORG, greg@nas.nasa.gov In-Reply-To: <199806240431.BAA20677@roma.coe.ufrj.br> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >#define quoting(Graeme Brown) >// thanks for info. I tried mrouted-3.8.2 on a FreeBSD box interworking to a >// CISCO router running PIM-SM but could not get mrouted-3.8.2 to prune even >// though I explicitly put "pruning on" in /etc/mrouted.conf. This is most likely because Cisco doesn't implement DVMRP pruning on multi-access interfaces (like Ethernets). They only implement DVMRP pruning on DVMRP tunnels. You should let Cisco know if this limitation causes you problems. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jun 23 23:04:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA08607 for freebsd-net-outgoing; Tue, 23 Jun 1998 23:04:24 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from alpha.xerox.com (omega.Xerox.COM [13.1.64.95]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA08563 for ; Tue, 23 Jun 1998 23:04:10 -0700 (PDT) (envelope-from fenner@parc.xerox.com) Received: from mango.parc.xerox.com ([13.1.102.232]) by alpha.xerox.com with SMTP id <40911(1)>; Tue, 23 Jun 1998 23:03:34 PDT Received: from mango.parc.xerox.com (localhost [127.0.0.1]) by mango.parc.xerox.com (8.8.8/8.8.8) with ESMTP id XAA05451; Tue, 23 Jun 1998 23:03:32 -0700 (PDT) (envelope-from fenner@mango.parc.xerox.com) Message-Id: <199806240603.XAA05451@mango.parc.xerox.com> To: ken lindahl cc: graeme.brown@bt-sys.bt.co.uk, freebsd-net@FreeBSD.ORG Subject: Re: Looking for FreeBSD version of mrouted-3.8 (DVMRP) In-reply-to: Your message of "Tue, 23 Jun 1998 07:25:43 PDT." <199806231425.HAA27759@ack.berkeley.edu> Date: Tue, 23 Jun 1998 23:03:32 PDT From: Bill Fenner Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ken, You're confusing two problems: 1. IOS and flooding, which has to do with poison-reverse. This issue is covered at http://sandbox.parc.xerox.com/~fenner/mcast/flooding.html, and is indeed fixed in 11.1(??)CC and 11.2(?) and 11.3 . 2. IOS and DVMRP prune reception on multi-access interfaces, which is not yet fixed in any IOS release. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jun 23 23:09:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA09597 for freebsd-net-outgoing; Tue, 23 Jun 1998 23:09:25 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from home.rest.ru (root@home.rest.ru [195.58.8.205]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA09567 for ; Tue, 23 Jun 1998 23:09:13 -0700 (PDT) (envelope-from zal@rest.ru) Received: from rest.ru (zal.rest.ru [194.135.175.178]) by home.rest.ru (8.8.8/8.8.8) with ESMTP id MAA19666 for ; Wed, 24 Jun 1998 12:09:05 +0600 (ESS) (envelope-from zal@rest.ru) Message-ID: <359097AE.A7369084@rest.ru> Date: Wed, 24 Jun 1998 12:07:42 +0600 From: Aleksey Zvyagin Organization: REST Ltd. X-Mailer: Mozilla 4.05 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-net@FreeBSD.ORG Subject: IP accounting Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, All! Please, tell me, are the workgroup of FreeBSD planing to implement an IP accounting in FreeBSD OS ? I would very like to have an IP accounting (an accounting of IP traffic through an interface)! What does the version of FreeBSD implement this the feature? Thanks P.S. Please, to forward the mails to my Email address: zal@rest.ru -- Best regards, Aleksey Zvyagin, Ekaterinburg city, Ural region, Russia. E-mail: zal@rest.ru; UIN: 1381198; ntalk compatible: zal@zal.rest.ru; Mini-site: http://www.almaz.rest.ru ; HomePage: http://www.rest.ru/~zal/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jun 23 23:17:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA11054 for freebsd-net-outgoing; Tue, 23 Jun 1998 23:17:11 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from roma.coe.ufrj.br (jonny@roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA10942 for ; Tue, 23 Jun 1998 23:16:37 -0700 (PDT) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id DAA22380; Wed, 24 Jun 1998 03:16:24 -0300 (EST) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199806240616.DAA22380@roma.coe.ufrj.br> Subject: Re: FreeBSD and default IP Multicast support In-Reply-To: <199806240513.WAA00324@rah.star-gate.com> from Amancio Hasty at "Jun 23, 98 10:13:08 pm" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Wed, 24 Jun 1998 03:16:24 -0300 (EST) Cc: bmah@CA.Sandia.GOV, net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (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 #define quoting(Amancio Hasty) // The condition for multicast routing remains , that is to rebuild/install the // kernel with option MROUTING or build/load ip_mroute_mod . Did you note this in /usr/src/lkm/Makefile ? ... # $Id: Makefile,v 1.24.2.1 1997/11/06 13:03:53 msmith Exp $ # XXX present but broken: ip_mroute_mod mfs SUBDIR= atapi ccd cd9660 coff fdesc ibcs2 if_disc if_ppp if_sl if_tun \ ipfw joy kernfs linux msdos nfs nullfs \ pcic portal procfs qcam syscons umapfs # BROKEN due to lkm.h changes precluding > 1 module device per file. #wcd # XXX builds, but not useable with present design # fpu gnufpu union .include ... ip_mrouted_mod is broken, then ? Maybe that's why I've never seen it before. :) BTW: This is a very recent -stable. Jonny PS: If it's not broken, what about re-enabling it ? -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jun 23 23:26:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA13261 for freebsd-net-outgoing; Tue, 23 Jun 1998 23:26:37 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA13135 for ; Tue, 23 Jun 1998 23:25:53 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id XAA00952; Tue, 23 Jun 1998 23:25:42 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199806240625.XAA00952@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Joao Carlos Mendes Luis cc: bmah@CA.Sandia.GOV, net@FreeBSD.ORG Subject: Re: FreeBSD and default IP Multicast support In-reply-to: Your message of "Wed, 24 Jun 1998 03:16:24 -0300." <199806240616.DAA22380@roma.coe.ufrj.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Jun 1998 23:25:42 -0700 From: Amancio Hasty Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Yeap, I just noticed that :( Cheers, Amancio > #define quoting(Amancio Hasty) > // The condition for multicast routing remains , that is to rebuild/install the > // kernel with option MROUTING or build/load ip_mroute_mod . > > Did you note this in /usr/src/lkm/Makefile ? > > ... > # $Id: Makefile,v 1.24.2.1 1997/11/06 13:03:53 msmith Exp $ > > # XXX present but broken: ip_mroute_mod mfs > SUBDIR= atapi ccd cd9660 coff fdesc ibcs2 if_disc if_ppp if_sl if_tun \ > ipfw joy kernfs linux msdos nfs nullfs \ > pcic portal procfs qcam syscons umapfs > # BROKEN due to lkm.h changes precluding > 1 module device per file. > #wcd > > # XXX builds, but not useable with present design > # fpu gnufpu union > > .include > ... > > ip_mrouted_mod is broken, then ? Maybe that's why I've never > seen it before. :) > > BTW: This is a very recent -stable. > > Jonny > > PS: If it's not broken, what about re-enabling it ? > > -- > Joao Carlos Mendes Luis M.Sc. Student > jonny@jonny.eng.br Universidade Federal do Rio de Janeiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jun 24 01:27:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA06119 for freebsd-net-outgoing; Wed, 24 Jun 1998 01:27:04 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA06043 for ; Wed, 24 Jun 1998 01:26:39 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id QAA11269; Wed, 24 Jun 1998 16:25:52 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199806240825.QAA11269@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Open Systems Networking cc: Jim Lemieux , freebsd-net@FreeBSD.ORG Subject: Re: FreeBSD X.25 support In-reply-to: Your message of "Mon, 22 Jun 1998 14:45:30 -0400." Date: Wed, 24 Jun 1998 16:25:52 +0800 From: Peter Wemm Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Open Systems Networking wrote: > On Mon, 22 Jun 1998, Jim Lemieux wrote: > > > Does anybody know at what release this support and the associated > > files were last provided in? > > I believe my 2.0-ALPHA CD has a working copy. Not that I ever tried them > but I believe 2.0 was before the decision to rip them out due to bit rot. I believe "working" isn't exactly appropriate there. I'd suggest "compiling" would be better. Just because the code compiled doesn't mean that it worked or was useable. The X.25-proper stuff in the 4.4BSDLite[2] distributions under /usr/src/ contrib was never a part of FreeBSD. It has user space daemons and a lot of other stuff to make a complete complete X.25 system. It's a very long time since I looked at what was there, I'm not sure if it was an add-on to the netccitt stuff, or a replacement, or was 4.3-net2 level and not ported to 4.4Lite or something else. > Chris Cheers, -Peter -- Peter Wemm Netplex Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jun 24 02:50:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA19142 for freebsd-net-outgoing; Wed, 24 Jun 1998 02:50:00 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from home.rest.ru (root@home.rest.ru [195.58.8.205]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA19040 for ; Wed, 24 Jun 1998 02:49:01 -0700 (PDT) (envelope-from zal@rest.ru) Received: from rest.ru (zal.rest.ru [194.135.175.178]) by home.rest.ru (8.8.8/8.8.8) with ESMTP id PAA22380 for ; Wed, 24 Jun 1998 15:48:45 +0600 (ESS) (envelope-from zal@rest.ru) Message-ID: <3590CB2B.D45887A3@rest.ru> Date: Wed, 24 Jun 1998 15:47:23 +0600 From: Aleksey Zvyagin Organization: REST Ltd. X-Mailer: Mozilla 4.05 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-net@FreeBSD.ORG Subject: Re: IP accounting References: <359097AE.A7369084@rest.ru> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, All! I have written my previos letter but i mistake! Aleksey Zvyagin wrote: > > Hello, All! > > Please, tell me, are the workgroup of FreeBSD planing to implement an IP > accounting in FreeBSD OS ? I would very like to have an IP accounting > (an accounting of IP traffic through an interface)! What does the ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ I meant the IP traffic not through an interface! I meant the IP traffic like this: [IP destiantion address] [IP source address] [IP account packets] [IP received/transmited bytes] Sorry for mistake. But the question has stood here. Sorry for my English! > version of FreeBSD implement this the feature? > > Thanks > P.S. Please, to forward the mails to my Email address: zal@rest.ru -- Best regards, Aleksey Zvyagin, Ekaterinburg city, Ural region, Russia. E-mail: zal@rest.ru; UIN: 1381198; ntalk compatible: zal@zal.rest.ru; Mini-site: http://www.almaz.rest.ru ; HomePage: http://www.rest.ru/~zal/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jun 24 05:56:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA27106 for freebsd-net-outgoing; Wed, 24 Jun 1998 05:56:39 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from ktpk.dp.ua (ktpk.dp.ua [195.24.130.245]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA26869 for ; Wed, 24 Jun 1998 05:55:43 -0700 (PDT) (envelope-from os@ktpk.dp.ua) Received: from admin.dnepr.com (admin.dnepr.com [192.168.0.4]) by ktpk.dp.ua (8.8.7/8.8.7) with SMTP id PAA06460 for ; Wed, 24 Jun 1998 15:54:06 +0300 (EEST) (envelope-from os@ktpk.dp.ua) From: "Oleg Semyonov" To: Subject: FreeBSD+natd = tcp connection problems Date: Wed, 24 Jun 1998 15:59:17 +0400 Message-ID: <01bd9f67$83b3f9e0$0400a8c0@admin.dnepr.com> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all! I have some problems with tcp connections to some servers (ftp, irc and some others). My network configuration is quite simple: FreeBSD box is connected via slip (sl0) to IP provider (BSDI 2.1) and via NIC (de0) - to LAN (Win95/NT workstations). I have one real IP for FreeBSD box and private network 192.168.0.* for LAN. Natd is used for NAT, and all was ok, but... PROBLEM DESCRIPTION: When I trying to ftp to some servers from FreeBSD, in some cases I can enter login/password, and then see only first 230- line, and connection hangs. When using password in form of -user@ (disable that 230- messages) - all ok. For example, connect to ftp.kiae.su and ftp.hp.com was failed, connect to ftp.microsoft.com - ok. Then I found that we are using different MTU values on both sides of slip link (308 by defaul on BSDI, 507 by default on FreeBSD). I'm setting my side to 308. All ok, ftp with no problems. But only from FreeBSD box. Workstations from LAN via natd cannot ftp with same problem: 230- and stop. Workstations on LAN and de0 interface on FreeBSD are using MTU=1500. Next stage was to replace slip by ppp with mtu=1500. Effect was same: dropped connections from FreeBSD (and LAN too). Changing ppp0 MTU to 296-308 solves problem, but for FreeBSD box only. LAN cannot ftp to such servers. Irc connections from LAN hangs in same manner. What is the reason and what can I do? Does anybody help me? PS. Sorry for not so good English... --- Oleg Semyonov, the Head of IT Department of KTPK "Dnepr", Energodar, UA Internet mail: os@altavista.net, finger/talk: os@ktpk.dp.ua, ICQ:12900788 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jun 24 07:46:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA15620 for freebsd-net-outgoing; Wed, 24 Jun 1998 07:46:17 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from ibridge.iohk.com (root@ibridge.iohk.com [202.21.128.82]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA15599 for ; Wed, 24 Jun 1998 07:46:09 -0700 (PDT) (envelope-from percy@iohk.com) Received: from igate.iohk.com (root@igate.iohk.com [202.21.128.81]) by ibridge.iohk.com (8.8.5/8.8.5) with ESMTP id WAA15093 for ; Wed, 24 Jun 1998 22:48:44 +0800 (HKT) Received: from iohk.com (pm1p17.iohk.com [202.21.128.147]) by igate.iohk.com (8.8.5/8.8.5) with ESMTP id WAA27301 for ; Wed, 24 Jun 1998 22:48:43 +0800 (HKT) Message-ID: <2E0AF078.A65122B6@iohk.com> Date: Fri, 24 Jun 1994 22:40:56 +0800 From: Percy Cheng X-Mailer: Mozilla 4.03 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-net@FreeBSD.ORG Subject: Why? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just bind my network card to the system, but sadly it seems could not work properly, I'm using NE2000 compatible NIC, after I'd checked the startup log, I discovered that some devices had conflicted with the NIC's 0x300 address. After the system started, I triied to ping the local host, it seccessed, but when I try to ping the another machine on the lan, it failed........ Have anyone can tell me what;s wrong on it?? PErcy Cheng To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jun 24 08:16:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20450 for freebsd-net-outgoing; Wed, 24 Jun 1998 08:16:27 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from stennis.ca.sandia.gov (stennis.ca.sandia.gov [146.246.243.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA20364 for ; Wed, 24 Jun 1998 08:16:08 -0700 (PDT) (envelope-from bmah@stennis.ca.sandia.gov) Received: (from bmah@localhost) by stennis.ca.sandia.gov (8.9.0/8.9.0) id IAA26431; Wed, 24 Jun 1998 08:14:59 -0700 (PDT) Message-Id: <199806241514.IAA26431@stennis.ca.sandia.gov> X-Mailer: exmh version 2.0.2 2/24/98 To: Joao Carlos Mendes Luis Cc: hasty@rah.star-gate.com (Amancio Hasty), bmah@california.sandia.gov, net@FreeBSD.ORG Subject: Re: FreeBSD and default IP Multicast support In-Reply-To: Your message of "Wed, 24 Jun 1998 03:16:24 -0300." <199806240616.DAA22380@roma.coe.ufrj.br> From: bmah@CA.Sandia.GOV (Bruce A. Mah) Reply-To: bmah@CA.Sandia.GOV X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Url: http://www.ca.sandia.gov/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1645038762P"; micalg=pgp-md5; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Wed, 24 Jun 1998 08:14:59 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --==_Exmh_1645038762P Content-Type: text/plain; charset=us-ascii If memory serves me right, Joao Carlos Mendes Luis wrote: > ip_mrouted_mod is broken, then ? Maybe that's why I've never > seen it before. :) Well, at least I knew I wasn't missing anything either (but I'm only running 2.2.6-RELEASE). From reading the CVS tree, it looks like it's been this way since 2.1.0-RELEASE. So...it sounds like the answer to FAQ 10.15 ("How do I enable IP multicast support?") should read something like this: ----- Multicast host operations are fully supported in FreeBSD 2.0 and above by default. If you want your box to run as a multicast router, you will need to recompile your kernel with the MROUTING option and run mrouted. FreeBSD 2.2 and newer can run mrouted at boot time by setting mrouted_enable to "YES" in /etc/rc.conf. MBONE tools are available in their own ports category... ----- Should I file a PR on this? Bruce. --==_Exmh_1645038762P Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.2 iQCVAwUBNZEX8qjOOi0j7CY9AQGZlQP/Urp57TlnI5vggR2SEYJMPKEnhsicXG0r wclPFE+DfDZl9dDjnkOJSvJxGIJMW7SlAYeeMr7LQW/alwAf6/nF9iXWdC301DHu lyd+KxN6EmOyM76II+WI5DnxT89AgDQTndm7NAnrXjkXhVoOzJWd7NaSnsLhxsdK le/GlF0ssxo= =JlHl -----END PGP MESSAGE----- --==_Exmh_1645038762P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jun 24 10:19:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14398 for freebsd-net-outgoing; Wed, 24 Jun 1998 10:19:45 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from socrates.i-pi.com (socrates.i-pi.com [198.49.217.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14309 for ; Wed, 24 Jun 1998 10:19:08 -0700 (PDT) (envelope-from ingham@i-pi.com) Received: (from ingham@localhost) by socrates.i-pi.com (8.8.8/8.8.7) id LAA28574; Wed, 24 Jun 1998 11:15:02 -0600 (MDT) (envelope-from ingham) Message-ID: <19980624111501.45457@i-pi.com> Date: Wed, 24 Jun 1998 11:15:01 -0600 From: Kenneth Ingham To: Percy Cheng , freebsd-net@FreeBSD.ORG Subject: Re: Why? References: <2E0AF078.A65122B6@iohk.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <2E0AF078.A65122B6@iohk.com>; from Percy Cheng on Fri, Jun 24, 1994 at 10:40:56PM +0800 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org You'll have to resolve the conflict with 0x300 before the card will work properly. Kenneth On Fri, Jun 24, 1994 at 10:40:56PM +0800, Percy Cheng wrote: > I just bind my network card to the system, but sadly it seems could > not work properly, > I'm using NE2000 compatible NIC, after I'd checked the startup log, I > discovered that > some devices had conflicted with the NIC's 0x300 address. After the > system started, > I triied to ping the local host, it seccessed, but when I try to ping > the another machine > on the lan, it failed........ > > Have anyone can tell me what;s wrong on it?? > > PErcy Cheng > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jun 24 17:41:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08057 for freebsd-net-outgoing; Wed, 24 Jun 1998 17:41:14 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from almond.elite.net (root@almond.elite.net [205.199.220.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08006; Wed, 24 Jun 1998 17:40:49 -0700 (PDT) (envelope-from nate@almond.elite.net) Received: (from nate@localhost) by almond.elite.net (8.8.3/ELITE) id RAA05172; Wed, 24 Jun 1998 17:40:45 -0700 (PDT) From: Nate Lawson Message-Id: <199806250040.RAA05172@almond.elite.net> Subject: Apparent bug in sendto() with raw sockets To: freebsd-bugs@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Date: Wed, 24 Jun 1998 17:40:43 -0700 (PDT) X-Mailer: ELM [version 2.4 PL25] 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 had some code that opens a raw socket and sends packets. It worked on 2.0.5 and I recently had to dust it off. To my surprise, the same code (recompiled, of course) now gets "Invalid argument" in the sendto() call on 2.2.5. I stripped out all irrelevant code, and came up with the code fragment below. It works on: OpenBSD 2.4, Linux 2.0.something It fails on: FreeBSD 2.2.5, 2.2.6, 3.0-current The error is always EINVAL in sendto(). Answers? Thanks, Nate /* Cut here for sample code */ #include #include #include #include #include #include main () { static struct sockaddr sa; int fd; int on=1; struct sockaddr_in *p; u_char buf[] = { 0x45, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0xa, 0x2, 0x2, 0x2, 0xa, 0x1, 0x1, 0x1 }; p = (struct sockaddr_in*)&sa; p->sin_family = AF_INET; p->sin_addr.s_addr = inet_addr ("10.1.1.1"); if ((fd = socket (AF_INET, SOCK_RAW, IPPROTO_RAW)) < 0) { perror("socket"); exit(1); } if (setsockopt (fd, IPPROTO_IP, IP_HDRINCL, &on, sizeof(on)) < 0) { perror("setsockopt IP_HDRINCL"); exit(1); } if (sendto (fd, buf, sizeof(buf), 0, &sa, sizeof(sa)) < 0) { perror("sendto"); exit(1); } fprintf (stderr, "Success.\n"); exit(0); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jun 24 18:14:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13350 for freebsd-net-outgoing; Wed, 24 Jun 1998 18:14:47 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from ibridge.iohk.com (root@ibridge.iohk.com [202.21.128.82]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13182 for ; Wed, 24 Jun 1998 18:13:56 -0700 (PDT) (envelope-from percy@iohk.com) Received: from igate.iohk.com (percy@igate.iohk.com [202.21.128.81]) by ibridge.iohk.com (8.8.5/8.8.5) with ESMTP id JAA22452 for ; Thu, 25 Jun 1998 09:16:21 +0800 (HKT) Received: from localhost (percy@localhost) by igate.iohk.com (8.8.5/8.8.5) with SMTP id JAA07964 for ; Thu, 25 Jun 1998 09:16:20 +0800 (HKT) Date: Thu, 25 Jun 1998 09:16:19 +0800 (HKT) From: Percy Cheng To: freebsd-net@FreeBSD.ORG Subject: keyboard problem In-Reply-To: <2E0AF078.A65122B6@iohk.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 When I try to enter minicom, how I couldnt press alt-D to enter phone book? It seems all functions were disabled, anyone can tell me how to solve this problem becos I just a new comer to Unix/FreeBSD, and my keyboard already mapped to US style... Thanks for your kind attention...^_^ Percy Cheng Internet Online Hong Kong Ltd. Our Web Site:http://www.iohk.com My email box:percy@iohk.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jun 25 07:53:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA20542 for freebsd-net-outgoing; Thu, 25 Jun 1998 07:53:20 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from arthur.axion.bt.co.uk (arthur.axion.bt.co.uk [132.146.5.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA20513 for ; Thu, 25 Jun 1998 07:53:12 -0700 (PDT) (envelope-from graeme.brown@bt-sys.bt.co.uk) Received: from rambo (actually rambo.futures.bt.co.uk) by arthur.axion.bt.co.uk (PP) with SMTP; Thu, 25 Jun 1998 15:00:19 +0100 Received: from maczebedee (actually macsmtp) by rambo with SMTP (PP); Thu, 25 Jun 1998 15:02:05 +0100 Message-ID: Date: 25 Jun 1998 15:01:34 +0100 From: Graeme Brown Subject: memory Leak Detection for C Programs under FreeBSD To: "FreeBSD-Net (FreeBSD.Org) List" X-Mailer: Mail*Link SMTP for Quarterdeck Mail; Version 4.0.0 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear List appologies if this enquiry is somehat off-base for networking stuff, but I have a routing demon written in C under development for FreeBSD with some memory leak problems. Does anyone know of public domain prog devel/debugging tools that I might be able to use under FreeBSD-2.2.6 to get a handle on this ? TIA Graeme N Brown email: graeme.brown@bt-sys.bt.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jun 25 09:44:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07505 for freebsd-net-outgoing; Thu, 25 Jun 1998 09:44:20 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from alpha.xerox.com (omega.Xerox.COM [13.1.64.95]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA07401; Thu, 25 Jun 1998 09:44:06 -0700 (PDT) (envelope-from fenner@parc.xerox.com) Received: from mango.parc.xerox.com ([13.1.102.232]) by alpha.xerox.com with SMTP id <40738(1)>; Thu, 25 Jun 1998 09:43:30 PDT Received: from mango.parc.xerox.com (localhost [127.0.0.1]) by mango.parc.xerox.com (8.8.8/8.8.8) with ESMTP id JAA13888; Thu, 25 Jun 1998 09:43:29 -0700 (PDT) (envelope-from fenner@mango.parc.xerox.com) Message-Id: <199806251643.JAA13888@mango.parc.xerox.com> To: Nate Lawson cc: freebsd-bugs@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Apparent bug in sendto() with raw sockets In-reply-to: Your message of "Wed, 24 Jun 1998 17:40:43 PDT." <199806250040.RAA05172@almond.elite.net> Date: Thu, 25 Jun 1998 09:43:28 PDT From: Bill Fenner Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Fill in the IP length field. You're writing what claims to be a zero-length packet, and the kernel doesn't think that's a good idea. The IP length field (and the IP offset, if you ever fill that in) need to be stored in host byte order, not network byte order. Linux and OpenBSD want the fields in network byte order. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jun 25 10:29:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17121 for freebsd-net-outgoing; Thu, 25 Jun 1998 10:29:41 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17115; Thu, 25 Jun 1998 10:29:36 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA13476; Thu, 25 Jun 1998 10:19:18 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd013465; Thu Jun 25 17:19:12 1998 Date: Thu, 25 Jun 1998 10:18:57 -0700 (PDT) From: Julian Elischer To: Bill Fenner cc: Nate Lawson , freebsd-bugs@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Apparent bug in sendto() with raw sockets In-Reply-To: <199806251643.JAA13888@mango.parc.xerox.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 Why are we grtuiously different? I vaguely remember something about this a few years ago.. On Thu, 25 Jun 1998, Bill Fenner wrote: > Fill in the IP length field. You're writing what claims to be a zero-length > packet, and the kernel doesn't think that's a good idea. > > The IP length field (and the IP offset, if you ever fill that in) need > to be stored in host byte order, not network byte order. Linux and > OpenBSD want the fields in network byte order. > > Bill > > 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 Jun 25 11:41:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00705 for freebsd-net-outgoing; Thu, 25 Jun 1998 11:41:54 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from alpha.xerox.com (omega.Xerox.COM [13.1.64.95]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA00652; Thu, 25 Jun 1998 11:41:34 -0700 (PDT) (envelope-from fenner@parc.xerox.com) Received: from mango.parc.xerox.com ([13.1.102.232]) by alpha.xerox.com with SMTP id <40733(1)>; Thu, 25 Jun 1998 11:41:00 PDT Received: from mango.parc.xerox.com (localhost [127.0.0.1]) by mango.parc.xerox.com (8.8.8/8.8.8) with ESMTP id LAA14290; Thu, 25 Jun 1998 11:40:54 -0700 (PDT) (envelope-from fenner@mango.parc.xerox.com) Message-Id: <199806251840.LAA14290@mango.parc.xerox.com> To: Julian Elischer cc: Bill Fenner , Nate Lawson , freebsd-bugs@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Apparent bug in sendto() with raw sockets In-reply-to: Your message of "Thu, 25 Jun 1998 10:18:57 PDT." Date: Thu, 25 Jun 1998 11:40:54 PDT From: Bill Fenner Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message you w rite: >Why are we ... different? Because the original implementation of raw sockets (the patches included with LBL's traceroute) simply exposed ip_output()'s interface, which requires length and offset in host order. AFAIK, this original implementation happened on suns, which is why nobody noticed at the time. We are compatible with this original implementation. OpenBSD and Linux chose to change the semantics to the ones that are less surprising but not backwards compatible. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jun 25 14:30:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29974 for freebsd-net-outgoing; Thu, 25 Jun 1998 14:30:12 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from almond.elite.net (root@almond.elite.net [205.199.220.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29890; Thu, 25 Jun 1998 14:29:29 -0700 (PDT) (envelope-from nate@almond.elite.net) Received: (from nate@localhost) by almond.elite.net (8.8.3/ELITE) id OAA24992; Thu, 25 Jun 1998 14:29:20 -0700 (PDT) From: Nate Lawson Message-Id: <199806252129.OAA24992@almond.elite.net> Subject: Re: Apparent bug in sendto() with raw sockets To: fenner@parc.xerox.com (Bill Fenner) Date: Thu, 25 Jun 1998 14:29:18 -0700 (PDT) Cc: julian@whistle.com, fenner@parc.xerox.com, nate@elite.net, freebsd-bugs@FreeBSD.ORG, freebsd-net@FreeBSD.ORG In-Reply-To: <199806251840.LAA14290@mango.parc.xerox.com> from "Bill Fenner" at Jun 25, 98 11:40:54 am X-Mailer: ELM [version 2.4 PL25] 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 In a previous message, Bill Fenner said: >In message you w >rite: >>Why are we ... different? > >Because the original implementation of raw sockets (the patches >included with LBL's traceroute) simply exposed ip_output()'s >interface, which requires length and offset in host order. AFAIK, >this original implementation happened on suns, which is why nobody >noticed at the time. We are compatible with this original >implementation. OpenBSD and Linux chose to change the semantics >to the ones that are less surprising but not backwards compatible. The fix was to place ip->ip_id in host order (it wasn't zero-length in the original code). Since traceroute ships as a standard utility with FreeBSD, couldn't the change to network byte order be done simultaneously, minimizing headaches? Current versions of traceroute circulating around the net also assume the proper behavior (network byte order for everything), so they should work then as well. Thanks for the help, Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jun 25 14:32:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00511 for freebsd-net-outgoing; Thu, 25 Jun 1998 14:32:25 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from almond.elite.net (root@almond.elite.net [205.199.220.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00341; Thu, 25 Jun 1998 14:31:20 -0700 (PDT) (envelope-from nate@almond.elite.net) Received: (from nate@localhost) by almond.elite.net (8.8.3/ELITE) id OAA25149; Thu, 25 Jun 1998 14:31:13 -0700 (PDT) From: Nate Lawson Message-Id: <199806252131.OAA25149@almond.elite.net> Subject: Re: Apparent bug in sendto() with raw sockets To: nate@elite.net (Nate Lawson) Date: Thu, 25 Jun 1998 14:31:13 -0700 (PDT) Cc: fenner@parc.xerox.com, julian@whistle.com, nate@elite.net, freebsd-bugs@FreeBSD.ORG, freebsd-net@FreeBSD.ORG In-Reply-To: <199806252129.OAA24992@almond.elite.net> from "Nate Lawson" at Jun 25, 98 02:29:18 pm X-Mailer: ELM [version 2.4 PL25] 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 In a previous message, Nate Lawson said: >The fix was to place ip->ip_id in host order (it wasn't zero-length in the ^^^^^ Should read ip_len. Sorry. -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jun 25 15:08:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07604 for freebsd-net-outgoing; Thu, 25 Jun 1998 15:08:22 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from alpha.xerox.com (omega.Xerox.COM [13.1.64.95]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA07508; Thu, 25 Jun 1998 15:07:47 -0700 (PDT) (envelope-from fenner@parc.xerox.com) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <40744(1)>; Thu, 25 Jun 1998 15:07:06 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <177515>; Thu, 25 Jun 1998 15:06:59 -0700 To: Nate Lawson cc: fenner@parc.xerox.com (Bill Fenner), julian@whistle.com, nate@elite.net, freebsd-bugs@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Apparent bug in sendto() with raw sockets In-reply-to: Your message of "Thu, 25 Jun 98 14:29:18 PDT." <199806252129.OAA24992@almond.elite.net> Date: Thu, 25 Jun 1998 15:06:52 PDT From: Bill Fenner Message-Id: <98Jun25.150659pdt.177515@crevenia.parc.xerox.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199806252129.OAA24992@almond.elite.net> Nate Lawson wrote: >Since traceroute ships as a standard utility with FreeBSD, couldn't the >change to network byte order be done simultaneously, minimizing headaches? The standard utilities could be changed easily. I'm worried about compatibility with externally-written programs; e.g. the binary-only "pathchar" from LBL would become useless on an OS with this change. Externally-written programs that are written to the well known BSD raw socket interface would all have to be patched to work with an updated system, as well. (For example, LBL's traceroute program.) Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jun 25 15:21:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09993 for freebsd-net-outgoing; Thu, 25 Jun 1998 15:21:49 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from almond.elite.net (root@almond.elite.net [205.199.220.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09882; Thu, 25 Jun 1998 15:21:01 -0700 (PDT) (envelope-from nate@almond.elite.net) Received: (from nate@localhost) by almond.elite.net (8.8.3/ELITE) id PAA28609; Thu, 25 Jun 1998 15:20:43 -0700 (PDT) From: Nate Lawson Message-Id: <199806252220.PAA28609@almond.elite.net> Subject: Re: Apparent bug in sendto() with raw sockets To: fenner@parc.xerox.com (Bill Fenner) Date: Thu, 25 Jun 1998 15:20:43 -0700 (PDT) Cc: nate@elite.net, fenner@parc.xerox.com, julian@whistle.com, freebsd-bugs@FreeBSD.ORG, freebsd-net@FreeBSD.ORG In-Reply-To: <98Jun25.150659pdt.177515@crevenia.parc.xerox.com> from "Bill Fenner" at Jun 25, 98 03:06:52 pm X-Mailer: ELM [version 2.4 PL25] 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 In a previous message, Bill Fenner said: >In message <199806252129.OAA24992@almond.elite.net> Nate Lawson wrote: >>Since traceroute ships as a standard utility with FreeBSD, couldn't the >>change to network byte order be done simultaneously, minimizing headaches? > >The standard utilities could be changed easily. I'm worried about >compatibility with externally-written programs; e.g. the binary-only >"pathchar" from LBL would become useless on an OS with this change. >Externally-written programs that are written to the well known BSD raw >socket interface would all have to be patched to work with an updated >system, as well. (For example, LBL's traceroute program.) A friend of mine, jpm@elite.net, suggested that it might be possible to handle both orderings (like endian-switching on an Alpha). The only thing I see this would break is raw packets over 32768 bytes long (i.e. if ip_len > 32768, swap bytes and use the result). Might a sysctl variable also be an option? I know that 2.0.5R behaved the way that OpenBSD and Linux behave. Were there any complaints or problems with it back then? -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jun 25 15:59:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16375 for freebsd-net-outgoing; Thu, 25 Jun 1998 15:59:30 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from alpha.xerox.com (omega.Xerox.COM [13.1.64.95]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA15932; Thu, 25 Jun 1998 15:56:29 -0700 (PDT) (envelope-from fenner@parc.xerox.com) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <40747(2)>; Thu, 25 Jun 1998 15:55:46 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <177515>; Thu, 25 Jun 1998 15:55:35 -0700 To: Nate Lawson cc: fenner@parc.xerox.com (Bill Fenner), nate@elite.net, julian@whistle.com, freebsd-bugs@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Apparent bug in sendto() with raw sockets In-reply-to: Your message of "Thu, 25 Jun 98 15:20:43 PDT." <199806252220.PAA28609@almond.elite.net> Date: Thu, 25 Jun 1998 15:55:31 PDT From: Bill Fenner Message-Id: <98Jun25.155535pdt.177515@crevenia.parc.xerox.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199806252220.PAA28609@almond.elite.net> you write: >I know that 2.0.5R behaved the way that OpenBSD and Linux behave. Were there >any complaints or problems with it back then? It didn't. The code in FreeBSD is almost exactly the same as when IP_HDRINCL was introduced in 4.3-Reno. The change that caused more recent versions of FreeBSD to return EINVAL was that it started checking the validity of the length field and returns EINVAL if the IP length is longer than the length of the buffer that was provided. I had tossed around the idea of a socket option to switch behaviors, for both input and output, but decided it would be relatively wasted effort; if you can conditionally set a socket option you can also conditionally (fail to) byte-swap the appropriate fields. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jun 25 16:13:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19343 for freebsd-net-outgoing; Thu, 25 Jun 1998 16:13:29 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from alpha.xerox.com (omega.Xerox.COM [13.1.64.95]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA19237 for ; Thu, 25 Jun 1998 16:12:42 -0700 (PDT) (envelope-from fenner@parc.xerox.com) Received: from mango.parc.xerox.com ([13.1.102.232]) by alpha.xerox.com with SMTP id <40744(1)>; Thu, 25 Jun 1998 16:11:59 PDT Received: from mango.parc.xerox.com (localhost [127.0.0.1]) by mango.parc.xerox.com (8.8.8/8.8.8) with ESMTP id QAA15301; Thu, 25 Jun 1998 16:11:51 -0700 (PDT) (envelope-from fenner@mango.parc.xerox.com) Message-Id: <199806252311.QAA15301@mango.parc.xerox.com> To: Nate Lawson cc: fenner@parc.xerox.com (Bill Fenner), julian@whistle.com, freebsd-net@FreeBSD.ORG Subject: Re: Apparent bug in sendto() with raw sockets In-reply-to: Your message of "Thu, 25 Jun 1998 15:20:43 PDT." <199806252220.PAA28609@almond.elite.net> Date: Thu, 25 Jun 1998 16:11:51 PDT From: Bill Fenner Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [I removed -bugs from the CC] I take it back. I think a socket option could work. As your friend suggested, byte order could be auto-determined, not just via "ip_len > 32767" but by comparing the ip_len with the length of the packet that was written and turning on the automagic byte swap socket option if ip_len == htonl(send len). This is kind of hokey magic, since if the output side set the socket option automagically, the input side would be affected too. If you output before you input, everything would be in the order you'd expect. If you input first, then output, then input, you could get awfully confused since the input behavior would change after the first output. (And if the output side didn't set the socket flag that affected input, then a program written to assume no byte swapping would end up with non-byte-swapped output but byte-swapped (and otherwise munged) input...) I'll work on a patch. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jun 25 20:14:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA22333 for freebsd-net-outgoing; Thu, 25 Jun 1998 20:14:54 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA22327 for ; Thu, 25 Jun 1998 20:14:50 -0700 (PDT) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id XAA22044 for ; Thu, 25 Jun 1998 23:08:20 -0400 (EDT) Date: Thu, 25 Jun 1998 23:14:49 -0400 (EDT) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: freebsd-net@FreeBSD.ORG Subject: aborted web connections ? 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 Ive noticed this several times now. I cant seem to figure out what causes it cause im not logging with tcpdump. But I have noticed that when I abort web conenctions sometimes it gets wedged in a loop with whoever I was connecting to, and it winds up creating a "flooding" action and totally nukes my poor ppp link. It seems to happen with linux boxes. Ive included tcpdump output below. So read on at your own risk. Is there anyway to "patch" this or a sysctl to disable to keep this from happening its rather annoying. This is a 3.0-current box BTW. 22:05:58.527822 206.252.171.10.4623 > 128.183.250.18.ftp-data: . ack 43801 win 17520 (DF) (ttl 64, id 41346) 22:05:58.729163 147.155.137.28.http > 206.252.171.10.4616: . 265064:266524(1460) ack 1 win 31744 (ttl 53, id 5345) 22:05:58.927804 206.252.171.10.4616 > 147.155.137.28.http: . ack 266524 win 17520 (DF) (ttl 64, id 41347) 22:05:59.119064 147.155.137.28.http > 206.252.171.10.4616: . 266524:267984(1460) ack 1 win 31744 (ttl 53, id 5346) 22:05:59.127815 206.252.171.10.4616 > 147.155.137.28.http: . ack 267984 win 17520 (DF) (ttl 64, id 41348) 22:05:59.348774 147.155.137.28.http > 206.252.171.10.4616: P 267984:268876(892) ack 1 win 31744 (DF) (ttl 53, id 5347) 22:06:02.127722 206.252.171.10.4616 > 147.155.137.28.http: . ack 278528 win 17520 (DF) (ttl 64, id 41357) 22:06:02.298999 147.155.137.28.http > 206.252.171.10.4617: . 131072:132532(1460) ack 1 win 31744 (DF) (ttl 53, id 5355) 22:06:02.327750 206.252.171.10.4617 > 147.155.137.28.http: . ack 132532 win 17520 (DF) (ttl 64, id 41358) 22:06:02.658828 147.155.137.28.http > 206.252.171.10.4617: . 132532:133992(1460) ack 1 win 31744 (DF) (ttl 53, id 5356) 22:06:02.727653 206.252.171.10.4617 > 147.155.137.28.http: . ack 133992 win 17520 (DF) (ttl 64, id 41359) 22:06:02.988706 147.155.137.28.http > 206.252.171.10.4617: . 133992:135452(1460) ack 1 win 31744 (DF) (ttl 53, id 5357) 22:06:03.127658 206.252.171.10.4617 > 147.155.137.28.http: . ack 135452 win 17520 (DF) (ttl 64, id 41360) 22:06:03.379003 147.155.137.28.http > 206.252.171.10.4616: . 278528:279988(1460) ack 1 win 31744 (ttl 53, id 5358) 22:06:03.527637 206.252.171.10.4616 > 147.155.137.28.http: . ack 279988 win 17520 (DF) (ttl 64, id 41361) 22:06:03.768710 147.155.137.28.http > 206.252.171.10.4616: . 279988:281448(1460) ack 1 win 31744 (ttl 53, id 5359) 22:06:03.927615 206.252.171.10.4616 > 147.155.137.28.http: . ack 281448 win 17520 (DF) (ttl 64, id 41362) 22:06:04.128768 147.155.137.28.http > 206.252.171.10.4619: . 252493:253953(1460) ack 0 win 31744 (ttl 53, id 5360) 22:06:04.327623 206.252.171.10.4619 > 147.155.137.28.http: . ack 253953 win 17520 (DF) (ttl 64, id 41363) 22:06:04.518920 147.155.137.28.http > 206.252.171.10.4619: . 253953:255413(1460) ack 0 win 31744 (ttl 53, id 5361) 22:06:04.527618 206.252.171.10.4619 > 147.155.137.28.http: . ack 255413 win 17520 (DF) (ttl 64, id 41364) 22:06:04.908681 147.155.137.28.http > 206.252.171.10.4617: . 135452:136912(1460) ack 1 win 31744 (ttl 53, id 5362) 22:06:04..927575 206.252.171.10.4617 > 147.155.137.28.http: . ack 136912 win 17520 (DF) (ttl 64, id 41365) 22:06:05.268844 147.155.137.28.http > 206.252.171.10.4619: . 255413:256873(1460) ack 0 win 31744 (ttl 53, id 5363) 22:06:05.327661 206.252.171.10.4619 > 147.155.137.28.http: . ack 256873 win 17520 (DF) (ttl 64, id 41366) 22:06:05.658729 147.155.137.28.http > 206.252.171.10.4619: . 256873:258333(1460) ack 0 win 31744 (ttl 53, id 5364) 22:06:05.727579 206.252.171.10.4619 > 147.155.137.28.http: . ack 258333 win 17520 (DF) (ttl 64, id 41367) 22:06:06.018713 147.155.137.28.http > 206.252.171.10.4619: . 258333:259793(1460) ack 0 win 31744 (ttl 53, id 5365) 22:06:06.127535 206.252.171.10.4619 > 147.155.137.28.http: . ack 259793 win 17520 (DF) (ttl 64, id 41368) 22:06:06.268623 147.155.137.28.http > 206.252.171.10.4619: P 259793:260685(892) ack 0 win 31744 (DF) (ttl 53, id 5366) 22:06:06.327537 206.252.171.10.4619 > 147.155.137.28.http: . ack 260685 win 17520 (DF) (ttl 64, id 41369) 22:06:06.658673 147.155.137.28.http > 206.252.171.10.4619: . 260685:262145(1460) ack 0 win 31744 (ttl 53, id 5367) 22:06:06.727562 206.252.171.10.4619 > 147.155.137.28.http: . ack 262145 win 17520 (DF) (ttl 64, id 41370) 22:06:07.020933 147.155.137.28.http > 206.252.171.10.4619: . 262145:263605(1460) ack 0 win 31744 (ttl 53, id 5368) 22:06:07.127501 206.252.171.10.4619 > 147.155.137.28.http: . ack 263605 win 17520 (DF) (ttl 64, id 41371) 22:06:07.408738 147.155.137.28.http > 206.252.171.10.4619: . 263605:265065(1460) ack 0 win 31744 (ttl 53, id 5369) 22:06:07.527490 206.252.171.10.4619 > 147.155.137.28.http: . ack 265065 win 17520 (DF) (ttl 64, id 41372) 22:06:07.768567 147.155.137.28.http > 206.252.171.10.4619: . 265065:266525(1460) ack 0 win 31744 (ttl 53, id 5370) 22:06:07.927486 206.252.171.10.4619 > 147.155.137.28.http: . ack 266525 win 17520 (DF) (ttl 64, id 41373) -- "Linux... The choice of a GNUtered generation." ===================================| Open Systems Networking And Consulting. FreeBSD 2.2.6 is available now! | Phone: 316-326-6800 -----------------------------------| 1402 N. Washington, Wellington, KS-67152 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting-Network Engineering-Security ===================================| http://open-systems.net -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= =BBjp -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jun 25 21:35:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA03229 for freebsd-net-outgoing; Thu, 25 Jun 1998 21:35:36 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from compound.east.sun.com (port13.prairietech.net [208.141.230.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA03207 for ; Thu, 25 Jun 1998 21:35:15 -0700 (PDT) (envelope-from alk@compound.east.sun.com) Received: (from alk@localhost) by compound.east.sun.com (8.8.8/8.7.3) id XAA10497; Thu, 25 Jun 1998 23:35:53 -0500 (CDT) From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 25 Jun 1998 23:35:51 -0500 (CDT) X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn Reply-To: alk@pobox.com To: graeme.brown@bt-sys.bt.co.uk Subject: memory Leak Detection for C Programs under FreeBSD References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13715.9339.786764.535101@compound.east> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Quoth Graeme Brown on , 25 June: : Dear List : : appologies if this enquiry is somehat off-base for networking stuff, : but I have a routing demon written in C under development for FreeBSD : with some memory leak problems. freebsd-questions (black hole, I know -- so try comp.unix.bsd.freebsd.misc?) : Does anyone know of public domain prog devel/debugging tools that : I might be able to use under FreeBSD-2.2.6 to get a handle on this ? /usr/ports/devel/libmalloc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jun 26 06:05:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA02834 for freebsd-net-outgoing; Fri, 26 Jun 1998 06:05:46 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from heron.doc.ic.ac.uk (nhqVL+RPXJmKHZR8PbMcGl2YtPUTE0DN@heron.doc.ic.ac.uk [146.169.46.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA02801; Fri, 26 Jun 1998 06:05:33 -0700 (PDT) (envelope-from njs3@doc.ic.ac.uk) Received: from oak67.doc.ic.ac.uk [146.169.33.67] ([eTs3tGkng938xwU5Pn53Xecw1dgXvdIc]) by heron.doc.ic.ac.uk with smtp (Exim 1.62 #3) id 0ypYBD-0007Tx-00; Fri, 26 Jun 1998 14:04:39 +0100 Received: from njs3 by oak67.doc.ic.ac.uk with local (Exim 1.62 #3) id 0ypYBC-0005Qv-00; Fri, 26 Jun 1998 14:04:38 +0100 From: njs3@doc.ic.ac.uk (Niall Smart) Date: Fri, 26 Jun 1998 14:04:38 +0100 In-Reply-To: Bill Fenner "Re: Apparent bug in sendto() with raw sockets" (Jun 25, 11:40am) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Bill Fenner , Julian Elischer Subject: Re: Apparent bug in sendto() with raw sockets Cc: Nate Lawson , freebsd-bugs@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Message-Id: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Jun 25, 11:40am, Bill Fenner wrote: } Subject: Re: Apparent bug in sendto() with raw sockets > In message you w > interface, which requires length and offset in host order. AFAIK, > this original implementation happened on suns, which is why nobody > noticed at the time. We are compatible with this original > implementation. OpenBSD and Linux chose to change the semantics > to the ones that are less surprising but not backwards compatible. I think its more important to be correct in this area, raw sockets programming can be tricky enough without what will seem to the user like gratuitous changes. If Linux and OpenBSD have done it, thats all the more reason to go for it... $2c Niall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jun 26 06:35:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA06700 for freebsd-net-outgoing; Fri, 26 Jun 1998 06:35:44 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from brooklyn.slack.net (root@brooklyn.slack.net [206.41.21.102]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA06685; Fri, 26 Jun 1998 06:35:27 -0700 (PDT) (envelope-from andrewr@brooklyn.slack.net) Received: from localhost (andrewr@localhost) by brooklyn.slack.net (8.8.7/8.8.7) with SMTP id JAA05984; Fri, 26 Jun 1998 09:38:34 -0400 (EDT) Date: Fri, 26 Jun 1998 09:38:33 -0400 (EDT) From: andrewr To: Bill Fenner cc: Nate Lawson , nate@elite.net, julian@whistle.com, freebsd-bugs@FreeBSD.ORG, freebsd-net@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Apparent bug in sendto() with raw sockets In-Reply-To: <98Jun25.155535pdt.177515@crevenia.parc.xerox.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 Speaking of IP_HDRINCL, after reading raw_ip.c and noticing the protection against spoofing (can't use IP_HDRINCL in certain situations), I started thinking about actually comparing the user dsupplied ip->ip_src with the actual IP address defined for the outgoing interface. While looking for a quick hack to get the interface ip, I was looking through ip_output.c and saw a neat little algo there. While I have not tested this yet, I will in the next couple of days, I figure it should be a pretty fail safe block against spoofing IF AND ONLY IF the user has not created there own data structure, ie. struct raw_pkt_hdr { struct ip ip; struct udphdr udp; } raw_pkt_hdr; This will be an easy work around for the user to spoof packets. In my opinion, while I don't see how it can be done, I believe there should be a way to test for a user defined data structure containing the IP header, etc.. From my speaking with a few FreeBSD kernel developers/hackers this is not possible, and I fully see why it is not.. but, I am just throwing the idea out into the open for all of you to digest. Andrew ***************************************** AWR XNS, Inc. "Drink beer, it will save your life." On Thu, 25 Jun 1998, Bill Fenner wrote: > In message <199806252220.PAA28609@almond.elite.net> you write: > >I know that 2.0.5R behaved the way that OpenBSD and Linux behave. Were there > >any complaints or problems with it back then? > > It didn't. The code in FreeBSD is almost exactly the same as when > IP_HDRINCL was introduced in 4.3-Reno. The change that caused > more recent versions of FreeBSD to return EINVAL was that it > started checking the validity of the length field and returns > EINVAL if the IP length is longer than the length of the buffer > that was provided. > > I had tossed around the idea of a socket option to switch behaviors, > for both input and output, but decided it would be relatively wasted > effort; if you can conditionally set a socket option you can also > conditionally (fail to) byte-swap the appropriate fields. > > Bill > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-bugs" 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 Fri Jun 26 08:10:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA22157 for freebsd-net-outgoing; Fri, 26 Jun 1998 08:10:44 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA22047 for ; Fri, 26 Jun 1998 08:10:04 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id XAA25215; Fri, 26 Jun 1998 23:08:45 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199806261508.XAA25215@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Open Systems Networking cc: freebsd-net@FreeBSD.ORG Subject: Re: aborted web connections ? In-reply-to: Your message of "Thu, 25 Jun 1998 23:14:49 -0400." Date: Fri, 26 Jun 1998 23:08:44 +0800 From: Peter Wemm Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Open Systems Networking wrote: > > > Ive noticed this several times now. I cant seem to figure out what causes > it cause im not logging with tcpdump. > But I have noticed that when I abort web conenctions sometimes it gets > wedged in a loop with whoever I was connecting to, and it winds up > creating a "flooding" action and totally nukes my poor ppp link. > It seems to happen with linux boxes. Ive included tcpdump output below. So > read on at your own risk. Is there anyway to "patch" this or a sysctl to > disable to keep this from happening its rather annoying. > This is a 3.0-current box BTW. I had this a couple of times on a 2.2-stable machine as well, but wasn't able to make much sense of it. It was on a front-line machine that really didn't need the link drain, so it was rebooted before I had much of a chance to look at it. :-( BTW, in the tcpdump, which IP address is yours? 206.252.171.10? Hmm. This looks different to what I've seen.. If I reduce the tcpdump a little, there doesn't appear to be anthing odd except for some missing lines... You have multiple TCP streams mixed together as well Session 1: 22:05:58.729163 them.http > you.4616: . 265064:266524(1460) ack 1 win 31744 22:05:58.927804 you.4616 > them.http: . ack 266524 win 17520 22:05:59.119064 them.http > you.4616: . 266524:267984(1460) ack 1 win 31744 22:05:59.127815 you.4616 > them.http: . ack 267984 win 17520 22:05:59.348774 them.http > you.4616: P 267984:268876(892) ack 1 win 31744 [appears to have soem sequence space missing here, the seq jumps ~10KB ] 22:06:02.127722 you.4616 > them.http: . ack 278528 win 17520 22:06:03.379003 them.http > you.4616: . 278528:279988(1460) ack 1 win 31744 22:06:03.527637 you.4616 > them.http: . ack 279988 win 17520 22:06:03.768710 them.http > you.4616: . 279988:281448(1460) ack 1 win 31744 22:06:03.927615 you.4616 > them.http: . ack 281448 win 17520 This looks like a typical HTTP connection to me, possibly crossing a write() boundary on the server with the automatic PSH. Otherwise it's a persistant http connection. Session 2: 22:06:02.298999 them.http > you.4617: . 131072:132532(1460) ack 1 win 31744 22:06:02.327750 you.4617 > them.http: . ack 132532 win 17520 22:06:02.658828 them.http > you.4617: . 132532:133992(1460) ack 1 win 31744 22:06:02.727653 you.4617 > them.http: . ack 133992 win 17520 22:06:02.988706 them.http > you.4617: . 133992:135452(1460) ack 1 win 31744 22:06:03.127658 you.4617 > them.http: . ack 135452 win 17520 22:06:04..927575 you.4617 > them.http: . ack 136912 win 17520 ^^ what's this? There is another sequence space gap here. 22:06:04.908681 them.http > you.4617: . 135452:136912(1460) ack 1 win 31744 This looks like a conventional HTTP download. Session 3: 22:06:04.128768 them.http > you.4619: . 252493:253953(1460) ack 0 win 31744 22:06:04.327623 you.4619 > them.http: . ack 253953 win 17520 22:06:04.518920 them.http > you.4619: . 253953:255413(1460) ack 0 win 31744 22:06:04.527618 you.4619 > them.http: . ack 255413 win 17520 22:06:05.268844 them.http > you.4619: . 255413:256873(1460) ack 0 win 31744 22:06:05.327661 you.4619 > them.http: . ack 256873 win 17520 22:06:05.658729 them.http > you.4619: . 256873:258333(1460) ack 0 win 31744 22:06:05.727579 you.4619 > them.http: . ack 258333 win 17520 22:06:06.018713 them.http > you.4619: . 258333:259793(1460) ack 0 win 31744 22:06:06.127535 you.4619 > them.http: . ack 259793 win 17520 22:06:06.268623 them.http > you.4619: P 259793:260685(892) ack 0 win 31744 22:06:06.327537 you.4619 > them.http: . ack 260685 win 17520 22:06:06.658673 them.http > you.4619: . 260685:262145(1460) ack 0 win 31744 22:06:06.727562 you.4619 > them.http: . ack 262145 win 17520 22:06:07.020933 them.http > you.4619: . 262145:263605(1460) ack 0 win 31744 22:06:07.127501 you.4619 > them.http: . ack 263605 win 17520 22:06:07.408738 them.http > you.4619: . 263605:265065(1460) ack 0 win 31744 22:06:07.527490 you.4619 > them.http: . ack 265065 win 17520 22:06:07.768567 them.http > you.4619: . 265065:266525(1460) ack 0 win 31744 22:06:07.927486 you.4619 > them.http: . ack 266525 win 17520 Also looks like a conventional HTTP download. I note that the 'them' IP address is: www.scl.ameslab.gov. You're not by any chance trying to view some page that's got a HTTP REFRESH tag or something else to cause your browser to reload faster than you can download? Perhaps a self refreshing status page or something? It looks basically like you're simply downloading gobs of data in parallel. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jun 26 08:29:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA24891 for freebsd-net-outgoing; Fri, 26 Jun 1998 08:29:03 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from itesec.hsc.fr (root@itesec.hsc.fr [192.70.106.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA24764; Fri, 26 Jun 1998 08:28:09 -0700 (PDT) (envelope-from pb@hsc.fr) Received: from mars.hsc.fr (mars.hsc.fr [192.70.106.44]) by itesec.hsc.fr (8.8.8/8.8.5/itesec-1.12-nospam) with ESMTP id RAA13257; Fri, 26 Jun 1998 17:19:01 +0200 (MET DST) Received: (from pb@localhost) by mars.hsc.fr (8.8.8/8.8.8/pb-19980526) id RAA18988; Fri, 26 Jun 1998 17:27:48 +0200 (CEST) (envelope-from pb) Message-ID: <19980626172748.A18953@mars.hsc.fr> Date: Fri, 26 Jun 1998 17:27:48 +0200 From: Pierre Beyssac To: andrewr , Bill Fenner Cc: Nate Lawson , nate@elite.net, julian@whistle.com, freebsd-bugs@FreeBSD.ORG, freebsd-net@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Apparent bug in sendto() with raw sockets References: <98Jun25.155535pdt.177515@crevenia.parc.xerox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.8i In-Reply-To: ; from andrewr on Fri, Jun 26, 1998 at 09:38:33AM -0400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jun 26, 1998 at 09:38:33AM -0400, andrewr wrote: > Speaking of IP_HDRINCL, after reading raw_ip.c and noticing the protection > against spoofing (can't use IP_HDRINCL in certain situations), I started > thinking about actually comparing the user dsupplied ip->ip_src with the Are you sure you're talking about FreeBSD here ? SunOS 4 has such a protection (it checks that the source address belongs to one of the interfaces, or so it seems) but I've successfully spoofed packets on FreeBSD without any problem using IP_HDRINCL. Anyway, such a protection can easily bypassed by sending raw link-level packets through bpf (or probably /dev/nit in the case of SunOS, although I've never tried this). -- Pierre.Beyssac@hsc.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jun 26 08:59:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00253 for freebsd-net-outgoing; Fri, 26 Jun 1998 08:59:37 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from alpha.xerox.com (omega.Xerox.COM [13.1.64.95]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA29999 for ; Fri, 26 Jun 1998 08:59:02 -0700 (PDT) (envelope-from fenner@parc.xerox.com) Received: from mango.parc.xerox.com ([13.1.102.232]) by alpha.xerox.com with SMTP id <40661(1)>; Fri, 26 Jun 1998 08:58:22 PDT Received: from mango.parc.xerox.com (localhost [127.0.0.1]) by mango.parc.xerox.com (8.8.8/8.8.8) with ESMTP id IAA18471; Fri, 26 Jun 1998 08:58:18 -0700 (PDT) (envelope-from fenner@mango.parc.xerox.com) Message-Id: <199806261558.IAA18471@mango.parc.xerox.com> To: njs3@doc.ic.ac.uk (Niall Smart) cc: Bill Fenner , Julian Elischer , Nate Lawson , freebsd-net@FreeBSD.ORG Subject: Re: Apparent bug in sendto() with raw sockets In-reply-to: Your message of "Fri, 26 Jun 1998 06:04:38 PDT." Date: Fri, 26 Jun 1998 08:58:18 PDT From: Bill Fenner Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message you write: >I think its more important to be correct in this area, raw sockets >programming can be tricky enough without what will seem to the >user like gratuitous changes. Changing the interface from what it currently is is a gratuitous change. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jun 26 09:50:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08249 for freebsd-net-outgoing; Fri, 26 Jun 1998 09:50:07 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from heron.doc.ic.ac.uk (vhMVCklc93W9msExElerSzEMNJx0NogG@heron.doc.ic.ac.uk [146.169.46.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA08180 for ; Fri, 26 Jun 1998 09:49:53 -0700 (PDT) (envelope-from njs3@doc.ic.ac.uk) Received: from oak74.doc.ic.ac.uk [146.169.46.74] ([HsSguO7vGdpN8iyFKPlye3eGt7pHXq3X]) by heron.doc.ic.ac.uk with smtp (Exim 1.62 #3) id 0ypbgx-0000GR-00; Fri, 26 Jun 1998 17:49:40 +0100 Received: from njs3 by oak74.doc.ic.ac.uk with local (Exim 1.62 #3) id 0ypbgw-0006R9-00; Fri, 26 Jun 1998 17:49:38 +0100 From: njs3@doc.ic.ac.uk (Niall Smart) Date: Fri, 26 Jun 1998 17:49:38 +0100 In-Reply-To: Bill Fenner "Re: Apparent bug in sendto() with raw sockets" (Jun 26, 8:58am) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Bill Fenner , njs3@doc.ic.ac.uk (Niall Smart) Subject: Re: Apparent bug in sendto() with raw sockets Cc: Julian Elischer , Nate Lawson , freebsd-net@FreeBSD.ORG Message-Id: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Jun 26, 8:58am, Bill Fenner wrote: } Subject: Re: Apparent bug in sendto() with raw sockets > In message you write: > >I think its more important to be correct in this area, raw sockets > >programming can be tricky enough without what will seem to the > >user like gratuitous changes. > > Changing the interface from what it currently is is a gratuitous change. No it isn't, its a bug fix, you yourself noted the problem only happened because the code was originally developed on a Sun box. Having one or two of the fields in host byte order while the rest are in network byte order is silly and the only reason to keep it this way is bug compatability, but I'm not so sure thats so important in this case. Niall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jun 26 09:59:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09990 for freebsd-net-outgoing; Fri, 26 Jun 1998 09:59:38 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from alpha.xerox.com (omega.Xerox.COM [13.1.64.95]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA09950 for ; Fri, 26 Jun 1998 09:59:18 -0700 (PDT) (envelope-from fenner@parc.xerox.com) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <40754(2)>; Fri, 26 Jun 1998 09:58:43 PDT Received: by crevenia.parc.xerox.com id <177515>; Fri, 26 Jun 1998 09:58:36 -0700 From: Bill Fenner To: fenner@parc.xerox.com, njs3@doc.ic.ac.uk Subject: Re: Apparent bug in sendto() with raw sockets Cc: freebsd-net@FreeBSD.ORG, julian@whistle.com, nate@almond.elite.net Message-Id: <98Jun26.095836pdt.177515@crevenia.parc.xerox.com> Date: Fri, 26 Jun 1998 09:58:27 PDT Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I'm not so sure [compatability is] so important in this case. As I said before, I'm worried about externally-written programs, particularly about externally-written programs that are not distributed with source (like pathchar). I'd also like to see a definitive way to tell which order the kernel is expecting, so that externally-written programs that want to be portable (like, for example, mrouted, mrinfo, mtrace, rsvpd, etc.) don't have to use __FreeBSD_version. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jun 26 10:12:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12988 for freebsd-net-outgoing; Fri, 26 Jun 1998 10:12:26 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from brooklyn.slack.net (root@brooklyn.slack.net [206.41.21.102]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12759; Fri, 26 Jun 1998 10:10:45 -0700 (PDT) (envelope-from andrewr@brooklyn.slack.net) Received: from localhost (andrewr@localhost) by brooklyn.slack.net (8.8.7/8.8.7) with SMTP id NAA17555; Fri, 26 Jun 1998 13:13:39 -0400 (EDT) Date: Fri, 26 Jun 1998 13:13:39 -0400 (EDT) From: andrewr To: Pierre Beyssac cc: Bill Fenner , Nate Lawson , nate@elite.net, julian@whistle.com, freebsd-bugs@FreeBSD.ORG, freebsd-net@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Apparent bug in sendto() with raw sockets In-Reply-To: <19980626172748.A18953@mars.hsc.fr> 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 too have spoofed packets under FreeBSD, I am just noting somethings that might want to be changed. ***************************************** AWR XNS, Inc. "Drink beer, it will save your life." On Fri, 26 Jun 1998, Pierre Beyssac wrote: > On Fri, Jun 26, 1998 at 09:38:33AM -0400, andrewr wrote: > > Speaking of IP_HDRINCL, after reading raw_ip.c and noticing the protection > > against spoofing (can't use IP_HDRINCL in certain situations), I started > > thinking about actually comparing the user dsupplied ip->ip_src with the > > Are you sure you're talking about FreeBSD here ? SunOS 4 has such > a protection (it checks that the source address belongs to one of > the interfaces, or so it seems) but I've successfully spoofed > packets on FreeBSD without any problem using IP_HDRINCL. > > Anyway, such a protection can easily bypassed by sending raw > link-level packets through bpf (or probably /dev/nit in the case > of SunOS, although I've never tried this). > -- > Pierre.Beyssac@hsc.fr > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" 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 Fri Jun 26 10:13:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13160 for freebsd-net-outgoing; Fri, 26 Jun 1998 10:13:27 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from heron.doc.ic.ac.uk (QIR9ioBVavbFpvjn64N2K8izYrm5ZaUb@heron.doc.ic.ac.uk [146.169.46.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA12980 for ; Fri, 26 Jun 1998 10:12:07 -0700 (PDT) (envelope-from njs3@doc.ic.ac.uk) Received: from oak74.doc.ic.ac.uk [146.169.46.74] ([CY/0IoQbBlzEssdi1ALafW1eXaYlEI4m]) by heron.doc.ic.ac.uk with smtp (Exim 1.62 #3) id 0ypc2W-0000KZ-00; Fri, 26 Jun 1998 18:11:56 +0100 Received: from njs3 by oak74.doc.ic.ac.uk with local (Exim 1.62 #3) id 0ypc2V-0006Wh-00; Fri, 26 Jun 1998 18:11:55 +0100 From: njs3@doc.ic.ac.uk (Niall Smart) Date: Fri, 26 Jun 1998 18:11:54 +0100 In-Reply-To: Bill Fenner "Re: Apparent bug in sendto() with raw sockets" (Jun 26, 9:58am) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Bill Fenner , njs3@doc.ic.ac.uk Subject: Re: Apparent bug in sendto() with raw sockets Cc: freebsd-net@FreeBSD.ORG, julian@whistle.com, nate@almond.elite.net Message-Id: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Jun 26, 9:58am, Bill Fenner wrote: } Subject: Re: Apparent bug in sendto() with raw sockets > >I'm not so sure [compatability is] so important in this case. > > As I said before, I'm worried about externally-written programs, > particularly about externally-written programs that are not distributed > with source (like pathchar). > > I'd also like to see a definitive way to tell which order the kernel is > expecting, so that externally-written programs that want to be portable > (like, for example, mrouted, mrinfo, mtrace, rsvpd, etc.) don't have to > use __FreeBSD_version. Well, then they would need to go #ifdef __FreeBSD to see if that interface was available =) The convention of using network byte order is sufficient imho niall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jun 26 10:38:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20088 for freebsd-net-outgoing; Fri, 26 Jun 1998 10:38:44 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from alpha.xerox.com (omega.Xerox.COM [13.1.64.95]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA19996 for ; Fri, 26 Jun 1998 10:38:20 -0700 (PDT) (envelope-from fenner@parc.xerox.com) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <40757(2)>; Fri, 26 Jun 1998 10:37:44 PDT Received: by crevenia.parc.xerox.com id <177515>; Fri, 26 Jun 1998 10:37:25 -0700 From: Bill Fenner To: fenner@parc.xerox.com, njs3@doc.ic.ac.uk Subject: Re: Apparent bug in sendto() with raw sockets Cc: freebsd-net@FreeBSD.ORG, julian@whistle.com, nate@almond.elite.net Message-Id: <98Jun26.103725pdt.177515@crevenia.parc.xerox.com> Date: Fri, 26 Jun 1998 10:37:23 PDT Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >The convention of using network byte order is sufficient imho If we were designing this interface from scratch, I'd say you were right. However, what we're really doing is changing a 9 year old poorly-designed interface. Changing an interface that has been in existence and use for 9 years in a completely incompatible way requires some care. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jun 26 13:18:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22671 for freebsd-net-outgoing; Fri, 26 Jun 1998 13:18:48 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from almond.elite.net (root@almond.elite.net [205.199.220.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22646; Fri, 26 Jun 1998 13:18:40 -0700 (PDT) (envelope-from nate@almond.elite.net) Received: (from nate@localhost) by almond.elite.net (8.8.3/ELITE) id NAA08152; Fri, 26 Jun 1998 13:18:29 -0700 (PDT) From: Nate Lawson Message-Id: <199806262018.NAA08152@almond.elite.net> Subject: Re: sendto()/raw sockets and now spoofing To: andrewr@slack.net (andrewr) Date: Fri, 26 Jun 1998 13:18:29 -0700 (PDT) Cc: Pierre.Beyssac@hsc.fr, fenner@parc.xerox.com, nate@elite.net, julian@whistle.com, freebsd-bugs@FreeBSD.ORG, freebsd-net@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "andrewr" at Jun 26, 98 01:13:39 pm X-Mailer: ELM [version 2.4 PL25] 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 >On Fri, 26 Jun 1998, Pierre Beyssac wrote: >> On Fri, Jun 26, 1998 at 09:38:33AM -0400, andrewr wrote: >> > Speaking of IP_HDRINCL, after reading raw_ip.c and noticing the protection >> > against spoofing (can't use IP_HDRINCL in certain situations), I started >> > thinking about actually comparing the user dsupplied ip->ip_src with the >> >> Are you sure you're talking about FreeBSD here ? SunOS 4 has such >> a protection (it checks that the source address belongs to one of >> the interfaces, or so it seems) but I've successfully spoofed >> packets on FreeBSD without any problem using IP_HDRINCL. >> >> Anyway, such a protection can easily bypassed by sending raw >> link-level packets through bpf (or probably /dev/nit in the case >> of SunOS, although I've never tried this). > >I too have spoofed packets under FreeBSD, I am just noting somethings that >might want to be changed. The whole point of IP_HDRINCL is to allow the (privileged) user to supply their own IP header. There should be no code to prevent spoofing because it is quite necessary to be able to write arbitrary parts of the IP header. A DHCP server is a perfect example of a program that must "spoof" its source address. How far do you start to go with this crusade? Do you then go on and verify ip_id is appropriate? What about making sure ip_p isn't equal to ANY of the known protocols since they are accessible through the ordinary sockets interface? If you put the checks in sendto(), I'll be forced to use BPF for my tools. If you put the checks in BPF too, I'll be forced to include an LKM that patches your BPF which ... An operating system provides a layer of abstraction from the hardware that provides protection -- you have this understanding right. But when a properly authenticated and privileged user (root in this case) uses an OS mechanism, IP_HDRINCL, to circumvent these checks, that user takes responsibility for the behavior of his code by explicitly forgoing the normal OS checks. This is the part you were missing. -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jun 26 13:35:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA25290 for freebsd-net-outgoing; Fri, 26 Jun 1998 13:35:03 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from brooklyn.slack.net (root@brooklyn.slack.net [206.41.21.102]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA25179; Fri, 26 Jun 1998 13:34:29 -0700 (PDT) (envelope-from andrewr@brooklyn.slack.net) Received: from localhost (andrewr@localhost) by brooklyn.slack.net (8.8.7/8.8.7) with SMTP id QAA24846; Fri, 26 Jun 1998 16:37:38 -0400 (EDT) Date: Fri, 26 Jun 1998 16:37:38 -0400 (EDT) From: andrewr To: Nate Lawson cc: Pierre.Beyssac@hsc.fr, fenner@parc.xerox.com, nate@elite.net, julian@whistle.com, freebsd-bugs@FreeBSD.ORG, freebsd-net@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: sendto()/raw sockets and now spoofing In-Reply-To: <199806262018.NAA08152@almond.elite.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 I agree with nate on this, and is why I stopped in the middle of my coding. I only coded the dumb ip_src checker, and I stopped there. I thought to my self "Uhm, who would be spoofing the packets?? Root, most likely.. 'doh'" And I stopped. Andrew ***************************************** AWR XNS, Inc. "Drink beer, it will save your life." On Fri, 26 Jun 1998, Nate Lawson wrote: > >On Fri, 26 Jun 1998, Pierre Beyssac wrote: > >> On Fri, Jun 26, 1998 at 09:38:33AM -0400, andrewr wrote: > >> > Speaking of IP_HDRINCL, after reading raw_ip.c and noticing the protection > >> > against spoofing (can't use IP_HDRINCL in certain situations), I started > >> > thinking about actually comparing the user dsupplied ip->ip_src with the > >> > >> Are you sure you're talking about FreeBSD here ? SunOS 4 has such > >> a protection (it checks that the source address belongs to one of > >> the interfaces, or so it seems) but I've successfully spoofed > >> packets on FreeBSD without any problem using IP_HDRINCL. > >> > >> Anyway, such a protection can easily bypassed by sending raw > >> link-level packets through bpf (or probably /dev/nit in the case > >> of SunOS, although I've never tried this). > > > >I too have spoofed packets under FreeBSD, I am just noting somethings that > >might want to be changed. > > The whole point of IP_HDRINCL is to allow the (privileged) user to supply > their own IP header. There should be no code to prevent spoofing because it > is quite necessary to be able to write arbitrary parts of the IP header. > A DHCP server is a perfect example of a program that must "spoof" its source > address. > > How far do you start to go with this crusade? Do you then go on and verify > ip_id is appropriate? What about making sure ip_p isn't equal to ANY of the > known protocols since they are accessible through the ordinary sockets > interface? > > If you put the checks in sendto(), I'll be forced to use BPF for my tools. If > you put the checks in BPF too, I'll be forced to include an LKM that patches > your BPF which ... > > An operating system provides a layer of abstraction from the hardware that > provides protection -- you have this understanding right. But when a properly > authenticated and privileged user (root in this case) uses an OS mechanism, > IP_HDRINCL, to circumvent these checks, that user takes responsibility for the > behavior of his code by explicitly forgoing the normal OS checks. This is the > part you were missing. > > -Nate > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jun 26 14:01:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00806 for freebsd-net-outgoing; Fri, 26 Jun 1998 14:01:48 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00465; Fri, 26 Jun 1998 14:00:23 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id NAA22834; Fri, 26 Jun 1998 13:59:48 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma022830; Fri Jun 26 13:59:25 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id NAA01163; Fri, 26 Jun 1998 13:59:25 -0700 (PDT) From: Archie Cobbs Message-Id: <199806262059.NAA01163@bubba.whistle.com> Subject: Re: Apparent bug in sendto() with raw sockets In-Reply-To: from Niall Smart at "Jun 26, 98 02:04:38 pm" To: njs3@doc.ic.ac.uk (Niall Smart) Date: Fri, 26 Jun 1998 13:59:25 -0700 (PDT) Cc: fenner@parc.xerox.com, julian@whistle.com, nate@almond.elite.net, freebsd-bugs@FreeBSD.ORG, freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (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 Niall Smart writes: > On Jun 25, 11:40am, Bill Fenner wrote: > } Subject: Re: Apparent bug in sendto() with raw sockets > > In message you w > > interface, which requires length and offset in host order. AFAIK, > > this original implementation happened on suns, which is why nobody > > noticed at the time. We are compatible with this original > > implementation. OpenBSD and Linux chose to change the semantics > > to the ones that are less surprising but not backwards compatible. > > I think its more important to be correct in this area, raw sockets > programming can be tricky enough without what will seem to the > user like gratuitous changes. If Linux and OpenBSD have done it, > thats all the more reason to go for it... I agree.. and there's a precedent for this. The BPF code had a similar bug, where you would read an IP packet and get some of the header fields reversed. This was fixed in FreeBSD sometime in the Summer of '96 I believe (north america, that is :-) -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jun 26 14:05:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01514 for freebsd-net-outgoing; Fri, 26 Jun 1998 14:05:02 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA01145; Fri, 26 Jun 1998 14:03:24 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id OAA22869; Fri, 26 Jun 1998 14:02:48 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma022865; Fri Jun 26 14:02:44 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id OAA01182; Fri, 26 Jun 1998 14:02:44 -0700 (PDT) From: Archie Cobbs Message-Id: <199806262102.OAA01182@bubba.whistle.com> Subject: Re: Apparent bug in sendto() with raw sockets In-Reply-To: from andrewr at "Jun 26, 98 09:38:33 am" To: andrewr@slack.net (andrewr) Date: Fri, 26 Jun 1998 14:02:44 -0700 (PDT) Cc: fenner@parc.xerox.com, nate@almond.elite.net, nate@elite.net, julian@whistle.com, freebsd-bugs@FreeBSD.ORG, freebsd-net@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (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 andrewr writes: > Speaking of IP_HDRINCL, after reading raw_ip.c and noticing the protection > against spoofing (can't use IP_HDRINCL in certain situations), I started > thinking about actually comparing the user dsupplied ip->ip_src with the > actual IP address defined for the outgoing interface. While looking for a What's wrong with being able to spoof an IP address? If I have root access (required to open a raw socket), and I want to do so, the kernel shouldn't prevent me. There are legitimate reasons for wanting to send spoofed source IP addresses (eg, testing situations). -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jun 26 14:39:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10072 for freebsd-net-outgoing; Fri, 26 Jun 1998 14:39:36 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from alpha.xerox.com (omega.Xerox.COM [13.1.64.95]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA09990 for ; Fri, 26 Jun 1998 14:39:10 -0700 (PDT) (envelope-from fenner@parc.xerox.com) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <40766(2)>; Fri, 26 Jun 1998 14:38:29 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <177515>; Fri, 26 Jun 1998 14:38:24 -0700 To: Archie Cobbs cc: freebsd-net@FreeBSD.ORG Subject: Re: Apparent bug in sendto() with raw sockets In-reply-to: Your message of "Fri, 26 Jun 98 13:59:25 PDT." <199806262059.NAA01163@bubba.whistle.com> Date: Fri, 26 Jun 1998 14:38:22 PDT From: Bill Fenner Message-Id: <98Jun26.143824pdt.177515@crevenia.parc.xerox.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199806262059.NAA01163@bubba.whistle.com> Archie Cobbs wrote: >The BPF code had a similar bug, where you would read an IP packet >and get some of the header fields reversed. This is not a bug in the code. This is a bug in the interface. The BPF interface gives you the packet as it appears on the wire, so it's a bug for BPF not to do that. The raw IP interface exposes the ip_output() interface as protocols would use it, and the demuxed protocol interface as ip_input() passes packets to protocols. If we want to change the raw IP interface to "exactly as the packet appears on the wire", then that is a change in the interface and has to be handled much more carefully than a bug fix. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jun 26 15:22:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16985 for freebsd-net-outgoing; Fri, 26 Jun 1998 15:22:35 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16914 for ; Fri, 26 Jun 1998 15:21:20 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id PAA23825; Fri, 26 Jun 1998 15:20:20 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma023819; Fri Jun 26 15:20:05 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id PAA14578; Fri, 26 Jun 1998 15:20:05 -0700 (PDT) From: Archie Cobbs Message-Id: <199806262220.PAA14578@bubba.whistle.com> Subject: Re: Apparent bug in sendto() with raw sockets In-Reply-To: <98Jun26.143824pdt.177515@crevenia.parc.xerox.com> from Bill Fenner at "Jun 26, 98 02:38:22 pm" To: fenner@parc.xerox.com (Bill Fenner) Date: Fri, 26 Jun 1998 15:20:05 -0700 (PDT) Cc: freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (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 Bill Fenner writes: > protocol interface as ip_input() passes packets to protocols. If we > want to change the raw IP interface to "exactly as the packet appears > on the wire", then that is a change in the interface and has to be > handled much more carefully than a bug fix. That's what I always took "raw packet" to mean.. exactly as the packet appears on the wire. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jun 26 16:06:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA21993 for freebsd-net-outgoing; Fri, 26 Jun 1998 16:06:08 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from roma.coe.ufrj.br (jonny@roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA21924 for ; Fri, 26 Jun 1998 16:05:38 -0700 (PDT) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id UAA08481 for net@freebsd.org; Fri, 26 Jun 1998 20:05:29 -0300 (EST) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199806262305.UAA08481@roma.coe.ufrj.br> Subject: arpproxy_all To: net@FreeBSD.ORG Date: Fri, 26 Jun 1998 20:05:29 -0300 (EST) X-Mailer: ELM [version 2.4ME+ PL40 (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, Is there a recipe on how to use arpproxy_all ? I think I'll need it, but could find no references about it anywhere. Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Jun 27 00:18:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA27211 for freebsd-net-outgoing; Sat, 27 Jun 1998 00:18:16 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from smtp03.primenet.com (daemon@smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA27115; Sat, 27 Jun 1998 00:18:05 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id AAA04404; Sat, 27 Jun 1998 00:18:04 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp03.primenet.com, id smtpd004394; Sat Jun 27 00:17:57 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id AAA22908; Sat, 27 Jun 1998 00:17:47 -0700 (MST) From: Terry Lambert Message-Id: <199806270717.AAA22908@usr08.primenet.com> Subject: Re: Apparent bug in sendto() with raw sockets To: archie@whistle.com (Archie Cobbs) Date: Sat, 27 Jun 1998 07:17:47 +0000 (GMT) Cc: andrewr@slack.net, fenner@parc.xerox.com, nate@almond.elite.net, nate@elite.net, julian@whistle.com, freebsd-bugs@FreeBSD.ORG, freebsd-net@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199806262102.OAA01182@bubba.whistle.com> from "Archie Cobbs" at Jun 26, 98 02:02:44 pm X-Mailer: ELM [version 2.4 PL25] 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 > > Speaking of IP_HDRINCL, after reading raw_ip.c and noticing the protection > > against spoofing (can't use IP_HDRINCL in certain situations), I started > > thinking about actually comparing the user dsupplied ip->ip_src with the > > actual IP address defined for the outgoing interface. While looking for a > > What's wrong with being able to spoof an IP address? If I have root > access (required to open a raw socket), and I want to do so, the kernel > shouldn't prevent me. There are legitimate reasons for wanting to send > spoofed source IP addresses (eg, testing situations). A number of "netnanny" packages rely on being able to say "host unreachable" in response to a request before the (actually reachable) site is able to respond with the information. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Jun 27 21:33:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22834 for freebsd-net-outgoing; Sat, 27 Jun 1998 21:33:26 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from roma.coe.ufrj.br (jonny@roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA22829 for ; Sat, 27 Jun 1998 21:33:23 -0700 (PDT) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id BAA22277 for net@freebsd.org; Sun, 28 Jun 1998 01:33:22 -0300 (EST) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199806280433.BAA22277@roma.coe.ufrj.br> Subject: mrouting and ioctl(SIOCGETVIFCNT) To: net@FreeBSD.ORG Date: Sun, 28 Jun 1998 01:33:22 -0300 (EST) X-Mailer: ELM [version 2.4ME+ PL40 (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'm trying to use ioctl SIOCGETVIFCNT to get traffic statistics on multicast vifs. But my results are very strange: vif0, inp=12573, inb=503855516, outp=35900, outb=1835387904 vif1, inp=35900, inb=1835387904, outp=11262, outb=462654994 vif2, inp=0, inb=0, outp=1039, outb=34649536 vif3, inp=0, inb=0, outp=0, outb=0 On vif2, for example, suppose it has really sent 34649536 bytes, using 1039 packets. The average packet size would be 33348 ! No, this is not real... Is there a known bug in kernel ? It seems to be some kind of host/network format conversion. The program couldn't be simpler (stripping includes): void main( void ) { int vif; int s; struct sioc_vif_req vr; if ( ( s = socket( AF_INET, SOCK_DGRAM, 0 ) ) < 0 ) err( 1, "Cannot open control socket" ); vif = 0; while ( 1 ) { vr.vifi = vif; if ( ioctl( s, SIOCGETVIFCNT, &vr ) < 0 ) { if ( errno == EINVAL ) break; err( 2, "socket(SIOCGETVIFCNT)" ); } printf( "vif%d, inp=%lu, inb=%lu, outp=%lu, outb=%lu\n", vif, vr.icount, vr.ibytes, vr.ocount, vr.obytes ); ++vif; } close( s ); } Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message