[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] network-bridge script and the ip route list command


  • To: xen users <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Christopher G. Stach II" <cgs@xxxxxxxxx>
  • Date: Fri, 29 Dec 2006 21:44:14 -0200
  • Delivery-date: Fri, 29 Dec 2006 15:44:19 -0800
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Jerry Amundson wrote:
> On 12/29/06, Christopher G. Stach II <cgs@xxxxxxxxx> wrote:
>> If you have two default routes with one over a higher cost path, why
>> wouldn't you want a higher metric?
> 
> Because the metric is defined as a measurement of hops, not cost.
> Metric The "distance" to the target (usually counted in  hops).  It  is
>              not  used  by  recent kernels, but may be needed by routing
> dae-
>              mons.
> By definition then, a metric on a default route (or routes) is not
> definable - there is no concrete target, only "all other targets".
> 
> That said, however, advanced routing techniques (rules, tables, etc.)
> could be in place which would give additional output from "ip route
> list" after the device. Hence the suggestion to file a bug anyway.

Hop count is a path cost.

You can certainly have more than one default route.  If you have one
with a higher cost, it won't be used if the lower cost route is available.

Why would metrics not be used for routing in the kernel?  That would
more or less castrate Linux as a an IP router.  What changeset did this
happen in?

-- 
Christopher G. Stach II


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.