Download raw body.
iked/isakmpd: Explain ikev1 keyword and mention daemon coupling
iked/isakmpd: Explain ikev1 keyword and mention daemon coupling
iked/isakmpd: Explain ikev1 keyword and mention daemon coupling
Hi, On Tue, Nov 10, 2026 at 06:25:24PM +0100, Omar Polo wrote: > hshoexer <hshoexer@yerbouti.franken.de> wrote: > > Hi, > > > > some basic documentation for ikev1 in iked.conf. And mention in > > the isakmpd manpage the "internal" option for coupling with iked. > > > > ok? > > okay op@; just a question below for isakmpd.8 > > > --- a/sbin/isakmpd/isakmpd.8 > > +++ b/sbin/isakmpd/isakmpd.8 > > @@ -271,6 +271,17 @@ With verbose logging > > reports successful completion of phase 1 (Main and Aggressive) and phase 2 > > (Quick) exchanges (Information and Transaction exchanges do not generate any > > additional status information). > > +.It Fl Fl iked-mode > > +Run as the IKEv1 process of > > +.Xr iked 8 . > > +This flag is used internally by > > +.Xr iked 8 , > > +which starts > > +.Nm > > +with its own command line following the flag and talks to it over > > +.Xr imsg_init 3 > > +channels. > > +It is not meant to be used directly. > > two questions: > > 1. do we really need to document this knob? > afaik, we have a few of this thingy around the tree but usually > they're not documented, or at least that's my impression. good point, thank! That knob is internal; iked also has some for setup from proc.c (eg. -I). I'll just commit the iked.conf.5 change. > 2. in case it really needs to be documented, I think there's a small > mandoc issue and instead of the double Fl it wants a single -, i.e.: > > -.It Fl Fl iked-mode > +.It Fl -iked-mode > > > Thanks, > Omar Polo
iked/isakmpd: Explain ikev1 keyword and mention daemon coupling
iked/isakmpd: Explain ikev1 keyword and mention daemon coupling
iked/isakmpd: Explain ikev1 keyword and mention daemon coupling