2 ISP on one FreeBSD router

2004-05-25 Thread Piotr Gnyp
Hi.
Right now we have one ISP, our servers that uses IP from this ISP are
running several services (dns, www, databases, mta etc).
We want to increase stability of our network access by obtaining backup
internet connection from another ISP.
My question is:
Is there a way to configure FreeBSD, so the NATed workstations will use
two ISP at once and in case of one ISP failure the whole traffic will be
put on one connection?
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 2 ISP on one FreeBSD router

2004-05-25 Thread Chuck Swiger
Piotr Gnyp wrote:
My question is:
Is there a way to configure FreeBSD, so the NATed workstations will use
two ISP at once and in case of one ISP failure the whole traffic will be
put on one connection?
Sure, that's a standard multihoming scenario.
Get an AS number (www.arin.net) and set up BGP peering with your ISPs.
--
-Chuck
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 2 ISP on one FreeBSD router

2004-05-25 Thread Paul Chvostek
On Tue, May 25, 2004 at 12:44:04PM -0400, Chuck Swiger wrote:
 
 Piotr Gnyp wrote:
 My question is:
 Is there a way to configure FreeBSD, so the NATed workstations will use
 two ISP at once and in case of one ISP failure the whole traffic will be
 put on one connection?
 
 Sure, that's a standard multihoming scenario.
 Get an AS number (www.arin.net) and set up BGP peering with your ISPs.

That's a good answer, but not for this particular question.

Piotr, if your FreeBSD router has an Ethernet interface bound to the IP
assigned by each ISP, then the easiest way to transfer your NAT from one
ISP to the other is probably simply to kill the existing natd and re-run
it with a different -n option.  This *will* have the effect of taking
down your NAT for the transition period -- this is unavoidable.

You could achieve the transition with a simple shell script that would
ping the active connection, and if it fails, `killall natd`, wait for
the process to die, and re-launch with the different command line opts.

The exact mechanics are left as an exercise for the reader.  Or the
consultant he hires.  ;)

p

-- 
  Paul Chvostek [EMAIL PROTECTED]
  Operations / Abuse / Whatever
  it.canada, hosting and development   http://www.it.ca/

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]