On Sun, Mar 18, 2001 at 07:42:10PM -0800, Julian Elischer scribbled:
| Wes Peters wrote:
| > It struck me last night that if you want to load-balance between two ISPs,
| > you could simply pick a bit in the address and use it to select one or the
Buy a Layer >4 switch for your home DSL+cable mode
Wes Peters wrote:
>
>
> It struck me last night that if you want to load-balance between two ISPs,
> you could simply pick a bit in the address and use it to select one or the
> other. If you pick your bit appropriately -- I'd go for something in the
> second byte -- you might luck out and get
Nick Rogness wrote:
>
> On Sat, 17 Mar 2001, Wes Peters wrote:
>
> > > >
> > > >
> > > > Packet 1 comes in through ISP #2 network. It comes into your
> > > > internal network to machine 1. Machine 1 replies to the
> > > > packet...but where does it go? It will exit through i
Nick Rogness wrote:
>
> On Sat, 17 Mar 2001, Julian Elischer wrote:
>
> > Alex Pilosov wrote:
> > >
> > > On Sat, 17 Mar 2001, Nick Rogness wrote:
> > >
> > > > There is no way to tell your packet to go back out to ISP #2. That is the
> > > > point I'm trying to get across. Unless your running
Nick Rogness wrote:
>
>
> >
> > The final step is to select to which divert rule the packets eventually get
> > sent.
> > Each divert rule goes to a different natd, each of which is attached to a
> > different outgoing interface.
>
> I am going to look at what you suggested this afterno
On Sat, 17 Mar 2001, Wes Peters wrote:
> > >
> > >
> > > Packet 1 comes in through ISP #2 network. It comes into your
> > > internal network to machine 1. Machine 1 replies to the
> > > packet...but where does it go? It will exit through interface
> > > to ISP #1 becaus
Alex Pilosov wrote:
>
> On Sat, 17 Mar 2001, Garrett Wollman wrote:
>
> > That's the way Internet routing is supposed to work. If your routing
> > table says a packet supposed to go one way, and it really needs to go
> > another way, that's *user error* -- if you misconfigure your routing,
> >
Nick Rogness wrote:
>
> On Sat, 17 Mar 2001, Nick Rogness wrote:
>
> More clarification.
>
> >
> > > I completely fail to see that you have actually stated a problem yet.
> > >
> > > What exactly is the problem you think you're trying to solve here?
> > >
> >
> > Consider the following.
Alex Pilosov wrote:
>
> On Sat, 17 Mar 2001, Nick Rogness wrote:
>
> > There is no way to tell your packet to go back out to ISP #2. That is the
> > point I'm trying to get across. Unless your running a routing
> > daemon. But is that really practical with cable modems, dsl, etc?...I
> > don'
Nick Rogness wrote:
>
> On Sat, 17 Mar 2001, Wes Peters wrote:
>
> [Wes, if you get this, for some reason I can't send to your
> domain.]
>
> You are not understanding what I am trying to say. Once again I'll try to
> clarify.
>
> > > For dual-homed hos
On Sat, 17 Mar 2001, Garrett Wollman wrote:
> That's the way Internet routing is supposed to work. If your routing
> table says a packet supposed to go one way, and it really needs to go
> another way, that's *user error* -- if you misconfigure your routing,
> FreeBSD will do what you ask it to;
On Sat, 17 Mar 2001, Julian Elischer wrote:
> Alex Pilosov wrote:
> >
> > On Sat, 17 Mar 2001, Nick Rogness wrote:
> >
> > > There is no way to tell your packet to go back out to ISP #2. That is the
> > > point I'm trying to get across. Unless your running a routing
> > > daemon. But is that
On Sat, 17 Mar 2001, Garrett Wollman wrote:
> < said:
>
> > Packet 1 comes in through ISP #2 network. It comes into your
> > internal network to machine 1. Machine 1 replies to the
> > packet...but where does it go? It will exit through interface
> > to ISP #1 because of the
< said:
> Packet 1 comes in through ISP #2 network. It comes into your
> internal network to machine 1. Machine 1 replies to the
> packet...but where does it go? It will exit through interface
> to ISP #1 because of the default gateway. It came in ISP #2 and
> l
On Sat, 17 Mar 2001, Alex Pilosov wrote:
> On Sat, 17 Mar 2001, Nick Rogness wrote:
>
> > > b) route-cache means fast lookup of destination gateway. Lookup of
> > > destination gateway may be slow (see d), and it makes sense to keep track
> > > of a TCP connection and 'fast-switch' (cisco lingo)
On Sat, 17 Mar 2001, Julian Elischer wrote:
> this will do what you want for OUTGOING packets.
> incoming packets will probably all come in on one network.
And to fix this, you play tricks with your DNS server :)
A setup that I have at home:
Domain with two listed nameservers (same machine, diff
Alex Pilosov wrote:
> You don't need to know the interface. You must route based on the source
> IP. I.E:
>
> ISP A ISP B
> \ /
> ra rb
> \ /
> your router
> |
> |
> |
> (local)
>
> (ra
Alex Pilosov wrote:
>
> On Sat, 17 Mar 2001, Nick Rogness wrote:
>
> > There is no way to tell your packet to go back out to ISP #2. That is the
> > point I'm trying to get across. Unless your running a routing
> > daemon. But is that really practical with cable modems, dsl, etc?...I
> > don'
Nick Rogness wrote:
>
> On Sat, 17 Mar 2001, Nick Rogness wrote:
>
> There is no way to tell your packet to go back out to ISP #2. That is the
> point I'm trying to get across. Unless your running a routing
> daemon. But is that really practical with cable modems, dsl, etc?...I
> don't think
On Sat, 17 Mar 2001, Nick Rogness wrote:
> > b) route-cache means fast lookup of destination gateway. Lookup of
> > destination gateway may be slow (see d), and it makes sense to keep track
> > of a TCP connection and 'fast-switch' (cisco lingo) the following packets,
> > caching the following da
On Sat, 17 Mar 2001, Alex Pilosov wrote:
> On Sat, 17 Mar 2001, Nick Rogness wrote:
>
> > There is no way to tell your packet to go back out to ISP #2. That is the
> > point I'm trying to get across. Unless your running a routing
> > daemon. But is that really practical with cable modems, dsl
On Sat, 17 Mar 2001, Nick Rogness wrote:
> There is no way to tell your packet to go back out to ISP #2. That is the
> point I'm trying to get across. Unless your running a routing
> daemon. But is that really practical with cable modems, dsl, etc?...I
> don't think so.
Is the clue really gon
On Sat, 17 Mar 2001, Nick Rogness wrote:
More clarification.
>
> > I completely fail to see that you have actually stated a problem yet.
> >
> > What exactly is the problem you think you're trying to solve here?
> >
>
> Consider the following. I have to restate this every damn couple
On Sat, 17 Mar 2001, Wes Peters wrote:
[Wes, if you get this, for some reason I can't send to your
domain.]
You are not understanding what I am trying to say. Once again I'll try to
clarify.
> > For dual-homed hosts, this is a problem because your pa
Nick Rogness wrote:
>
> On Fri, 16 Mar 2001, Jeroen Ruigrok/Asmodai wrote:
>
> > -On [20010310 04:00], Nick Rogness ([EMAIL PROTECTED]) wrote:
> > >
> > >Is anyone working on route caching functionality within FreeBSD? This
> > >would eliminate a lot of problems with using FreeBSD as a router..
< said:
> Correct me if wrong, but if I recall BSD natively already held a route
> cache, although it might not be the best route cache which we could come
> up with.
It does, but there is only a single route cached there. A better
implementation might have a small hash table (e.g., 16 entries)
On Fri, 16 Mar 2001, Jeroen Ruigrok/Asmodai wrote:
> -On [20010310 04:00], Nick Rogness ([EMAIL PROTECTED]) wrote:
> >
> >Is anyone working on route caching functionality within FreeBSD? This
> >would eliminate a lot of problems with using FreeBSD as a router...which
> >seems to be a common role
-On [20010310 04:00], Nick Rogness ([EMAIL PROTECTED]) wrote:
>
>Is anyone working on route caching functionality within FreeBSD? This
>would eliminate a lot of problems with using FreeBSD as a router...which
>seems to be a common role of which FreeBSD seems to fit. Especially for
>machine that
Is anyone working on route caching functionality within FreeBSD? This
would eliminate a lot of problems with using FreeBSD as a router...which
seems to be a common role of which FreeBSD seems to fit. Especially for
machine that are dual-homed.
It may be implemented nicely as a sysctl var or ma
29 matches
Mail list logo
