Openvpn - quagga ospf - mesh
-
Hi Eveyone,
I will be setting something like this up very soon. (Two sites both with dual WAN/Carp)Is this problem fixed with or without the patch?
thanks in advance.
vito -
for me it's still working with patch on client side, no patch on server side… and since I saw no update for the package itself...
-
it works for redundant vpn's between 2 sites.
it does not work when making a "triangle" between 3 sites.
I still hope someday some brilliant mind will come up with a solution for this ;) -
Quagga works for doing many sites. I've seen some with half a dozen or more sites on the same "area" doing redundant OSPF+OpenVPN.
-
I figure the rush to 2.1 is over now and am wondering if there are plans to
improve the way quagga behaves. As it still distributes tunnel networks this causes issues with mesh'd sites. -
for completion of this thread/documentation:
- final pfSense 2.1 works fine without the Quagga OSPF Patch offered by Jimp in this threat.
- Quagga OSPF recognizes its neighbour over OpenVPN only if you use a peer2peer network /30.
No idea why for instance a /24 won't work (I see on both sides HELO packages, but no Quagga OSPF response).
Bests
-
If you want to use a /24 you can, but it requires using TAP.
Using a /24 with topology subnet appears to work but for some reason … doesn't. Switching to tap it works fine.
The tunnel networks being distributed is fixed in the newest version of the Quagga package, either check the "accept filter" button on the tunnel interfaces, or add them manually to the main list with 'accept filter' checked.
-
Jimp,
I still see this problem, even with the "Accept Filter" checked.
The routes don't show up in the "Quagga OSPF Database" section anymore, but they absolutely still show up in the "Quagga OSPF Router Database", and in the "Quagga OSPF Routes".
This means they are still distributed to the other OSPF clients, at which point, if you have a "triangle" topology, OpenVPN breaks on one leg during ifconfig because it sees a route to the other end of its private tunnel. -
Jimp,
I still see this problem, even with the "Accept Filter" checked.
The routes don't show up in the "Quagga OSPF Database" section anymore, but they absolutely still show up in the "Quagga OSPF Router Database", and in the "Quagga OSPF Routes".
This means they are still distributed to the other OSPF clients, at which point, if you have a "triangle" topology, OpenVPN breaks on one leg during ifconfig because it sees a route to the other end of its private tunnel.you can sort of fix it by manually adding the tunnel IP to the "disable acceptance" list in the global-settings tab of the quagga service.
for example you have a tunnel net of 192.168.22.1/24:
on the server end add to "subnet to route': 192.168.22.1/32 (check disable acceptance)
on the client end add to "subnet to route': 192.168.22.2/32 (check disable acceptance)do this for all the tunnel subnets on both ends and you won't have the problems with ifconfig.
i know it's a hassle, but its the only way i know, to get the job doneenjoy
-
If you keep all of your tunnel networks in a close range you can add a manual accept filter for the entire larger subnet which includes the smaller tunnel networks. For example if you have 192.168.22.0/30, 192.168.22.4/30, 192.168.22.8/30 and so on for tunnel networks, then you can setup an accept filter for 192.168.22.0/24 and I believe that should work OK.
