From owner-freebsd-net Fri Jul 5 7:10:50 2002 Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 86B7037B400 for ; Fri, 5 Jul 2002 07:10:45 -0700 (PDT) Received: from rack.purplecat.net (rack.purplecat.net [208.133.44.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id B261B43E3B for ; Fri, 5 Jul 2002 07:10:44 -0700 (PDT) (envelope-from pbrezny@purplecat.net) Received: (qmail 13436 invoked from network); 5 Jul 2002 14:11:00 -0000 Received: from unknown (HELO micron) (208.150.25.130) by rack.purplecat.net with SMTP; 5 Jul 2002 14:11:00 -0000 From: "Peter Brezny" To: Subject: freebsd vs. Cisco for two t1's Date: Fri, 5 Jul 2002 10:07:32 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org We're considering bringing two more t1's into the office through a separate provider to diversify our path out. The new circuits will terminate in dc, as opposed to Atlanta where our current circuits terminate. We've got two t1 cards laying around from other systems we've pulled back, and I was wondering if anyone has had success using freebsd for nothing but terminating t1's and routing traffic. What we want: both t1's multiplexed coming into the freebsd system bgp4/eigrp to communicating with the Cisco on the other t1's so that packets always take the best path out to the internet. It would be nice to run picobsd for this system, or boot it off a flash card so as not to have to worry about drives. Any comments or suggestions are welcome. TIA Peter Brezny purplecat.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message