From owner-freebsd-small Sun Apr 22 4:28:28 2001 Delivered-To: freebsd-small@freebsd.org Received: from tao.org.uk (genesis.tao.org.uk [212.135.162.62]) by hub.freebsd.org (Postfix) with ESMTP id 67E8C37B423 for ; Sun, 22 Apr 2001 04:28:25 -0700 (PDT) (envelope-from joe@tao.org.uk) Received: by tao.org.uk (Postfix, from userid 100) id 5CC6F31E1; Sun, 22 Apr 2001 12:28:24 +0100 (BST) Date: Sun, 22 Apr 2001 12:28:23 +0100 From: Josef Karthauser To: Henk Wevers Cc: "freebsd-small@FreeBSD. ORG" Subject: Re: PicoBSD who is maintaining this? Message-ID: <20010422122823.E225@tao.org.uk> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="o0ZfoUVt4BxPQnbU" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from henk@home.cg.nu on Sat, Apr 21, 2001 at 10:34:53PM +0200 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --o0ZfoUVt4BxPQnbU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Apr 21, 2001 at 10:34:53PM +0200, Henk Wevers wrote: > Hi, >=20 > PicoBSD is not working correct, there are problems with the scripts. > Is PicoBSD mantained? In -current or -stable? Joe --o0ZfoUVt4BxPQnbU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjriwFcACgkQXVIcjOaxUBaNVgCeMF/igWhafp7JXxaVRObnp+69 twQAnAxKmKax7YTQQ4eHVS1DhL950Vw0 =D6A1 -----END PGP SIGNATURE----- --o0ZfoUVt4BxPQnbU-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon Apr 23 20: 9:34 2001 Delivered-To: freebsd-small@freebsd.org Received: from mailcore4.oh.voyager.net (mailcore4.oh.voyager.net [207.90.100.18]) by hub.freebsd.org (Postfix) with ESMTP id EAC0537B423 for ; Mon, 23 Apr 2001 20:09:31 -0700 (PDT) (envelope-from offworld@richnet.net) Received: from quick (d137.as0.asld.oh.voyager.net [209.239.149.137]) by mailcore4.oh.voyager.net (8.9.3/8.9.3) with SMTP id XAA76814 for ; Mon, 23 Apr 2001 23:09:19 -0400 (EDT) Message-ID: <002001c0cc6d$be9aee20$8995efd1@quick> From: "Mark" To: "freebsd-small@FreeBSD.ORG\"" Subject: Is BSD capable?? Date: Mon, 23 Apr 2001 23:22:06 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is BSD capable of taking 2 half duplex NICs like with a coax (BNC) cabled network and having them work "send only" and "receive only" to form a full duplex link? For that matter, is any of the *nux OS's capable of doing this? Or Cisco for that matter. I have a project that needs this type of solution, making a full duplex network out of 2 half duplex devices. Any hope for me? Just a man or howto would be more than enough. Thanks, Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon Apr 23 21:22: 8 2001 Delivered-To: freebsd-small@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 6ECC737B424 for ; Mon, 23 Apr 2001 21:22:06 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f3O4M4V02295; Mon, 23 Apr 2001 21:22:04 -0700 Date: Mon, 23 Apr 2001 21:22:04 -0700 From: Brooks Davis To: Mark Cc: "freebsd-small@FreeBSD.ORG" Subject: Re: Is BSD capable?? Message-ID: <20010423212204.B32567@Odin.AC.HMC.Edu> References: <002001c0cc6d$be9aee20$8995efd1@quick> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="4bRzO86E/ozDv8r1" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <002001c0cc6d$be9aee20$8995efd1@quick>; from offworld@richnet.net on Mon, Apr 23, 2001 at 11:22:06PM -0400 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --4bRzO86E/ozDv8r1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 23, 2001 at 11:22:06PM -0400, Mark wrote: > Is BSD capable of taking 2 half duplex NICs like with a coax (BNC) cabled > network and having them work "send only" and "receive only" to form a full > duplex link? For that matter, is any of the *nux OS's capable of doing th= is? > Or Cisco for that matter. I have a project that needs this type of soluti= on, > making a full duplex network out of 2 half duplex devices. Any hope for m= e? > Just a man or howto would be more than enough. Full duplex communication on coax (a shared medium) isn't even a valid concept. If you're talking no one else can be, there's literaly only one wire. What do you actually want to do here? -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --4bRzO86E/ozDv8r1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE65P9rXY6L6fI4GtQRAvHXAJoDOMZv2GszlR2Lh+voz3LpBYK6+gCfXE3t TmflmWq1IkgFyJ2eJbUmnzg= =Xwg6 -----END PGP SIGNATURE----- --4bRzO86E/ozDv8r1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 24 0:37:58 2001 Delivered-To: freebsd-small@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id E75F937B424 for ; Tue, 24 Apr 2001 00:37:49 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.1) with ESMTP id f3O7bh809710 for ; Tue, 24 Apr 2001 01:37:48 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200104240737.f3O7bh809710@harmony.village.org> To: freebsd-small@freebsd.org Subject: Fix for current Date: Tue, 24 Apr 2001 01:37:43 -0600 From: Warner Losh Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, the boot sequence is ugly, but at least it works for me. People can clean up the ugliness by redirecting things, but for now I'd like to see the ugliness. I plan on committing the following patches, unless there's an objection. If someone comes up with a cooler architecture for mdconfig, then so be it. They can commit it. These are quick fixes to get past phk's sleep 15's. Oh, these do require that one does a MAKEDEV md{0,1,2,3} in the /dev that is mounted by the diskless stuff. I also think that the mfs mounting of /etc should be optional in rc.diskless1 since that's how our embedded device runs, but I'll leave that for later. Also, 4096 is way too big for /dev. It really should be more like 300 with some "tweaks" to the disklabel. We do that in our embedded device as well. http://people.freebsd.org/~imp/rc.diskless.diff Warner P.S. The above url will be the most current one, but here's the patch right now: Index: rc.diskless1 =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/etc/rc.diskless1,v retrieving revision 1.8 diff -u -r1.8 rc.diskless1 --- rc.diskless1 2001/04/20 23:10:11 1.8 +++ rc.diskless1 2001/04/24 07:24:22 @@ -62,6 +62,13 @@ esac } +mount_md() { + /sbin/mdconfig -a -t malloc -s $1 -u $3 + /sbin/disklabel -r -w md$3 auto + /sbin/newfs /dev/md$3c + /sbin/mount /dev/md$3c $2 +} + # DEBUGGING # # set -v @@ -93,12 +100,13 @@ # Create an MFS /tmp to temporarily hold files from /etc until we # can bootstrap /etc as an MFS. -/sbin/mount_mfs -s 4096 -T qp120at dummy /tmp +mount_md 4096 /tmp 0 +chmod 1777 /tmp chkerr $? "MFS mount on /tmp" /bin/cp -Rp /etc /tmp chkerr $? "cp /etc to /tmp/etc MFS" -/sbin/mount_mfs -s 4096 -T qp120at dummy /etc +mount_md 4096 /etc 1 chkerr $? "MFS mount on /etc" /bin/chmod 755 /etc @@ -107,7 +115,7 @@ rm -rf /tmp/etc /sbin/umount /tmp - +/sbin/mdconfig -d -u 0 # Allow for override files to replace files in /etc. Use /conf/*/etc # to find the override files. First choice is default files that Index: rc.diskless2 =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/etc/rc.diskless2,v retrieving revision 1.8 diff -u -r1.8 rc.diskless2 --- rc.diskless2 2001/04/24 07:02:01 1.8 +++ rc.diskless2 2001/04/24 07:24:22 @@ -29,6 +29,13 @@ # rc.diskless2 # +mount_md() { + /sbin/mdconfig -a -t malloc -s $1 -u $3 + /sbin/disklabel -r -w md$3 auto + /sbin/newfs /dev/md$3c + /sbin/mount /dev/md$3c $2 +} + # If there is a global system configuration file, suck it in. # if [ -r /etc/defaults/rc.conf ]; then @@ -39,7 +46,7 @@ fi echo "+++ mfs_mount of /var" -mount_mfs -s ${varsize:=65536} -T qp120at dummy /var +mount_md ${varsize:=65536} /var 2 echo "+++ populate /var using /etc/mtree/BSD.var.dist" /usr/sbin/mtree -deU -f /etc/mtree/BSD.var.dist -p /var @@ -65,5 +72,5 @@ # extract a list of device entries, then copy them to a writable partition (cd /; find -x dev | cpio -o -H newc) > /tmp/dev.tmp echo "+++ mount_mfs of /dev" -mount_mfs -s 4096 -i 512 -T qp120at dummy /dev +mount_md 4096 /dev 3 (cd /; cpio -i -H newc -d < /tmp/dev.tmp) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 24 8:13:19 2001 Delivered-To: freebsd-small@freebsd.org Received: from rgmail.regenstrief.org (rgmail.regenstrief.org [134.68.31.197]) by hub.freebsd.org (Postfix) with ESMTP id B578C37B423 for ; Tue, 24 Apr 2001 08:13:14 -0700 (PDT) (envelope-from gunther@aurora.regenstrief.org) Received: from aurora.regenstrief.org (rgnout.regenstrief.org [134.68.31.38]) by rgmail.regenstrief.org (8.11.0/8.8.7) with ESMTP id f3OFDZA16702 for ; Tue, 24 Apr 2001 10:13:36 -0500 Message-ID: <3AE59808.E1CC8B49@aurora.regenstrief.org> Date: Tue, 24 Apr 2001 15:13:12 +0000 From: Gunther Schadow Organization: Regenstrief Institute for Health Care X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-small@freebsd.org Subject: PicoBSD's kernel, /dev/kmem, and the kernfs Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, trying to use the ipfilter suite with PicoBSD poses problems. Ipfstat uses /kernel and /dev/kmem to read the filter statistics and this seems not available on PicoBSD. Sure this is because the PicoBSD kernel is without any symbols and is gzipped, and is not even in the root file system. There are all good reasons why this is so (even if PicoBSD is used from a flash ROM instead of a floppy.) But could one not make kernel and kmem available anyway using the kernfs virtual file system? I could imagine that we need not absolutely strip the kernel from its symbol table. We could still gzip the kernel. Given that the kernel is loaded into physical memory, could it not be accessible from there to the kernfs virtual file system? Or mapped into the mfs root file system? How hard would it be? There are a number of system tools that use kernel and kmem, moving all of them to something like sps and vm etc. would be a lot of repetitive work, there should be a more fundamental solution... Any thoughts? -Gunther -- Gunther Schadow, M.D., Ph.D. gschadow@regenstrief.org Medical Information Scientist Regenstrief Institute for Health Care Adjunct Assistent Professor Indiana University School of Medicine tel:1(317)630-7960 http://aurora.regenstrief.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 24 8:52:47 2001 Delivered-To: freebsd-small@freebsd.org Received: from rgmail.regenstrief.org (rgmail.regenstrief.org [134.68.31.197]) by hub.freebsd.org (Postfix) with ESMTP id 095B837B422 for ; Tue, 24 Apr 2001 08:52:45 -0700 (PDT) (envelope-from gunther@aurora.regenstrief.org) Received: from aurora.regenstrief.org (rgnout.regenstrief.org [134.68.31.38]) by rgmail.regenstrief.org (8.11.0/8.8.7) with ESMTP id f3OFr6A17213 for ; Tue, 24 Apr 2001 10:53:06 -0500 Message-ID: <3AE5A14B.2E365CA2@aurora.regenstrief.org> Date: Tue, 24 Apr 2001 15:52:43 +0000 From: Gunther Schadow Organization: Regenstrief Institute for Health Care X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-small@freebsd.org Subject: Re: PicoBSD's kernel, /dev/kmem, and the kernfs References: <3AE59808.E1CC8B49@aurora.regenstrief.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, on my earlier message, none of this magic seems to be needed just to get ipfstat working, although the man page for ipfstat mumbles about kmem and kernel. What's really needed for it is /dev/ipl. However, I still wonder if it isn't possible to map kmem and kernel into the kernfs. Thanks, -Gunther -- Gunther Schadow, M.D., Ph.D. gschadow@regenstrief.org Medical Information Scientist Regenstrief Institute for Health Care Adjunct Assistent Professor Indiana University School of Medicine tel:1(317)630-7960 http://aurora.regenstrief.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 24 9: 7: 6 2001 Delivered-To: freebsd-small@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [213.162.131.14]) by hub.freebsd.org (Postfix) with ESMTP id 913C937B423 for ; Tue, 24 Apr 2001 09:06:59 -0700 (PDT) (envelope-from abial@webgiro.com) Received: from mx.webgiro.com (unknown [192.168.10.2]) by mimer.webgiro.com (Postfix) with ESMTP id C85C11003EE; Tue, 24 Apr 2001 19:19:32 +0200 (CEST) Received: by mx.webgiro.com (Postfix, from userid 1001) id D07BC7817; Tue, 24 Apr 2001 18:06:44 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id CAF2010E1E; Tue, 24 Apr 2001 18:06:44 +0200 (CEST) Date: Tue, 24 Apr 2001 18:06:38 +0200 (CEST) From: Andrzej Bialecki To: Gunther Schadow Cc: freebsd-small@freebsd.org Subject: Re: PicoBSD's kernel, /dev/kmem, and the kernfs In-Reply-To: <3AE59808.E1CC8B49@aurora.regenstrief.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 Apr 2001, Gunther Schadow wrote: > Hi, > > trying to use the ipfilter suite with PicoBSD poses problems. Ipfstat > uses /kernel and /dev/kmem to read the filter statistics and this seems > not available on PicoBSD. Sure this is because the PicoBSD kernel is > without any symbols and is gzipped, and is not even in the root file > system. There are all good reasons why this is so (even if PicoBSD is > used from a flash ROM instead of a floppy.) But could one not make > kernel and kmem available anyway using the kernfs virtual file system? > I could imagine that we need not absolutely strip the kernel from its > symbol table. We could still gzip the kernel. Given that the kernel > is loaded into physical memory, could it not be accessible from there > to the kernfs virtual file system? Or mapped into the mfs root file > system? How hard would it be? > > There are a number of system tools that use kernel and kmem, moving ********* "a rapidly decreasing number"... > all of them to something like sps and vm etc. would be a lot of > repetitive work, there should be a more fundamental solution... > > Any thoughts? > -Gunther Well, the general trend in FreeBSD kernel development is to phase out all /dev/kmem access, even when wrapped with libkvm calls, using sysctl(9) instead. Groping through kernel memory is Bad. Sysctl(9) presents consistent, safe, and well-defined interface. The utilities like vm, ns, and others are in fact now much closer to the standard utilities, because recently most (if not all) kvm_* calls in the latter have been replaced with sysctl calls. So, the fundamental solution is to move everything that needs to access from user-space any internal kernel data structures either to a device or a sysctl. Consequently, my POV on this is: if ipfilter uses /dev/kmem, then it should be fixed. Andrzej // ---------------------------------------------------------------- // Andrzej Bialecki , Chief System Architect // WebGiro AB, Sweden (http://www.webgiro.com) // ---------------------------------------------------------------- // FreeBSD developer (http://www.freebsd.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 24 9:27:38 2001 Delivered-To: freebsd-small@freebsd.org Received: from coopercitrus.com.br (coopages.coopercitrus.com.br [200.230.122.8]) by hub.freebsd.org (Postfix) with ESMTP id 9733537B424; Tue, 24 Apr 2001 09:27:28 -0700 (PDT) (envelope-from ennio@coopercitrus.com.br) Received: by coopercitrus.com.br from localhost (router,SLMail V5.0); Tue, 24 Apr 2001 13:26:17 -0200 for Received: from scarpellini [200.230.122.43] by coopercitrus.com.br [200.230.122.8] (SLmail 5.0.0.4342) with SMTP id 6D71A40137E511D5B89100500408B19F for plus 1 more; Tue, 24 Apr 2001 13:26:11 -0300 Message-ID: <000f01c0ccdb$76cfae00$2b7ae6c8@scarpellini> From: "Ennio da Silveira Scarpellini" To: , Subject: picoBSD Dial-up Date: Tue, 24 Apr 2001 13:27:31 -0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000C_01C0CCC2.50DA9D40" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-SLUIDL: 56979583-37EC11D5-B8910050-0408B19F Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_000C_01C0CCC2.50DA9D40 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable ###English I have a NoteBook 486 with 4MB of RAM and processor Cyrix. =20 In this NoteBook I tried run PicoBSD-DialUp and PicoBSD-Router, but not = obtained success with the version Dial-Up. =20 The Router-version doesn't satisfy me...: / =20 Because I want a version with which I can me to connect in Internet =20 using PPP (Dial-Up). In the Router-version text editor doesn't exist = (ee). =20 All this makes to want me a better version. =20 I consider the Version Dial-Up as a good version of PicoBSD, but when =20 I place the boot disk, PicoBSD begins to be read [0:fd(0,a)kernel] and = he usually works to begin uncompressing of Kernel (Uncompressing = Kernel...), =20 but he appears an error message " invalid compressed format ". =20 The version in that happens that error message it is PicoBSD Dial-Up = (freebsd.org/~picobsd/picobsd.html) =20 I like to usually use the version Dial-Up, or please teach me to use = internet with the version Router =20 You would like to obtain a solution for my problem. =20 If somebody has some other version Dial-Up that is compatible with my = NoteBook, please send me an e-mail. ###Portugu=EAs Eu tenho um NoteBook 486 com 4MB de RAM e processador Cyrix. =20 Neste NoteBook tentei rodar o PicoBSD-DialUp e PicoBSD-Router, mas n=E3o = =20 obtive sucesso com a vers=E3o Dial-Up. =20 A Vers=E3o Router n=E3o me satisfaz... :/ =20 Pois quero uma vers=E3o com a qual posso me conectar na Internet =20 usando PPP (Dial-Up). Na Vers=E3o Router n=E3o existe editor de texto = (ee). =20 Tudo isso me faz querer uma vers=E3o melhor. =20 Eu considero a Vers=E3o Dial-Up como uma boa vers=E3o do PicoBSD, mas = quando =20 coloco o disco de boot, o PicoBSD come=E7a a ser lido [0:fd(0,a)kernel] = e =20 funciona normalmente at=E9 a come=E7ar adescompacta=E7=E3o do Kernel = (Uncompressing Kernel...), =20 mas aparece uma mensagem de erro "invalid compressed format" e o = computador trava. =20 A vers=E3o em que ocorre esse mensagem de erro =E9 o PicoBSD Dial-Up = (freebsd.org/~picobsd/picobsd.html) =20 Gostaria de poder usar normalmente a vers=E3o Dial-Up ou por favor me = ensinem a usar internet com a vers=E3o Router =20 Gostaria de obter uma solu=E7=E3o para o meu problema. =20 Se algu=E9m tem alguma outra vers=E3o Dial-Up que seja compat=EDvel com = meu NoteBook, por favor envie-me um e-mail. ------=_NextPart_000_000C_01C0CCC2.50DA9D40 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
 
