<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[FRR OSPF static routing Virtual IPs]]></title><description><![CDATA[<p dir="auto">Upfront - I am neither an OSPF nor FRR hero. So everything here can also be caused by basic lack of knowledge. Nevertheless - I am a little puzzled about the behaviour of the FRR package. Maybe anyone can give me a hint how to deal with this.</p>
<p dir="auto">I have FRR/OSPF running to manage fail over between sites (OpenVPN tunnels) as described in the Hangout by John Pringle. So far - everything is working really well and doing exactly what it should for interfaces.</p>
<p dir="auto">I now wanted to add Virtual IPs to an interface and distribute those via static routes (Zebra) to the neighbours. Now comes the weird thing. When I first tried it, Zebra recognised it as a connected route but did neither select nor forward it.</p>
<p dir="auto">By accident, when validating the config, did I mess up the network mask and increased it on the zebra side (27 zebra vs. 28 on the Virtual IP side). And voila - the route was selected and forwarded to the neighbours.</p>
<p dir="auto">It can be reproduced. Adjusting the network mask in zebra or Virtual IP kills the routing again.</p>
<p dir="auto">That's how I set up the static routing now - having a large mask on zebra side. But this seems awkward to me - especially knowing pfsense for some time now.</p>
<p dir="auto">So where is my mistake in setting up this. Is there an order to follow to avoid this behaviour?</p>
<p dir="auto">A bit clueless - honestly</p>
<p dir="auto">P.S. All nodes running on pfsense 2.4.4-RELEASE-p2</p>
]]></description><link>https://forum.netgate.com/topic/143422/frr-ospf-static-routing-virtual-ips</link><generator>RSS for Node</generator><lastBuildDate>Wed, 22 Apr 2026 23:18:29 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/143422.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 16 May 2019 14:56:31 GMT</pubDate><ttl>60</ttl></channel></rss>