> > This is an issue with the routing system design. Many routers
> > allow duplicate routes (same netmask) that have different priorities.
> > This makes it quicker to switch routes during a failure.
>
> FreeBSD permits this as well. It is the responsibility of the routing
> process to manage which specific route is installed in the kernel
> forwarding table at any given time. (FreeBSD's `routed' can do this
> in some instances.) FreeBSD does not directly support multiple static
> routes to a given destination, since it has no knowledge which would
> enable it to choose among them; again, a routing process can be used
> to manage this.
FreeBSD permits this so long as you write a program to do it. The kernel
table is not really a routing table as many networking folks would define it.
It's a forwarding table mixed with other things. In many routing
systems there is a routing table that multiple routing processes can
share. It is a common database and is treated as such. It is from
this arena that such questions arise.
The way things work in FreeBSD is that you run a single routing process
(Zebra, Routed, GateD etc.) that maintains a real routing database
and then periodically pushing things down into the kernel.
Later,
George
--
George V. Neville-Neil [EMAIL PROTECTED]
NIC:GN82
"Those who would trade liberty for temporary security deserve neither"
- Benjamin Franklin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
