Help with peering, routes are not being imported

[Maria Matejka]

Hello Marek,

On Tue, Sep 16, 2025 at 12:59:51PM +0000, Marek Küthe wrote:

> naain and I are trying to set up peering, but it's not working. We are
> doing the peering via a WireGuard tunnel. This is working. We can ping
> each other's endpoints without any problems. On my side, it shows me
> that I am exporting the routes. However, naain's bird does not show any
> imported routes (despite a filter that accepts everything). We enabled
> the debug function for testing purposes and he received "filtered out"
> log messages. Neither he nor I can explain this, since the import
> filter accepts everything.

```
Tue Sep 16 15:00:29 2025 daemon.debug bird: marek_v6.ipv6 < filtered out fdec:a476:db6e::/48 0L 10G unicast
Tue Sep 16 15:00:29 2025 daemon.debug bird: marek_v6.ipv6 < filtered out fdb5:32:ad4a::/48 0L 10G unicast
Tue Sep 16 15:00:29 2025 daemon.debug bird: marek_v6.ipv6 < filtered out fdcb:dded:cbcc::/48 0L 10G unicast
Tue Sep 16 15:00:30 2025 daemon.debug bird: marek_v6.ipv6 < filtered out fdb5:32:ad4a::/48 0L 12G unicast
Tue Sep 16 15:00:30 2025 daemon.debug bird: marek_v6.ipv6 < filtered out fdb5:32:ad4a::/48 0L 11G unicast
Tue Sep 16 15:00:30 2025 daemon.debug bird: marek_v6.ipv6 < filtered out fdcb:dded:cbcc::/48 0L 12G unicast
Tue Sep 16 15:00:30 2025 daemon.debug bird: marek_v6.ipv6 < filtered out fdec:a476:db6e::/48 0L 12G unicast
Tue Sep 16 15:00:30 2025 daemon.debug bird: marek_v6.ipv4 < filtered out 172.23.126.128/27 0L 12G unicast
Tue Sep 16 15:00:30 2025 daemon.debug bird: marek_v6.ipv6 < filtered out fdcb:dded:cbcc::/48 0L 11G unicast
Tue Sep 16 15:00:30 2025 daemon.debug bird: marek_v6.ipv6 < filtered out fdec:a476:db6e::/48 0L 11G unicast
Tue Sep 16 15:00:30 2025 daemon.debug bird: marek_v6.ipv4 < filtered out 172.23.126.128/27 0L 11G unicast
Tue Sep 16 15:01:01 2025 daemon.debug bird: marek_v6.ipv4 < filtered out 172.21.100.24/29 0L 11G unicast
Tue Sep 16 15:01:01 2025 daemon.debug bird: marek_v6.ipv6 < filtered out fd40:e3b7:1d77:1234::/64 0L 11G unicast
Tue Sep 16 15:01:01 2025 daemon.debug bird: marek_v6.ipv6 < filtered out fd40:e3b7:1d77:1234::/64 0L 10G unicast
Tue Sep 16 15:01:11 2025 daemon.debug bird: marek_v6.ipv4 < filtered out 172.20.212.0/26 0L 10G unicast
Tue Sep 16 15:01:11 2025 daemon.debug bird: marek_v6.ipv6 < filtered out fdcc:abcd:cafe::/48 0L 13G unicast
Tue Sep 16 15:01:16 2025 daemon.debug bird: marek_v6: Sending KEEPALIVE
```

This is admittedly cryptic but `<` is export and `>` is import,
therefore what you are looking at are logs of BIRD refusing to export
non-own routes, as configured.

You'll need to look for `>` records for import, and probably `tcpdump`
might help to check whether it actually comes out from the right link.
With WireGuard though … are you sure that the packets actually come
through? I remember having weird MTU issues with my wireguard setup,
and TCP very easily sends packets big enough to hit it.

Have a nice day!  
Maria

-- 
Maria Matejka (she/her) | BIRD Team Leader | CZ.NIC, z.s.p.o.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20250916/7c73f795/attachment.htm>