From owner-freebsd-questions Fri Apr 25 11:23:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA02551 for questions-outgoing; Fri, 25 Apr 1997 11:23:40 -0700 (PDT) Received: from cedb.dpcsys.com (cedb.DPCSYS.com [209.25.4.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA02543 for ; Fri, 25 Apr 1997 11:23:38 -0700 (PDT) Received: from localhost (dan@localhost) by cedb.dpcsys.com (8.8.5/8.8.2) with SMTP id SAA07599; Fri, 25 Apr 1997 18:23:29 GMT Date: Fri, 25 Apr 1997 11:23:29 -0700 (PDT) From: Dan Busarow To: Anthony Barlow cc: freebsd-questions@freebsd.org Subject: Re: IP Muticasting In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 25 Apr 1997, Anthony Barlow wrote: > We have 2 networks, one Unix based for the Internet '194.207.68-69 real > ip numbers', the other Novel based '194.168 pvt network ip numbers'. The > 194.168 network is blocked on our routers to disable access from the > Internet. We use muticasting on a Linux box so that users on the Novel > network can still browse the web and ftp. There is a Linux how-to that > shows you how to set these things up. Is there something similar for FBSD? Multi-casting is not what you are looking for. You need to implement NAT (network address translation) or install proxies. I have a hunch that NAT is what you were using with Linux. IP Filter can do both NAT and transparent proxies, see http://cheops.anu.edu.au/~avalon/ip-filter.html Also, take a look at RFC 1918. There are IP address ranges reserved for what you are doing (192.168 fits for you). If you use these addresses you don't need to worry about your "private" addresses leaking. While you are there (RFC repository) take a look at RFC 1919, all about transparent proxies. Dan -- Dan Busarow 714 443 4172 DPC Systems / Beach.Net dan@dpcsys.com Dana Point, California 83 09 EF 59 E0 11 89 B4 8D 09 DB FD E1 DD 0C 82