[EMAIL PROTECTED] wrote:
>
> In article <[EMAIL PROTECTED]> you wrote:
>
> : on this new code. It shows that the routing flags must be set to
> : distict values when deleting routes, even if the route in question
> : ist compeltely determined by destination and netmask. Gated doesn't
> : honor those flags in the required way, so it's not able to delete any
> : routes, even those that were previously created by gated itself.
>
> It is wrong statement. Gated cannot read remnants because it is buggy,
> rather than because of any change in 2.1. Hope, the bug will be fixed
> in gated 3.5.11. BTW I do not remember, that you asked me about this,
> in this case you would receive one character patch to fix it
> in exiting gateds.
>
> : This, in conjunction with the 'double route entry feature' (see this
> : mailing list some days ago) IMHO may be considered a bug.
>
> And this does not affect gated behaviour at all.
>
> Alexey
Alexey,
i really don't want to bother you, but your're not quite right from my
point of view. What i was talking about was **deleting** routes, not
reading them. There are, of course, some oddities in gated 3-5-10 when
it comes to initial route set up. But that does not affect the basic
functionality of gated in **my** case. Please remember: i do not run
gated simply to replace routed. What i need is a route processor, that
can deal with RIP Version 2 and OSPF (both using IP Multicalst).
For more than 4 years i'm running gated 3-5-x on several machines using
Linux (i86) and Digital/UNIX (Alpha) . May be there **are** bugs
in gated, it nevertheless serves my needs very well. Al long as there
is nothing around in the Linux world coming at least near to gated's
functionality when one has to deal with a wide variety of routing
protocols, i'm not willing to condamn it as a whole.
What i have done in the above case was patching the module
'krt_rt_ioctl.c' to set the flags in question more correctly.
This did not solve all problems, especially with RIP Version 2,
but now i'm in the same position as with Linux 2.0.35:
I now **can** successfully run gated 3-5-10!
One last word concerning the new Linux kernel routing environment.
Please do not take may words as a flame !
The efforts made in upgrading the kernel routing environment are really
great, but there is absolutely no documentation about the new API.
I checked the kernel sources several times without success, when trying
to find an entry point. I got a bunch of public and home-brew routing
utilities, most of them refused to work with the 2.1.x kernel.
In many cases, it's not a big thing to fix that, if you get the chance
to know how the API is intended to work **now**.
Times ago i was told 'nothing is done before the paperwork is done'.
So, if you need help in documenting what has already been implemented,
don't hesitate to contact me; im willing to bring in my share of work.
Regards, Andreas
--
Dr. Andreas G. Schindler c/o Alpha Zero One Computersysteme GmbH
[EMAIL PROTECTED] Frankfurter Str. 141, D-63303 Dreieich
Tel +49 6103 936018 Germany
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
