On Fri, May 10, 2019 at 2:46 AM Andrey V. Elsukov wrote:
>
> On 09.05.2019 22:13, Kyle Evans wrote:
> >> there is two IPsec related interfaces that have problem with automatic
> >> loading - if_enc and if_ipsec. So, if you add both to the mapping list,
> >> this will be useful. CAM enc driver has
On 09.05.2019 22:13, Kyle Evans wrote:
>> there is two IPsec related interfaces that have problem with automatic
>> loading - if_enc and if_ipsec. So, if you add both to the mapping list,
>> this will be useful. CAM enc driver has conflicting name and prevents to
>> automatic loading of if_enc(4).
On Thu, May 9, 2019 at 1:43 PM Andrey V. Elsukov wrote:
>
> On 09.05.2019 21:36, Kyle Evans wrote:
> > Any chance the mechanism I introduced for ifconfig mapping ifname <->
> > kld in r347241 would solve the same set of problems this would?
> > (unsure if there are any non-ifconfig(8) problems in
On 09.05.2019 21:36, Kyle Evans wrote:
> Any chance the mechanism I introduced for ifconfig mapping ifname <->
> kld in r347241 would solve the same set of problems this would?
> (unsure if there are any non-ifconfig(8) problems in consideration) If
> we have more consumers of it than just vmnet (f
On Thu, May 9, 2019 at 1:06 PM Andrey V. Elsukov wrote:
>
> Author: ae
> Date: Thu May 9 18:06:11 2019
> New Revision: 347402
> URL: https://svnweb.freebsd.org/changeset/base/347402
>
> Log:
> Add if_ipsec.ko symlink to ipsec.ko kernel module.
>
> This add ability to automatically load ipsec
Author: ae
Date: Thu May 9 18:06:11 2019
New Revision: 347402
URL: https://svnweb.freebsd.org/changeset/base/347402
Log:
Add if_ipsec.ko symlink to ipsec.ko kernel module.
This add ability to automatically load ipsec kernel module, when
if_ipsec(4) virtual interface is created using ifco
