> Do you get any more output if you do "rcctl -f -d start iked"? the output is: doing _rc_parse_conf doing _rc_quirks iked_flags empty, using default >< doing _rc_parse_conf /var/run/rc.d/iked doing _rc_quirks doing rc_check iked doing rc_pre configuration OK
and then the terminal is blocked again > What happens if you press ^T to get status (assuming common > shell setup)? Or if you don't get anything useful there, what > is shown in the WAIT column in top for iked? ("top -g iked" if > you have lots running and need to cut it down) ^T does not do anything (standard installation without further config), top lists 4 processes, one running as root (parent) with "wait" and the other three processes (control, ca, ikev2) with "kqread" in the wait-column. > It might be useful to include your config file (obviously masking > anything sensitive, but try to avoid hiding anything that might be > important..). the exact configuration (does not matter if active or passive): ikev2 "test" active esp \ from 10.85.0.0/24 to 10.86.0.0/24 \ local 10.85.0.2 peer 10.86.0.2 \ psk thisisjustatestpassword sysctl is not touched except: net.inet.ip.forwarding=1 Thanks in advance!