From owner-freebsd-hackers Tue Dec 9 16:26:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA22300 for hackers-outgoing; Tue, 9 Dec 1997 16:26:17 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA22266 for ; Tue, 9 Dec 1997 16:25:58 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id BAA01861 for freebsd-hackers@freebsd.org; Wed, 10 Dec 1997 01:25:44 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id AAA04738; Wed, 10 Dec 1997 00:36:02 +0100 (MET) Date: Wed, 10 Dec 1997 00:36:02 +0100 (MET) Message-Id: <199712092336.AAA04738@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 0.9.8 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: I seriously need some networking help X-Original-Newsgroups: local.freebsd.hackers To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "Jamil J. Weatherbee" wrote: > .., it is > possible for ed0 to have a different ip address than ed1 but router0 must > believe that it is on the windoze ethernet and the windoze ethernet must > believe that router0 is local to it. Nope, all IP interfaces on one machine must be in different IP networks. (The only exception: for p2p interfaces (SLIP, PPP), the IP address of the remote end counts, while the local one can be duplicated.) For me, it would seem to be best to use a 192.168.something net between router0 and the FreeBSD packet filter, but of course, this requires some minor reconfiguration on router0 (which turns into a major reconfiguration since router0 happens to be an Ascend P50, which has a rather confusing terminology and setup screens when it comes to something like this -- been there last week, done that). Note that the WAN-side IP address of router0 would remain unaffected by this, so there's not much visible about this reconfiguration from your ISP's point of view, except traceroute will trace one additional gateway with some 192.168 address. Failing this, maybe you could do some cute and clever tricks with divert sockets, natd, and explicit host routing out an Ethernet interface, but all this looks rather hacky compared to the above `transit network' solution. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)