From owner-freebsd-small Tue May 22 6:21: 2 2001 Delivered-To: freebsd-small@freebsd.org Received: from postfix2-2.free.fr (postfix2-2.free.fr [213.228.0.140]) by hub.freebsd.org (Postfix) with ESMTP id EC1EA37B424 for ; Tue, 22 May 2001 06:20:58 -0700 (PDT) (envelope-from pmialon@free.fr) Received: from imp2-1.free.fr (imp2-1.free.fr [213.228.0.22]) by postfix2-2.free.fr (Postfix) with ESMTP id A89426B757 for ; Tue, 22 May 2001 15:20:57 +0200 (CEST) Received: (from www-data@localhost) by imp2-1.free.fr (8.12.0.Beta7/8.12.0.Beta7/Debian 8.12.0-1) id f4MDKvYU005007 for freebsd-small@freebsd.org; Tue, 22 May 2001 15:20:57 +0200 To: freebsd-small@freebsd.org Subject: PPP + NAT + PPPo + PicoBSD Message-ID: <990537657.3b0a67b92cab3@imp.free.fr> Date: Tue, 22 May 2001 15:20:57 +0200 (MEST) From: Pierre-Gilles Mialon MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.3 X-Originating-IP: 217.11.163.217 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, Is it possible to see ppp working in PicoBSD with nat in the ppp.conf (without natd working) and to have the option of NETGRAPH working in the kernel. I want to use it as an ADSL router firewall, port forwarder for a small network... I try to make it work with the latest source of the stable, but I don't succeed. I have warning like kernel cannot load eg_netgraph and the nat is not recognised in my ppp.conf file (unknown option ) So I should I do to compile the kernel and to compile the ppp ? I have no error during the linking of the kernel and ppp. I believed that PicoBSD was compiled with the stable source of FreeBSD but it seems that there is some special script which don't take all the source and make some binary special... _____________________________________________________________________ Pierre-Gilles Mialon | Métro Place Monge | email : 48 rue Monge | Digicode : 07521 | 75005 PARIS | tel : 01 43 26 40 06 | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed May 23 11:45:39 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 27EE337B424 for ; Wed, 23 May 2001 11:45:37 -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 f4NImQX23987 for ; Wed, 23 May 2001 13:48:26 -0500 Message-ID: <3B0C0549.7C2E596E@aurora.regenstrief.org> Date: Wed, 23 May 2001 18:45: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: freebsd-small@freebsd.org Subject: booting hangs after sio1 (console) is probed? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I have had this with two different boards, one does it consistently the other did it ocasionally. With a specific kernel (that happens to include some NWIP encapsulation pseudo device) I the machine hangs after the sio (console) device is probed. This NWIP thing works mostly on a different machine. So, my guess is this doesn't have anything to do with the sio driver but happens somewhere in the initialization of that pseudo device. Why do I even bother this list with this? Well, anyone ever tried to do NetWare tunneled through a VPN? I do it and it works on one kind of machine but not on the other kind. 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 May 23 14:43:40 2001 Delivered-To: freebsd-small@freebsd.org Received: from critter.freebsd.dk (beachchick.freebsd.dk [212.242.34.253]) by hub.freebsd.org (Postfix) with ESMTP id 4B6EF37B443 for ; Wed, 23 May 2001 14:43:37 -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 f4NLhTm52372 for ; Wed, 23 May 2001 23:43:29 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: small@freebsd.org Subject: DiskOnChip driver updated to OSAK-4.1 firmware... From: Poul-Henning Kamp Date: Wed, 23 May 2001 23:43:29 +0200 Message-ID: <52370.990654209@critter> Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have just MFC'ed the new firmware to the DiskOnChip driver so that the new 288MB devices are supported, have at it. My time for doing the update was kindly sponsored by RedfernNetworks.com. -- 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 Thu May 24 8:55:52 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 4199F37B423 for ; Thu, 24 May 2001 08:55:48 -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 RAA35813; Thu, 24 May 2001 17:52:32 +0200 (CEST) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200105241552.RAA35813@info.iet.unipi.it> Subject: cross-compiling PicoBSD To: small@freebsd.org Date: Thu, 24 May 2001 17:52:32 +0200 (CEST) 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I have been trying to do a "cross-compile" of PicoBSD, ie. use a source tree different from the installed one. Basically the idea is to be able to use checked-out sources for, say, 5.0 using 4.x as build environment. The tricky point seems to be using a standard include directory different from /usr/include. I tried setting CFLAGS in the environment as below, and it seems to work, but I would like some comments from those of you familiar with the build process. In any case, I did the following: # cd to the directory where you extract your source tree lcvs co -r RELENG_4 src # extract sources ... lcvs co -r RELENG_4 ports/picobsd # .. and relevant ports mkdir -p usr/include # include files go here (setenv DESTDIR=`pwd` ; cd src; make includes) # create include tree setenv SRC `pwd` # used later by picobsd script setenv CFLAGS "-nostdinc -I`pwd`/usr/include" picobsd hope this helps... 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 Thu May 24 8:56:35 2001 Delivered-To: freebsd-small@freebsd.org Received: from femail2.sdc1.sfba.home.com (femail2.sdc1.sfba.home.com [24.0.95.82]) by hub.freebsd.org (Postfix) with ESMTP id 2D9F137B422 for ; Thu, 24 May 2001 08:56:33 -0700 (PDT) (envelope-from kd5fid@repairguy.net) Received: from repairguy.net ([24.1.65.199]) by femail2.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010524155632.KUWW22201.femail2.sdc1.sfba.home.com@repairguy.net> for ; Thu, 24 May 2001 08:56:32 -0700 Message-ID: <3B0D2F90.85436452@repairguy.net> Date: Thu, 24 May 2001 08:58:08 -0700 From: Steve Ahrendt X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-small@freebsd.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG help index To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sat May 26 17:58:50 2001 Delivered-To: freebsd-small@freebsd.org Received: from manifestation.org (cphiber.COM [205.142.78.243]) by hub.freebsd.org (Postfix) with ESMTP id 29C1037B422 for ; Sat, 26 May 2001 17:58:44 -0700 (PDT) (envelope-from s@manifestation.org) Received: from localhost (s@localhost) by manifestation.org (8.11.3/8.10.1) with ESMTP id f4R10JY20405 for ; Sat, 26 May 2001 18:00:19 -0700 (PDT) Date: Sat, 26 May 2001 18:00:19 -0700 (PDT) From: spyn To: picobsd Subject: ppp problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hello, i'm using the 0.41 release of picobsd configured for "modem/dialup" usage... after establishing a PPP connection, i see that i can send outgoing packets but am not receiving any incoming. (this is from netstat -s.) has anyone encountered this? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message