Two ISP lines

[Juan Rodriguez Hervella]

Just some questions about this paper:

"(...) Note that this route has to be at the same level of the tree, i.e.
the code cannot return a less specific match or a more specific
match (...)"

Question: I don't understand why if you are looking for an alternate
route you aren't allowed to retrieve a more specific route. This doesn't
make sense to me. If you are routing packets using a route when
there is a more specific match, you aren't doing "longest prefix match".

Another question: if ISP-1 goes down, and you use this feature of
alternatives routes, this still doesn't fix the communication problem. Unless
you make something with the source addr. of the multihomed site's
packets, the reply packets will be lost in the faulty ISP, imho.

Regards.




On Friday 23 January 2004 01:38, Randall R. Stewart (home) wrote:
> Andrea/all:
>
> An interesting question... the following link has
> some thoughts along these lines... and something
> for the BSD community to think upon...
>
> http://www.sctp.org/what_is_alt_route
>
> TCP could definetly use something like the above (with Itojun's Multi-path
> updates as well).. it would give more reliability to  even a singly
> homed protocol such as TCP :->
>
> R
>
> Andrea Venturoli wrote:
> >Ok, I asked already asked something similar to this in the past, but it's
> > not the same thing... maybe it's a trivial question...
> >If I had two lines to the Internet: how would I use both?
> >Could I just provide two default routes? How?
> >What algorithm would be used to choose among the two?
> >What if one failed?
> >
> > bye & Thanks
> >        av.
> >
> >
> >
> >_______________________________________________
> >freebsd-net at freebsd.org mailing list
> >http://lists.freebsd.org/mailman/listinfo/freebsd-net
> >To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"

-- 
******
JFRH
******

"If a camel flies, no one laughs if it doesn't get very far."
		-- Paul White