I agree, the weight parameter is also what I need;) but I ask again: It isn't possible to solve this at a higher level (routing) ?
There is the 'metric' option for routes, I can put a bigger metric for the backup link. Will this link be automatically used when the primary link with a lower metric is down? Or RIP running on both routers can be a solution for this? thanks -- Ciprian Badescu On Thu, 19 Jun 2003, Michael Sierchio wrote: > Date: Thu, 19 Jun 2003 07:47:15 -0700 > From: Michael Sierchio <[EMAIL PROTECTED]> > To: Hendrik Scholz <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Subject: Re: Redundant link configuration > > Hendrik Scholz wrote: > > > Have a look at the ng_one2many module. The manpage comes with a nice > > example and offers the needed featuers. > > NG_ONE2MANY(4) > > TRANSMIT ALGORITHMS > At this time, the only algorithm for determing the outgoing many hook is > a simple round-robin delivery algorithm. Packets are delivered out the > many hooks in sequential order. > > In the future other algorithms may be added as well. > > That would be nice -- in particular, links with different > characteristic capacities and latencies would be nice to bond -- > as in a shared DS3 and a 256kb frame relay, my current problem. > > We have an expensively idle backup frame relay link which could > be carrying "stuff" -- even simple parameters such as weighted > preference would suffice. > > _______________________________________________ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
