From owner-freebsd-questions@FreeBSD.ORG Fri Nov 23 13:34:24 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6A2F16A418 for ; Fri, 23 Nov 2007 13:34:24 +0000 (UTC) (envelope-from wmoran@potentialtech.com) Received: from mail.potentialtech.com (internet.potentialtech.com [66.167.251.6]) by mx1.freebsd.org (Postfix) with ESMTP id 9C89713C448 for ; Fri, 23 Nov 2007 13:34:24 +0000 (UTC) (envelope-from wmoran@potentialtech.com) Received: from working (c-71-60-127-199.hsd1.pa.comcast.net [71.60.127.199]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.potentialtech.com (Postfix) with ESMTP id 32B55EBC84; Fri, 23 Nov 2007 08:34:16 -0500 (EST) Date: Fri, 23 Nov 2007 08:34:15 -0500 From: Bill Moran To: "Alaor Barroso de Carvalho Neto" Message-Id: <20071123083415.838efb76.wmoran@potentialtech.com> In-Reply-To: <2949641c0711230452t202d4875k821d5ff753ca0307@mail.gmail.com> References: <2949641c0711210609xc9fcb89t8217cd0995d1c86b@mail.gmail.com> <474440FC.5090901@ibctech.ca> <2949641c0711210644y3ffe8d19ub409b581971e2b1d@mail.gmail.com> <2949641c0711210646p7ded7321g66c4978bb56f1868@mail.gmail.com> <47444C3C.3000003@ibctech.ca> <2949641c0711230452t202d4875k821d5ff753ca0307@mail.gmail.com> X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.1; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: routing problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Nov 2007 13:34:25 -0000 "Alaor Barroso de Carvalho Neto" wrote: > > OK guyz, I did some tests and I found the error, like you said, it's a > config problem with the routes, I thought the routed daemon would care of it > for me but it seems like it don't. Please I ask you to forget the scenario I > said before, now what i have is: > > The dns server is now with the IP 192.168.1.1. But to turn things more easy > I installed it in the FreeBSD box that is gonna be my gateway and proxy > machine, so the problem isn't about the dns anymore. > > I work in a school and I have now this sccenario two local networks, > 192.168.1/24, an administrative network and 192.168.2/24, an academic > network, plus I must have access to a network of other school with the ip > 10.10/16, because they share their database serverwith us. So the FreeBSD > machine have four network cards: > > em0 external world XXX.XXX.XXX.XXX > rl0 adm 192.168.1.80 > rl1 acad 192.168.2.90 > rl3 database 10.10.0.50 > > They are all separated networks. What I want: 192.168.2 should only access > the internet, shouldn't have access to 192.168.1 or 10.10/16. > 192.168.1should access the internet and > 10.10/16, but shouldn't access the academic network. 10.10/16 should access > only the 192.168.1 network, but it's not a problem if they had access to > internet too. > > How I would set up my rc.conf with my static routes? This is beyond the scope of routing. You'll need to install a packet filter. The best at this time is probably pf: http://www.freebsd.org/cgi/man.cgi?query=pfctl&sektion=8&apropos=0&manpath=FreeBSD+6.2-RELEASE http://www.freebsd.org/cgi/man.cgi?query=pf.conf&apropos=0&sektion=0&manpath=FreeBSD+6.2-RELEASE&format=html -- Bill Moran http://www.potentialtech.com