From owner-freebsd-ipfw Sat Jan 15 19:24: 0 2000 Delivered-To: freebsd-ipfw@freebsd.org Received: from mail.rz.fh-wilhelmshaven.de (mail.rz.fh-wilhelmshaven.de [139.13.25.134]) by hub.freebsd.org (Postfix) with ESMTP id C3B70150F5 for ; Sat, 15 Jan 2000 19:23:53 -0800 (PST) (envelope-from ohoyer@fbwi.fh-wilhelmshaven.de) Received: from fettesau.stuwo.fh-wilhelmshaven.de (stuwopc5.stuwo.fh-wilhelmshaven.de [139.13.209.5]) by mail.rz.fh-wilhelmshaven.de (8.9.3/8.9.3) with SMTP id EAA23769; Sun, 16 Jan 2000 04:23:24 +0100 (MET) Message-Id: <4.1.20000116041246.0097bd50@mail.rz.fh-wilhelmshaven.de> X-Sender: ohoyer@mail.rz.fh-wilhelmshaven.de X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 16 Jan 2000 04:21:24 +0100 To: "f.johan.beisser" From: Olaf Hoyer Subject: Re: Simple router with basic firewall functionalioties Cc: freebsd-ipfw@FreeBSD.ORG In-Reply-To: References: <4.1.20000114165656.00c8d940@mail.rz.fh-wilhelmshaven.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-ipfw@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i'd suggest using picobsd (it fits on a floppy) and eliminating the >harddrive all together. you can do the NAT/FW with that off of the network >app build ($SRCDIR/release/picobsd for more info) > >this can (and does) support most harddrives for backing up too, but it >doesn't require them. HI! Yes, will also have a look at that. > >> I also thought about a SAMBA server, to ensure compatibility to exchanga >> data with the M$ machines running here. Any security issues? > >yes, but i think a better question is why? We use a peer -to peer network here, with mostly M$ machines using SMB/Netbeui/Netbios here. To transfer files, we mostly use the M$ directory stuff to allow access and so. Its easy, and even the girls here can figure it out... BTW, it is explicitly forbidden here in our home to use stuff like FTP servers. > >if you're using TCP/IP as the transport, there shouldn't be a need to run >samba as a service inside your network. consider that SAMBA is a file >service daemon, i think this would be pointless for you. > >unless the machine is going to do more than just be a firewall... That was my second thought, to capsule the main box completely from the rest of the network. > >compatable how? > >windows 95/98/NT/2k all should work fine through the firewall, with no >real issues. if they don't, then there is a problem with the setup >somewhere, and i doubt it would be that hard to fix. Yes, with TCP/IP no prob. I cared for the SMB part. >> Is it also possible to Send/receive the "messenging service" of NT, >> respective the "Popups"? SMB messenging (broadcast type, used by the "telephony/popup" application in WIn3.x/Win9x/NT) >explain more on the "popups" if it's an Instant Messaging Service (AIM, >ICQ, etc) it should work if there isn't to much interferance from the >firewall/NAT. ICQ should be no prob since it is IP based. Problems are that here I have to care about SMB based stuff in M$ world. Regards Olaf Hoyer -------- Olaf Hoyer www.nightfire.de mailto:Olaf.Hoyer@nightfire.de FreeBSD- The power to serve ICQ:22838075 Liebe und Hass sind nicht blind, aber geblendet vom Feuer, dass sie selber mit sich tragen. (Nietzsche) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ipfw" in the body of the message