From owner-freebsd-isp@FreeBSD.ORG Wed Nov 19 10:15:33 2003 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 84D1C16A4CE for ; Wed, 19 Nov 2003 10:15:33 -0800 (PST) Received: from mx1.clickcom.com (mx2.clickcom.com [209.198.22.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4FFC643FDD for ; Wed, 19 Nov 2003 10:15:31 -0800 (PST) (envelope-from jsmailing@clickcom.com) Received: from aesop (calefaction.clickcom.com [209.198.22.19]) by mx1.clickcom.com (email) with ESMTP id E6061146C67; Wed, 19 Nov 2003 13:15:29 -0500 (EST) From: "John Straiton" To: "'Chip McClure'" Date: Wed, 19 Nov 2003 13:07:48 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2727.1300 Thread-index: AcOuxEa7cwAETsipQpOSNjIY60n66gAAGBiw In-Reply-To: <23310.216.195.235.103.1069264920.squirrel@webmail.gigguardian.com> Message-Id: <20031119181529.E6061146C67@mx1.clickcom.com> cc: freebsd-isp@freebsd.org Subject: RE: Dual Ethernet NIC w/ failover X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Nov 2003 18:15:33 -0000 I had thought about that as a possibility. My thought was if I created like a /dev/ether0 and then symlink'ed it to /dev/fxp0, in the event of a failure, I could just change the link over to fxp1 and my firewall rules, dhcpd configurations, et al would still work since they were just reference the symlink (assuming I can do something oddball like that). I was just hoping that someone with more skill than I had put together a more fluid means of all this happening.. Thanks, John > -----Original Message----- > From: Chip McClure [mailto:vhm3@gigguardian.com] > Sent: Wednesday, November 19, 2003 1:02 PM > To: jsmailing@clickcom.com > Cc: freebsd-isp@freebsd.org > Subject: Re: Dual Ethernet NIC w/ failover > > John Straiton said: > > Hello John, > > Although I didn't do this for any gigabit nic's, it should > work the same, no less. > > I worte up a small shell script, that pings the gateway > device. If the ping fails, the shell script de-configures the > primary interface of that card, and configures the secondary > interface, assuming the identity of the 1st interface. she > shell script also write a value to a text file, as to which > is the active interface, so it knows to revert back, if the > secondary were to fail. This script was added into the cron > job, to run every minute. > > Chip > > > Greets! > > I have seen a number of posts regarding support of the > dual ethernet > > cards, however I haven't seen a lot of posts regarding the > > availability of dual ethernet cards with working failover > software... > > I have a couple of the Intel 10/100/1000's on hand but it > appears that > > the software they use only comes in a linux binary. I'm a > bit leary of > > trying to shoehorn it into working with the linux binary > compatibility > > (assuming I could) since the whole purpose of having a dual > ethernet > > NIC is to take variables *out* of the networking. > > I'm looking to try to hook a 5.1-R machine up to two separate > > switches that connect to the same core and run spanning > tree so that a > > failure in either a switch or a network cable would > automagically fail > > over to the other port at the same IP. > > Does anyone have any suggestions on dual gigabit NICs > that they have > > been able to get into switch-failover mode? > > > > John Straiton > > jks@ clickcom.com > > Clickcom, Inc > > 704-365-9970x101 > > > > > > _______________________________________________ > > freebsd-isp@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-isp > > To unsubscribe, send any mail to > "freebsd-isp-unsubscribe@freebsd.org" > > > ----- > Chip McClure > Sr. Unix Administrator > GigGuardian, Inc. > > http://www.gigguardian.com/ > ----- > > >