<?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[Quagga OSPF problems [SOLVED (Sort of…)]]]></title><description><![CDATA[<p dir="auto">I'm a bit rusty on my OSPF skills, maybe someone can help me out here? :)</p>
<p dir="auto">I've got three pfSense boxes connected like this</p>
<p dir="auto">OPT1,2&amp;3                                      LAN                                     OpenVPN                        LAN<br />
–----------------pfsense1----------------------------pfsense2--------------------------pfsense3--------------<br />
                         192.168.20.15       192.168.20.1    192.168.17.2      192.168.17.1   192.168.15.1</p>
<p dir="auto">All the 192.168 networks above are /24's. On pfsense1's OPT-interfaces are several 10.x subnets.<br />
I want pfsense1 to know about pfsense3's networks and the other way around.</p>
<p dir="auto">I have added firewall rules to allow OSPF on all interfaces involved.<br />
I have checked the "Redistribute connected networks" box.<br />
All boxes are set to area 0.0.0.0<br />
pfsense1 shows pfsense2 as a fully adjacent neighbor.<br />
pfsense2 shows only pfsense3 as a fully adjacent neighbor.<br />
pfsense3 shows pfsense2 as a fulla adjacent neigbour.<br />
pfsense 2 and 3 seems to talk nicely to eachother, they both know about each others connected networks.<br />
pfsense 1 knows about pfsense2's networks, but not the other way around.<br />
pfsense 1 and 3 know nothing about eachother.</p>
<p dir="auto">They way i see it, there is a problem between pfsense 1 and 2 where 2 pretends not to know about 1.<br />
On the status page on pfsense 2 it says it has only one interface in area 0.0.0.0, that seems odd to me. Shouldn't that be 2?</p>
]]></description><link>https://forum.netgate.com/topic/45148/quagga-ospf-problems-solved-sort-of</link><generator>RSS for Node</generator><lastBuildDate>Sat, 11 Apr 2026 23:52:35 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/45148.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 21 May 2012 07:51:44 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Quagga OSPF problems [SOLVED (Sort of…)] on Mon, 21 May 2012 09:12:03 GMT]]></title><description><![CDATA[<p dir="auto">After a series of reboots it's all working now. I'm not thrilled by the stability here, but hey, I am running 2.1-DEVELOPMENT so I guess I can live with it for now :)<br />
Any ideas of when 2.1-STABLE will be out? I read a lot about IPv6 Launch Day, and that's not very far away.</p>
]]></description><link>https://forum.netgate.com/post/337508</link><guid isPermaLink="true">https://forum.netgate.com/post/337508</guid><dc:creator><![CDATA[m.algoe]]></dc:creator><pubDate>Mon, 21 May 2012 09:12:03 GMT</pubDate></item><item><title><![CDATA[Reply to Quagga OSPF problems [SOLVED (Sort of…)] on Mon, 21 May 2012 08:57:16 GMT]]></title><description><![CDATA[<p dir="auto">I restarted all 3 boxes and now things are slightly better, but not 100%.</p>
<p dir="auto">pfsense2 now has two interfaces in area 0.0.0.0 and lists both pfsense 1 and 3 as neighbors.<br />
problem is, now negotiations with pfsense3 fails and gets stuck in ExStart state. Googling this indicates the most common problem to be MTU settings. The link to pfsense3 is a OpenVPN link, but i don't know where to change the MTU, I have never messed with it.<br />
Also, on pfsense3, the pfsense2-box is listed as Full. That makes no sense to me…</p>
]]></description><link>https://forum.netgate.com/post/337502</link><guid isPermaLink="true">https://forum.netgate.com/post/337502</guid><dc:creator><![CDATA[m.algoe]]></dc:creator><pubDate>Mon, 21 May 2012 08:57:16 GMT</pubDate></item></channel></rss>