From owner-freebsd-net Wed Jan 29 14: 7:36 2003 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 BDF7137B401 for ; Wed, 29 Jan 2003 14:07:34 -0800 (PST) Received: from white.dogwood.com (white.dogwood.com [63.96.228.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D2EE43F43 for ; Wed, 29 Jan 2003 14:07:34 -0800 (PST) (envelope-from dave@dogwood.com) Received: from white.dogwood.com (localhost [127.0.0.1]) by white.dogwood.com (8.12.6/8.12.5) with ESMTP id h0TM7XSC094934 for ; Wed, 29 Jan 2003 14:07:33 -0800 (PST) (envelope-from dave@white.dogwood.com) Received: (from dave@localhost) by white.dogwood.com (8.12.6/8.12.6/Submit) id h0TM7XPL094933 for freebsd-net@freebsd.org; Wed, 29 Jan 2003 14:07:33 -0800 (PST) From: Dave Cornejo Message-Id: <200301292207.h0TM7XPL094933@white.dogwood.com> Subject: unique routing problem To: freebsd-net@freebsd.org Date: Wed, 29 Jan 2003 14:07:32 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL99b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I've got a unique routing problem: local network is 192.168.1.0/24 192.168.1.4 | | 192.168.1.1 -- ethernet -- 192.168.1.2 / global IP addr -- internet | | 192.168.1.3 now, the rules: 1) .1 may directly exchange packets with .4 and .2 only, it may not exchange packets with .3 directly. 2) .2 may directly exchange packets with any host 3) .2 acts as the gateway to the internet the problem is that I need to be able to set up the routing tables so that if .1 needs to connect to .3 that it goes through .2. If it needs to connect to .4 or .2 it can do that directly. To make things even more fun, any number of hosts may join or leave the network at any point and the lists of which hosts have direct connectivity is dynamic. But I think that if I can solve the above problem that I'll have what I need to solve the rest of it. I have a solution that uses Linux, but I'm reasonably certain that it really uses a flaw in the Linux kernel to work as it's dicey to set up, requires a specific order of steps and requires a reboot when things like the hosts IP address changes. BTW, If anyone that can answer this needs a job or contract please let me know... thanks, dave c -- Dave Cornejo @ Dogwood Media, Fremont, California (also dcornejo@ieee.org) "There aren't any monkeys chasing us..." - Xochi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message