Date: Fri, 23 Jun 2006 23:50:05 +1000 From: "Christopher Martin" <outsidefactor@iinet.net.au> To: "'Vadim Goncharov'" <vadimnuclight@tpu.ru>, "'Baldur Gislason'" <baldur@foo.is> Cc: 'FreeBSD Net Mailing list' <freebsd-net@freebsd.org> Subject: RE: Multiple routes to the same destination Message-ID: <52se08$adeqot@iinet-mail.icp-qv1-irony6.iinet.net.au> In-Reply-To: <optbll3eso4fjv08@nuclight.avtf.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Actually, round robin is exactly what I want. And I am not saying I > don't > > use a routing protocol, in fact I do, but I want packets to be able to > > use two or more diverse paths of equivalent cost. > > You can try to use ng_one2many(4) netgraph node for simple round-robin, if > this all what you want. I guess I could, but I would resent the need, if for no other reason than it isn't required anywhere but BSD. Even Windows does this. And I'd have to do extra work to get quagga/openospf to work with netgraph. And I'd have to setup each node manually for each possible destination. And it couldn't auto learn new multipaths automatically through OSPF, I'd have to re-visit every router each time I brought new paths online. And, from what I read I need to have a card for every path (read it here: http://www.gsp.com/cgi-bin/man.cgi?section=4&topic=ng_one2many). Seems like a lot of work for something that is just there everywhere else. My original points were: 1) Why isn't it there and why not, and is there good reason it isn't 2) If it's just a case of no-one doing it, can anyone give a quick appraisal in their opinion of how much effort it would take to include?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52se08$adeqot>