###English
I have a NoteBook 486 with 4MB of RAM and processor=20 Cyrix.   
In this NoteBook I tried run PicoBSD-DialUp = and=20 PicoBSD-Router, but not 
obtained success with the version=20 Dial-Up.   
The Router-version doesn't satisfy me...: = /   
Because I want a version with which I can me to = connect=20 in Internet  
using PPP (Dial-Up). In the Router-version = text=20 editor doesn't exist (ee). 
All this makes to want me a better=20 version.   
I consider the Version Dial-Up as a good = version=20 of PicoBSD, but when  
I place the boot disk, PicoBSD = begins to be=20 read [0:fd(0,a)kernel] and  
he usually works to begin=20 uncompressing of Kernel (Uncompressing Kernel...),  
but = he=20 appears an error message " invalid compressed format ". 
The = version in=20 that happens that error message it is PicoBSD Dial-Up=20 (freebsd.org/~picobsd/picobsd.html)   
I like to = usually use=20 the version Dial-Up, or please teach me to use internet with the version = Router 
You would like to obtain a solution for my = problem. =20
If somebody has some other version Dial-Up that is compatible with = my=20 NoteBook, please send me an e-mail.
 
###Portugu=EAs
Eu tenho um NoteBook 486 com 4MB de RAM e = processador=20 Cyrix.   
Neste NoteBook tentei rodar o = PicoBSD-DialUp e=20 PicoBSD-Router, mas n=E3o 
obtive sucesso com a vers=E3o=20 Dial-Up.   
A Vers=E3o Router n=E3o me satisfaz...=20 :/   
Pois quero uma vers=E3o com a qual posso me = conectar na=20 Internet  
usando PPP (Dial-Up). Na Vers=E3o Router n=E3o = existe=20 editor de  texto (ee). 
Tudo isso me faz querer uma = vers=E3o=20 melhor.   
Eu considero a Vers=E3o Dial-Up como uma = boa vers=E3o=20 do PicoBSD, mas quando  
coloco o disco de boot, o PicoBSD = come=E7a=20 a ser lido [0:fd(0,a)kernel] e  
funciona normalmente = at=E9 a=20 come=E7ar adescompacta=E7=E3o do Kernel (Uncompressing = Kernel...),  
mas=20 aparece uma mensagem de erro "invalid compressed format" e o computador=20 trava. 
A vers=E3o em que ocorre esse mensagem de erro =E9 o = PicoBSD=20 Dial-Up (freebsd.org/~picobsd/picobsd.html)    =
Gostaria de=20 poder usar normalmente a vers=E3o Dial-Up ou por favor me ensinem a usar = internet=20 com a vers=E3o Router 
Gostaria de obter uma solu=E7=E3o para o = meu=20 problema. 
Se algu=E9m tem alguma outra vers=E3o Dial-Up que = seja=20 compat=EDvel com meu NoteBook, por favor envie-me um = e-mail.
 
