From owner-freebsd-net Sun Jan 23 0:30:30 2000 Delivered-To: freebsd-net@freebsd.org Received: from entic.net (shell.entic.net [209.157.122.66]) by hub.freebsd.org (Postfix) with SMTP id DB30F15028 for ; Sun, 23 Jan 2000 00:30:27 -0800 (PST) (envelope-from aj@entic.net) Received: (qmail 14149 invoked by uid 1000); 23 Jan 2000 08:30:30 -0000 Date: Sun, 23 Jan 2000 00:30:30 -0800 (PST) From: Anil Jangity To: net@freebsd.org Subject: nfs ports 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 Is there a descritipion of all the sysctls available on the web? I am trying to setup my IPfilters and NFS. I was wondering what the vfs.nfs.nfs_privport sysctl does. I am guessing it has something to do with the ports NFS uses or listens on (;-)) but setting it to 0 and 1 resulted in the same filter logs: vfs.nfs.nfs_privport: 0 23/01/2000 00:12:34.859266 fxp0 @0:18 p A.B.C.67,664 -> A.B.C.69,111 PR udp len 20 84 IN 23/01/2000 00:12:34.860216 fxp0 @0:18 p A.B.C.67,663 -> A.B.C.69,111 PR udp len 20 84 IN 23/01/2000 00:12:34.861003 fxp0 @0:18 p A.B.C.67,662 -> A.B.C.69,2049 PR udp len 20 68 IN 23/01/2000 00:12:34.861583 fxp0 @0:18 p A.B.C.67,661 -> A.B.C.69,111 PR udp len 20 84 IN 23/01/2000 00:12:34.862554 fxp0 @0:18 p A.B.C.67,660 -> A.B.C.69,998 PR udp len 20 148 IN 23/01/2000 00:12:34.863924 fxp0 @0:18 p A.B.C.67,659 -> A.B.C.69,2049 PR udp len 20 148 IN vfs.nfs.nfs_privport: 1 23/01/2000 00:14:36.845852 fxp0 @0:18 p A.B.C.67,654 -> A.B.C.69,111 PR udp len 20 84 IN 23/01/2000 00:14:36.846794 fxp0 @0:18 p A.B.C.67,653 -> A.B.C.69,111 PR udp len 20 84 IN 23/01/2000 00:14:36.847567 fxp0 @0:18 p A.B.C.67,652 -> A.B.C.69,2049 PR udp len 20 68 IN 23/01/2000 00:14:36.848147 fxp0 @0:18 p A.B.C.67,651 -> A.B.C.69,111 PR udp len 20 84 IN 23/01/2000 00:14:36.849110 fxp0 @0:18 p A.B.C.67,650 -> A.B.C.69,998 PR udp len 20 148 IN 23/01/2000 00:14:36.850477 fxp0 @0:18 p A.B.C.67,649 -> A.B.C.69,2049 PR udp len 20 148 IN I need the filter to be as secure as possible with NFS. Any hints will be welcome. Thanks. -Anil To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Jan 23 2:31:54 2000 Delivered-To: freebsd-net@freebsd.org Received: from awfulhak.org (dynamic-120.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.248]) by hub.freebsd.org (Postfix) with ESMTP id 132DF14DFD for ; Sun, 23 Jan 2000 02:31:51 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id KAA23203; Sun, 23 Jan 2000 10:09:03 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id KAA53664; Sun, 23 Jan 2000 10:09:03 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200001231009.KAA53664@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: ROsteen Cc: freebsd-net@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: unix doskey type program In-Reply-To: Message from ROsteen of "Sat, 22 Jan 2000 22:06:42 EST." <388A7042.AAE33988@elpn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 23 Jan 2000 10:09:03 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Can anyone tell me the name of a program that will allow me to recall > past commands like an up arrow or something? This should have been asked on -questions or -newbies. Type ``set -o emacs''. > thanks, > Rick -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Jan 23 9:53:54 2000 Delivered-To: freebsd-net@freebsd.org Received: from altair.origenbio.com (altair.origenbio.com [216.30.62.130]) by hub.freebsd.org (Postfix) with ESMTP id BD4BC14C88 for ; Sun, 23 Jan 2000 09:53:52 -0800 (PST) (envelope-from dmartin@origen.com) Received: from origen.com (dubhe.origen [192.168.0.5]) by altair.origenbio.com (8.9.3/8.9.3) with ESMTP id LAA23748; Sun, 23 Jan 2000 11:53:48 -0600 (CST) (envelope-from dmartin@origen.com) Message-ID: <388B3FE9.B5125D18@origen.com> Date: Sun, 23 Jan 2000 11:52:41 -0600 From: Richard Martin X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: ROsteen Cc: freebsd-net@FreeBSD.ORG Subject: Re: unix doskey type program References: <388A7042.AAE33988@elpn.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Rick, If you use the bash shell, it has both filename completion (type a few letters of the filename and hit the tab to complete the rest) as well as a .bash_history file where you can recall/scroll thru the last 50 or so commands you have completed. bash name completion also works on commands: typing umo[tab] puts umount on the command line. Find our where bash is (probably in /usr/local/bin/bash) and use chsh to change your shell. Use a .bash_profile and .bashrc in your home directory to set aliases and customize your prompt. I find it hand to have the last bit of the directory name in the prompt line. Holler if you need a screed for these. -- Richard Martin dmartin@origen.com OriGen Biomedical Tel: +1 512 474 7278 2525 Hartford Rd. Fax: +1 512 708 8522 Austin, TX 78703 http://www.cardiacdocs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Jan 23 14:47:54 2000 Delivered-To: freebsd-net@freebsd.org Received: from valis.olywa.net (valis.olywa.net [216.173.192.2]) by hub.freebsd.org (Postfix) with ESMTP id ACDFA14D18 for ; Sun, 23 Jan 2000 14:47:51 -0800 (PST) (envelope-from william.a@carrel.org) Received: from [216.173.212.205] by valis.olywa.net (Post.Office MTA v3.5.3 release 223 ID# 0-56662U5000L500S0V35) with ESMTP id net for ; Sun, 23 Jan 2000 14:47:51 -0800 User-Agent: Microsoft Outlook Express Macintosh Edition - 5.01 (1630) Date: Sun, 23 Jan 2000 14:47:51 -0800 Subject: PR: kern/16318 From: William Carrel To: Message-ID: 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 screwed up when I filed this so it wound up under pending, but it is a kernel patch that corrects some misbehavior by the ifa_ifwithroute(). It is quite possible that the routing table has a better idea where packets should be going than the interfaces do, so it makes sense to ask. This corrects a problem I have on my setup where there is a point-to-point connection on one interface with an address that happens to be on another. xx1: 10.0.0.2/32 xx0: 10.0.0.2/24 route add 10.0.0.1/32 -interface xx1 -cloning route add default 10.0.0.1 Under the old code, the default route would go to xx0, under the new code it goes to xx1 like it should according to the static routes that have been added. I've done testing and come up clean on this. If anyone else wants to double check this they are more than welcome. The unified diff is in the PR. It is worth noting that, at least from looking at the code, NetBSD and OpenBSD also suffer this same bug and could probably benefit from the exact same patch. -- William Carrel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Jan 23 21:32:51 2000 Delivered-To: freebsd-net@freebsd.org Received: from Dolinca.IBC.IskraSistemi.SI (Dolinca.IBC.IskraSistemi.Si [194.249.213.241]) by hub.freebsd.org (Postfix) with ESMTP id B9EDF157A3 for ; Sun, 23 Jan 2000 21:32:43 -0800 (PST) (envelope-from brodnik@Dolinca.IBC.IskraSistemi.SI) Received: (from brodnik@localhost) by Dolinca.IBC.IskraSistemi.SI (8.9.3/8.9.3) id GAA94403; Mon, 24 Jan 2000 06:45:27 GMT (envelope-from brodnik) From: Andrej Brodnik (Andy) Message-Id: <200001240645.GAA94403@Dolinca.IBC.IskraSistemi.SI> Subject: Re: unix doskey type program In-Reply-To: <388B3FE9.B5125D18@origen.com> from Richard Martin at "Jan 23, 2000 11:52:41 am" To: dmartin@origen.com (Richard Martin) Date: Mon, 24 Jan 2000 07:45:27 +0100 (CET) Cc: rosteen@elpn.com (ROsteen), freebsd-net@FreeBSD.ORG Organization: IBC, Iskra Systems Reply-To: Andrej.Brodnik@IBC.IskraSistemi.SI (Andrej Brodnik (Andy)) X-Mailer: ELM [version 2.4ME+ PL54 (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 there, > Date: Sun, 23 Jan 2000 11:52:41 -0600 > From: Richard Martin > Subject: Re: unix doskey type program > > If you use the bash shell, it has both filename completion (type a few letters > of the filename and hit the tab to complete the rest) as well as a > .bash_history file where you can recall/scroll thru the last 50 or so commands > you have completed. bash name completion also works on commands: typing > umo[tab] puts umount on the command line. > > Find our where bash is (probably in /usr/local/bin/bash) and use chsh to > change your shell. Use a .bash_profile and .bashrc in your home directory to > set aliases and customize your prompt. I find it hand to have the last bit of > the directory name in the prompt line. Holler if you need a screed for these. The same goes for the tcsh. The tcsh shell is /usr/local/bin/tcsh (you have to install it first through ports, of course). LPA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jan 24 9: 8: 5 2000 Delivered-To: freebsd-net@freebsd.org Received: from mx01-ext.netapp.com (mx01-ext.netapp.com [198.95.224.34]) by hub.freebsd.org (Postfix) with SMTP id D02F615B26 for ; Mon, 24 Jan 2000 09:07:50 -0800 (PST) (envelope-from jeff.mohler@netapp.com) Received: (qmail 25809 invoked from network); 24 Jan 2000 17:10:06 -0000 Received: from herra.netapp.com (HELO herra.corp.netapp.com) (198.95.224.184) by mx01-ext.netapp.com with SMTP; 24 Jan 2000 17:10:06 -0000 Received: from tahoe.corp.netapp.com (tahoe.netapp.com [10.10.10.112]) by herra.corp.netapp.com (8.9.3/8.9.3/NTAP-1.0) with ESMTP id JAA07790 for ; Mon, 24 Jan 2000 09:07:46 -0800 (PST) Received: by tahoe.corp.netapp.com with Internet Mail Service (5.5.2650.21) id ; Mon, 24 Jan 2000 09:07:46 -0800 Message-ID: <242EA98B2B7DD311985A0090277AED5101355B73@CLEARCREEK.corp.netapp.com> From: "Mohler, Jeff" To: "'freebsd-net@freebsd.org'" Subject: NFS Performance Date: Mon, 24 Jan 2000 09:13:58 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greetings: I need to use a Fbsd box to do a 1Tb data migration via NFS between two NetApp boxes, and unfortunately the NetApp tools such as 'vol copy' are not applicable. Ive used Fbsd for years, but have never thought much about tuning NFS for maximum thruput. I hope to be using the Alteon Gig-E card(s) in the Fbsd box, this is a P3/550/256Mb system. Questions: 1) Will the box perform better with ONE card doing reads from one box, and the other writing to the destination filer? Or one card doing both. (mainly a question about how will the data work best..across the bus, or within the same card during the Xfer) 2) Specific kernel tricks to enhance data movement. The data set isnt all large files, but a large free WWW hosting site, tons of small files as well as www server logs for thousands of virtual servers. 3) Can anyone reccomend perhaps a better card than the Alteon? We stopped using the Alteon at NetApp because of it's overall dismal performance. The Intel GigE card would be quite nice..if I had a choice. Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jan 24 9:35:53 2000 Delivered-To: freebsd-net@freebsd.org Received: from goodnet.com (goodnet.com [207.98.129.1]) by hub.freebsd.org (Postfix) with ESMTP id A1F24151A4 for ; Mon, 24 Jan 2000 09:35:27 -0800 (PST) (envelope-from weyrich@goodnet.com) Received: from localhost (weyrich@localhost) by goodnet.com with ESMTP id KAA16593; Mon, 24 Jan 2000 10:35:12 -0700 (MST) Date: Mon, 24 Jan 2000 10:35:12 -0700 (MST) From: Weyrich Computing Consulting To: "Mohler, Jeff" Cc: "'freebsd-net@freebsd.org'" Subject: Re: NFS Performance In-Reply-To: <242EA98B2B7DD311985A0090277AED5101355B73@CLEARCREEK.corp.netapp.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 My first reaction is to question your premise that you need to use NFS to do this -- running find into a cpio pipe across the network is much more efficient, since individual file operations are not being done across the network. orville. On Mon, 24 Jan 2000, Mohler, Jeff wrote: > Date: Mon, 24 Jan 2000 09:13:58 -0800 > From: "Mohler, Jeff" > To: "'freebsd-net@freebsd.org'" > Subject: NFS Performance > > Greetings: > > I need to use a Fbsd box to do a 1Tb data migration via NFS between two NetApp > boxes, and unfortunately the NetApp tools such as 'vol copy' are not applicable. > > Ive used Fbsd for years, but have never thought much about tuning NFS for > maximum thruput. > > I hope to be using the Alteon Gig-E card(s) in the Fbsd box, this is a > P3/550/256Mb system. > > Questions: > > 1) Will the box perform better with ONE card doing reads from one box, and the > other writing to the destination filer? Or one card doing both. (mainly a > question about how will the data work best..across the bus, or within the same > card during the Xfer) > > 2) Specific kernel tricks to enhance data movement. The data set isnt all > large files, but a large free WWW hosting site, tons of small files as well as > www server logs for thousands of virtual servers. > > 3) Can anyone reccomend perhaps a better card than the Alteon? We stopped > using the Alteon at NetApp because of it's overall dismal performance. The > Intel GigE card would be quite nice..if I had a choice. > > Thanks > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > ------------------------------------------------------------------- Orville R. Weyrich, Jr. Weyrich Computer Consulting mailto:orville@weyrich.com KD7HJV http://www.weyrich.com ------------------------------------------------------------------- Visit our online collection of book reviews: http://www.weyrich.com/book_reviews/ Ask about our world wide web services! ------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jan 24 9:37:32 2000 Delivered-To: freebsd-net@freebsd.org Received: from mx01-ext.netapp.com (mx01-ext.netapp.com [198.95.224.34]) by hub.freebsd.org (Postfix) with SMTP id 618B81597C for ; Mon, 24 Jan 2000 09:36:35 -0800 (PST) (envelope-from jeff.mohler@netapp.com) Received: (qmail 13945 invoked from network); 24 Jan 2000 17:38:48 -0000 Received: from herra.netapp.com (HELO herra.corp.netapp.com) (198.95.224.184) by mx01-ext.netapp.com with SMTP; 24 Jan 2000 17:38:48 -0000 Received: from tahoe.corp.netapp.com (tahoe.netapp.com [10.10.10.112]) by herra.corp.netapp.com (8.9.3/8.9.3/NTAP-1.0) with ESMTP id JAA14160; Mon, 24 Jan 2000 09:36:24 -0800 (PST) Received: by tahoe.corp.netapp.com with Internet Mail Service (5.5.2650.21) id ; Mon, 24 Jan 2000 09:36:21 -0800 Message-ID: <242EA98B2B7DD311985A0090277AED5101355B79@CLEARCREEK.corp.netapp.com> From: "Mohler, Jeff" To: "'Weyrich Computing Consulting'" Cc: "'freebsd-net@freebsd.org'" Subject: RE: NFS Performance Date: Mon, 24 Jan 2000 09:42:29 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Yes, Network Appliance boxes are not actual servers, just network attached data. The only way in or out is via NFS or CIFS. -----Original Message----- From: Weyrich Computing Consulting [mailto:weyrich@goodnet.com] Sent: Monday, January 24, 2000 9:35 AM To: Mohler, Jeff Cc: 'freebsd-net@freebsd.org' Subject: Re: NFS Performance My first reaction is to question your premise that you need to use NFS to do this -- running find into a cpio pipe across the network is much more efficient, since individual file operations are not being done across the network. orville. On Mon, 24 Jan 2000, Mohler, Jeff wrote: > Date: Mon, 24 Jan 2000 09:13:58 -0800 > From: "Mohler, Jeff" > To: "'freebsd-net@freebsd.org'" > Subject: NFS Performance > > Greetings: > > I need to use a Fbsd box to do a 1Tb data migration via NFS between two NetApp > boxes, and unfortunately the NetApp tools such as 'vol copy' are not applicable. > > Ive used Fbsd for years, but have never thought much about tuning NFS for > maximum thruput. > > I hope to be using the Alteon Gig-E card(s) in the Fbsd box, this is a > P3/550/256Mb system. > > Questions: > > 1) Will the box perform better with ONE card doing reads from one box, and the > other writing to the destination filer? Or one card doing both. (mainly a > question about how will the data work best..across the bus, or within the same > card during the Xfer) > > 2) Specific kernel tricks to enhance data movement. The data set isnt all > large files, but a large free WWW hosting site, tons of small files as well as > www server logs for thousands of virtual servers. > > 3) Can anyone reccomend perhaps a better card than the Alteon? We stopped > using the Alteon at NetApp because of it's overall dismal performance. The > Intel GigE card would be quite nice..if I had a choice. > > Thanks > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > ------------------------------------------------------------------- Orville R. Weyrich, Jr. Weyrich Computer Consulting mailto:orville@weyrich.com KD7HJV http://www.weyrich.com ------------------------------------------------------------------- Visit our online collection of book reviews: http://www.weyrich.com/book_reviews/ Ask about our world wide web services! ------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jan 24 12:45:17 2000 Delivered-To: freebsd-net@freebsd.org Received: from Brigada-A.Ethereal.RU (Brigada-A.ethereal.ru [195.230.65.30]) by hub.freebsd.org (Postfix) with ESMTP id A55D314E8C for ; Mon, 24 Jan 2000 12:44:12 -0800 (PST) (envelope-from nms@Brigada-A.Ethereal.RU) Received: by Brigada-A.Ethereal.RU (Postfix, from userid 1002) id 55CC6126; Mon, 24 Jan 2000 23:44:01 +0300 (MSK) Received: from Brigada-A.Ethereal.RU (localhost [127.0.0.1]) by Brigada-A.Ethereal.RU (Postfix) with ESMTP id 42116B7 for ; Mon, 24 Jan 2000 23:44:01 +0300 (MSK) To: freebsd-net@freebsd.org Subject: How to connect two computers via nullmodem with netgraph? From: Nikolai Saoukh Date: Mon, 24 Jan 2000 23:43:56 +0300 Message-Id: <20000124204401.55CC6126@Brigada-A.Ethereal.RU> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well, subject say almost all. Samples provided with netgraph in 4.0-CURRENT gives me no clues/tips. Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jan 24 16:13:14 2000 Delivered-To: freebsd-net@freebsd.org Received: from nimitz.ca.sandia.gov (nimitz.ca.sandia.gov [146.246.243.56]) by hub.freebsd.org (Postfix) with ESMTP id 854DA14A07 for ; Mon, 24 Jan 2000 16:13:12 -0800 (PST) (envelope-from bmah@nimitz.ca.sandia.gov) Received: (from bmah@localhost) by nimitz.ca.sandia.gov (8.9.3/8.9.3) id OAA83327; Mon, 24 Jan 2000 14:16:32 -0800 (PST) Message-Id: <200001242216.OAA83327@nimitz.ca.sandia.gov> X-Mailer: exmh version 2.1.1-cvs 10/15/1999 To: freebsd-net@freebsd.org Cc: bmah@CA.Sandia.GOV Subject: pchar-1.1 available 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_-599610112P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Mon, 24 Jan 2000 14:16:32 -0800 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --==_Exmh_-599610112P Content-Type: text/plain; charset=us-ascii I'm pleased to announce the release of pchar-1.1, a reimplementation of Van Jacobson's pathchar utility for characterizing the individual hops of a path between two network hosts. pchar works on both IPv4 and IPv6 networks. pchar has been tested on various versions of FreeBSD, NetBSD, OpenBSD, Linux, IRIX, and OSF/1 (a.k.a Digital UNIX or Tru64), with the primary development on FreeBSD and Solaris. pchar is written in C++, primarily using recent versions of gcc, but with some testing also on the SparcWorks C++ compiler and the IRIX C++ compiler. Recent additions to pchar include: Better compatability with more OSs (in particular, IRIX and OSF). Better IPv6 compatability (on BSDs and glibc systems with integrated IPv6). Numerous small bugfixes and usability enhancements. More information, as well as downloadable source code, can be found at: http://www.ca.sandia.gov/~bmah/Software/pchar/ --==_Exmh_-599610112P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: dbqGIyVYoioWF6IBLzXsTZmMK1XQws2f iQA/AwUBOIzPQNjKMXFboFLDEQJ4PwCdGPKVEawu8B+M3HUX48me2NEPk2AAnRQm SKm5PnS+kLH8j2cI15fkXuqf =J+sa -----END PGP SIGNATURE----- --==_Exmh_-599610112P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jan 24 22:34:45 2000 Delivered-To: freebsd-net@freebsd.org Received: from meer.meer.net (meer.meer.net [140.174.164.2]) by hub.freebsd.org (Postfix) with ESMTP id 40C6A14DAC for ; Mon, 24 Jan 2000 22:34:43 -0800 (PST) (envelope-from gnn@neville-neil.com) Received: from jchurch.meer.net (unknown-35-202.wrs.com [147.11.35.202]) by meer.meer.net (8.9.3/8.9.3/meer) with ESMTP id WAA4559997 for ; Mon, 24 Jan 2000 22:34:41 -0800 (PST) Received: from neville-neil.com (localhost [127.0.0.1]) by jchurch.meer.net (8.9.3/8.9.2) with ESMTP id WAA11550 for ; Mon, 24 Jan 2000 22:37:57 -0800 (PST) (envelope-from gnn@neville-neil.com) Message-Id: <200001250637.WAA11550@jchurch.meer.net> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-net@freebsd.org Subject: TCP connection setup question... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 24 Jan 2000 22:37:57 -0800 From: George Neville-Neil Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Folks, Can anyone tell me why a recieving TCP does not send an ICMP Port Unreachable error if there is no matching PCB for the packet that is received? I looked a bit at Volume II and it just shows that the source does not have this, nor does the FreeBSD 3.3 source. (At least it's not in tcp_input() where we lookup the PCB). Thanks, George To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jan 24 23:45:38 2000 Delivered-To: freebsd-net@freebsd.org Received: from hotmail.com (f27.law7.hotmail.com [216.33.237.27]) by hub.freebsd.org (Postfix) with SMTP id 673131529D for ; Mon, 24 Jan 2000 23:45:34 -0800 (PST) (envelope-from ntvsunix@hotmail.com) Received: (qmail 93688 invoked by uid 0); 25 Jan 2000 07:45:33 -0000 Message-ID: <20000125074533.93687.qmail@hotmail.com> Received: from 209.53.54.44 by www.hotmail.com with HTTP; Mon, 24 Jan 2000 23:45:32 PST X-Originating-IP: [209.53.54.44] From: "Some Person" To: freebsd-newbies@FreeBSD.ORG Cc: freebsd-net@freebsd.org Subject: Network Connectivity Issues/Problems... Date: Mon, 24 Jan 2000 23:45:32 PST Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hey ppl, I'm having some weird weird issues. I have lets say 2 FreeBSD machines (more in reality) @ home, both have two NICs. One NIC on each for the internal LAN via hub, 100Mbs Mactronix - mx0 & mx1 devices (on the problem machine). And the other NICs for external network, ADSL. From say machine A, I can ping machine B fine sometimes, or for a limited time (Machine B, being the one with the problem, and not A.) I can telnet into machine B from A, I can ping B from A, and vice versa then maybe some odd minutes later, or sometimes after a reboot of Machine B, I can't ping B from A. "host down". If I logon to the console of machine B, and ping A then ping from A -> B starts working again. As if the NIC somehow goes into sleep mode? If I'm telnet'd in, leave it there for a while, it'll eventually drop connection. I'm checked the NICs for any IRQ conflicts, changed PCI buses, changed cable, change hub ports, still samething. Does anyone have any ideas, or how I can start to diagnose this more? I'm out of ideas and don't know where else to turn. On the internal LAN, I'm using RFC1918 based IP's, 192.168.x.x/24. FreeBSD 3.4-RELEASE on Machine B and FreeBSD 3.4-STABLE on machine A. Machine B is just a p5-133 w/48megs RAM but running great. No X installed, minimal install. If anyone has any ideas to this or anything, could you please let me know, I'm going nuts trying to figure this out. I need to get this corrected as I plan on having machine B as my NAT router/Firewall/Bastion host, and eventually (jsut for fun) setting up a DMZ with a third NIC. Please CC to my e-mail address, especially if from freebsd-net@freebsd.org as I'm not on the mailing list yet, and can't afford being on too many mailing lists as I'm already swamped in email. Thanks! ntvsunix@hotmail.com ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jan 25 8:32:52 2000 Delivered-To: freebsd-net@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id D3DA014FC3 for ; Tue, 25 Jan 2000 08:32:42 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id RAA09122; Tue, 25 Jan 2000 17:33:11 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200001251633.RAA09122@info.iet.unipi.it> Subject: sysctl net.inet.ip.fw.enable ? To: net@freebsd.org Date: Tue, 25 Jan 2000 17:33:11 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, when you enable bridge_ipfw, (violating bridging vs. routing principles as someone said!), there is a side effect: packets which are both bridged _and_ forwarded to the local stack get through the firewall twice: once in the bridging code, once in the IP stack. This happens for instance with multicast traffic even if there is no local receiver for such traffic, and could have some annoying effects if you are using bridge_ipfw to do traffic shaping. I am not sure what is a good workaround, but one quick hack could be to introduce a sysctl variable, net.inet.ip.fw.enable which controls whether or not ipfw is used in the ip layer. I cannot come up with better ways at the moment, and this one is not totally satisfactory as if you have net.inet.ip.fw.enable=0 net.link.ether.bridge_ipfw=1 the packets to the local stack will NOT go through the firewall. Probably one ought to add an ipfw feature to be able to write rules which match only bridged packets (this is easy). Comments ? cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jan 25 8:58:27 2000 Delivered-To: freebsd-net@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 29A8614EB8 for ; Tue, 25 Jan 2000 08:57:20 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id LAA70043; Tue, 25 Jan 2000 11:57:07 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200001251657.LAA70043@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: George Neville-Neil Cc: freebsd-net@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: TCP connection setup question... References: <200001250637.WAA11550@jchurch.meer.net> In-reply-to: Your message of "Mon, 24 Jan 2000 22:37:57 PST." <200001250637.WAA11550@jchurch.meer.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Jan 2000 11:57:07 -0500 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi Folks, > > Can anyone tell me why a recieving TCP does not send an ICMP Port Unreachable > error if there is no matching PCB for the packet that is received? Probably because the stack must send a TCP reset segment anyway. The ICMP port unreachable would probably be redundant. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jan 25 18:59:25 2000 Delivered-To: freebsd-net@freebsd.org Received: from tomts2-srv.bellnexxia.net (tomts2.bellnexxia.net [209.226.175.140]) by hub.freebsd.org (Postfix) with ESMTP id 13BA514DB7; Tue, 25 Jan 2000 18:59:12 -0800 (PST) (envelope-from drkangel@pathcom.com) Received: from bastardos ([216.209.47.45]) by tomts3-srv.bellnexxia.net (InterMail vM.4.01.02.07 201-229-116-107) with SMTP id <20000126025311.FVGS627.tomts3-srv.bellnexxia.net@bastardos>; Tue, 25 Jan 2000 21:53:11 -0500 From: "Marco Paulo Rodrigues" To: , , Subject: pccard problems.. I think Date: Tue, 25 Jan 2000 21:51:50 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I just recently installed FreeBSd 3.4 on my Thinkpad 390E. I have an IBM Etherjet 10/100. I read the relnotes and it says the 3.4 kernel has support for it in. I check the pccard.conf.sample and found it. Problem is, or maybe i'm doing something wrong is when I boot and it beings to load the daemons, ie portmap (the rc.386 startups) I get an error from pccardd saying """ not found in card database? I've never configued a laptop for FreeBSD so I don't know if these flags are correct in the rc.conf. I'm using the original pccard.conf.sample just renamed to pccard.conf and here is what I have in my rc.conf as of this moment.. pccard_enable="YES" # Set to YES if you want to configure PCCARD devices. pccard_mem="DEFAULT" # If pccard_enable=YES, this is card memory address. pccard_ifconfig="ed0 192.168.0.4" # Specialized pccard ethernet configuration (or NO). pccardd_flags="" # Additional flags for pccardd. Is there anything i'm missing? Any help or guidance would be appreciated. ---------------------------------- Marco Paulo Rodrigues Pathway Communications Phone : (416) 907-2880 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jan 25 22: 6: 7 2000 Delivered-To: freebsd-net@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id DD6DD14A04; Tue, 25 Jan 2000 22:06:02 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from imap.gv.tsc.tdk.com (imap.gv.tsc.tdk.com [192.168.241.198]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id WAA10216; Tue, 25 Jan 2000 22:05:44 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by imap.gv.tsc.tdk.com (8.9.3/8.9.3) with ESMTP id WAA77519; Tue, 25 Jan 2000 22:05:44 -0800 (PST) (envelope-from Don.Lewis@tsc.tdk.com) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id WAA28922; Tue, 25 Jan 2000 22:05:43 -0800 (PST) From: Don Lewis Message-Id: <200001260605.WAA28922@salsa.gv.tsc.tdk.com> Date: Tue, 25 Jan 2000 22:05:43 -0800 In-Reply-To: <4.2.2.20000125113518.01a59100@localhost> References: <4.2.2.20000125095042.01a5aba0@localhost> <200001251722.KAA04527@harmony.village.org> <4.2.2.20000125113518.01a59100@localhost> X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: Brett Glass , Matthew Dillon Subject: Re: Merged patches Cc: security@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Followups to -net only, please. On Jan 25, 11:52am, Brett Glass wrote: } Subject: Re: Merged patches } Switches also make the code more readable and make it easy to handle } every case. Some of the problems we're seeing in this code have been caused } by failure to account for some combinations of the TCP option flags. The best } way to ensure code correctness -- now and for the long term -- is to use } a construct that makes it easy to be sure you cover all the bases! It's } not only good style; it's good insurance. A switch based on the TCP flags would be a very unnatural implementation. For instance, most of the processing done on a packet received on an established connection is the same whether the FIN bit is set or not. If the switch expression was based on the flags, then a large part of the code would be duplicated between these two cases. Also, the code may do some processing on the segment, clear the SYN and/or FIN bits, and then continue. A implementation that used a switch based on the socket state would be somewhat more natural, but this is still not an exact fit. As a matter of fact, if you look at the implemention, this is pretty much what a lot of it does. switch (tp->t_state) { case TCPS_LISTEN: { ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jan 25 22:38:30 2000 Delivered-To: freebsd-net@freebsd.org Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (Postfix) with ESMTP id 8A86014D61; Tue, 25 Jan 2000 22:38:21 -0800 (PST) (envelope-from brett@lariat.org) Received: from mustang (IDENT:ppp0.lariat.org@lariat.lariat.org [206.100.185.2]) by lariat.lariat.org (8.9.3/8.9.3) with ESMTP id XAA18453; Tue, 25 Jan 2000 23:38:11 -0700 (MST) Message-Id: <4.2.2.20000125232750.04074b50@localhost> X-Sender: brett@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Tue, 25 Jan 2000 23:38:09 -0700 To: Don Lewis , Matthew Dillon From: Brett Glass Subject: Re: Merged patches Cc: security@FreeBSD.ORG, freebsd-net@FreeBSD.ORG In-Reply-To: <200001260605.WAA28922@salsa.gv.tsc.tdk.com> References: <4.2.2.20000125113518.01a59100@localhost> <4.2.2.20000125095042.01a5aba0@localhost> <200001251722.KAA04527@harmony.village.org> <4.2.2.20000125113518.01a59100@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 11:05 PM 1/25/2000 , Don Lewis wrote: >A switch based on the TCP flags would be a very unnatural implementation. >For instance, most of the processing done on a packet received on an >established connection is the same whether the FIN bit is set or not. A switch statement can allow the same group of statements to be executed for more than one combination of the flags. >If the switch expression was based on the flags, then a large part of >the code would be duplicated between these two cases. It is also possible to "fall through" from one case to another. This makes the switch statement a very powerful tool for this sort of situation. It is also possible to call a common subroutine. The overhead of a fixed subroutine call is often less than that of a conditional branch on today's CPUs. > Also, the code >may do some processing on the segment, clear the SYN and/or FIN bits, >and then continue. I'd think it would be unusual -- perhaps bad form -- to alter the flags, as it would make the code harder to follow. In what situation(s) would you do this? In any event, one cannot always subsume ALL of the conditional jumps in a routine into a single switch. But one usually CAN reduce the number greatly. Matt seems skeptical, and I am sure that no one will want to change the code much before the freeze. But I'd like to take a shot at rewriting the code, using some switches instead of if statements, after the freeze. I think that it will have several major benefits: it'll make the code faster; it'll make it easier to read; and it will make it glaringly obvious if a case that should be considered has been missed. >A implementation that used a switch based on the socket state would >be somewhat more natural, but this is still not an exact fit. As >a matter of fact, if you look at the implemention, this is pretty >much what a lot of it does. > > switch (tp->t_state) { > case TCPS_LISTEN: { > ... Yes, it is true that switching on the socket state would be handy. The real power of the switch statement, however, shows when it is used to consider combinations of flags in parallel, as with the TCP option flags. Again, I see some skepticism here about whether it will really make the code faster or more readable, so as soon as 4.0 is frozen I'll generate some code that shows what I have in mind. --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jan 25 22:44:18 2000 Delivered-To: freebsd-net@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id 7156E15089; Tue, 25 Jan 2000 22:44:12 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from imap.gv.tsc.tdk.com (imap.gv.tsc.tdk.com [192.168.241.198]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id WAA10511; Tue, 25 Jan 2000 22:44:07 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by imap.gv.tsc.tdk.com (8.9.3/8.9.3) with ESMTP id WAA77644; Tue, 25 Jan 2000 22:44:06 -0800 (PST) (envelope-from Don.Lewis@tsc.tdk.com) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id WAA28985; Tue, 25 Jan 2000 22:44:06 -0800 (PST) From: Don Lewis Message-Id: <200001260644.WAA28985@salsa.gv.tsc.tdk.com> Date: Tue, 25 Jan 2000 22:44:06 -0800 In-Reply-To: <4.2.2.20000125095042.01a5aba0@localhost> References: <4.2.2.20000125095042.01a5aba0@localhost> X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: Brett Glass , Warner Losh , security@FreeBSD.ORG Subject: Re: Merged patches Cc: freebsd-net@FreeBSD.ORG Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Jan 25, 10:09am, Brett Glass wrote: } Subject: Re: Merged patches } This is a very, VERY concervative patch. As such, it } doesn't include rate limiting of RSTs independently of } ICMP_BANDLIM (which is really a different beast -- on } a router, you might NOT want to limit ICMP but want to } limit bandwidth). A router probably does want to limit ICMP. } The patch also does not prevent a } non-SYN packet from matching a listening socket (this } condition is caught later, but piecemeal with many } individual tests; the coverage isn't comprehensive). A better (more efficient and less convoluted) fix that the one I posted in my patch would be to unroll the findpcb loop, but that change is non-trivial and would not be appropriate to make at this time. Even without this particular fix the patch successfully limits the bandwidth consumed by RST responses when the host is under attack. } And it does not shield the entire TCP stack from } sending or receiving multicast packets -- just this } path. It's still possible to emit a TCP packet with } a multicast source or destination address after } this patch. How? The only responses that can be generated are RST packets and ACK packets. We check the problematical addresses before generating RST packets, and ACK packets are sent to the other endpoint of an "established" connection. If we prevent the creation of an established connection where the other endpoint has a bogus address, then we don't have to worry about sending an ACK to any bogus addresses. I don't see how it would be possible to generate a response with a multicast source address, since the source address has to be one of the IP addresses on the local host. } The source addresses of packets are still } tested to see if they're muticast addresses in MANY } places instead of in one place.... It seems to } me that it pays to use a flag in the mbuf (as is } done with B_CAST) to centralize the test. (A new } flag called, say, SRC_B_CAST would do this. There's } room in the flag word.) That would require doing this test on each incoming packet. I would imagine that most of the packets received by ftp.cdrom.com are normal TCP packets. Doing extra sanity tests on these packets would consume CPU cycles that it could be using for other things such as doing filesystem I/O. "Optimizing" the network stack so that it drops multicast-source packets earlier to save CPU cycles when ftp.cdrom.com is under attack and has its network interface saturated with multicast-source packets is pointless because there will be plenty of CPU cycles to spare because no file transfer requests will be getting through so there won't be any filesystem I/O to do. I believe that setting an mbuf flag for multicast-source packets would be the wrong thing to do anyway, since packets with multicast-source addresses are bogus. The only thing you want to do with these packets is to drop them. } Also, in at least one place (maybe more), the code does } multiple tests of the TCP option flags in succession. } Several tests of this kind should generally be merged } into a switch for speed (the many conditional jumps } cause pipeline stalls on many processors, especially } older ones) and readability. if (thflags & TH_RST) goto drop; if (thflags & TH_ACK) goto dropwithreset; if ((thflags & TH_SYN) == 0) goto drop; vs switch (thflags & (TH_RST|TH_ACK|TH_SYN)) { case TH_RST: case TH_RST|TH_ACK: case TH_RST|TH_SYN: case TH_RST|TH_ACK|TH_SYN: goto drop; case TH_ACK: case TH_ACK|TH_SYN: goto dropwithreset; case TH_SYN: break; case 0: goto drop; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jan 25 23: 1:35 2000 Delivered-To: freebsd-net@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id 481F214F0E for ; Tue, 25 Jan 2000 23:01:32 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from imap.gv.tsc.tdk.com (imap.gv.tsc.tdk.com [192.168.241.198]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id XAA10658; Tue, 25 Jan 2000 23:01:28 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by imap.gv.tsc.tdk.com (8.9.3/8.9.3) with ESMTP id XAA77723; Tue, 25 Jan 2000 23:01:27 -0800 (PST) (envelope-from Don.Lewis@tsc.tdk.com) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id XAA29038; Tue, 25 Jan 2000 23:01:27 -0800 (PST) From: Don Lewis Message-Id: <200001260701.XAA29038@salsa.gv.tsc.tdk.com> Date: Tue, 25 Jan 2000 23:01:27 -0800 In-Reply-To: <4.2.2.20000125232750.04074b50@localhost> References: <200001251722.KAA04527@harmony.village.org> <4.2.2.20000125113518.01a59100@localhost> <4.2.2.20000125232750.04074b50@localhost> X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: Brett Glass , Don Lewis , Matthew Dillon Subject: Re: Merged patches Cc: freebsd-net@FreeBSD.ORG Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Jan 25, 11:38pm, Brett Glass wrote: } Subject: Re: Merged patches } At 11:05 PM 1/25/2000 , Don Lewis wrote: } } >A switch based on the TCP flags would be a very unnatural implementation. } >For instance, most of the processing done on a packet received on an } >established connection is the same whether the FIN bit is set or not. } } A switch statement can allow the same group of statements to be executed } for more than one combination of the flags. Yes, but the processing has to be identical unless you add extra flags tests inside the case block. } >If the switch expression was based on the flags, then a large part of } >the code would be duplicated between these two cases. } } It is also possible to "fall through" from one case to another. This makes } the switch statement a very powerful tool for this sort of situation. This only works if one case is preamble for the next. You have to add extra tests if you want to exit the case early for some sets of flags values. And don't forget the /* fall through */. } It } is also possible to call a common subroutine. The overhead of a fixed } subroutine call is often less than that of a conditional branch on } today's CPUs. Don't forget about all the nice unstructured "goto drop" statements that bail out of deeply nested blocks in tcp_input(). It would be pretty inconvenient if you wanted to bail out from the middle of a subroutine. } > Also, the code } >may do some processing on the segment, clear the SYN and/or FIN bits, } >and then continue. } } I'd think it would be unusual -- perhaps bad form -- to alter the flags, } as it would make the code harder to follow. In what situation(s) would } you do this? You have to do this if the flags fall outside the window. if (todrop > 0) { if (thflags & TH_SYN) { thflags &= ~TH_SYN; th->th_seq++; if (th->th_urp > 1) th->th_urp--; else thflags &= ~TH_URG; todrop--; } /* * Following if statement from Stevens, vol. 2, p. 960. */ if (todrop > tlen || (todrop == tlen && (thflags & TH_FIN) == 0)) { /* * Any valid FIN must be to the left of the window. * At this point the FIN must be a duplicate or out * of sequence; drop it. */ thflags &= ~TH_FIN; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jan 25 23:52:18 2000 Delivered-To: freebsd-net@freebsd.org Received: from uemsconnsp1.cpf.navy.mil (oban-nat-1.cpf.navy.mil [199.124.14.1]) by hub.freebsd.org (Postfix) with ESMTP id 638101514F; Tue, 25 Jan 2000 23:52:12 -0800 (PST) (envelope-from KuriyaKK@cpf.navy.mil) Received: by u661-serv-1-host-257.cpf.navy.mil with Internet Mail Service (5.5.2448.0) id ; Tue, 25 Jan 2000 21:52:08 -1000 Message-ID: From: "Kuriyama, Kent K Mr (CPF N651KK)" To: 'Marco Paulo Rodrigues' Cc: freebsd-stable@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: RE: pccard problems.. I think Date: Tue, 25 Jan 2000 21:52:02 -1000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Marco, I have run into a similar problem with 3.4 RELEASE. I have a Dell 300CPI with a 3COM 3C589D PC card that refuses to be recognized by the 3.4 installation disks. 3.3 RELEASE works fine. I ended up installing 3.3 then CVSUP'd to 3.4. With 3.4 RELEASE on the hard drive, there's no problem with recognizing the 3C589D. Kent -----Original Message----- From: Marco Paulo Rodrigues [mailto:drkangel@pathcom.com] Sent: Tuesday, January 25, 2000 4:52 PM To: freebsd-stable@FreeBSD.ORG; freebsd-net@FreeBSD.ORG; freebsd-chat@FreeBSD.ORG Subject: pccard problems.. I think Hello, I just recently installed FreeBSd 3.4 on my Thinkpad 390E. I have an IBM Etherjet 10/100. I read the relnotes and it says the 3.4 kernel has support for it in. I check the pccard.conf.sample and found it. Problem is, or maybe i'm doing something wrong is when I boot and it beings to load the daemons, ie portmap (the rc.386 startups) I get an error from pccardd saying """ not found in card database? I've never configued a laptop for FreeBSD so I don't know if these flags are correct in the rc.conf. I'm using the original pccard.conf.sample just renamed to pccard.conf and here is what I have in my rc.conf as of this moment.. pccard_enable="YES" # Set to YES if you want to configure PCCARD devices. pccard_mem="DEFAULT" # If pccard_enable=YES, this is card memory address. pccard_ifconfig="ed0 192.168.0.4" # Specialized pccard ethernet configuration (or NO). pccardd_flags="" # Additional flags for pccardd. Is there anything i'm missing? Any help or guidance would be appreciated. ---------------------------------- Marco Paulo Rodrigues Pathway Communications Phone : (416) 907-2880 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 26 2:11: 0 2000 Delivered-To: freebsd-net@freebsd.org Received: from marvin.axion.bt.co.uk (marvin.axion.bt.co.uk [132.146.16.82]) by hub.freebsd.org (Postfix) with ESMTP id 409FD14F77 for ; Wed, 26 Jan 2000 02:10:57 -0800 (PST) (envelope-from graeme.n.brown@bt.com) Received: from cbtlipnt01.btlabs.bt.co.uk by marvin (local) with ESMTP; Wed, 26 Jan 2000 10:07:02 +0000 Received: by cbtlipnt01.btlabs.bt.co.uk with Internet Mail Service (5.5.2448.0) id ; Wed, 26 Jan 2000 10:08:21 -0000 Message-ID: <71DA16F18D32D2119A1D0000F8FE9A9402B5A3D2@mbtlipnt01.btlabs.bt.co.uk> From: graeme.n.brown@bt.com To: freebsd-net@freebsd.org Subject: distributing software updates to boxes on a network Date: Wed, 26 Jan 2000 10:08:20 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I want to develop unicast routing software and deliver/share new versions to FreeBSD PC routers on a test network under my administration in an automated hands-off way. I would appreciate suggestions for any neat ways of doing this. In the past I have tried doing this (i) via NFS where master version of S/W is held on an NFS server with individulal routers mounting exported directory for the s/w and thus all routers can execute same uptodate version of code OR (ii) via each router running a PERL script which does an ftp download of the s/w from an ftp server and then compiles/runs new version of code. TIA Graeme Brown BT Adastral Park, UK email: graeme.n.brown@bt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 26 2:36:18 2000 Delivered-To: freebsd-net@freebsd.org Received: from vidle.i.cz (vidle.i.cz [193.179.36.138]) by hub.freebsd.org (Postfix) with ESMTP id 3E50B150E1 for ; Wed, 26 Jan 2000 02:36:15 -0800 (PST) (envelope-from mm@i.cz) Received: from ns.i.cz (brana.i.cz [193.179.36.134]) by vidle.i.cz (Postfix) with ESMTP id A1BD230702 for ; Wed, 26 Jan 2000 11:36:13 +0100 (CET) Received: from woody.i.cz (woody.i.cz [192.168.18.29]) by ns.i.cz (Postfix) with ESMTP id 215E236417 for ; Wed, 26 Jan 2000 11:36:13 +0100 (CET) Content-Length: 1441 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <71DA16F18D32D2119A1D0000F8FE9A9402B5A3D2@mbtlipnt01.btlabs.bt.co.uk> Date: Wed, 26 Jan 2000 11:36:13 +0100 (MET) Reply-To: mm@i.cz From: Martin Machacek To: freebsd-net@freebsd.org Subject: RE: distributing software updates to boxes on a network Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 26-Jan-00 graeme.n.brown@bt.com wrote: > In the past I have tried doing this > > (i) via NFS where master version of S/W is held on an NFS server with > individulal routers mounting exported directory for the s/w and thus > all routers can execute same uptodate version of code > > OR > > (ii) via each router running a PERL script which does an ftp download > of the s/w from an ftp server and then compiles/runs new version of > code. OR have a master that keeps binaries and configuration for all routers/servers and uses rsync (preferrably over ssh) to distribute them to target machine. This scheme of course assumes that target machines have local harddisks. The big advantage of this scheme is security. Target machines have to trust the master but the master need not to trust anybody. Every action (with regards to changing binaries and/or configuration on target machines) is invoked from the master. Of course the master machine must be properly secured. I'm using this scheme to manage over 40 servers (DNS/mail servers and firewalls) for one of our customers. An extra goodie of this setup is that I can reinstall any machine remotely. I only need somebody to exchange crashed disk for new one and insert a boot floppy with minimal system (derived from picobsd). I'm working on using netboot instead of the floppy. So far I'm very happy with this setup. As usual YMMV :-) Martin --- [PGP KeyID F3F409C4] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 26 5:22:10 2000 Delivered-To: freebsd-net@freebsd.org Received: from apollo.ocsny.com (apollo.ocsny.com [204.107.76.2]) by hub.freebsd.org (Postfix) with ESMTP id 74FD514FA2 for ; Wed, 26 Jan 2000 05:22:05 -0800 (PST) (envelope-from mikel@ocsny.com) Received: from ocsny.com (thoth.upan.org [204.107.76.16]) by apollo.ocsny.com (8.9.2/8.9.3) with ESMTP id IAA10045; Wed, 26 Jan 2000 08:19:14 -0500 (EST) Message-ID: <388EF5B7.9712A2C4@ocsny.com> Date: Wed, 26 Jan 2000 08:25:12 -0500 From: Mikel Organization: Optimized Computer Solutions, Inc. X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: mm@i.cz Cc: freebsd-net@FreeBSD.ORG Subject: Re: distributing software updates to boxes on a network References: Content-Type: multipart/mixed; boundary="------------8A1EEFBC140DCC0E3DFE9CD7" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. --------------8A1EEFBC140DCC0E3DFE9CD7 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Martin Machacek wrote: > On 26-Jan-00 graeme.n.brown@bt.com wrote: > > In the past I have tried doing this > > > > (i) via NFS where master version of S/W is held on an NFS server with > > individulal routers mounting exported directory for the s/w and thus > > all routers can execute same uptodate version of code > > > > OR > > > > (ii) via each router running a PERL script which does an ftp download > > of the s/w from an ftp server and then compiles/runs new version of > > code. > > OR > > have a master that keeps binaries and configuration for all routers/servers and > uses rsync (preferrably over ssh) to distribute them to target machine. This > scheme of course assumes that target machines have local harddisks. The big > advantage of this scheme is security. Target machines have to trust the master > but the master need not to trust anybody. Every action (with regards to changing > binaries and/or configuration on target machines) is invoked from the master. > Of course the master machine must be properly secured. I'm using this scheme to > manage over 40 servers (DNS/mail servers and firewalls) for one of our > customers. An extra goodie of this setup is that I can reinstall any machine > remotely. I only need somebody to exchange crashed disk for new one and insert > a boot floppy with minimal system (derived from picobsd). I'm working on using > netboot instead of the floppy. So far I'm very happy with this setup. > > As usual YMMV :-) > > Martin > I find that an interesting possibility...I wouldn't mind hearing mor about it in the future...I've used rsync for mail, and account synchronization...but never thought about total reinstall before...;) I've also used fetch which works amazingly well and it relatively simple in its approach...the down side is to fetch is the need for either ftp or http services... -- Cheers, Mikel +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ | Optimized Computer Solutions, Inc http://www.ocsny.com | 39 W14th Street, Suite 203 212 727 2238 x132 | New York, NY 10011 +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ | Labor rates: Tech $125 hourly | Net Engineer $150 hourly | Phone Support $ 33 quarter hourly | Lost Password $ 45 per incedent +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ | http://www.ocsny.com/~mikel +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ --------------8A1EEFBC140DCC0E3DFE9CD7 Content-Type: text/x-vcard; charset=us-ascii; name="mikel.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Mikel Content-Disposition: attachment; filename="mikel.vcf" begin:vcard n:King;Mikel x-mozilla-html:TRUE org:Optimized Computer Solutions version:2.1 email;internet:mikel@ocsny.com title:Procurement Manager tel;fax:2124638402 tel;home:http://www.upan.org/vizkr tel;work:2127272100 adr;quoted-printable:;;39 W14th St.=0D=0ASte 203;New York;NY;10011;US x-mozilla-cpt:;0 fn:Mikel King end:vcard --------------8A1EEFBC140DCC0E3DFE9CD7-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 26 8:45:30 2000 Delivered-To: freebsd-net@freebsd.org Received: from goodnet.com (goodnet.com [207.98.129.1]) by hub.freebsd.org (Postfix) with ESMTP id 6B79F151C9 for ; Wed, 26 Jan 2000 08:45:09 -0800 (PST) (envelope-from weyrich@goodnet.com) Received: from localhost (weyrich@localhost) by goodnet.com with ESMTP id JAA09666; Wed, 26 Jan 2000 09:40:43 -0700 (MST) Date: Wed, 26 Jan 2000 09:40:42 -0700 (MST) From: Weyrich Computing Consulting To: graeme.n.brown@bt.com Cc: freebsd-net@FreeBSD.ORG Subject: Re: distributing software updates to boxes on a network In-Reply-To: <71DA16F18D32D2119A1D0000F8FE9A9402B5A3D2@mbtlipnt01.btlabs.bt.co.uk> 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 Try rdist orville. On Wed, 26 Jan 2000 graeme.n.brown@bt.com wrote: > Date: Wed, 26 Jan 2000 10:08:20 -0000 > From: graeme.n.brown@bt.com > To: freebsd-net@FreeBSD.ORG > Subject: distributing software updates to boxes on a network > > I want to develop unicast routing software and deliver/share new versions > to FreeBSD PC routers on a test network under my administration in an > automated hands-off way. I would appreciate suggestions for any neat ways > of doing this. > > In the past I have tried doing this > > (i) via NFS where master version of S/W is held on an NFS server with > individulal routers mounting exported directory for the s/w and thus > all routers can execute same uptodate version of code > > OR > > (ii) via each router running a PERL script which does an ftp download > of the s/w from an ftp server and then compiles/runs new version of > code. > > TIA > > Graeme Brown > BT Adastral Park, UK > email: graeme.n.brown@bt.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > ------------------------------------------------------------------- Orville R. Weyrich, Jr. Weyrich Computer Consulting mailto:orville@weyrich.com KD7HJV http://www.weyrich.com ------------------------------------------------------------------- Visit our online collection of book reviews: http://www.weyrich.com/book_reviews/ Ask about our world wide web services! ------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 26 9:22:47 2000 Delivered-To: freebsd-net@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 49B3115436 for ; Wed, 26 Jan 2000 09:22:44 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id JAA16720; Wed, 26 Jan 2000 09:22:03 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id JAA14635; Wed, 26 Jan 2000 09:22:03 -0800 Received: from softweyr.com (dyn0.utah.xylan.com [198.206.184.236]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id JAA02030; Wed, 26 Jan 2000 09:22:00 -0800 (PST) Message-ID: <388F2E5B.BD454D41@softweyr.com> Date: Wed, 26 Jan 2000 10:26:51 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Mikel Cc: mm@i.cz, freebsd-net@freebsd.org Subject: Re: distributing software updates to boxes on a network References: <388EF5B7.9712A2C4@ocsny.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mikel wrote: > > Martin Machacek wrote: > > > > have a master that keeps binaries and configuration for all routers/servers and > > uses rsync (preferrably over ssh) to distribute them to target machine. This > > scheme of course assumes that target machines have local harddisks. The big > > advantage of this scheme is security. [...] > > I find that an interesting possibility...I wouldn't mind hearing mor about it in > the future...I've used rsync for mail, and account synchronization...but never > thought about total reinstall before...;) > > I've also used fetch which works amazingly well and it relatively simple in its > approach...the down side is to fetch is the need for either ftp or http services... So use scp instead. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 26 10: 3:59 2000 Delivered-To: freebsd-net@freebsd.org Received: from benge.graphics.cornell.edu (benge.graphics.cornell.edu [128.84.247.43]) by hub.freebsd.org (Postfix) with ESMTP id 8134A14F77 for ; Wed, 26 Jan 2000 10:03:55 -0800 (PST) (envelope-from mkc@benge.graphics.cornell.edu) Received: from benge.graphics.cornell.edu (mkc@localhost) by benge.graphics.cornell.edu (8.9.3/8.9.3) with ESMTP id NAA54434; Wed, 26 Jan 2000 13:03:30 -0500 (EST) (envelope-from mkc@benge.graphics.cornell.edu) Message-Id: <200001261803.NAA54434@benge.graphics.cornell.edu> To: graeme.n.brown@bt.com Cc: freebsd-net@FreeBSD.ORG Subject: Re: distributing software updates to boxes on a network In-Reply-To: Message from graeme.n.brown@bt.com of "Wed, 26 Jan 2000 10:08:20 GMT." <71DA16F18D32D2119A1D0000F8FE9A9402B5A3D2@mbtlipnt01.btlabs.bt.co.uk> Date: Wed, 26 Jan 2000 13:03:30 -0500 From: Mitch Collinsworth Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I want to develop unicast routing software and deliver/share new versions >to FreeBSD PC routers on a test network under my administration in an >automated hands-off way. I would appreciate suggestions for any neat ways >of doing this. Have a look at cfengine: http://www.iu.hioslo.no/cfengine/ -Mitch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 26 16:56:13 2000 Delivered-To: freebsd-net@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id C28E1153C4; Wed, 26 Jan 2000 16:56:05 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from imap.gv.tsc.tdk.com (imap.gv.tsc.tdk.com [192.168.241.198]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id QAA23831; Wed, 26 Jan 2000 16:55:52 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by imap.gv.tsc.tdk.com (8.9.3/8.9.3) with ESMTP id QAA83640; Wed, 26 Jan 2000 16:55:52 -0800 (PST) (envelope-from Don.Lewis@tsc.tdk.com) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id QAA02295; Wed, 26 Jan 2000 16:55:51 -0800 (PST) From: Don Lewis Message-Id: <200001270055.QAA02295@salsa.gv.tsc.tdk.com> Date: Wed, 26 Jan 2000 16:55:51 -0800 In-Reply-To: <200001261114.DAA74269@gndrsh.dnsmgr.net> References: <200001261114.DAA74269@gndrsh.dnsmgr.net> X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: "Rodney W. Grimes" , Don.Lewis@tsc.tdk.com (Don Lewis) Subject: Re: Merged patches Cc: dillon@apollo.backplane.com (Matthew Dillon), imp@village.org (Warner Losh), security@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Jan 26, 3:14am, "Rodney W. Grimes" wrote: } Subject: Re: Merged patches } > On Jan 25, 11:34am, "Rodney W. Grimes" wrote: } > } Subject: Re: Merged patches } > } > I found a bug in the patch: } > } > } > } > : #endif } > } > :- if (IN_MULTICAST(ntohl(ip->ip_dst.s_addr))) } > } > :- goto drop; } > } > :+ if (IN_MULTICAST(ntohl(ip->ip_dst.s_addr)) || } > } > :+ IN_MULTICAST(ntohl(ip->ip_src.s_addr)) || } > } > :+ IN_EXPERIMENTAL(ntohl(ip->ip_src.s_addr))) } > } } > } And yet another bugger.... you just made it impossible for anyone } > } doing work with the EXPERIMENTAL block at 240.0.0.0/8 on FreeBSD } > } using TCP without hacking the kernel code. Please remove the } > } last check here. } > } > How about changing the last part to to } > ip->ip_src.s_addr == htonl(INADDR_BROADCAST) } > which is the subset of IN_EXPERIMENTAL that I was concerned about. } > } > Without this, someone will post yet another variant of this attack } > using a broadcast source address. } } The short and simple answer: } ipfw add deny ip from 240.0.0.0/4 to any } } The longer answer: } Manning is not very clear on Class E space, Technically 255.255.255.255 } is a class E address, and is part of ``a range left unspecified''. Putting } your patch above in would be ``specifing'' a behavior. But yet Manning } later says: } } Note: No addresses are allowed with the four highest-order bits } set to 1-1-1-1. These addresses, called "classE", are reserved. } } Reserved means we should not be putting in hard code that effects how } they behave, IMNSO. 255.255.255.255 is also defined as a broadcast address on the local network. There's already code in the kernel that treats that in a special way. In particular, if we send a TCP RST to this address, it will probably get turned into a MAC level broadcast and get forwarded all over the local network, though it wouldn't be forwarded by any routers. BTW, there already is code that treats class E addresses specially in in_canforward(), which gets called from the packet routing code to block the forwarding of packets in the address range, and also by the ICMP code to block replies to this address range. } Your going to have to do the short and simple answer covers to cover } the other parts of this space anyway, so you might as well only do it } one place and not create what may be a headache for someone else. I don't think that the rest of this address space will be as much of a problem. They stack might emit a RST packet with a destination address in this range, but it won't go anywhere except maybe to the default router. } Also don't some strange clients like DHCP use this as a source address } during their startup phase? No, they use 0.0.0.0 as their source address and 255.255.255.255 as their destination address. They also don't use TCP. There is also the problem of source addresses that are broadcast addresses on local networks. This shouldn't be remotely exploitable if you have anti-spoofing filter rules on the router between the local network and any untrusted networks. It might be a good idea to fix this as well at some point, but this is harder to fix. Hey, don't we have a knob to control the forwarding of directed broadcasts? I just looked and didn't see anything obvious. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 26 18: 7:44 2000 Delivered-To: freebsd-net@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 4A8F4154E7; Wed, 26 Jan 2000 18:07:07 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id SAA75635; Wed, 26 Jan 2000 18:06:53 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001270206.SAA75635@gndrsh.dnsmgr.net> Subject: Re: Merged patches In-Reply-To: <200001270055.QAA02295@salsa.gv.tsc.tdk.com> from Don Lewis at "Jan 26, 2000 04:55:51 pm" To: Don.Lewis@tsc.tdk.com (Don Lewis) Date: Wed, 26 Jan 2000 18:06:53 -0800 (PST) Cc: dillon@apollo.backplane.com (Matthew Dillon), imp@village.org (Warner Losh), security@FreeBSD.ORG, freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 ... > } Reserved means we should not be putting in hard code that effects how > } they behave, IMNSO. > > 255.255.255.255 is also defined as a broadcast address on the local network. > There's already code in the kernel that treats that in a special way. In > particular, if we send a TCP RST to this address, it will probably get turned > into a MAC level broadcast and get forwarded all over the local network, > though it wouldn't be forwarded by any routers. > > BTW, there already is code that treats class E addresses specially in > in_canforward(), which gets called from the packet routing code to > block the forwarding of packets in the address range, and also by the > ICMP code to block replies to this address range. Yes, I know, as I have had to rip it out in every ``experimental'' network project I have done. If I recall correctly that was done with the multicast intergration, and it was wrong, these are not defined to be multicast addresses by any standard, but the Deering multicast code treated them as such. > > } Your going to have to do the short and simple answer covers to cover > } the other parts of this space anyway, so you might as well only do it > } one place and not create what may be a headache for someone else. > > I don't think that the rest of this address space will be as much of > a problem. They stack might emit a RST packet with a destination address > in this range, but it won't go anywhere except maybe to the default router. And with the correct userland policy put in place via ipfw or ipfilter they won't even get that far. ... > > There is also the problem of source addresses that are broadcast addresses > on local networks. This shouldn't be remotely exploitable if you have > anti-spoofing filter rules on the router between the local network and > any untrusted networks. It might be a good idea to fix this as well at > some point, but this is harder to fix. More things that belong in firewall rules, not in the kernel. You going to complicate the code beyond comprehension and for little to no gain. > > Hey, don't we have a knob to control the forwarding of directed broadcasts? > I just looked and didn't see anything obvious. I think your thinking about net.inet.icmp.bmcastecho, I don't know of a directed broadcast forwarding knob on freebsd :-(. We deal with that issue with yet more ipfw policy. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jan 26 19:14: 4 2000 Delivered-To: freebsd-net@freebsd.org Received: from mickey.atarde.com.br (mickey.atarde.com.br [200.223.87.5]) by hub.freebsd.org (Postfix) with SMTP id 1A34A154B6 for ; Wed, 26 Jan 2000 19:14:00 -0800 (PST) (envelope-from boozy@rabelo.eti.br) Received: (qmail 57148 invoked from network); 27 Jan 2000 03:19:57 -0000 Received: from cartoon052.atarde.com.br (HELO robusto) (200.223.87.52) by mickey.atarde.com.br with SMTP; 27 Jan 2000 03:19:57 -0000 X-Sender: boozy%rabelo.eti.br@mickey.atarde.com.br X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Demo Date: Thu, 27 Jan 2000 01:03:47 -0200 To: itojun@itojun.org From: Boozy Subject: Re: (KAME-snap 1790) Re: DNS for IPv6 Cc: snap-users@kame.net, gorgonio@ufba.br, 6bone@isi.edu, ipv6@rnp.br, users@ipv6.org, freebsd-net@freebsd.org In-Reply-To: <4666.948850423@coconut.itojun.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-Id: <20000127031400.1A34A154B6@hub.freebsd.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I finished the installation and configuration of bind8 for FreeBSD/KAME but I don't know how I can set the reverse ipv6 address. I read the RFC 1886 (DNS Extensions to support IP version 6), but I didn't understand the "IP6.INT Domain". How can I use it? Where can I find more information about it? Thanks, Luciano Rabelo At 10:33 26/01/2000 +0900, you wrote: > >>I installed bind8 port for FreeBSD/Kame. Where can I get information about its >>configuration? > > read through manpages, and books. there's nothing special about it. > http://www.normos.org/ietf/rfc/rfc1886.txt may be of use. > >itojun > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 27 0:41:29 2000 Delivered-To: freebsd-net@freebsd.org Received: from samantha.lysator.liu.se (samantha.lysator.liu.se [130.236.254.202]) by hub.freebsd.org (Postfix) with ESMTP id 00E6C153DD for ; Thu, 27 Jan 2000 00:41:26 -0800 (PST) (envelope-from pontus@lysator.liu.se) Received: from sandra.lysator.liu.se (pontus@sandra.lysator.liu.se [130.236.254.203]) by samantha.lysator.liu.se (8.9.3/8.9.3) with ESMTP id JAA24862; Thu, 27 Jan 2000 09:40:17 +0100 (MET) Received: from localhost (pontus@localhost) by sandra.lysator.liu.se (8.9.0/8.8.7) with SMTP id JAA28846; Thu, 27 Jan 2000 09:40:11 +0100 (MET) X-Authentication-Warning: sandra.lysator.liu.se: pontus owned process doing -bs Date: Thu, 27 Jan 2000 09:40:11 +0100 (MET) From: Pontus Lidman To: Boozy Cc: itojun@itojun.org, snap-users@kame.net, gorgonio@ufba.br, 6bone@ISI.EDU, ipv6@rnp.br, users@ipv6.org, freebsd-net@freebsd.org Subject: Re: (KAME-snap 1790) Re: DNS for IPv6 In-Reply-To: <200001270314.TAA22901@tnt.isi.edu> Message-ID: X-Akademikerna-authorization: skitenkelt! MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 27 Jan 2000, Boozy wrote: > Hi, > > I finished the installation and configuration of bind8 for FreeBSD/KAME but > I don't know how I can set the reverse ipv6 address. I read the RFC 1886 > (DNS Extensions to support IP version 6), but I didn't understand the > "IP6.INT Domain". How can I use it? Where can I find more information about > it? You might want to read "IPv6 DNS examples" on http://www.visc.vt.edu/ipv6/doc/dns.html -- Pontus Lidman, pontus@mathcore.com, Software Engineer No matter how cynical you get, it's impossible to keep up. Scene: www.dc-s.com | MUD: tyme.envy.com 6969 | irc: irc.quakenet.eu.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 27 8:58:36 2000 Delivered-To: freebsd-net@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 30CA915766 for ; Thu, 27 Jan 2000 08:58:34 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 33FAA137FB6 for ; Thu, 27 Jan 2000 11:58:29 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id LAA02629; Thu, 27 Jan 2000 11:58:31 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14480.31030.981974.179703@trooper.velocet.net> Date: Thu, 27 Jan 2000 11:58:30 -0500 (EST) To: freebsd-net@freebsd.org Subject: netgraph documentation? X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've been having trouble finding documentation (especially examples) for netgraph. The man pages are good as far as they go, but some examples and some explainations would be handy. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 27 9:12:45 2000 Delivered-To: freebsd-net@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id B109A156E4 for ; Thu, 27 Jan 2000 09:12:43 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id MAA38013; Thu, 27 Jan 2000 12:11:31 -0500 (EST) Date: Thu, 27 Jan 2000 12:11:31 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: David Gilbert Cc: freebsd-net@FreeBSD.ORG Subject: Re: netgraph documentation? In-Reply-To: <14480.31030.981974.179703@trooper.velocet.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 On Thu, 27 Jan 2000, David Gilbert wrote: > I've been having trouble finding documentation (especially examples) > for netgraph. The man pages are good as far as they go, but some > examples and some explainations would be handy. > > Dave. > Have you taken a look at ftp://ftp.whistle.com/pub/archie/netgraph/index.html ? Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 27 9:26:41 2000 Delivered-To: freebsd-net@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id F251A157B9 for ; Thu, 27 Jan 2000 09:26:38 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 863D2137FDA; Thu, 27 Jan 2000 12:26:35 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id MAA03470; Thu, 27 Jan 2000 12:26:36 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14480.32715.899509.661306@trooper.velocet.net> Date: Thu, 27 Jan 2000 12:26:35 -0500 (EST) To: Kelly Yancey Cc: David Gilbert , freebsd-net@FreeBSD.ORG Subject: Re: netgraph documentation? In-Reply-To: References: <14480.31030.981974.179703@trooper.velocet.net> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> "Kelly" == Kelly Yancey writes: Kelly> Have you taken a look at Kelly> ftp://ftp.whistle.com/pub/archie/netgraph/index.html ? OK... good. While I'm looking at that, the evil telco wants to talk "pptp" to me ... specifically, they said my config should be: velocet peer name: velocet Nexxia peer name: nexxia7 Vlan: 32 ip address: 10.10.4.26 / 30 Tunel password: V3l0c3T ... now... I'd dearly like to avoid expensive cisco hardware (or even more expensive redback hardware)... so has anyone considered how I might configure this :). If this does require some writing of code... I'd be willing to make it worth someone's while. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 27 14:21:45 2000 Delivered-To: freebsd-net@freebsd.org Received: from web208.mail.yahoo.com (web208.mail.yahoo.com [128.11.68.108]) by hub.freebsd.org (Postfix) with SMTP id D6D9414D71 for ; Thu, 27 Jan 2000 14:21:40 -0800 (PST) (envelope-from julian_elischer@yahoo.com) Received: (qmail 5520 invoked by uid 60001); 27 Jan 2000 21:51:17 -0000 Message-ID: <20000127215117.5519.qmail@web208.mail.yahoo.com> Received: from [62.104.216.87] by web208.mail.yahoo.com; Thu, 27 Jan 2000 13:51:17 PST Date: Thu, 27 Jan 2000 13:51:17 -0800 (PST) From: Julian Elischer Subject: Re: netgraph documentation? To: Kelly Yancey , David Gilbert Cc: freebsd-net@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org but if you have specific questions or suggestions either archie@freebsd.org or julian@freebsd.org will get to us. (though my connection is a bit tenuous at the moment as I'm touring europe.. --- Kelly Yancey wrote: > On Thu, 27 Jan 2000, David Gilbert wrote: > > > I've been having trouble finding documentation > (especially examples) > > for netgraph. The man pages are good as far as > they go, but some > > examples and some explainations would be handy. > > > > Dave. > > > > Have you taken a look at > ftp://ftp.whistle.com/pub/archie/netgraph/index.html > ? > > Kelly > > -- > Kelly Yancey - kbyanc@posi.net - Richmond, VA > Analyst / E-business Development, Bell Industries > http://www.bellind.com/ > Maintainer, BSD Driver Database > http://www.posi.net/freebsd/drivers/ > Coordinator, Team FreeBSD > http://www.posi.net/freebsd/Team-FreeBSD/ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the > message > ===== +------------------------------------+ | __--_|\ Julian Elischer | | / \ julian@elischer.org +--from Perth to the world. | ( OZ ) World tour 2000 +- X_.---._/ presently in: Germany v __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 27 14:39:21 2000 Delivered-To: freebsd-net@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 4BE1F154A2 for ; Thu, 27 Jan 2000 14:39:19 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id OAA79004; Thu, 27 Jan 2000 14:39:17 -0800 (PST) From: Archie Cobbs Message-Id: <200001272239.OAA79004@bubba.whistle.com> Subject: Re: netgraph documentation? In-Reply-To: <14480.31030.981974.179703@trooper.velocet.net> from David Gilbert at "Jan 27, 2000 11:58:30 am" To: dgilbert@velocet.ca (David Gilbert) Date: Thu, 27 Jan 2000 14:39:17 -0800 (PST) Cc: freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org David Gilbert writes: > I've been having trouble finding documentation (especially examples) > for netgraph. The man pages are good as far as they go, but some > examples and some explainations would be handy. FYI- I'm writing up an article for the DaemonNews about netgraph that will give a lot more in-depth information. It won't appear until March but I'll make it available before then. -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 Thu Jan 27 16:55:57 2000 Delivered-To: freebsd-net@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id 5ED3915853 for ; Thu, 27 Jan 2000 16:55:37 -0800 (PST) (envelope-from mike@sentex.net) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by vinyl.sentex.ca (8.9.3/8.9.3) with ESMTP id TAA38097; Thu, 27 Jan 2000 19:55:33 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id TAA14401; Thu, 27 Jan 2000 19:55:32 -0500 (EST) From: mike@sentex.net (Mike Tancsa) To: dgilbert@velocet.ca (David Gilbert) Cc: freebsd-net@FreeBSD.ORG Subject: Re: netgraph documentation? Date: Fri, 28 Jan 2000 00:54:11 GMT Message-ID: <3890e7dd.156290844@mail.sentex.net> References: <14480.31030.981974.179703@trooper.velocet.net> In-Reply-To: X-Mailer: Forte Agent .99e/32.227 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 27 Jan 2000 12:27:08 -0500, in sentex.lists.freebsd.net you wrote: >>>>>> "Kelly" == Kelly Yancey writes: > >Kelly> Have you taken a look at >Kelly> ftp://ftp.whistle.com/pub/archie/netgraph/index.html ? > >OK... good. While I'm looking at that, the evil telco wants to talk >"pptp" to me ... specifically, they said my config should be: Did Bell give that option ? For us, our only choice was L2TP. >velocet peer name: velocet >Nexxia peer name: nexxia7 >Vlan: 32 >ip address: 10.10.4.26 / 30 >Tunel password: V3l0c3T > >... now... I'd dearly like to avoid expensive cisco hardware (or even >more expensive redback hardware)... so has anyone considered how I >might configure this :). See http://www.marko.net/l2tp/ In theory perhaps, but there seems to be a few things missing. ---Mike Mike Tancsa (mdtancsa@sentex.net) Sentex Communications Corp, Waterloo, Ontario, Canada "Given enough time, 100 monkeys on 100 routers could setup a national IP network." (KDW2) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 27 18:51:28 2000 Delivered-To: freebsd-net@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 3380114A1E for ; Thu, 27 Jan 2000 18:51:23 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 9FDA4137FDB; Thu, 27 Jan 2000 21:51:19 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id VAA21247; Thu, 27 Jan 2000 21:51:22 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14481.1066.490661.673416@trooper.velocet.net> Date: Thu, 27 Jan 2000 21:51:22 -0500 (EST) To: Julian Elischer Cc: Kelly Yancey , David Gilbert , freebsd-net@FreeBSD.ORG Subject: Re: netgraph documentation? In-Reply-To: <20000127215117.5519.qmail@web208.mail.yahoo.com> References: <20000127215117.5519.qmail@web208.mail.yahoo.com> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> "Julian" == Julian Elischer writes: Julian> but if you have specific questions or suggestions either Julian> archie@freebsd.org or julian@freebsd.org will get to us. Julian> (though my connection is a bit tenuous at the moment as I'm Julian> touring europe.. Well... having gone through the documentation, its not clear where the gap is, or how big it is. ng_pptpgre appears to be at least part of the protocol that I need to speak, but some of the documentation implies that this intended to work with a future work that will implement the rest of the rest of the protocol. Now the current ng_pppoe works with the current pppd... and the question arises if this pppd is capable of working with ng_pptpgre. Is this stuff close enough, or should I give up and use the Lucent box? Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 27 21:16:43 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail.rdc3.on.home.com (ha1.rdc3.on.home.com [24.2.9.68]) by hub.freebsd.org (Postfix) with ESMTP id 3D0F3155A4 for ; Thu, 27 Jan 2000 21:16:34 -0800 (PST) (envelope-from danyc@playground.net) Received: from playground.net ([24.114.192.235]) by mail.rdc3.on.home.com (InterMail v4.01.01.02 201-229-111-106) with ESMTP id <20000128051413.IABO17528.mail.rdc3.on.home.com@playground.net> for ; Thu, 27 Jan 2000 21:14:13 -0800 Message-ID: <389126F7.F9A3FBF9@playground.net> Date: Fri, 28 Jan 2000 00:19:52 -0500 From: Dany Cayouette X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@FreeBSD.org Subject: [Fwd: PPPoE Problems] Content-Type: multipart/mixed; boundary="------------C930ADDB649DEDE7207958CE" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. --------------C930ADDB649DEDE7207958CE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I posted this question over a week ago to the freebsd-questions list but didn't get any help/feedback yet. Sorry if the question is a bit basic for the gurus. I am just looking for a place to start searching. Thanks, Dany --------------C930ADDB649DEDE7207958CE Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Mozilla-Status2: 00000000 Message-ID: <3883BFE2.AE260F84@playground.net> Date: Mon, 17 Jan 2000 20:20:35 -0500 From: Dany Cayouette X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-questions@FreeBSD.ORG Subject: PPPoE Problems Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Greetings, I recently got my hands on an old DEC pentium 133 PC. I just got FreeBSD 3.4-RELEASE installed. I am interested in getting PPPoE running. I recompile a kernel with all the NETGRAPH options. The first problem I noticed is a 50% success rate on getting a successful connection. I start my session with the command "ppp -dedicated". I stop the session with "kill ". When the process terminates, I get the following 2 messages: /var/log/messages: Jan 12 16:48:19 freebsd ppp[265]: tun0: Warning: deflink: Oops: Got 8 bytes but 4 byte payload Jan 12 16:48:20 freebsd ppp[265]: tun0: Warning: deflink: Oops: Got 8 bytes but 4 byte payload When I try to restart "ppp -dedicated" I don't get any special error messages but a tcpdump suggests that nothing goes out on the Ethernet interface. I kill the ppp process and re-issue the command "ppp -dedicated" and everything works! I wanted to do more debugging today but now nothing works. I am getting a write error on the tun interface. Any idea on what extra debugging I could turn on... Here is my configuration, the output on /var/log/ppp.log for the write failure and finally output from a successful session: /etc/ppp/ppp.conf default: set device PPPoE:de0 set MRU 1490 set MTU 1490 set authname user@domain.com set authkey password set log Phase Chat LCP IPCP CCP tun command # set log Phase IPCP CCP tun LCP set dial set login "TIMEOUT 1.5 name:\\r-login:\\U:\\P ocol:PPP HELLO" set ifaddr 10.0.0.1/0 10.0.0.2/0 add default HISADDR # enable dns set cd off set crtscts off /var/log/ppp.log -------- Failing Session -------- Jan 17 13:31:30 freebsd ppp[6886]: Phase: Using interface: tun0 Jan 17 13:31:30 freebsd ppp[6886]: Phase: deflink: Created in closed state Jan 17 13:31:30 freebsd ppp[6887]: tun0: Phase: PPP Started (dedicated mode). Jan 17 13:31:30 freebsd ppp[6887]: tun0: Phase: bundle: Establish Jan 17 13:31:30 freebsd ppp[6887]: tun0: Phase: deflink: closed -> opening Jan 17 13:31:30 freebsd ppp[6887]: tun0: Phase: deflink: Connected! Jan 17 13:31:30 freebsd ppp[6887]: tun0: Phase: deflink: opening -> carrier Jan 17 13:31:31 freebsd ppp[6887]: tun0: Phase: deflink: Disconnected! Jan 17 13:31:31 freebsd ppp[6887]: tun0: Phase: deflink: carrier -> lcp Jan 17 13:31:31 freebsd ppp[6887]: tun0: LCP: FSM: Using "deflink" as a transport Jan 17 13:31:31 freebsd ppp[6887]: tun0: LCP: deflink: State change Initial --> Closed Jan 17 13:31:31 freebsd ppp[6887]: tun0: LCP: deflink: State change Closed --> Stopped Jan 17 13:31:32 freebsd ppp[6887]: tun0: LCP: deflink: LayerStart Jan 17 13:31:32 freebsd ppp[6887]: tun0: LCP: deflink: SendConfigReq(1) state = Stopped Jan 17 13:31:32 freebsd ppp[6887]: tun0: LCP: ACFCOMP[2] Jan 17 13:31:32 freebsd ppp[6887]: tun0: LCP: PROTOCOMP[2] Jan 17 13:31:32 freebsd ppp[6887]: tun0: LCP: ACCMAP[6] 0x00000000 Jan 17 13:31:32 freebsd ppp[6887]: tun0: LCP: MRU[4] 1490 Jan 17 13:31:32 freebsd ppp[6887]: tun0: LCP: MAGICNUM[6] 0x744e7a6d Jan 17 13:31:32 freebsd ppp[6887]: tun0: LCP: deflink: State change Stopped --> Req-Sent Jan 17 13:31:32 freebsd ppp[6887]: tun0: Phase: deflink: write (1): Network is unreachable Jan 17 13:31:32 freebsd ppp[6887]: tun0: LCP: deflink: State change Req-Sent --> Starting Jan 17 13:31:32 freebsd ppp[6887]: tun0: LCP: deflink: LayerFinish Jan 17 13:31:32 freebsd ppp[6887]: tun0: LCP: deflink: State change Starting --> Initial Jan 17 13:31:32 freebsd ppp[6887]: tun0: Phase: deflink: Disconnected! Jan 17 13:31:32 freebsd ppp[6887]: tun0: LCP: FSM: Using "deflink" as a transport Jan 17 13:31:32 freebsd ppp[6887]: tun0: LCP: deflink: State change Initial --> Closed Jan 17 13:31:32 freebsd ppp[6887]: tun0: LCP: deflink: State change Closed --> Stopped Jan 17 13:31:32 freebsd ppp[6887]: tun0: Phase: deflink: Disconnected! .......................... ------ Successful session ------ Jan 12 16:41:40 freebsd ppp[264]: Phase: Using interface: tun0 Jan 12 16:41:40 freebsd ppp[264]: Phase: deflink: Created in closed state Jan 12 16:41:41 freebsd ppp[265]: tun0: LCP: FSM: Using "deflink" as a transport Jan 12 16:41:41 freebsd ppp[265]: tun0: LCP: deflink: State change Initial --> Closed Jan 12 16:41:41 freebsd ppp[265]: tun0: LCP: deflink: State change Closed --> Stopped Jan 12 16:41:42 freebsd ppp[265]: tun0: LCP: deflink: LayerStart Jan 12 16:41:42 freebsd ppp[265]: tun0: LCP: deflink: SendConfigReq(1) state = Stopped Jan 12 16:41:42 freebsd ppp[265]: tun0: LCP: ACFCOMP[2] Jan 12 16:41:42 freebsd ppp[265]: tun0: LCP: PROTOCOMP[2] Jan 12 16:41:42 freebsd ppp[265]: tun0: LCP: ACCMAP[6] 0x00000000 Jan 12 16:41:42 freebsd ppp[265]: tun0: LCP: MRU[4] 1490 Jan 12 16:41:42 freebsd ppp[265]: tun0: LCP: MAGICNUM[6] 0x52516508 Jan 12 16:41:42 freebsd ppp[265]: tun0: LCP: deflink: State change Stopped --> Req-Sent Jan 12 16:41:42 freebsd ppp[265]: tun0: LCP: deflink: RecvConfigReq(249) state = Req-Sent Jan 12 16:41:42 freebsd ppp[265]: tun0: LCP: MAGICNUM[6] 0x5b6ecd20 Jan 12 16:41:42 freebsd ppp[265]: tun0: LCP: MRU[4] 1492 Jan 12 16:41:42 freebsd ppp[265]: tun0: LCP: AUTHPROTO[5] 0xc223 (CHAP 0x05) Jan 12 16:41:42 freebsd ppp[265]: tun0: LCP: deflink: SendConfigAck(249) state = Req-Sent Jan 12 16:41:42 freebsd ppp[265]: tun0: LCP: MAGICNUM[6] 0x5b6ecd20 Jan 12 16:41:42 freebsd ppp[265]: tun0: LCP: MRU[4] 1492 Jan 12 16:41:42 freebsd ppp[265]: tun0: LCP: AUTHPROTO[5] 0xc223 (CHAP 0x05) Jan 12 16:41:42 freebsd ppp[265]: tun0: LCP: deflink: State change Req-Sent --> Ack-Sent Jan 12 16:41:42 freebsd ppp[265]: tun0: LCP: deflink: RecvConfigRej(1) state = Ack-Sent Jan 12 16:41:42 freebsd ppp[265]: tun0: LCP: ACFCOMP[2] Jan 12 16:41:42 freebsd ppp[265]: tun0: LCP: PROTOCOMP[2] Jan 12 16:41:42 freebsd ppp[265]: tun0: LCP: ACCMAP[6] 0x00000000 Jan 12 16:41:42 freebsd ppp[265]: tun0: LCP: deflink: SendConfigReq(2) state = Ack-Sent Jan 12 16:41:42 freebsd ppp[265]: tun0: LCP: MRU[4] 1490 Jan 12 16:41:42 freebsd ppp[265]: tun0: LCP: MAGICNUM[6] 0x52516508 Jan 12 16:41:42 freebsd ppp[265]: tun0: LCP: deflink: RecvConfigAck(2) state = Ack-Sent Jan 12 16:41:42 freebsd ppp[265]: tun0: LCP: deflink: State change Ack-Sent --> Opened Jan 12 16:41:42 freebsd ppp[265]: tun0: LCP: deflink: LayerUp Jan 12 16:41:42 freebsd ppp[265]: tun0: CCP: FSM: Using "deflink" as a transport Jan 12 16:41:42 freebsd ppp[265]: tun0: CCP: deflink: State change Initial --> Closed Jan 12 16:41:42 freebsd ppp[265]: tun0: CCP: deflink: LayerStart. Jan 12 16:41:42 freebsd ppp[265]: tun0: CCP: deflink: SendConfigReq(1) state = Closed Jan 12 16:41:42 freebsd ppp[265]: tun0: CCP: DEFLATE[4] win 15 Jan 12 16:41:42 freebsd ppp[265]: tun0: CCP: PRED1[2] Jan 12 16:41:42 freebsd ppp[265]: tun0: CCP: deflink: State change Closed --> Req-Sent Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: FSM: Using "deflink" as a transport Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: deflink: State change Initial --> Closed Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: deflink: LayerStart. Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: deflink: SendConfigReq(1) state = Closed Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: IPADDR[6] 10.0.0.1 Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: COMPPROTO[6] 16 VJ slots with slot compression Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: PRIDNS[6] 10.10.10.10 Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: SECDNS[6] 20.20.20.20 Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: deflink: State change Closed --> Req-Sent Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: deflink: RecvConfigReq(220) state = Req-Sent Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: IPADDR[6] 10.64.178.94 Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: deflink: SendConfigAck(220) state = Req-Sent Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: IPADDR[6] 10.64.178.94 Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: deflink: State change Req-Sent --> Ack-Sent Jan 12 16:41:42 freebsd ppp[265]: tun0: LCP: deflink: RecvProtocolRej(250) state = Opened Jan 12 16:41:42 freebsd ppp[265]: tun0: LCP: deflink: -- Protocol 0x80fd (Compression Control Protocol) was rejected! Jan 12 16:41:42 freebsd ppp[265]: tun0: CCP: deflink: State change Req-Sent --> Stopped Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: deflink: RecvConfigRej(1) state = Ack-Sent Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: COMPPROTO[6] 16 VJ slots with slot compression Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: deflink: SendConfigReq(2) state = Ack-Sent Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: IPADDR[6] 10.0.0.1 Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: PRIDNS[6] 10.10.10.10 Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: SECDNS[6] 20.20.20.20 Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: deflink: RecvConfigNak(2) state = Ack-Sent Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: IPADDR[6] 10.200.0.6 Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: IPADDR[6] changing address: 10.0.0.1 --> 10.200.0.6 Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: deflink: SendConfigReq(3) state = Ack-Sent Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: IPADDR[6] 10.200.0.6 Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: PRIDNS[6] 10.10.10.10 Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: SECDNS[6] 20.20.20.20 Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: deflink: RecvConfigAck(3) state = Ack-Sent Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: deflink: State change Ack-Sent --> Opened Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: deflink: LayerUp. Jan 12 16:41:42 freebsd ppp[265]: tun0: IPCP: myaddr 10.200.0.6 hisaddr = 10.64.178.94 Jan 12 16:41:53 freebsd ppp[265]: tun0: LCP: deflink: RecvEchoRequest(0) state = Opened Jan 12 16:41:53 freebsd ppp[265]: tun0: LCP: deflink: SendEchoReply(0) state = Opened Jan 12 16:42:04 freebsd ppp[265]: tun0: LCP: deflink: RecvEchoRequest(1) state = Opened Jan 12 16:42:04 freebsd ppp[265]: tun0: LCP: deflink: SendEchoReply(1) state = Opened Jan 12 16:42:14 freebsd ppp[265]: tun0: LCP: deflink: RecvEchoRequest(2) state = Opened Jan 12 16:42:14 freebsd ppp[265]: tun0: LCP: deflink: SendEchoReply(2) state = Opened Jan 12 16:42:25 freebsd ppp[265]: tun0: LCP: deflink: RecvEchoRequest(3) state = Opened --- repeating lines deleted Jan 12 16:48:03 freebsd ppp[265]: tun0: LCP: deflink: RecvEchoRequest(34) state = Opened Jan 12 16:48:03 freebsd ppp[265]: tun0: LCP: deflink: SendEchoReply(34) state = Opened Jan 12 16:48:13 freebsd ppp[265]: tun0: LCP: deflink: RecvEchoRequest(35) state = Opened Jan 12 16:48:14 freebsd ppp[265]: tun0: LCP: deflink: SendEchoReply(35) state = Opened Jan 12 16:48:19 freebsd ppp[265]: tun0: IPCP: deflink: LayerDown: 10.200.0.6 Jan 12 16:48:19 freebsd ppp[265]: tun0: IPCP: deflink: SendTerminateReq(4) state = Opened Jan 12 16:48:19 freebsd ppp[265]: tun0: IPCP: deflink: State change Opened --> Closing Jan 12 16:48:19 freebsd ppp[265]: tun0: Warning: deflink: Oops: Got 8 bytes but 4 byte payload Jan 12 16:48:19 freebsd ppp[265]: tun0: IPCP: deflink: RecvTerminateAck(4) state = Closing Jan 12 16:48:19 freebsd ppp[265]: tun0: IPCP: deflink: LayerFinish. Jan 12 16:48:19 freebsd ppp[265]: tun0: IPCP: Connect time: 397 secs: 0 octets in, 0 octets out Jan 12 16:48:19 freebsd ppp[265]: tun0: IPCP: total 0 bytes/sec, peak 0 bytes/sec on Wed Jan 12 16:48:19 2000 Jan 12 16:48:19 freebsd ppp[265]: tun0: IPCP: deflink: State change Closing --> Closed Jan 12 16:48:19 freebsd ppp[265]: tun0: CCP: deflink: State change Stopped --> Closed Jan 12 16:48:19 freebsd ppp[265]: tun0: CCP: deflink: State change Closed --> Initial Jan 12 16:48:19 freebsd ppp[265]: tun0: LCP: deflink: LayerDown Jan 12 16:48:19 freebsd ppp[265]: tun0: LCP: deflink: SendTerminateReq(3) state = Opened Jan 12 16:48:19 freebsd ppp[265]: tun0: LCP: deflink: State change Opened --> Closing Jan 12 16:48:19 freebsd ppp[265]: tun0: IPCP: deflink: State change Closed --> Initial Jan 12 16:48:19 freebsd ppp[265]: tun0: Warning: deflink: Oops: Got 8 bytes but 4 byte payload Jan 12 16:48:19 freebsd ppp[265]: tun0: LCP: deflink: RecvTerminateAck(3) state = Closing Jan 12 16:48:19 freebsd ppp[265]: tun0: LCP: deflink: LayerFinish Jan 12 16:48:19 freebsd ppp[265]: tun0: LCP: deflink: State change Closing --> Closed Jan 12 16:48:19 freebsd ppp[265]: tun0: LCP: deflink: State change Closed --> Initial Regards, Dany Cayouette --------------C930ADDB649DEDE7207958CE-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jan 27 21:42:26 2000 Delivered-To: freebsd-net@freebsd.org Received: from phoenix.welearn.com.au (phoenix.welearn.com.au [139.130.44.81]) by hub.freebsd.org (Postfix) with ESMTP id 1B5F314E54 for ; Thu, 27 Jan 2000 21:42:15 -0800 (PST) (envelope-from jon@phoenix.welearn.com.au) Received: (from jon@localhost) by phoenix.welearn.com.au (8.9.3/8.9.3) id QAA50906 for freebsd-net@freebsd.org; Fri, 28 Jan 2000 16:42:07 +1100 (EST) (envelope-from jon) Date: Fri, 28 Jan 2000 16:42:05 +1100 From: Jonathan Michaels To: freebsd-net@freebsd.org Subject: ppp(8) or mpd by whistle ? Message-ID: <20000128164203.A50762@phoenix.welearn.com.au> Reply-To: jon@welearn.com.au Mail-Followup-To: freebsd-net@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org all, hopefully this, is the right place for this topic ? after may years of ms dos based uucp and 3 plus using the kernel pppd i figure its time for a change. well, that and i'd a better level of debuging/logging than is currently available from kernel pppd(8). i like the way logging and the various types of same that is possible to get from the userland version (and also exists in mpd, from doc's i've read). also i've got a recurrant and mysterious drop carrier every couple of days no rhyme or reason, just a note in the logs and a restart by kernel ppp ... at 25 cents a pop it can be quite annoying. here in australia we get charged 25 cents per connection fro our 'local' call, and its then "all you can eat" fro your local call connection fee. i've started to read about netgraph and like the idea, also that mpd is based on netgraph, so this would be a familiarisation process as well .. anyway i've rattled on for long enough. any war stories about mpd useage, abuse, reliability, relative ease of use configurability, etc, etc, would be apreciated. warm regards jonathan long time unix'ish user, still green around the gills in freebsd -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jan 28 17:12: 8 2000 Delivered-To: freebsd-net@freebsd.org Received: from awfulhak.org (dynamic-19.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.147]) by hub.freebsd.org (Postfix) with ESMTP id 0D10015E43 for ; Fri, 28 Jan 2000 17:11:55 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id BAA70255; Sat, 29 Jan 2000 01:11:52 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id JAA01067; Fri, 28 Jan 2000 09:23:00 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200001280923.JAA01067@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Dany Cayouette Cc: freebsd-net@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: [Fwd: PPPoE Problems] In-Reply-To: Message from Dany Cayouette of "Fri, 28 Jan 2000 00:19:52 EST." <389126F7.F9A3FBF9@playground.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Jan 2000 09:23:00 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [.....] > Greetings, > I recently got my hands on an old DEC pentium 133 PC. I just got > FreeBSD 3.4-RELEASE installed. I am interested in getting PPPoE > running. I recompile a kernel with all the NETGRAPH options. The first > problem I noticed is a 50% success rate on getting a successful > connection. I start my session with the command "ppp -dedicated". I > stop the session with "kill ". When the process terminates, > I get the following 2 messages: -dedicated isn't a good option for PPPoE as it attempts to keep the device open all the time. Use -ddial instead if you want a 24/7 connection. -dedicated is intended for things like dedicated serial links or (soon thanks to hm) dedicated isdn on-demand links. > /var/log/messages: > Jan 12 16:48:19 freebsd ppp[265]: tun0: Warning: deflink: Oops: Got 8 > bytes but 4 byte payload > Jan 12 16:48:20 freebsd ppp[265]: tun0: Warning: deflink: Oops: Got 8 > bytes but 4 byte payload You can probably ignore these, but they indicate that there may be a problem with the way the PPPoE module is trimming the packets - looks like it might be chopping a bit too much off the end. If you enable physical logging, it may be apparent whether the packet is truncated or is meant to be 4 bytes. [.....] > Regards, > Dany Cayouette -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Jan 29 14:52:17 2000 Delivered-To: freebsd-net@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id C24E11500C; Sat, 29 Jan 2000 14:52:15 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id B0FCB1CD7AA; Sat, 29 Jan 2000 14:52:15 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sat, 29 Jan 2000 14:52:15 -0800 (PST) From: Kris Kennaway To: David Gilbert Cc: Kelly Yancey , freebsd-net@FreeBSD.ORG Subject: Re: netgraph documentation? In-Reply-To: <14480.32715.899509.661306@trooper.velocet.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 On Thu, 27 Jan 2000, David Gilbert wrote: > Tunel password: V3l0c3T Perhaps you shouldn't have told us your password :-) > ... now... I'd dearly like to avoid expensive cisco hardware (or even > more expensive redback hardware)... so has anyone considered how I > might configure this :). Have you looked at net/pptpclient in ports? Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Jan 29 20: 1:10 2000 Delivered-To: freebsd-net@freebsd.org Received: from borg-cube.com (226-193.adsl2.avtel.net [207.71.226.193]) by hub.freebsd.org (Postfix) with ESMTP id 0A9F8158EE; Sat, 29 Jan 2000 20:01:02 -0800 (PST) (envelope-from dburr@borg-cube.com) Received: from borg-cube.com (dburr@borg-cube.com [207.71.226.193]) by borg-cube.com (8.9.3/8.9.3) with ESMTP id UAA01930; Sat, 29 Jan 2000 20:00:57 -0800 (PST) (envelope-from dburr@borg-cube.com) Date: Sat, 29 Jan 2000 20:00:56 -0800 (PST) From: Donald Burr To: freebsd-net@freebsd.org Cc: FreeBSD Hardware Subject: Drivers for Davicom DM9102 10/100 NIC chip 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 One of my suppliers has just started carrying a new item, called the "BookPC", a really nice fully integrated PC (built in AGP video, USB, 10/100 NIC, 56K modem, and AC97 audio) in an extremely small case (even smaller than MicroATX). I'd like to buy a couple of these and turn them into "tiny FreeBSD workstations". unfortunately, they use an ethernet controller that is not supported. It is the Davicom DM9102 (http://www.davicom8.com/lan/dm9102.htm). Fortunately it looks like this company is pretty open-source friendly, there is a datasheet that you can get right off the Web site, and there is even *source* for a Linux driver (also available on the web site). It would be great if this chip were supported under FreeBSD. Unfortunately, I lack the necessary mojo to pull this off. Any takers? Many thanks in advance! -- Donald Burr Resistance is Futile | FreeBSD: The WWW: http://www.borg-cube.com/ ICQ: UIN#16997506 | Power to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | Serve! http:// Phone: (805) 957-9666 FAX: (800) 492-5954 | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Jan 29 22:33:45 2000 Delivered-To: freebsd-net@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id A2B781577E; Sat, 29 Jan 2000 22:33:37 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id BAA48522; Sun, 30 Jan 2000 01:33:28 -0500 (EST) Date: Sun, 30 Jan 2000 01:33:28 -0500 (EST) From: "Matthew N. Dodd" To: Donald Burr Cc: freebsd-net@FreeBSD.ORG, FreeBSD Hardware Subject: Re: Drivers for Davicom DM9102 10/100 NIC chip In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Looks like its already supported in the 'dc' driver. In current or use an earlier driver supporting just the DM9102: http://www.freebsd.org/~wpaul/Davicom/ (Since I'm not sure if Bill has backported the 'dc' driver.) On Sat, 29 Jan 2000, Donald Burr wrote: > One of my suppliers has just started carrying a new item, called the > "BookPC", a really nice fully integrated PC (built in AGP video, USB, > 10/100 NIC, 56K modem, and AC97 audio) in an extremely small case > (even smaller than MicroATX). I'd like to buy a couple of these and > turn them into "tiny FreeBSD workstations". unfortunately, they use > an ethernet controller that is not supported. It is the Davicom > DM9102 (http://www.davicom8.com/lan/dm9102.htm). Fortunately it looks > like this company is pretty open-source friendly, there is a datasheet > that you can get right off the Web site, and there is even *source* > for a Linux driver (also available on the web site). > > It would be great if this chip were supported under > FreeBSD. Unfortunately, I lack the necessary mojo to pull this off. > > Any takers? Many thanks in advance! > -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message