On Sep 26, 2016, at 2:26 PM, Infoomatic wrote:
>> 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
>
> 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
On 2016-09-26, Infoomatic wrote:
>> On Mon, Sep 26, 2016 at 02:17:35PM +0200, Infoomatic wrote:
>> > also, the already running endpoint did not receive any packets.
>>
>> Nobody on this list can run ifconfig, route, and tcpdump on *your* box
>> to figure out where you're losing packets...
>
> thi
> On Mon, Sep 26, 2016 at 02:17:35PM +0200, Infoomatic wrote:
> > also, the already running endpoint did not receive any packets.
>
> Nobody on this list can run ifconfig, route, and tcpdump on *your* box
> to figure out where you're losing packets...
this is not a connectivity issue.
To clarify:
On Mon, Sep 26, 2016 at 02:17:35PM +0200, Infoomatic wrote:
> also, the already running endpoint did not receive any packets.
Nobody on this list can run ifconfig, route, and tcpdump on *your* box
to figure out where you're losing packets...
> On Mon, Sep 26, 2016 at 01:56:20PM +0200, Infoomatic wrote:
> > ipsec=YES in rc.conf.local does not change anything, and appending
> > "ikelifetime 60" to iked.conf neither.
>
> ipsec=YES and /etc/ipsec.conf are for use with isakmpd.
>
> iked does not use ipsec.conf.
that's what I thought, bu
On Mon, Sep 26, 2016 at 01:56:20PM +0200, Infoomatic wrote:
> ipsec=YES in rc.conf.local does not change anything, and appending
> "ikelifetime 60" to iked.conf neither.
ipsec=YES and /etc/ipsec.conf are for use with isakmpd.
iked does not use ipsec.conf.
> I am quite sure this is just a minor
7 matches
Mail list logo