------=_NextPart_000_000C_01C0CCC2.50DA9D40-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 24 9:29: 4 2001 Delivered-To: freebsd-small@freebsd.org Received: from rgmail.regenstrief.org (rgmail.regenstrief.org [134.68.31.197]) by hub.freebsd.org (Postfix) with ESMTP id E924F37B424 for ; Tue, 24 Apr 2001 09:29:00 -0700 (PDT) (envelope-from gunther@aurora.regenstrief.org) Received: from aurora.regenstrief.org (rgnout.regenstrief.org [134.68.31.38]) by rgmail.regenstrief.org (8.11.0/8.8.7) with ESMTP id f3OGT1A17714; Tue, 24 Apr 2001 11:29:06 -0500 Message-ID: <3AE5A9B6.FF7546CC@aurora.regenstrief.org> Date: Tue, 24 Apr 2001 16:28:38 +0000 From: Gunther Schadow Organization: Regenstrief Institute for Health Care X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Andrzej Bialecki Cc: freebsd-small@freebsd.org Subject: Re: PicoBSD's kernel, /dev/kmem, and the kernfs References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki wrote: > Well, the general trend in FreeBSD kernel development is to phase out all > /dev/kmem access, even when wrapped with libkvm calls, using sysctl(9) > instead. Groping through kernel memory is Bad. Sysctl(9) presents > consistent, safe, and well-defined interface. ... > Consequently, my POV on this is: if ipfilter uses /dev/kmem, then it > should be fixed. This makes perfect sense to me, thanks for the clarification. regards, -Gunther Sometimes it is hard to keep up with a world that is constantly getting better :-) -- Gunther Schadow, M.D., Ph.D. gschadow@regenstrief.org Medical Information Scientist Regenstrief Institute for Health Care Adjunct Assistent Professor Indiana University School of Medicine tel:1(317)630-7960 http://aurora.regenstrief.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 24 12: 3:34 2001 Delivered-To: freebsd-small@freebsd.org Received: from rgmail.regenstrief.org (rgmail.regenstrief.org [134.68.31.197]) by hub.freebsd.org (Postfix) with ESMTP id 5D72B37B42C for ; Tue, 24 Apr 2001 12:03:31 -0700 (PDT) (envelope-from gunther@aurora.regenstrief.org) Received: from aurora.regenstrief.org (rgnout.regenstrief.org [134.68.31.38]) by rgmail.regenstrief.org (8.11.0/8.8.7) with ESMTP id f3OJ3nA19963; Tue, 24 Apr 2001 14:03:49 -0500 Message-ID: <3AE5CDFE.9900D18B@aurora.regenstrief.org> Date: Tue, 24 Apr 2001 19:03:26 +0000 From: Gunther Schadow Organization: Regenstrief Institute for Health Care X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Luigi Rizzo , freebsd-small@freebsd.org Subject: ipfw vs. ipf (was: Re: PicoBSD's kernel, /dev/kmem, and the kernfs References: <200104241825.UAA32171@info.iet.unipi.it> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luigi Rizzo wrote: > for once i should say: > > try ipfw, it does most of the things ipfilter does (except for > in-kernel nat) and something more (dummynet and fair queueing) Yes, I actually started with ipfw but I now migrate to ipf. I find ipfw and the DIVERT socket quite elegant, but still, I migrate. The reasons I migrate to ipf (and the reason you might want to think about this too) are: - ipf is accross all *BSD's - ipf is more likely to play well with IPsec - ipf is (arguably) more secure These points are actually dependent. The maintenance of ipf sounds pretty strong to me, so I'd trust it more. I am generally worried about too much splintering between the *BSDs, and I prefer what leaves me compatible. For PicoBSD issues there is a great benefit of staying somewhat compatible to NetBSD, namely NetBSD's support of other machine architectures. StrongARM or MIPS bases systems are often smaller and cheaper. The IPsec/ipf* integration is a concern of everyone who builds a VPN-gateway and firewall. The KAME people lean towards better IPsec SPD integration with ipf, because ipf is a platform used accross all *BSDs. Finally, for dummynet and fair queuing I prefer using ALTQ, for similar reasons. After I have survived the pain of saying goodbye to ipfw, I wonder why FreeBSD tries to make its own thing with ipfw instead of just riding the wave of ipf. regards -Gunther -- Gunther Schadow, M.D., Ph.D. gschadow@regenstrief.org Medical Information Scientist Regenstrief Institute for Health Care Adjunct Assistent Professor Indiana University School of Medicine tel:1(317)630-7960 http://aurora.regenstrief.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 24 12:41:42 2001 Delivered-To: freebsd-small@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 1B42037B422 for ; Tue, 24 Apr 2001 12:41:39 -0700 (PDT) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id VAA34068; Tue, 24 Apr 2001 21:39:49 +0200 (CEST) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200104241939.VAA34068@info.iet.unipi.it> Subject: Re: ipfw vs. ipf (was: Re: PicoBSD's kernel, /dev/kmem, and the kernfs In-Reply-To: <3AE5CDFE.9900D18B@aurora.regenstrief.org> from Gunther Schadow at "Apr 24, 2001 07:03:26 pm" To: Gunther Schadow Date: Tue, 24 Apr 2001 21:39:49 +0200 (CEST) Cc: freebsd-small@freebsd.org 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-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [this is a serious reply even if the tone sounds not] > Finally, for dummynet and fair queuing I prefer using ALTQ, for > similar reasons. After I have survived the pain of saying goodbye > to ipfw, I wonder why FreeBSD tries to make its own thing with > ipfw instead of just riding the wave of ipf. and i wonder why BSD tries to make its own thing with the operating system instead of just riding the wave of BSD. My understanding is that diversity is good. Case in point, dummynet and ALTQ are really two different beasts with different features, goals and performance. Sometimes you need one, sometimes you need the other, and understandably no developer on either side has the interest or energy to merge features. Also from a developer's point of view, it surely takes me, or Darren, or Kenjiro, very little programming effort, and no politics, to modify our own babies, whereas it would take endless email exchanges just to reach consensus on features, followed by discussions on 2 vs 4 vs 8 space indentation etc. etc. Not to mention NIH syndrome which plays a fundamental role in all camps :) 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-small" in the body of the message From owner-freebsd-small Tue Apr 24 12:43:44 2001 Delivered-To: freebsd-small@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id F1F0B37B422 for ; Tue, 24 Apr 2001 12:43:40 -0700 (PDT) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id VAA34133; Tue, 24 Apr 2001 21:41:52 +0200 (CEST) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200104241941.VAA34133@info.iet.unipi.it> Subject: Re: ipfw vs. ipf (was: Re: PicoBSD's kernel, /dev/kmem, and the kernfs In-Reply-To: <3AE5CDFE.9900D18B@aurora.regenstrief.org> from Gunther Schadow at "Apr 24, 2001 07:03:26 pm" To: Gunther Schadow Date: Tue, 24 Apr 2001 21:41:51 +0200 (CEST) Cc: freebsd-small@FreeBSD.ORG 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-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > - ipf is more likely to play well with IPsec can you be more specific on this one ? cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 24 13:12:57 2001 Delivered-To: freebsd-small@freebsd.org Received: from rgmail.regenstrief.org (rgmail.regenstrief.org [134.68.31.197]) by hub.freebsd.org (Postfix) with ESMTP id 5895237B422 for ; Tue, 24 Apr 2001 13:12:54 -0700 (PDT) (envelope-from gunther@aurora.regenstrief.org) Received: from aurora.regenstrief.org (rgnout.regenstrief.org [134.68.31.38]) by rgmail.regenstrief.org (8.11.0/8.8.7) with ESMTP id f3OKDDA20897; Tue, 24 Apr 2001 15:13:13 -0500 Message-ID: <3AE5DE42.75523F60@aurora.regenstrief.org> Date: Tue, 24 Apr 2001 20:12:50 +0000 From: Gunther Schadow Organization: Regenstrief Institute for Health Care X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Luigi Rizzo Cc: freebsd-small@FreeBSD.ORG Subject: Re: ipfw vs. ipf (was: Re: PicoBSD's kernel, /dev/kmem, and the kernfs References: <200104241941.VAA34133@info.iet.unipi.it> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luigi Rizzo wrote: > > > - ipf is more likely to play well with IPsec > > can you be more specific on this one ? Yes, in fact I'm just about checking this again. You can see Itojun's thoughts about this at: http://www.netbsd.org/Documentation/network/ipsec/#ipf-interaction and there is a patch that had been applied to the recent KAME SNAP kit that implements the rule. The rule is: IPsec AH and ESP processing occurs on the inside of packet filtering. That is, before the filter on outgoing packets and after the filter on incoming packets. This may or may not have been fixed with ipfw. In fact, I was quite able to use IPsec with ipfw on one host, but I was never really sure about it. And, I'm looking forward to IPsec SPD packet matching rules to be combined with ipf. I remember Itojun or Sakane mentioning those further plans recently. regards, -Gunther -- Gunther Schadow, M.D., Ph.D. gschadow@regenstrief.org Medical Information Scientist Regenstrief Institute for Health Care Adjunct Assistent Professor Indiana University School of Medicine tel:1(317)630-7960 http://aurora.regenstrief.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 24 14:51:48 2001 Delivered-To: freebsd-small@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 6895E37B422 for ; Tue, 24 Apr 2001 14:51:45 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f3OLpcF02538; Tue, 24 Apr 2001 14:51:38 -0700 Date: Tue, 24 Apr 2001 14:51:38 -0700 From: Brooks Davis To: Mark Cc: freebsd-small@FreeBSD.ORG Subject: Re: Is BSD capable?? Message-ID: <20010424145138.B30762@Odin.AC.HMC.Edu> References: <002001c0cc6d$be9aee20$8995efd1@quick> <20010423212204.B32567@Odin.AC.HMC.Edu> <01042421341401.14955@offworld1.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="Pd0ReVV5GZGQvF3a" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <01042421341401.14955@offworld1.net>; from mark@offworld1.net on Tue, Apr 24, 2001 at 09:33:11PM -0400 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Pd0ReVV5GZGQvF3a Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 24, 2001 at 09:33:11PM -0400, Mark wrote: > The real application is with 2.4 Ghz wireless radios. They are half duple= x. I > want to take 2 (two) half duplex links, 4 radios total, and have them set= up in > transmit / receive pairs to give me "full duplex" type of operation. If i= t can > be done, it will save me THOUSANDS of dollars ($$$$$$$$$). >=20 > I hope that this clears things up a bit ;-) Much better. ;-) I think this should be doable. I suspect doing something with netgraph and the ng_eiface node. The eiface node would be the virtual interface and it's output would go to the input of the sending card. The output of the recieving card would go to the other one. I think that would work. If I remember my Ethernet basics correctly, it won't work perfectly because of the delay before sending another packet but I think it will work. I am wondering why you want to do this rather then useing Bill Paul's EtherChannel module to bond a couple links since most applications aren't symetric bandwidth users all the time. http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=3D448009+451351+/usr/local/www/= db/text/2001/freebsd-net/20010211.freebsd-net -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --Pd0ReVV5GZGQvF3a Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE65fVpXY6L6fI4GtQRAk/uAJ9atZ3fojeOWrwZVnvqMWP3nSXCZQCeO8+t Rf3CInvZatw48cONb+o3JGw= =UHeE -----END PGP SIGNATURE----- --Pd0ReVV5GZGQvF3a-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 24 16:40:40 2001 Delivered-To: freebsd-small@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id EA6C937B423 for ; Tue, 24 Apr 2001 16:40:35 -0700 (PDT) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id BAA36223; Wed, 25 Apr 2001 01:38:40 +0200 (CEST) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200104242338.BAA36223@info.iet.unipi.it> Subject: Re: ipfw vs. ipf (was: Re: PicoBSD's kernel, /dev/kmem, and the kernfs In-Reply-To: <3AE5DE42.75523F60@aurora.regenstrief.org> from Gunther Schadow at "Apr 24, 2001 08:12:50 pm" To: Gunther Schadow Date: Wed, 25 Apr 2001 01:38:40 +0200 (CEST) Cc: freebsd-small@FreeBSD.ORG 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-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > can you be more specific on this one ? > > Yes, in fact I'm just about checking this again. You can see Itojun's > thoughts about this at: > > http://www.netbsd.org/Documentation/network/ipsec/#ipf-interaction > > and there is a patch that had been applied to the recent KAME SNAP > kit that implements the rule. The rule is: i suppose it is better waiting for the daylight in japan... surely itojun and friends know what issues (if any) are there with ipfw. (also note that there are ipfw and ipfw6 which are not the same thing, and mightbe slightly out of sync). cheers luigi > IPsec AH and ESP processing occurs on the inside of packet filtering. > That is, before the filter on outgoing packets and after the filter > on incoming packets. This may or may not have been fixed with ipfw. > In fact, I was quite able to use IPsec with ipfw on one host, but > I was never really sure about it. And, I'm looking forward to IPsec > SPD packet matching rules to be combined with ipf. I remember Itojun > or Sakane mentioning those further plans recently. > > regards, > -Gunther > > -- > Gunther Schadow, M.D., Ph.D. gschadow@regenstrief.org > Medical Information Scientist Regenstrief Institute for Health Care > Adjunct Assistent Professor Indiana University School of Medicine > tel:1(317)630-7960 http://aurora.regenstrief.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-small" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 24 18:18:54 2001 Delivered-To: freebsd-small@freebsd.org Received: from borg.inreach.com (borg.inreach.com [209.142.2.66]) by hub.freebsd.org (Postfix) with SMTP id A69DE37B422 for ; Tue, 24 Apr 2001 18:18:51 -0700 (PDT) (envelope-from norami@unlimited.net) Received: (qmail 22930 invoked from network); 25 Apr 2001 01:18:41 -0000 Received: from 209-142-4-28.stk.inreach.net (HELO unlimited.net) (209.142.4.28) by mail.unlimited.net with SMTP; 25 Apr 2001 01:18:41 -0000 Message-ID: <3AE6269C.3CFB42B9@unlimited.net> Date: Tue, 24 Apr 2001 18:21:32 -0700 From: John Oram X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Mark Cc: Brooks Davis , freebsd-small@FreeBSD.ORG Subject: Re: Is BSD capable?? References: <002001c0cc6d$be9aee20$8995efd1@quick> <20010423212204.B32567@Odin.AC.HMC.Edu> <01042421341401.14955@offworld1.net> <20010424145138.B30762@Odin.AC.HMC.Edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark: Take a look at Lonnie Nunweiler @ Web Warehouse is running 2.4 GHz wireless radios and can assist you in using either PicoBSD or Linux. He has more than four experience doing what your asking about. His approach may save you a lot of time and money. Another place to look is the Archives: If I can be of assistance, let me know. John Oram Brooks Davis wrote: > > On Tue, Apr 24, 2001 at 09:33:11PM -0400, Mark wrote: > > The real application is with 2.4 Ghz wireless radios. They are half duplex. I > > want to take 2 (two) half duplex links, 4 radios total, and have them setup in > > transmit / receive pairs to give me "full duplex" type of operation. If it can > > be done, it will save me THOUSANDS of dollars ($$$$$$$$$). > > > > I hope that this clears things up a bit ;-) > > Much better. ;-) I think this should be doable. I suspect doing > something with netgraph and the ng_eiface node. The eiface node would > be the virtual interface and it's output would go to the input of the > sending card. The output of the recieving card would go to the other one. > I think that would work. If I remember my Ethernet basics correctly, > it won't work perfectly because of the delay before sending another > packet but I think it will work. I am wondering why you want to do this > rather then useing Bill Paul's EtherChannel module to bond a couple > links since most applications aren't symetric bandwidth users all the > time. > > http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=448009+451351+/usr/local/www/db/text/2001/freebsd-net/20010211.freebsd-net > > -- Brooks > > -- > Any statement of the form "X is the one, true Y" is FALSE. > PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 > > ------------------------------------------------------------------------ > Part 1.2Type: application/pgp-signature To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 24 21: 3:36 2001 Delivered-To: freebsd-small@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id A87BC37B424 for ; Tue, 24 Apr 2001 21:03:33 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f3P43Wu01999; Tue, 24 Apr 2001 21:03:32 -0700 Date: Tue, 24 Apr 2001 21:03:32 -0700 From: Brooks Davis To: Mark Cc: freebsd-small@FreeBSD.ORG Subject: Re: Is BSD capable?? Message-ID: <20010424210332.A30795@Odin.AC.HMC.Edu> References: <002001c0cc6d$be9aee20$8995efd1@quick> <01042421341401.14955@offworld1.net> <20010424145138.B30762@Odin.AC.HMC.Edu> <01042503542301.15147@offworld1.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="AqsLC8rIMeq19msA" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <01042503542301.15147@offworld1.net>; from mark@offworld1.net on Wed, Apr 25, 2001 at 03:50:33AM -0400 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --AqsLC8rIMeq19msA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 25, 2001 at 03:50:33AM -0400, Mark wrote: > What I have here is a network set up something like the following (simpli= fied > the best I can). Here at the NOC I have a half duplex Access Point (AP1). > This is linked to Remote Site 1 (RS1). Connected to RS1 are 2 more Access > Points (AP2, AP3). All are half duplex. End users connect to AP2 and AP3.= What > happens is, that when a user connects to say AP2 and starts a download, a= nd a > user connected to AP3 attempts to send an MP3 to his bud up in Spider Bre= ath > MO., AP2 and AP3 both attempt to access the gateway, RS1, in two separate > directions at the same time into a half duplex back haul link.=20 >=20 > In practice, one or the other suffers, and when you have 3 doing a downlo= ad=20 > and one fighting upstream, guess which one loses. That is because there is > no control between AP2 and AP3. Neither one knows what the other is doing. > Being able to install a full duplex link in the backbone would give me a > big boost in overall network performance. Trouble is that a full duplex > link is thou$and$ of dollars more than 2 half duplex links. If this can > be done, great, If not, I start saving my pennies.=20 Ok, so if I understand correctly, you have an oversubscribed half duplex link that gets pounded by collisions when in heavy (bi-directional) use. If that's the case, you might try cranking the rts threshold way down on both ends of the link (that's the -r option to {wi,an}control). This introduces a bit more latency by forcing both ends to ask nicely before they send anything, but if most of you're traffic is big it could be a hugh win. Enabling it on my access point raised ping latench from 1.9ms to 2.1ms, enabling it on my Cisco 340 card turned off the pipe so it appears there's some work to be done in that driver. ;-) If that works, then you could use the money you would have spent building a full-duplex link to double your link speed. ;-) -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --AqsLC8rIMeq19msA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE65kyKXY6L6fI4GtQRAjthAJwKC6qvrDpyl6IO6EWmMFEvzU4K/gCgubM+ lLvrvFbKKdGXvqpSw/yAKrU= =m4A/ -----END PGP SIGNATURE----- --AqsLC8rIMeq19msA-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 25 2:28: 5 2001 Delivered-To: freebsd-small@freebsd.org Received: from mailcore1.oh.voyager.net (mailcore1.oh.voyager.net [207.0.229.19]) by hub.freebsd.org (Postfix) with ESMTP id 6373437B422 for ; Wed, 25 Apr 2001 02:28:01 -0700 (PDT) (envelope-from offworld@richnet.net) Received: from quick (d107.as0.asld.oh.voyager.net [209.239.149.107]) by mailcore1.oh.voyager.net (8.9.3/8.9.3) with SMTP id FAA37832; Wed, 25 Apr 2001 05:27:56 -0400 (EDT) Message-ID: <006f01c0cd6b$ceba8960$6b95efd1@quick> From: "Mark" To: "Brooks Davis" Cc: "'freebsd-small@freebsd.org'" References: <002001c0cc6d$be9aee20$8995efd1@quick> <01042421341401.14955@offworld1.net> <20010424145138.B30762@Odin.AC.HMC.Edu> <01042503542301.15147@offworld1.net> <20010424210332.A30795@Odin.AC.HMC.Edu> Subject: Re: Is BSD capable?? Date: Wed, 25 Apr 2001 05:40:42 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would say that the system is far from being oversubscribed. I would call it the "hidden node" problem. These are not smart radios, more like bridges. The upload problem is not a big one and all users are happy as of now. I am just looking forward to the time when I get the system loaded down. Regardless to how the units are performing, dumping the half duplex units onto a full duplex backbone can only be of benefit. If I could do this with a BSD router and equipment on hand, life would be good and I would be doing something that most are not. I need to get my routers replaced with the BSD boxes soon any way. I am using the cable / DSL routers now out at the remote sites and in all candor, they suck!! Very limited in features. They work and are not crashing but place to many limits on the system and they appear to be adding some unnecessary latency into the system. On Wed, Apr 25, 2001 at 03:50:33AM -0400, Mark wrote: > What I have here is a network set up something like the following (simplified > the best I can). Here at the NOC I have a half duplex Access Point (AP1). > This is linked to Remote Site 1 (RS1). Connected to RS1 are 2 more Access > Points (AP2, AP3). All are half duplex. End users connect to AP2 and AP3. What > happens is, that when a user connects to say AP2 and starts a download, and a > user connected to AP3 attempts to send an MP3 to his bud up in Spider Breath > MO., AP2 and AP3 both attempt to access the gateway, RS1, in two separate > directions at the same time into a half duplex back haul link. > > In practice, one or the other suffers, and when you have 3 doing a download > and one fighting upstream, guess which one loses. That is because there is > no control between AP2 and AP3. Neither one knows what the other is doing. > Being able to install a full duplex link in the backbone would give me a > big boost in overall network performance. Trouble is that a full duplex > link is thou$and$ of dollars more than 2 half duplex links. If this can > be done, great, If not, I start saving my pennies. Ok, so if I understand correctly, you have an oversubscribed half duplex link that gets pounded by collisions when in heavy (bi-directional) use. If that's the case, you might try cranking the rts threshold way down on both ends of the link (that's the -r option to {wi,an}control). This introduces a bit more latency by forcing both ends to ask nicely before they send anything, but if most of you're traffic is big it could be a hugh win. Enabling it on my access point raised ping latench from 1.9ms to 2.1ms, enabling it on my Cisco 340 card turned off the pipe so it appears there's some work to be done in that driver. ;-) If that works, then you could use the money you would have spent building a full-duplex link to double your link speed. ;-) -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 ----- Original Message ----- From: Brooks Davis To: Mark Cc: Sent: Wednesday, April 25, 2001 12:03 AM Subject: Re: Is BSD capable?? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 25 7:50:48 2001 Delivered-To: freebsd-small@freebsd.org Received: from tpts4.seed.net.tw (tpts4.seed.net.tw [139.175.55.242]) by hub.freebsd.org (Postfix) with ESMTP id 0582137B424 for ; Wed, 25 Apr 2001 07:50:46 -0700 (PDT) (envelope-from andytien@tpts4.seed.net.tw) Received: from swtp131-103.adsl.seed.net.tw ([211.74.131.103] helo=t) by tpts4.seed.net.tw with smtp (Seednet Mail Server v2.313fd) id 14sQcW-0003Aw-00 for freebsd-small@FreeBSD.ORG; Wed, 25 Apr 2001 22:50:20 +0800 Date: Wed, 25 Apr 2001 22:51:38 +0800 From: Andy Tien To: freebsd-small@FreeBSD.ORG Subject: How can I using picobsd for ADSL dialup X-mailer: FoxMail 2.1 [en] Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi sir, recently I upgrade my system to FreeBSD 4.3 and using picobsd 0.5 try to connect with a ADSL connection to internet in the complete system the ADSL dial can work , but the picobsd just diaplay the message "PPPOE:de0 unknow host " I vabe include options netgraph , and netgrapg_pppoe Why ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 25 10: 0:16 2001 Delivered-To: freebsd-small@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 6CE7A37B43F for ; Wed, 25 Apr 2001 10:00:10 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f3PH07O11798; Wed, 25 Apr 2001 10:00:07 -0700 Date: Wed, 25 Apr 2001 10:00:07 -0700 From: Brooks Davis To: Mark Cc: "'freebsd-small@freebsd.org'" Subject: Re: Is BSD capable?? Message-ID: <20010425100006.B32753@Odin.AC.HMC.Edu> References: <002001c0cc6d$be9aee20$8995efd1@quick> <01042421341401.14955@offworld1.net> <20010424145138.B30762@Odin.AC.HMC.Edu> <01042503542301.15147@offworld1.net> <20010424210332.A30795@Odin.AC.HMC.Edu> <006f01c0cd6b$ceba8960$6b95efd1@quick> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="XF85m9dhOBO43t/C" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <006f01c0cd6b$ceba8960$6b95efd1@quick>; from offworld@richnet.net on Wed, Apr 25, 2001 at 05:40:42AM -0400 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --XF85m9dhOBO43t/C Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 25, 2001 at 05:40:42AM -0400, Mark wrote: > I would say that the system is far from being oversubscribed. I would call > it the "hidden node" problem. These are not smart radios, more like bridg= es. The rts/cts handshake is designed to solve the hidden node problem. The RTS tells everyone who can hear it that they can't broadcast and the CTS does the same. Assuming minimal weird multipath (always a issue at 2.4Ghz) that means no one should talk until the message is sent. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --XF85m9dhOBO43t/C Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE65wKWXY6L6fI4GtQRAhZ9AJ9kIad4LjiWd3FKaWD5gRdkXkeHEgCePSjD ySZJkuUCJdHKSd120h8yzOs= =fVSE -----END PGP SIGNATURE----- --XF85m9dhOBO43t/C-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 25 11:55: 1 2001 Delivered-To: freebsd-small@freebsd.org Received: from rgmail.regenstrief.org (rgmail.regenstrief.org [134.68.31.197]) by hub.freebsd.org (Postfix) with ESMTP id 47E6937B422; Wed, 25 Apr 2001 11:54:57 -0700 (PDT) (envelope-from gunther@aurora.regenstrief.org) Received: from aurora.regenstrief.org (rgnout.regenstrief.org [134.68.31.38]) by rgmail.regenstrief.org (8.11.0/8.8.7) with ESMTP id f3PItCA31666; Wed, 25 Apr 2001 13:55:12 -0500 Message-ID: <3AE71D7F.14ECB429@aurora.regenstrief.org> Date: Wed, 25 Apr 2001 18:54:55 +0000 From: Gunther Schadow Organization: Regenstrief Institute for Health Care X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@freebsd.org, freebsd-small@freebsd.org Subject: DHCP vulnerabilities ... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm just about configuring a PicoBSD-based VPN gateway settop box kind of thing :-). I am dealing with cable modem ISPs and decided to do it the right way, i.e. DHCP. I discovered some problems with DHCP during the setup phase, where the machine is in a weird state, the firewall may not be configured right and neither are the IPsec policies. During that short time frame after DHCP has assigned a new address and the completion of the IPsec ipf stuff called from /etc/dhclinent-exit-hooks the interface is up and may be unprotected. It would be nice if there was a way to keep the re-configured interface down and only bring it up after all is well in /etc/dhclient-exit-hooks. Sure I can (and will) do that in my dhclient-script ("ifconfig if0 down" "ifconfig if0 up",) but just wanted folks to know about this. regards -Gunther -- Gunther Schadow, M.D., Ph.D. gschadow@regenstrief.org Medical Information Scientist Regenstrief Institute for Health Care Adjunct Assistent Professor Indiana University School of Medicine tel:1(317)630-7960 http://aurora.regenstrief.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 25 13:15: 4 2001 Delivered-To: freebsd-small@freebsd.org Received: from rgmail.regenstrief.org (rgmail.regenstrief.org [134.68.31.197]) by hub.freebsd.org (Postfix) with ESMTP id 33AD737B424; Wed, 25 Apr 2001 13:14:58 -0700 (PDT) (envelope-from gunther@aurora.regenstrief.org) Received: from aurora.regenstrief.org (rgnout.regenstrief.org [134.68.31.38]) by rgmail.regenstrief.org (8.11.0/8.8.7) with ESMTP id f3PKFCA32650; Wed, 25 Apr 2001 15:15:12 -0500 Message-ID: <3AE7303F.957DE6DC@aurora.regenstrief.org> Date: Wed, 25 Apr 2001 20:14:55 +0000 From: Gunther Schadow Organization: Regenstrief Institute for Health Care X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@freebsd.org, freebsd-small@freebsd.org, snap-users@kame.net Subject: VPN tunnel with DHCP ... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, about my SOHO router project, I came accross a tough problem, may be I overlook that there is a solution already? The VPN gateway at the small office / home office (SOHO) has an IPsec tunnel connecting it to its headquarter: setkey -c < Date: Wed, 25 Apr 2001 23:35:00 +0000 From: Gunther Schadow Organization: Regenstrief Institute for Health Care X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Larry Baird Cc: freebsd-small@FreeBSD.ORG, phk@FreeBSD.ORG Subject: Re: the fla driver definitely has bugs ... References: <200104052057.QAA69722@gta.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Larry Baird wrote: > I hae thousands of systems installed using the fla driver and > 8MB DOCs without any problem. Initially based upon FreeBSD 3.5., > now based upon 4.2. I'm sorry but I can't confirm that. I have nothing but trouble with the fla device with all 5 boxes that I'm trying to configure. So, I know I don't just have a foul chip. - "stray irq 7" is something that should not ever happen in a clean kernel certainly not when mounting or otherwise accessing a flash disk device. - There is so much magic involved that I don't even dare to create a fresh flash filesystem. I have one image that appears to work and I use that as a template just writing different kernels and configs to it. - The magic as far as I can tell must have to do with the order in which physical "disk" blocks are written. The exact same files can be written such that the system won't boot at all (anything from errors while loading the kernel to panics early in the initialization phase of the kernel can happen) but if written with this magic template and fingers crossed and on a full moon it will work. (It's as if when blocks of the kernel file are not all in a row, the file will be deemed corrupted or something.) This is completely obscure to me and quite annoying, especially since my other device that uses Compact Flash has just *no* problems with any of this, period. So I know I'm not doing anything obvious wrong, I just seem to be falling into the gaps of a brittle device / driver combination. BTW: the systems on which I have problems are the Flytech NetPC B62 systems with 8 MB DiskOnChip. The computers are quite fine otherwise, just that this stupid DiskOnChip thing causes me to rip my hair out. (As you can hear in my tone.) Has anyone from the PicoBSD crew any advice as to why the ordering in which files are written can decide between live or die of an installation? regards -Gunther -- Gunther Schadow, M.D., Ph.D. gschadow@regenstrief.org Medical Information Scientist Regenstrief Institute for Health Care Adjunct Assistent Professor Indiana University School of Medicine tel:1(317)630-7960 http://aurora.regenstrief.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 25 20: 0: 2 2001 Delivered-To: freebsd-small@freebsd.org Received: from gta.com (mailgate.gta.com [199.120.225.4]) by hub.freebsd.org (Postfix) with ESMTP id A89DD37B424; Wed, 25 Apr 2001 19:59:57 -0700 (PDT) (envelope-from lab@gta.com) Received: from gta.com (GTA internal mail system) by gta.com id WAA59170; Wed, 25 Apr 2001 22:53:58 -0400 (EDT) Date: Wed, 25 Apr 2001 22:53:58 -0400 From: Larry Baird To: Gunther Schadow Cc: freebsd-small@FreeBSD.ORG, phk@FreeBSD.ORG Subject: Re: the fla driver definitely has bugs ... Message-ID: <20010425225358.A58470@gta.com> References: <200104052057.QAA69722@gta.com> <3AE75F24.564CC9D4@gta.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <3AE75F24.564CC9D4@gta.com>; from gunther@aurora.regenstrief.org on Wed, Apr 25, 2001 at 11:35:00PM +0000 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm sorry but I can't confirm that. I have nothing but trouble > with the fla device with all 5 boxes that I'm trying to configure. > So, I know I don't just have a foul chip. What can I say. There in the customer's hands without any complaints. (-; > - "stray irq 7" is something that should not ever happen in a clean > kernel certainly not when mounting or otherwise accessing a flash > disk device. Never saw this problem. > - There is so much magic involved that I don't even dare to create > a fresh flash filesystem. I have one image that appears to work > and I use that as a template just writing different kernels and > configs to it. I agree there is definitly some magic. You have to keep your kernel within the first 2 megs. The 2 meg number if from memory. They geometry reported by the DOCs is very strange. You can very easily put a kernel on a DOC that you can't load using the BIOS. > This is completely obscure to me and quite annoying, especially since > my other device that uses Compact Flash has just *no* problems with > any of this, period. So I know I'm not doing anything obvious wrong, > I just seem to be falling into the gaps of a brittle device / driver > combination. I never had any problems with the fla driver. I had to be careful with kernel location so the BIOS could load it. > BTW: the systems on which I have problems are the Flytech NetPC > B62 systems with 8 MB DiskOnChip. The computers are quite fine > otherwise, just that this stupid DiskOnChip thing causes me to rip > my hair out. (As you can hear in my tone.) I know you are not going to want to hear this, but we have delivered thousands of systems based around the flytech NetPC boxes using 8MB DOCs. We have quit using the DOCs except for supporting legacy systems. I'll dig out some installation floppies that you can use as a sanity check on your hardware. Larry -- ------------------------------------------------------------------------ Larry Baird | http://www.gnatbox.com Global Technology Associates, Inc. | Orlando, FL Email: lab@gta.com | TEL 407-380-0220, FAX 407-380-6080 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 25 20: 4:57 2001 Delivered-To: freebsd-small@freebsd.org Received: from gta.com (mailgate.gta.com [199.120.225.4]) by hub.freebsd.org (Postfix) with ESMTP id 402EF37B424 for ; Wed, 25 Apr 2001 20:04:55 -0700 (PDT) (envelope-from lab@gta.com) Received: from gta.com (GTA internal mail system) by gta.com id XAA59451; Wed, 25 Apr 2001 23:03:26 -0400 (EDT) Date: Wed, 25 Apr 2001 23:03:26 -0400 (EDT) Message-Id: <200104260303.XAA59451@gta.com> From: Larry Baird To: Gunther Schadow Cc: freebsd-small@FreeBSD.ORG Subject: Re: VPN tunnel with DHCP ... In-Reply-To: <3AE7303F.957DE6DC@gta.com> User-Agent: tin/1.4.2-20000205 ("Possession") (UNIX) (FreeBSD/3.5-STABLE (i386)) Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > about my SOHO router project, I came accross a tough problem, may > be I overlook that there is a solution already? The VPN gateway > at the small office / home office (SOHO) has an IPsec tunnel > connecting it to its headquarter: Take a look at the development version of KAME. There is a new experimental option to handle dynamic connections. Larry -- ------------------------------------------------------------------------ Larry Baird | http://www.gnatbox.com Global Technology Associates, Inc. | Orlando, FL Email: lab@gta.com | TEL 407-380-0220, FAX 407-380-6080 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 25 20:55: 9 2001 Delivered-To: freebsd-small@freebsd.org Received: from cody.jharris.com (cody.jharris.com [205.238.128.83]) by hub.freebsd.org (Postfix) with ESMTP id E825437B423; Wed, 25 Apr 2001 20:54:59 -0700 (PDT) (envelope-from nick@rogness.net) Received: from localhost (nick@localhost) by cody.jharris.com (8.11.1/8.9.3) with ESMTP id f3Q53Ex44782; Thu, 26 Apr 2001 00:03:14 -0500 (CDT) (envelope-from nick@rogness.net) Date: Thu, 26 Apr 2001 00:03:14 -0500 (CDT) From: Nick Rogness X-Sender: nick@cody.jharris.com To: Gunther Schadow Cc: freebsd-net@FreeBSD.ORG, freebsd-small@FreeBSD.ORG, snap-users@kame.net Subject: Re: VPN tunnel with DHCP ... In-Reply-To: <3AE7303F.957DE6DC@aurora.regenstrief.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 25 Apr 2001, Gunther Schadow wrote: > Hi, > > about my SOHO router project, I came accross a tough problem, may > be I overlook that there is a solution already? The VPN gateway > at the small office / home office (SOHO) has an IPsec tunnel > connecting it to its headquarter: > > setkey -c < spdadd ${sohonet} ${homenet} -P out ipsec > esp/tunnel/${sohoip}-${homeip}/require; > spdadd ${homenet} ${sohonet} -P in ipsec > esp/tunnel/${homeip}-${sohoip}/require; > END > > now, the problem is that the ${sohoip} is dynamically assigned > with DHCP. How can the gateway at the headquarter know that > ${sohoip} address? > > Options I can see are: > > A DNS (provided that the SOHO endpoint has a reliable name assigned > by the ISP ... doesn't work for intermittent/dialup lines.) > > B an authenticated message from the SOHO endpoint to headquarter > stating that the network ${sohonet} is reachable through the > tunnel with endpoint ${sohoip}. > > Is there anything like B defined in IPsec / ISAKMP or something? I had a similar problem but I had 1 static server and the tunnels were between several DHCP machines...not between the DHCP machines and the server. I ended up writing a client/server perl program in which the server held information about the client interconnecting gif tunnels. The clients would login and receive tunnel endpoints, routing info, updates and such. I'm sure this won't suffice but I will send it to you for your own hacking pleasure if you wish. Or hell, I'll even modify it so it fits your needs. Nick Rogness - Keep on Routing in a Free World... "FreeBSD: The Power to Serve!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 25 21:15:45 2001 Delivered-To: freebsd-small@freebsd.org Received: from rgmail.regenstrief.org (rgmail.regenstrief.org [134.68.31.197]) by hub.freebsd.org (Postfix) with ESMTP id EA45237B423; Wed, 25 Apr 2001 21:15:42 -0700 (PDT) (envelope-from gunther@aurora.regenstrief.org) Received: from aurora.regenstrief.org (aurora.rg.iupui.edu [134.68.31.122]) by rgmail.regenstrief.org (8.11.0/8.8.7) with ESMTP id f3Q4FiA03599; Wed, 25 Apr 2001 23:15:44 -0500 Message-ID: <3AE7A0E1.6B022C5E@aurora.regenstrief.org> Date: Thu, 26 Apr 2001 04:15:29 +0000 From: Gunther Schadow Organization: Regenstrief Institute for Health Care X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Larry Baird Cc: freebsd-small@FreeBSD.ORG, phk@FreeBSD.ORG Subject: Re: the fla driver definitely has bugs ... References: <200104052057.QAA69722@gta.com> <3AE75F24.564CC9D4@gta.com> <20010425225358.A58470@gta.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Larry Baird wrote: > What can I say. There in the customer's hands without any > complaints. (-; Larry, thaks for helping me keep the faith! > I agree there is definitly some magic. You have to keep your > kernel within the first 2 megs. The 2 meg number if from memory. > They geometry reported by the DOCs is very strange. You can > very easily put a kernel on a DOC that you can't load using the > BIOS. Yes, this may explain it. So, all I have to do is write the kernel first onto the filesystem so that it fits into the first 2 MB. I will try this right tomorrow. I found my way working around this weirdness. > I know you are not going to want to hear this, but we have delivered > thousands of systems based around the flytech NetPC boxes using 8MB > DOCs. No, no, I like what I'm hearing. Of course 1 or 1000 systems doesn't matter, since you have to get it right only once and then clone it a 1000 times. Thanks, -Gunther -- Gunther Schadow, M.D., Ph.D. gschadow@regenstrief.org Medical Information Scientist Regenstrief Institute for Health Care Adjunct Assistent Professor Indiana University School of Medicine tel:1(317)630-7960 http://aurora.regenstrief.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 25 21:36:13 2001 Delivered-To: freebsd-small@freebsd.org Received: from rgmail.regenstrief.org (rgmail.regenstrief.org [134.68.31.197]) by hub.freebsd.org (Postfix) with ESMTP id F182F37B42C; Wed, 25 Apr 2001 21:36:09 -0700 (PDT) (envelope-from gunther@aurora.regenstrief.org) Received: from aurora.regenstrief.org (aurora.rg.iupui.edu [134.68.31.122]) by rgmail.regenstrief.org (8.11.0/8.8.7) with ESMTP id f3Q4aBA03665; Wed, 25 Apr 2001 23:36:11 -0500 Message-ID: <3AE7A5AC.FA719D45@aurora.regenstrief.org> Date: Thu, 26 Apr 2001 04:35:56 +0000 From: Gunther Schadow Organization: Regenstrief Institute for Health Care X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Larry Baird Cc: freebsd-small@FreeBSD.ORG, phk@FreeBSD.ORG Subject: Re: the fla driver definitely has bugs ... References: <200104052057.QAA69722@gta.com> <3AE75F24.564CC9D4@gta.com> <20010425225358.A58470@gta.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Larry Baird wrote: > > - There is so much magic involved that I don't even dare to create > > a fresh flash filesystem. I have one image that appears to work > > and I use that as a template just writing different kernels and > > configs to it. > I agree there is definitly some magic. You have to keep your > kernel within the first 2 megs. The 2 meg number if from memory. > They geometry reported by the DOCs is very strange. You can > very easily put a kernel on a DOC that you can't load using the > BIOS. Yes, this did it!!! Let it be known for the record that he, who wants to boot from an fla device (DiskOnChip) muat write all of the following as the first thing on the medium: 1.) boot loader 2.) kernel 3.) root mfs (if applicable) This is necessary because the BIOS can't load anything that is beyond this mark of 2 MB (or may be more or less than 2 MB.) This is a FAQ ... may be it should be described in the fla driver documentation. regards -Gunther -- Gunther Schadow, M.D., Ph.D. gschadow@regenstrief.org Medical Information Scientist Regenstrief Institute for Health Care Adjunct Assistent Professor Indiana University School of Medicine tel:1(317)630-7960 http://aurora.regenstrief.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 25 22:40:37 2001 Delivered-To: freebsd-small@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 625B437B424 for ; Wed, 25 Apr 2001 22:40:34 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f3Q5e3U80760; Thu, 26 Apr 2001 07:40:03 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Gunther Schadow Cc: Larry Baird , freebsd-small@FreeBSD.ORG Subject: Re: the fla driver definitely has bugs ... In-Reply-To: Your message of "Wed, 25 Apr 2001 23:35:00 -0000." <3AE75F24.564CC9D4@aurora.regenstrief.org> Date: Thu, 26 Apr 2001 07:40:02 +0200 Message-ID: <80758.988263602@critter> From: Poul-Henning Kamp Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3AE75F24.564CC9D4@aurora.regenstrief.org>, Gunther Schadow writes: >I'm sorry but I can't confirm that. I have nothing but trouble >with the fla device with all 5 boxes that I'm trying to configure. >So, I know I don't just have a foul chip. > >- "stray irq 7" is something that should not ever happen in a clean > kernel certainly not when mounting or otherwise accessing a flash > disk device. The DoC has no interrupt line, so all operations to it are polled. This basically makes the rest of the system suffer while you access the DoC. >- There is so much magic involved that I don't even dare to create > a fresh flash filesystem. I have one image that appears to work > and I use that as a template just writing different kernels and > configs to it. You need to respect the 1024 cylinder thing on all disks. This is more of an issue with devices as small as the DoC. I have a contract right now to update the DoC driver to the OSAK-4.1 kit from M-sys, which should amongst other things make it possible to run on the 288MB devices, but I don't have an actual release-note which can tell me if any bugs are fixed. If any of you want to help test the new version: send me email. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 25 23:59:55 2001 Delivered-To: freebsd-small@freebsd.org Received: from gta.com (mailgate.gta.com [199.120.225.4]) by hub.freebsd.org (Postfix) with ESMTP id B5B4637B423 for ; Wed, 25 Apr 2001 23:59:53 -0700 (PDT) (envelope-from lab@gta.com) Received: from gta.com (GTA internal mail system) by gta.com id CAA66422; Thu, 26 Apr 2001 02:46:02 -0400 (EDT) Date: Thu, 26 Apr 2001 02:46:02 -0400 From: Larry Baird To: Poul-Henning Kamp Cc: freebsd-small@FreeBSD.ORG Subject: Re: the fla driver definitely has bugs ... Message-ID: <20010426024602.A66333@gta.com> References: <3AE75F24.564CC9D4@aurora.regenstrief.org> <80758.988263602@gta.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <80758.988263602@gta.com>; from phk@critter.freebsd.dk on Thu, Apr 26, 2001 at 07:40:02AM +0200 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You need to respect the 1024 cylinder thing on all disks. This > is more of an issue with devices as small as the DoC. Currious as to what other small devices you have seen that have the BIOS limitations associated with the DOC? All of of the others I have seen (compact flash and DOM) map more than one sector per track. This keeps the max cylinder down at a reasonable value for the BIOS. Larry -- ------------------------------------------------------------------------ Larry Baird | http://www.gnatbox.com Global Technology Associates, Inc. | Orlando, FL Email: lab@gta.com | TEL 407-380-0220, FAX 407-380-6080 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 26 8:15:38 2001 Delivered-To: freebsd-small@freebsd.org Received: from web13605.mail.yahoo.com (web13605.mail.yahoo.com [216.136.175.116]) by hub.freebsd.org (Postfix) with SMTP id DC0A037B422 for ; Thu, 26 Apr 2001 08:15:36 -0700 (PDT) (envelope-from pk123fr@yahoo.fr) Message-ID: <20010426150750.95754.qmail@web13605.mail.yahoo.com> Received: from [194.51.129.84] by web13605.mail.yahoo.com; Thu, 26 Apr 2001 17:07:50 CEST Date: Thu, 26 Apr 2001 17:07:50 +0200 (CEST) From: =?iso-8859-1?q?pierrick=20le=20fol?= Subject: subscribe freebsd-small To: freebsd-small@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-small ___________________________________________________________ Do You Yahoo!? -- Pour faire vos courses sur le Net, Yahoo! Shopping : http://fr.shopping.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 26 8:22:13 2001 Delivered-To: freebsd-small@freebsd.org Received: from web13606.mail.yahoo.com (web13606.mail.yahoo.com [216.136.175.117]) by hub.freebsd.org (Postfix) with SMTP id 7C4FE37B422 for ; Thu, 26 Apr 2001 08:22:11 -0700 (PDT) (envelope-from pk123fr@yahoo.fr) Message-ID: <20010426152211.39480.qmail@web13606.mail.yahoo.com> Received: from [194.51.129.84] by web13606.mail.yahoo.com; Thu, 26 Apr 2001 17:22:11 CEST Date: Thu, 26 Apr 2001 17:22:11 +0200 (CEST) From: =?iso-8859-1?q?pierrick=20le=20fol?= Subject: subscribe freebsd-small To: freebsd-small@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-small ___________________________________________________________ Do You Yahoo!? -- Pour faire vos courses sur le Net, Yahoo! Shopping : http://fr.shopping.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 26 8:37:19 2001 Delivered-To: freebsd-small@freebsd.org Received: from web13604.mail.yahoo.com (web13604.mail.yahoo.com [216.136.175.115]) by hub.freebsd.org (Postfix) with SMTP id A920437B422 for ; Thu, 26 Apr 2001 08:37:17 -0700 (PDT) (envelope-from pk123fr@yahoo.fr) Message-ID: <20010426153411.84927.qmail@web13604.mail.yahoo.com> Received: from [194.51.129.84] by web13604.mail.yahoo.com; Thu, 26 Apr 2001 17:34:11 CEST Date: Thu, 26 Apr 2001 17:34:11 +0200 (CEST) From: =?iso-8859-1?q?pierrick=20le=20fol?= Subject: isdn router To: freebsd-small@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I want use the network version of picobsd to do a router ISDN. is it possible to settle a ISDN card on this OS type ? If somebody has already settled this type of system, can him communicate me some documentation or explain how it set itself there. Thank you. ___________________________________________________________ Do You Yahoo!? -- Pour faire vos courses sur le Net, Yahoo! Shopping : http://fr.shopping.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Apr 27 3:35:55 2001 Delivered-To: freebsd-small@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [213.162.131.14]) by hub.freebsd.org (Postfix) with ESMTP id 595A837B422 for ; Fri, 27 Apr 2001 03:35:44 -0700 (PDT) (envelope-from abial@webgiro.com) Received: from mx.webgiro.com (unknown [192.168.10.2]) by mimer.webgiro.com (Postfix) with ESMTP id 282C11003EE; Fri, 27 Apr 2001 13:48:16 +0200 (CEST) Received: by mx.webgiro.com (Postfix, from userid 1001) id 4F82F7817; Fri, 27 Apr 2001 12:35:42 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id 4D46B10E1E; Fri, 27 Apr 2001 12:35:42 +0200 (CEST) Date: Fri, 27 Apr 2001 12:35:40 +0200 (CEST) From: Andrzej Bialecki To: "Nielsen, Roy S" Cc: freebsd-small@freebsd.org Subject: Re: fyi.... acsfl In-Reply-To: <9ABEE73CE8D0D211AC4300A0C96B345C035C5B0B@fmsmsx53.fm.intel.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 25 Apr 2001, Nielsen, Roy S wrote: > This was actually intended for embedded applications -- if you'd like some > information on it, > let me know and i can send you a bit more -- > > AC SF library is a set of chipset and memory initialization functions... IE. > one can create their > own firmware with these libraries... one blurb states: "it provides a > modular and extensible > library of functions for component-level initialization of intel > microprocessors and chipsets" > > i'm trying to push *bsd around here... let me know if you know anyone that > might be interested > in acsfl, Yes, there might be some interest for those of us who use *bsd in deeply embedded environments... I took the liberty to cc: the freebsd-small@freebsd.org mailing list, which is the right forum to ask this type of qustions. Andrzej // ---------------------------------------------------------------- // Andrzej Bialecki , Chief System Architect // WebGiro AB, Sweden (http://www.webgiro.com) // ---------------------------------------------------------------- // FreeBSD developer (http://www.freebsd.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Apr 27 11:17:48 2001 Delivered-To: freebsd-small@freebsd.org Received: from mail.cruzio.com (dsl3i239.cruzio.com [205.179.211.239]) by hub.freebsd.org (Postfix) with ESMTP id AA64037B422 for ; Fri, 27 Apr 2001 11:17:45 -0700 (PDT) (envelope-from brucem@mail.cruzio.com) Received: (from brucem@localhost) by mail.cruzio.com (8.11.3/8.11.3) id f3RI66t00690 for freebsd-small@FreeBSD.ORG; Fri, 27 Apr 2001 11:06:06 -0700 (PDT) (envelope-from brucem) Date: Fri, 27 Apr 2001 11:06:06 -0700 (PDT) From: "Bruce R. Montague" Message-Id: <200104271806.f3RI66t00690@mail.cruzio.com> To: freebsd-small@FreeBSD.ORG Subject: Internal PCI ADSL cards/drivers? Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone on this list know of any single-slot internal PCI-card ADSL solutions with FreeBSD driver support? Perhaps even PC/104 formfactor? Near as I can tell, FreeBSD supports no such cards and that isn't likely to change soon because of the nature of drivers for these cards (that is, much of the value in the product is the signal-processing code or whatever in the drivers, which companies want to keep proprietary). Extern ADSL modems work fine, but are often larger than a "small" system... - bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message