From owner-freebsd-questions Wed Jul 7 9: 5:57 1999 Delivered-To: freebsd-questions@freebsd.org Received: from web220.mail.yahoo.com (web220.mail.yahoo.com [128.11.68.120]) by hub.freebsd.org (Postfix) with SMTP id A02FF14E8E for ; Wed, 7 Jul 1999 09:05:49 -0700 (PDT) (envelope-from starslab@yahoo.com) Message-ID: <19990707160202.3037.rocketmail@web220.mail.yahoo.com> Received: from [209.53.36.71] by web220.mail.yahoo.com; Wed, 07 Jul 1999 09:02:02 PDT Date: Wed, 7 Jul 1999 09:02:02 -0700 (PDT) From: Andrew Fremantle Subject: Networking To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As the title suggests, those of you not familiar with networking may want to skip this over. I have two questions. One is FreeBSD specific the other is not. 1) I have accumulated a large amount of experience with the Linux implementation of NAT, a kernel-land trick they call "IP Masquerade". I am aware that FreeBSD, and presumably the other BSDs offer similar functionality in the form of a user-land "NATd". I need to know if it is as functional as the Linux implmentation? The Linux implementation has "helper" modules for troublesome protocols such as ftp, irc, icq, even Quake (I do HalfLife though :). Will these work across a BSD box doing NAT? 2) This one is a bit lengthy, involves ASCII artwork, and is network-general, though I hope it will apply to FreeBSD or any free 'nix. 10BaseT Ethernet A (WinNT) | ADSL --- HUB --- B (Win95) | C (whatever) All the machines in this scenario pull IP off a DHCP server over the ADSL. Transfers from any local machines, such as A sending a file to B cause the ADSL modem to go nutzo. The transfer is also very slow (by ethernet standards). Just pull the ethernet wire from the ADSL modem and it speeds up DRAMATICALLY. I am looking at putting a 'nix box on this network, and if I can make it act as a switch* between the ADSL modem and the rest of the network, than so much the better. The only "switch" I have seen or have experience with is a 3Com SuperStack ][ (I think), which is more than a little bit out of my budget. Can anyone suggest a cheap piece of network hardware or a 'nix OS that can do this? * I understand a "switch" to be a device that examines the MAC address of machines on the network, and only passes packets on to another interface if such is necessary. This would mean packets from A to B don't need to go over the modem, and would not. If you reply to this, PLEASE snip appropriately, I hate seeing >>>>>>>> all over the place :) === "Binaries may die but source code lives forever" -- Unknown SkyHawk Andrew Fremantle starslab@yahoo.com _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message