From owner-freebsd-net@FreeBSD.ORG Mon Oct 17 18:13:34 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E358F16A41F for ; Mon, 17 Oct 2005 18:13:34 +0000 (GMT) (envelope-from zanecb@midwest-connections.com) Received: from mail.midwest-connections.com (mail.midwest-connections.com [69.148.152.10]) by mx1.FreeBSD.org (Postfix) with SMTP id 69D5C43D46 for ; Mon, 17 Oct 2005 18:13:34 +0000 (GMT) (envelope-from zanecb@midwest-connections.com) Received: (qmail 28861 invoked from network); 17 Oct 2005 18:13:04 -0000 Received: from unknown (HELO mwc-acomputer) (zanecb@69.155.32.130) by 0 with SMTP; 17 Oct 2005 18:13:04 -0000 Date: Mon, 17 Oct 2005 13:13:35 -0500 From: "Zane C. B." To: G Bryant Message-ID: <20051017131335.0000239b@mwc-acomputer> In-Reply-To: <4350BC26.6030406@roamingsolutions.net> References: <20051014142223.000048c8@mwc-acomputer> <4350BC26.6030406@roamingsolutions.net> X-Mailer: Sylpheed-Claws 1.0.4.1 Win32 (GTK+ 1.3.0; Win32) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: FreeBSD Subject: Re: How would I go about routing something like this? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Oct 2005 18:13:35 -0000 Yeah, currently got it setup like that. What I want to do is to route all traffic out through the secondary machine, for packets originating from a specific IP#. So the main router routes packets coming in from some IP#s to the secondary one for filtering. This possible or not workable? Been reading and I am not seeing any thing about how this would be achieved. On Sat, 15 Oct 2005 10:21:58 +0200 G Bryant wrote: > You can either use ipfw fwd command (has to be enabled in the kernel), > where you forward all lan incoming packets with destination port 80, to > the ip and port that the other proxy is listening on, > or (more complicated) you can use squid proxy on your local machine, use > ipfw to fwd all lan incoming packets with destination port 80 to the > port that squid is listening on (normally 3128), and then you have to > specify in the squid config that it must use a different proxy as it's > "parent" proxy. You could then either enable caching on this machine, > or configure it as a "dummy" proxy. > You will probably have to read all the man pages anyway, so use this as > a starting point.