Hi all
I have 2 Openbsd 4.0 systems running I have the systems plugged into a gigabit (4 port intel server adapter) management switch (external interface) I then have the 2 systems plugged together via the pfsync on a 100mb intel card Carp is working fine, pf is working fine. I allow all carp and pfsync data to pass per the manual(s) Here is an example of my files Server1 Hostname.em0 Ip is 1.2.3.4 Mygate 1.2.3.254 Hostname.carp0 (used by em0) Primary ip is 1.2.3.10 Alias 1.2.3.11 Alias 1.2.3.12 Alias 1.2.3.13 Hostname.em1 (internal interface) Ip is 10.50.50.1 Hostname.carp1 (used by em1) Ip is 10.50.50.254 Sasyncd.conf interface carp0 peer 1.2.3.5 sharedkey /etc/aes1922.key Server2 Hostname.em0 Ip is 1.2.3.5 Mygate 1.2.3.254 Hostname.carp0 (used by em0) Primary ip is 1.2.3.10 Alias 1.2.3.11 Alias 1.2.3.12 Alias 1.2.3.13 Hostname.em1 (internal interface) Ip is 10.50.50.1 Hostname.carp1 (used by em1) Ip is 10.50.50.254 Sasyncd.conf interface carp0 peer 1.2.3.4 sharedkey /etc/aes1922.key The VPN's, carp, and PF work perfectly fine, but if on say server1 I do a interface em0 down the vpn's die and never come back. Isakmpd runs fine but I do use flag -T on it because of some older fw's that seem not to communicate properly with later fw's without it. Sasyncd is running fine as I have it set to start in rc.conf I am using the same key as I did on 3.9 and failover worked perfectly, of course, fail back didn't work in 3.9 version of sasyncd Anyhow, can anyone offer some advice as I am using the same files (other then change the sasyncd.conf from carp interface carp0 to interface carp0 as it wouldn't load until doing that) I'm rather stumped at the moment (going to do major testing this week on it) so any extra feedback/comments or input on who I can better enable details on the sa transfers the better. Thanks again James
