From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from server1.shellworld.net ([64.39.15.178] ident=root) by speech.braille.uwo.ca with esmtp (Exim 3.36 #1 (Debian)) id 1AG2VP-0006t7-00 for ; Sat, 01 Nov 2003 15:37:55 -0500 Received: from server1.shellworld.net (ldavis@localhost.shellworld.net [127.0.0.1]) by server1.shellworld.net (8.12.8/8.11.1) with ESMTP id hA1KbrwO070695 for ; Sat, 1 Nov 2003 14:37:53 -0600 (CST) (envelope-from ldavis@shellworld.net) Received: from localhost (ldavis@localhost) by server1.shellworld.net (8.12.8/8.12.8/Submit) with ESMTP id hA1Kbrq5070692 for ; Sat, 1 Nov 2003 14:37:53 -0600 (CST) (envelope-from ldavis@shellworld.net) X-Authentication-Warning: server1.shellworld.net: ldavis owned process doing -bs Date: Sat, 1 Nov 2003 14:37:53 -0600 (CST) From: Luke Davis To: "Speakup is a screen review system for Linux." In-Reply-To: Message-ID: References: Organization: "Tacticus Communications, Inc." MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: Battle Of The Iethernet Cards X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.3 Precedence: list Reply-To: "Speakup is a screen review system for Linux." List-Id: Speakup is a screen review system for Linux. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Nov 2003 20:37:56 -0000 On Sat, 1 Nov 2003, Geoff Shang wrote: > Not sure if I'm clear on your setup, but wouldn't a routing table clear up > this issue? Type the commmand: > route -n > and show us the output. That's kind of what I was thinking. It should be possible to set the default route, to work through the cablemodem router, and set only what ever private class C is desired, over the other card, and only that class C. Then, run Samba, listening only to the class C interface, and all other services listening to all interfaces, but only originating connections on the cable modem router interface. There are ways to forse all of this with iptables, but I would personally consider that a cluge. > Of course, unless you really needed your machines to use different internet > connections, you could just have your linux machine connected to the net If you run a big network, with many machines, and more than one server, his setup actually does make some sense. The windows segments use one highspeed conection, with their services, and the Linux side uses its highspeed connection, with its services. Depending upon your available connection speeds, this can be understood as valuable, although with a slight dubious factor. However, knowing various things about his setup, it does make sense. > and do IP masquerading for the other boxes. Note: when dealing with always-on connections, it qualifies as NAT. masquerading applies only to temporary (usually dialup) PPP connections. Luke