OSPF unexpectedly adds /128 interface route

[Lexi Winter]

hello,

i have an interface with a /64 address configured:

	# ifconfig bridge0.500
	bridge0.500: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
		options=0
		ether 58:9c:fc:10:8d:b4
		inet6 fe80::1%bridge0.500/64 scopeid 0x1c
		inet6 fd13:480d:2ffa:3::1/64
		groups: vlan
		vlan: 500 vlanproto: 802.1q vlanpcp: 0 parent interface: bridge0
		nd6 options=1<PERFORMNUD>

this is configured as an OSPF stub interface in BIRD:

	protocol ospf v3 core {
		area 0 {
			interface "bridge0.500" {
				stub yes;
			};
			...

however, BIRD only adds a /128 route into the OSPF database:

	# birdc show route in fd13:480d:2ffa:3::/64
	BIRD 3.2.0 ready.
	Table master6:
	fd13:480d:2ffa:3::1/128 unicast [core 13:25:02.965] ! I (150/0) [176.126.243.164]
		dev bridge0.500
	fd13:480d:2ffa:3::/64 unicast [direct1 13:38:01.578] * (240)
		dev bridge0.500

i would have expected it to add the /64 route instead.  filtering the /64
route in the direct protocol does not make any difference, except that the
direct route disappears from 'show route'.

am i doing something wrong?

the entire configuration is here: https://www.le-fay.org/tmp/30d/bird.conf

using BIRD 3.2.0 on FreeBSD 15.0.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20260510/86b5b2b6/attachment.sig>