okay, by
1. having multiple ip addresses on each isp,
2. advertising via dns multiple round-robin a records for www and multiple mx records
for mail
3. switching your default route away from failed paths
4. using dynamic dns (taking unreachable interfaces out of the sequence
as quickly as possible) you can accomplish some sort of diversity.
i would hope 4 is less necessary, because clients should know how
to handle multiple A records returned, and connect to the second
if the first fails (albeit, with a delay for the failed connect).
i'll look for the load-balancing thread, but several related questions:
what operating systems (besides cisco ios) support multiple default
routes with different metrics? so traffic could use the cheapest route
out, but come in via dns-selected ip addresses? (and so that load balancing
could be accomplished) (and so that failover default routing is automatic)
is there any way to send stuff which comes into a specific IP address
out via a specific route? (other than your QoS tagging, which
i don't quite understand -- i don't understand where the QoS tagging
takes place, and how an outgoing response is assigned the same QoS
as the incoming request).
anyone know of a good tutorial on QoS?
also, charles suggests that using a different masquerade address
as your source address will solve some problems. i don't understand
how that works when you still have a single default route.
On Fri, Jul 13, 2001 at 07:36:05AM -0700, Jack Coates wrote:
> On Thu, 12 Jul 2001, John P wrote:
>
> > Hi all,
> >
> > I know there's been lots of discussion about 'load balancing' in the past,
> > over two similar link types.
> >
> > I want to do something a little different but in the same vein. Our company
> > currently has a 2mb ADSL line, and for the most part it works great.
> > However, we might be taking on a leased line in the future, as we have a
> > mailserver/transaction server that we would like to ensure is always online.
> > (Always is a relative term, of course, compared to the DSL!). This will
> > probably only be 64k though.
> >
> > Anyway, what I would like to do is ensure all WWW/outgoing mail/downloads et
> > al goes over the 2mb line (fast, no bandwidth charges!) but the 'important'
> > traffic (incoming mail, incoming www requests) goes over the leased line.
> > Also if the DSL line fails, everything needs to go over the leased line.
> >
> > Is it possible with LEAF? Where to start looking?
> >
> > Cheers
> > John
> >
> > --
> > John Portwin
> >
> >
>
> If you can separate traffic type by IP address, then yes -- these are
> possible. However, LRP does not currently have the ability to route
> based on tags. In other words, we can use the QoS tools to tag traffic
> types, but we can't then say "tag 1 uses x.x.x.x for its default
> gateway, and everything else uses y.y.y.y". Supposedly this is being
> worked on, but I think the work is only being done in the 2.4 tree
> (which won't be realistic on LRP for a while).
>
> I've been trying to do the same thing for a while now, and it looks like
> OpenBSD will be able to do it -- I'll try to post to this list if I have
> success.
>
> --
> Jack Coates
> Monkeynoodle: It's what's for dinner!
>
>
> _______________________________________________
> Leaf-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/leaf-user
--
mark seiden, [EMAIL PROTECTED], 1-(650) 592 8559 (voice) Pacific Time Zone
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-user
