Description: Exporting via OSPF both static and aggregate routes
causes gated to die when the static routes are listed in the aggregate
statement.
ospf yes {
traceoptions all;
monitor-authentication simple "xxx";
backbone {
authtype none;
networks {
aaa.bbb.0.0 mask 255.255.224.0;
xxx.yyy.0.0 masklen 17;
};
interface de0;
};
};
static {
xxx.yyy.17.0 mask 255.255.255.192 gateway aaa.bbb.3.2;
xxx.yyy.17.128 mask 255.255.255.192 gateway aaa.bbb.3.14;
};
aggregate xxx.yyy.17.0 masklen 24 {
proto static {
xxx.yyy.17.0 masklen 26; # Citizen One Software
xxx.yyy.17.128 masklen 26; # Design Sciences
};
};
export proto ospfase {
proto aggregate metric 1 {all;};
proto static metric 2 {all;};
};
From the gated log file, first the aggregated /24 gets exported,
May 25 11:13:07 ospf_ase_export: export Add xxx.yyy.17/255.255.255
Then when it tries to export xxx.yyy.17/255.255.255.192 (Existing) (as
determined with gdb) it dies with an "assertion failed" on line 776 of
ospf_rt.c.
______________________________________________________________________________
Another related bug:
static {
xxx.yyy.24.0 masklen 24 gateway xxx.yyy.zzz.aaa;
};
aggregate xxx.yyy.24.0 makslen 24 {
proto static {
xxx.yyy.24.0 masklen 24;
};
};
export proto ospfase {
proto aggregate metric 1 {all;};
};
Does not export this network number. I would expect it to do so.
Rob
Rob Liebschutz <r...@rjl.com> writes:
> Gated Version: R3_5Beta_3
> OS: BSDI BSD/OS 2.1
>
> Description: Exporting via OSPF both static and aggregate routes
> causes gated to die when the static routes are listed in the aggregate
> statement.
>
>
GateD's OSPF currently supports RFC 1247 and does not support origination
of multiple ASE or summary LSA's with the same network number but different
masks. Refer to Appendix E2 of RFC 1583.
Note that Merit is working on fixing this with enhancements to GateD 3.6.
> ______________________________________________________________________________
> Another related bug:
>
> static {
> xxx.yyy.24.0 masklen 24 gateway xxx.yyy.zzz.aaa;
> };
>
> aggregate xxx.yyy.24.0 makslen 24 {
> proto static {
> xxx.yyy.24.0 masklen 24;
> };
> };
>
> export proto ospfase {
> proto aggregate metric 1 {all;};
> };
>
> Does not export this network number. I would expect it to do so.
>
I would expect the static route to have a lower preference than the
aggregate - hence the aggregate route will not be the active
route (no reject route) and will not be exported.
Acee