From owner-freebsd-questions@FreeBSD.ORG Sun Jan 18 01:54:26 2004 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 6172116A4CE for ; Sun, 18 Jan 2004 01:54:26 -0800 (PST) Received: from UNIX.ZA.NET (unix.za.net [137.158.96.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id C91ED43D48 for ; Sun, 18 Jan 2004 01:54:08 -0800 (PST) (envelope-from savage@savage.za.org) From: Chris Knipe To: freebsd-questions@freebsd.org References: <20040118130036.S98208-100000@prophet.alphaque.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <20040118095408.C91ED43D48@mx1.FreeBSD.org> Date: Sun, 18 Jan 2004 01:54:08 -0800 (PST) Subject: Re: Loading balancing with more than one ISP. 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: Sun, 18 Jan 2004 09:54:26 -0000 > On Sunday 18 January 2004 06:10, Dinesh Nair wrote: > > what i do today is i set the default route to the ISP i am more convinced > > off, with static routes of certain large CIDR address blocks going out to > > the other ISP. i decided on those large blocks after checking the global > > route tables, AS PATH diagrams and experience of link quality. you can do > > this by using tools such as the Looking Glass servers, RouteViews.Org and > > even Netlantis.org for your situation. i'm not running routed, > > zebra/bgpd/ospfd on this at all, since it's all static routes and i can't > > find an ISP ospf/bgp router willing to exchange routes with me. > > Same for me... > Anyway, thanks for the explanation :) > I really appreciated. > > Antoine Yes, here as well. However, this brings (to me at least) a very big problem. I route network A over gateway A, and network C over gateway B. (say, 2 x /12s) I have a service set up, some.host IN A A.A.A.x (i.e. in network A and gateway A). Now, the moment some one from network B connects to the service I've setup on network A, the FreeBSD Box will route the reply packets out on network B (because of the client's address) and hence, it follows a invalid networ path and the connection fails. The same will also happen when someone from Network A tries to connect to a IP on Network B.... ex: -- 192.168.1.0/24 --- | BSD ROUTER | --- 10.255.255.0/24 --- - Some Service on here - 192.168.1.0/24 routed to sis0 - 10.255.255.0/24 routed to sis1 The moment 192.168.1.x tries to connect to my IP address(es) from 10.255.255.0/25, the connection fails - and vica versa. If I can manage to solve this, then I'll be a *VERY* happy chappy. But other than that, as mentioned previously, the ipfw fwd thing doesn't work for me either - it forwards the packet to a port (won't really help forwarding ftp packets to port 21 of your router now, would it). So yes, I'm also stuck with this - and the sad part is I'll more than likely be adding a 3rd gateway to my network pretty soon.... Regards, Chris.