From owner-freebsd-net@FreeBSD.ORG Mon Apr 25 21:33:14 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 296241065676 for ; Mon, 25 Apr 2011 21:33:14 +0000 (UTC) (envelope-from mksmith@adhost.com) Received: from mail-defer02.adhost.com (mail-defer02.adhost.com [216.211.128.177]) by mx1.freebsd.org (Postfix) with ESMTP id F2DC58FC18 for ; Mon, 25 Apr 2011 21:33:13 +0000 (UTC) Received: from mail-in03.adhost.com (mail-in03.adhost.com [10.212.3.13]) by mail-defer02.adhost.com (Postfix) with ESMTP id E85DD4DF069 for ; Mon, 25 Apr 2011 14:16:57 -0700 (PDT) (envelope-from mksmith@adhost.com) Received: from AD-EXH02.adhost.lan (unknown [10.142.0.21]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail-in03.adhost.com (Postfix) with ESMTPS id 322DDE0481D; Mon, 25 Apr 2011 14:16:47 -0700 (PDT) (envelope-from mksmith@adhost.com) Received: from AD-EXH02.adhost.lan ([fe80::1c5b:7ead:8ba3:6108]) by AD-EXH02.adhost.lan ([fe80::1c5b:7ead:8ba3:6108%11]) with mapi id 14.01.0255.000; Mon, 25 Apr 2011 14:16:47 -0700 From: "Michael K. Smith - Adhost" To: "fbsdmail@dnswatch.com" , "freebsd-net@freebsd.org" Thread-Topic: two /24's and only one gateway - is routing still possible? Thread-Index: AQHMA3meV9Z7xNI95Uu1bMyEJLF0EZRvYr8AgAAU5YD//5sgQA== Date: Mon, 25 Apr 2011 21:16:46 +0000 Message-ID: References: <2b2485288a6e492b3c5c94cc21c79949.dnswclient@www.dnswatch.com> <87e10af65ceb06031196097d7b8920f8.dnswclient@www.dnswatch.com> In-Reply-To: <87e10af65ceb06031196097d7b8920f8.dnswclient@www.dnswatch.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.142.1.52] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Subject: RE: two /24's and only one gateway - is routing still possible? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2011 21:33:14 -0000 > -----Original Message----- > From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd- > net@freebsd.org] On Behalf Of fbsdmail@dnswatch.com > Sent: Monday, April 25, 2011 1:09 PM > To: freebsd-net@freebsd.org > Subject: Re: two /24's and only one gateway - is routing still possible? >=20 >=20 > On Mon, April 25, 2011 11:54 am, Chuck Swiger wrote: > > On Apr 25, 2011, at 11:47 AM, fbsdmail@dnswatch.com wrote: > > > >> I have a /24 with a prefix of 168.103.150.xxx with a gateway on this > >> prefix (DSLmodem). > >> I also have a /24 with a prefix of 75.160.109.xxx > >> My question(s) is/are: > >> 1) is it possible to route both of these across the same GW? > >> > > > > If these netblocks were both owned by you directly and you have an ASN, > > or if they're both owned by the same ISP who is willing to route them > > that way, sure. Talk to Quest... >=20 > I lease both, and have ASN's for both. > My question is more; what might be a solution that /I/ might employ > that would permit routing of both blocks across the single GW. > I can envision creating a freebsd based gateway that is directly > connected to the DSLmodem carrying an IP out of the 168 block, and one > out of the 75 block that routes traffic for both /24's. > But this consumes more IP's and creates an additional hop. You can't get there from here. Routing multiple blocks out of any interfa= ce is just a matter of routing. If you're getting into routing discrete bl= ocks, particularly with discrete autonomous system numbers, you will have t= o use BGP. In that case you can look at Quagga or Bird or similar. If you= 're just interested in the routing function, you can use route-to in PF to = set up whatever you wish. The outbound route is not a problem - it's how traffic is going to get back= to you. If you don't have some sort of dynamic routing protocol in play, = then the routes will come back the way your upstream directs them. Mike