On 03/24/16 15:47, Alexander Bluhm wrote:
> On Thu, Mar 24, 2016 at 03:03:18PM +0100, Florian Riehm wrote:
>> -void rt_missmsg(int, struct rt_addrinfo *, int, u_int, int, u_int);
>> +void rt_missmsg(int, struct rt_addrinfo *, int, u_char, u_int, int,
>> u_int);
>
>> -rt_missmsg(in
On Thu, Mar 24, 2016 at 03:03:18PM +0100, Florian Riehm wrote:
> -void rt_missmsg(int, struct rt_addrinfo *, int, u_int, int, u_int);
> +void rt_missmsg(int, struct rt_addrinfo *, int, u_char, u_int, int, u_int);
> -rt_missmsg(int type, struct rt_addrinfo *rtinfo, int flags, u_int ifidx,
> -
Hi,
Routing daemons like ospfd use two interfaces to obtain route information from
the kernel:
- sysctl
- route messages
Route information from sysctl contain correct route priorities, route messages
not. This can lead to incorrect routes inside the daemons. If daemons see routes
with different p
