Going back to the OP, here's a postmortem on exactly what happened:
In short, we had unknowingly downgraded from 64 bit to 32 bit during an
upgrade. It's covered here:
https://doc.pfsense.org/index.php/Upgrade_Guide#Avoiding_Unintended_Architecture_Change
Interestingly, it worked like this:
how about disabling pfs?
Eero
2017-02-03 13:25 GMT+02:00 Roland Giesler :
> On Fri, Feb 3, 2017 at 1:19 PM, Eero Volotinen
> wrote:
>
>> It's a bit antique selection of ciphers.
>>
>
> It is indeed. We were experimenting for a long time with
On Fri, Feb 3, 2017 at 1:19 PM, Eero Volotinen
wrote:
> It's a bit antique selection of ciphers.
>
It is indeed. We were experimenting for a long time with many others and
got similar result (no matches). So I opted to check what pfSense offers
and set Sonicwall to ask
It's a bit antique selection of ciphers.
Problem is in DH group. try enabling same DH also in pfsense.
--
Eero
2017-02-03 13:17 GMT+02:00 Roland Giesler :
> On Tue, Jan 24, 2017 at 8:16 PM, Eero Volotinen
> wrote:
>
>> What hardware is other
On Tue, Jan 24, 2017 at 8:16 PM, Eero Volotinen
wrote:
> What hardware is other side running? Why you are trying to use 3des?
>
The other side is Sonicwall. I'm using 3DES because it's enabled by
default and seeming a simple place to start.
However, regardless of what
On Tue, Jan 24, 2017 at 9:56 PM, Jim Thompson wrote:
> On Tue, Jan 24, 2017 at 12:16 PM, Eero Volotinen
> wrote:
> > What hardware is other side running? Why you are trying to use 3des?
> >
> > Eero
> >
> > 2017-01-17 16:36 GMT+02:00 Roland Giesler