Bug #4623
Carp not working under bhyve
0%
Description
It seems the carp implementation differs from the freebsd standard one, which cannot be used under bhyve.
On a fresh freebsd 10.1 bhyve install i could make carp work:
$ uname -a
FreeBSD darkthrone 10.1-RELEASE-p9 FreeBSD 10.1-RELEASE-p9 #0: Tue Apr 7 01:09:46 UTC 2015 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
$/sbin/ifconfig vtnet0 vhid 1 advskew 100 pass test 192.168.1.210/24 state master alias
ifconfig: SIOCSVH: Invalid argument
$kldload carp
$/sbin/ifconfig vtnet0 vhid 1 advskew 100 pass test 192.168.1.210/24 state master alias
$ ifconfig
...
media: Ethernet 10Gbase-T <full-duplex>
status: active
carp: BACKUP vhid 1 advbase 1 advskew 100
In pfsense the carp module is in the kernel, but i'll get the first error as on a fresh native fbsd install without / before loading the carp module
pfsense $/sbin/ifconfig vtnet0 vhid 1 advskew 100 pass test 192.168.1.210/24 state master alias
ifconfig: SIOCSVH: Invalid argument
I tested from early 2.2 RC versions till latest devel version.
I also tested OPNSense la 15.1.9, which had the pfsync / unconsistent changes to carp reversed. Worked there also.
So some custom stuff keeps me away from using pfSense under bhyve with carp (currently running single node only)
History
#1
Updated by Ermal Luçi almost 6 years ago
Did you try from the GUI since carp should not differ from FreeBSD at least in this regard!
#2
Updated by Matthias Breddin almost 6 years ago
Ermal Luçi wrote:
Did you try from the GUI since carp should not differ from FreeBSD at least in this regard!
Yes, that's when i checked for details...
cheers,
Matthias
#3
Updated by Matthias Breddin over 5 years ago
Just checked with 2.3-alpha, it works there. I don't really know if it's because of fbsd 10.2 or some reversed custom patches?
#4
Updated by Chris Buechler over 5 years ago
- Status changed from New to Resolved
- Target version set to 2.3
Thanks for the feedback. Probably going to 10-STABLE fixes (or removal of patches in the process, though those removed largely got upstreamed).
#5
Updated by Matthias Breddin over 5 years ago
So any idea it'll get backported to 2.2.x "soon". Or will 2.3 be released before any new 2.2.x version?
#6
Updated by Chris Buechler over 5 years ago
Matthias Breddin wrote:
So any idea it'll get backported to 2.2.x "soon". Or will 2.3 be released before any new 2.2.x version?
It won't be backported, not likely there will be another 2.2.x.