From owner-freebsd-questions@FreeBSD.ORG Sun Dec 7 23:15:31 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 078AD16A4CE for ; Sun, 7 Dec 2003 23:15:31 -0800 (PST) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B87F43FB1 for ; Sun, 7 Dec 2003 23:15:29 -0800 (PST) (envelope-from matthewedwards@comcast.net) Received: from MUGGLA (c-24-10-254-143.client.comcast.net[24.10.254.143]) by comcast.net (sccrmhc13) with SMTP id <20031208071528016001im51e>; Mon, 8 Dec 2003 07:15:28 +0000 Message-ID: <003c01c3bd5b$0eec32e0$0102000a@home.local> From: "Matt Edwards" To: "Vulpes Velox" , "Marwan Sultan" References: <20031207163138.M95960@kifco.net> <20031207215041.3e6a3e2d.kitbsdlists@HotPOP.com> Date: Mon, 8 Dec 2003 00:15:27 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 cc: FreeBSD questions List Subject: Re: NATd question X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2003 07:15:31 -0000 There some marketing scams out there that some ISP use to get you to pay just a bit more for service. One common scam is as follows: consumer: "I have two computers. I need to make sure they can both get on the internet." (Thinking: "I know my buddy did this with his setup") ISP: "Oh you mean you need a second IP address, right?" (Thinking: "The poor guy doesn't know he can do it with one and NAT server. But I ain't telling him that.") consumer: "Will that let me get both of these connected?" ISP: "Oh you bet. It will only be $5($10/$15/maybe even $20) more dollars a month" consumer: "Ok set it up. Lets do that. I really need to get these two on the internet." ;) Matt ----- Original Message ----- From: "Vulpes Velox" To: "Marwan Sultan" Cc: "FreeBSD questions List" Sent: Sunday, December 07, 2003 8:50 PM Subject: Re: NATd question > On Sun, 7 Dec 2003 19:56:14 +0300 > "Marwan Sultan" wrote: > > > Hello Everybody, > > > > > > Im on FreeBSD 4.8-R fresh installation. > > and this is the configuration i will use on my LAN > > > > Internet ->connected-> DSL Router -> FreeBSD box -> HUB -> LAN > > > > DSL Router has an IP 192.168.0.1 and the real IP too. > > > > FreeBSD box has 2 NIC's > > My question is: > > > > Where and How to sign 2 IPs for 2 NICs? > > > > which IP the NIC connected to DSL should sign? > > Which IP the NIC connected to HUB should sign? > > Which of these IPs will be as gateway IP the clients will sign? > > The DSL connection is probally going to be DHCP so just set the nic connected to > it for DHCP. Then for the lan select what ever private address you want. > > You will have to experiment a bit to figure out which is which. > > > I have read the instructions of freebsd.org, > > and it says the gateway will be the BSD machine 192.168.0.1 > > BUT this IP in my LAN is signed to the router automatilcaly. > > You can assign the gateway machine any private address you want. BTW if you have > a gateway why are you setting up a second? > > > Can someone explain? advise? This machine will be only for this use. > > It basically works like this... > LAN -> gateway -> natd -> dsl uplink device -> WAN > > Any thing on to a address not included in the subnet mask is going to leave > throught the gateway. The usual subnet mask is 255.255.255.0 so thus there are > 256 possabilities of address in the alloted space. Now lets say out gateway is > 192.168.0.1 any thing not belonging to 192.168.0.1/24 is going to leave thought > the gateway. On it's way out that packet is going to be monkeyed, by natd, with > so it will know where to send the returned info. This is done so that it will > know which machine on the LAN it should be sent too. >