hi Nico, Nico Schottelius via Bird-users wrote in <[email protected]>: > I believe the issue might be this one: > > define OSPF_V4_EXPORT = [ > 0.0.0.0/0 > ]; > > 0.0.0.0/0 matches only the default route *exactly*, nothing shorter. > What you probably meant is: > > 0.0.0.0/0+ (default route and everything shorter as well).
my understanding is that Type 1 LSAs for directly connected interfaces
are originated inside OSPF and aren't subject to the route filter. for
example, i have another interface with an identical configuration:
interface "wg.vpn" {
stub yes;
};
and this interface also has an IPv4 address assigned:
wg.vpn: flags=10080c1<UP,RUNNING,NOARP,MULTICAST,LOWER_UP> metric 0 mtu
1280
options=80000<LINKSTATE>
inet 198.18.66.1/24
and a Type 1 LSA for 198.18.66.0/24 is correctly originated, even though
198.18.66.0/24 isn't permitted in the filter.
the reason 0.0.0.0/0 is listed in the filter is that this router injects
a default route as a Type 5 (E1) LSA; that's not directly relevant to the
problem, i just wanted to show all the relevant config.
adding 81.187.73.117/32 to OSPF_V4_EXPORT does result in the address of
ng0 being originated as a Type 5 LSA, but since this is an interface
address, it seems more correct to originate it as a Type 1 LSA.
(but it's quite possible this is not how OSPF is meant to work with
point-to-point addresses, so i don't know if this is actually wrong;
it was just surprising.)
signature.asc
Description: PGP signature
