From owner-freebsd-questions Tue Jan 5 14:06:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17901 for freebsd-questions-outgoing; Tue, 5 Jan 1999 14:06:03 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from jaguar.ir.miami.edu (jaguar.ir.miami.edu [129.171.32.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17896 for ; Tue, 5 Jan 1999 14:06:01 -0800 (PST) (envelope-from marcus@miami.edu) Received: from jaguar.ir.miami.edu ("port 1465"@jaguar.ir.miami.edu [129.171.32.10]) by jaguar.ir.miami.edu (PMDF V5.2-29 #30976) with ESMTP id <0F53002ORXD2XZ@jaguar.ir.miami.edu> for freebsd-questions@FreeBSD.ORG; Tue, 5 Jan 1999 17:05:26 -0500 (EST) Date: Tue, 05 Jan 1999 17:05:26 -0500 (EST) From: "Joe \"Marcus\" Clarke" Subject: Re: Over my head. I need to route traffic out a particular ethernet card In-reply-to: To: mike grommet Cc: freebsd-questions@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, if you're simply routing between two machines on the "fake" network, then it's fairly easy. The default, directly connected routing, will do it for you. Configure your ip addresses on each adapter like normal, and make sure your default gateway points out to the internet NIC. If all you have is the NT box off the other NIC, you don't have to worry. The fact that the network is directly connected will make routing to it work. For instance, let's assume you have this setup: (10.1.1.1)NT ------- (10.1.1.2) FreeBSD (129.70.1.1) ----- Internet Then, simply telneting to 10.1.1.1 from the FreeBSD will work with no extra routing config. Joe Clarke On Tue, 5 Jan 1999, mike grommet wrote: > I have an internet based web server running 3.0 which is working like a > top... > > now, it needs to communicate with an NT server (probably with rumba) on a > network which is not internet reachable > in another part of the country. > > Ok, so the basic idea (right??) is to put a direct ISDN line between this > and the other machine, > I assume I will have a non routeable ip number on the local and the remote > side, but how do > I make it so the rumba stuff knows to go out the 2nd ethernet port (ISDN) > and not the first? I assume I will need some sort of route specification, > could anyone provide examples for me... > I've never had to do thisl > > > I assume once I get the routing goodies in place, then I just access it like > any other IP. > I just have to be certain that the data going out the "secure" line isnt > broadcast in any form out of the public internet line... > > > Mike Grommet > Unix Systems Adminstrator > Internet Solutions, Inc. > mgrommet@insolwwb.net > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message