Gareth Rowlands wrote:
> There isn't a simple way of stopping rip98d from advertising some routes,
> unless they are non-44. routes when the -r option can be used, so that
> only
Yes, I understand why: rip uses the kernel table as its storage for the
routes, as does *nos. Ok, good, that simplifies the program. There is
no way of doing a "route addprivate" in Linux ? Marking a route to not
to be exported.
> It may be possible to mod the source of rip98d, so that its routes
> are taken from a file other than /proc/net/route. You could then copy
> proc/net/route to this other file, censoring the unwanted contents via
> a script on the way.
Yes, but that should be a backgroud process. Not a bad idea.
Another one: rip98d could filter.
2 files:
One for put initial static routes, and another to put the routes
wich we don't want to announce.
> Out of interest, can I ask if there a 'technical' reason for having
> routes you don't want published ?
Another one, apart of the previous message:
In the gateway there is 3 internal routes, of hosts wich are
arp published, so their routes doesn't need to be published.
--
Saludos de Juli�n
-.-
