<p dir="ltr">Hi Thomas,</p>
<p dir="ltr">no, randomly adding host-routes to peers addresses is an unwanted behavour imo.</p>
<p dir="ltr">The more important question is: why are you using a /32 transit network? Your OS will add a route to your peer when using /31 or less.</p>
<div class="gmail_quote">Am 10.10.2014 12:05 schrieb "Thomas Goldberg" <<a href="mailto:t.goldberg77@gmail.com">t.goldberg77@gmail.com</a>>:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
we've OSPF running over a openvpn ptp tunnel and some problems with<br>
the routes injected by bird (v1.4.5).<br>
<br>
OSPF is running in PtP mode on the tun0 interface of each router. The<br>
problem is that bird doesn't inject any routers for the local<br>
interface IP as intra-area route into OSPF itself. We've to inject<br>
them as external route via import of routes learned by a direct<br>
protocol (d_local).<br>
This is how the end result looks:<br>
<br>
Router A:<br>
interface config:<br>
17: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc<br>
pfifo_fast state UNKNOWN qlen 100<br>
link/none<br>
inet 10.176.3.29 peer <a href="http://10.176.3.30/32" target="_blank">10.176.3.30/32</a> scope global tun0<br>
<br>
bird routes:<br>
<a href="http://10.176.3.30/32" target="_blank">10.176.3.30/32</a> dev tun0 [d_local 2014-10-07 16:13:46] * (240)<br>
<a href="http://10.176.3.29/32" target="_blank">10.176.3.29/32</a> via 10.176.3.30 on tun0 [o_internal 2014-10-09<br>
17:45:44] * E1 (150/100) [10.176.3.30]<br>
<br>
<br>
Router B:<br>
interface config:<br>
13: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc<br>
pfifo_fast state UNKNOWN group default qlen 100<br>
link/none<br>
inet 10.176.3.30 peer <a href="http://10.176.3.29/32" target="_blank">10.176.3.29/32</a> scope global tun0<br>
<br>
bird routes:<br>
<a href="http://10.176.3.29/32" target="_blank">10.176.3.29/32</a> dev tun0 [d_local 2014-10-09 17:45:43] * (240)<br>
<a href="http://10.176.3.30/32" target="_blank">10.176.3.30/32</a> via 10.176.3.29 on tun0 [o_internal 2014-10-09<br>
17:40:51] * E1 (150/100) [10.176.3.29]<br>
<br>
<br>
Shouldn't bird inject routes like this on the corresponding router<br>
(without having to learn them via the direct protocol)?<br>
<a href="http://10.176.3.29/32" target="_blank">10.176.3.29/32</a> dev lo [o_internal 2014-10-09 00:00:00] * I (150/0) [10.176.3.29]<br>
</blockquote></div>