Quagga OSPF problems [SOLVED (Sort of…)]
I'm a bit rusty on my OSPF skills, maybe someone can help me out here? :)
I've got three pfSense boxes connected like this
OPT1,2&3 LAN OpenVPN LAN
192.168.20.15 192.168.20.1 192.168.17.2 192.168.17.1 192.168.15.1
All the 192.168 networks above are /24's. On pfsense1's OPT-interfaces are several 10.x subnets.
I want pfsense1 to know about pfsense3's networks and the other way around.
I have added firewall rules to allow OSPF on all interfaces involved.
I have checked the "Redistribute connected networks" box.
All boxes are set to area 0.0.0.0
pfsense1 shows pfsense2 as a fully adjacent neighbor.
pfsense2 shows only pfsense3 as a fully adjacent neighbor.
pfsense3 shows pfsense2 as a fulla adjacent neigbour.
pfsense 2 and 3 seems to talk nicely to eachother, they both know about each others connected networks.
pfsense 1 knows about pfsense2's networks, but not the other way around.
pfsense 1 and 3 know nothing about eachother.
They way i see it, there is a problem between pfsense 1 and 2 where 2 pretends not to know about 1.
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?
I restarted all 3 boxes and now things are slightly better, but not 100%.
pfsense2 now has two interfaces in area 0.0.0.0 and lists both pfsense 1 and 3 as neighbors.
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.
Also, on pfsense3, the pfsense2-box is listed as Full. That makes no sense to me…
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 :)
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.