FreeBSD-update has outdated release lifetime data, and is emitting a
false warning that the End-of-Life date for FreeBSD 11.0-RELEASE-p8 is
approaching.
| WARNING: FreeBSD 11.0-RELEASE-p8 is approaching its End-of-Life date.
| It is strongly recommended that you upgrade to a newer
| release within
On 4/4/2017 7:18 AM, Andrey V. Elsukov wrote:
> On 04.04.2017 13:55, Mike Tancsa wrote:
>
> Yes, you need SA for both directions.
>
>> The man page for setkey implies I only need one entry.
>>
>> Also, should the SPI always been the same, or unique ?
>
> SPI is not used by this code, it only nee
On 4/4/2017 7:18 AM, Andrey V. Elsukov wrote:
> On 04.04.2017 13:55, Mike Tancsa wrote:
>>> You have many SAs with the same destination address, it seems to me,
>>> that this should not work with old IPsec code, because it uses SA
>>> lookups using only destination address. So, if you have not the
On 04.04.2017 13:55, Mike Tancsa wrote:
>> You have many SAs with the same destination address, it seems to me,
>> that this should not work with old IPsec code, because it uses SA
>> lookups using only destination address. So, if you have not the same
>> password for each SA, it should not work.
>
On 4/4/2017 2:24 AM, Andrey V. Elsukov wrote:
> On 04.04.2017 00:39, Mike Tancsa wrote:
> It seems you have encrypted your config, because I don't see IP with 128
> octets :)
:)
>
> One question, does this even worked before?
> You have many SAs with the same destination address, it seems to m
On 04/03/2017 18:09, Slawa Olhovchenkov wrote:
I am have strange issuse on stable/10:
# devinfo -v
nexus0
apic0
ram0
acpi0
[...]
pcib0 pnpinfo _HID=PNP0A08 _UID=0 at handle=\_SB_.PCI0
pci0
hostb0 pnpinfo vendor=0x8086 device=0xd130 subvendor=0x1014
subdevice=0x03ce class