I was recently working with this document and having issues getting CARP 
working.  I identified one of the issues as one of my own creation.  I was 
working with these settings on a VMware vSphere and by default this doesn't 
allow promiscuous mode.  I was wondering if the document should be updated to 
show this as a requirement of CARP.  The second problem I was having I noted 
during the boot of the server.  I had the following line in the rc.conf file:

ifconfig_vmx0_alias0="vhid 1 advskew 100 pass redacted alias 155.247.167.127/32"

This is close to the example given in the documentation outside of adjusting 
for my network card and settings.  During the boot I would get the following 
error:

/etc/rc: WARNING: $ifconfig_vmx0_alias0 needs leading "inet" keyword for an 
IPv4 address.

I changing the line to this:

ifconfig_vmx0_alias0="inet vhid 1 advskew 100 pass redacted alias 
155.247.167.127/32"

After changing the line I did not note any errors during the boot of the OS.  
I'm running a fully patched version of 10.2.  I did find this is similar to how 
a virtual host would be configured in the rc.conf file but find nothing about 
this for CARP.  Does this need to be updated in the document or is there some 
other issue?

Thanks,

Chris Hunnewell
[email protected]<mailto:[email protected]>
Temple University
Computer Services

CONFIDENTIALITY STATEMENT: The information contained in this e-mail, including 
attachments, is the confidential information of, and/or is the property of, 
Temple University. The information is intended for use solely by the individual 
or entity named in the e-mail. If you are not an intended recipient or you 
received this in error, then any review, printing, copying, or distribution of 
any such information is prohibited. Please notify the sender immediately by 
reply e-mail and then delete this e-mail from your system.

_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-doc
To unsubscribe, send any mail to "[email protected]"

Reply via email to