What CARP interface name I must use for OpenBGP "Depend on" parameter? v2.2

[dniesen]

I somehow glossed over that part of the post, thanks for pointing that out.

That looks simple enough my only worry is how might editing those scripts impact future upgrades?

[dotdash]

Yeah, it would get wiped on upgrade but you could just re-add it…

[dniesen]

That can certainly be done, I'm not a huge fan of having exceptions to remember after I upgrade (or leaving those surprises for the next guy) but maybe a temporary workaround until this is sorted in the 2.2 series.

Would this handle preventing/starting that service when the firewall reboots as well then since CARP wouldn't be master on reboot?

[dotdash]

Per Chris, the scripts execute when the firewall switches to master or backup, so it shouldn't start until the fw returns to master status.

[Derelict]

I take it the same method could be utilized for Quagga?

[dniesen]

That makes sense, thank you.  I've been looking at the /etc/rc.carpbackup and /etc/rc.carpmaster scripts, I would assume the best place to stop/start OpenBGPd would be at the end of the script.

Is there a recommended way to restart this service without issuing a shell command via PHP or is that the only way to do it?  I see other services that are built in can be restarted by including a file and then there's a function that performs the restart, not sure if that's the case with OpenBGP

[dniesen]

Anybody have any thoughts on how I can stop/start this service from the php scripts as suggested?

[gabi]

I`m interested too  8)

[dniesen]

Bump.

[jimp]

I added a CARP status field and code to support it on the latest version of the OpenBGPD package.

Notes on its use here:
https://doc.pfsense.org/index.php/OpenBGPD_package

2.2-RELEASE through 2.2.2-RELEASE will need a small patch via System Patches for it to work properly (linked on the article). On 2.2.3 it will work without anything extra, just fill in the CARP status VIP box and Save.

[dniesen]

Note that the patch URL doesn't seem to be provided on the Wiki:

http://files.atx.pfsense.org/jimp/patches/carp-status-fix.diff

[jimp]

Thanks for catching that, apparently I pasted in the wrong URL there. Should be good now!

[gabi]

thank you jimp
I already switch to new 2.2.2 with this patch
I made a short test but when I switch back to master, bgp remains in ACTIVE for 2 sessions from a total of 4
I wil make more tests on this weekend

P.S: attached my old 2.0.2 uptime  8)