Nick Upson wrote:
> I can try that out but the permanent solution needs to use the
> existing tls key, as it's also used, without problems, elsewhere and
> we don't want the headache of more key files than necessary
So you're already using the respective key with other openvpn instances?
can you p
can you try to regenerate the tls key file on your pfsense box and then
copy it to your clients? afaik your current key has not been generated on
your pfsense box, right? maybe thats why it says that there is not enough
key material to proceed ..
pfbox # openvpn --genkey --secret /var/etc/openvpn_
cur within 60 seconds"
>
> On 17 April 2010 19:27, i...@unseregedanken.de wrote:
>> Nick,
>>
>> can you please give some feedback?
>>
>> jan
>>
>> i...@unseregedanken.de wrote:
>>> Hi Nick,
>>>
>>> Nick Upso
okay, just let us know when your focus changes.
Nick Upson wrote:
> so far it's not working with tls,I've been concentrating on other
> areas but expect to return to this shortly
>
> On 17 April 2010 19:27, i...@unseregedanken.de wrote:
>> Nick,
>>
&g
Nick,
can you please give some feedback?
jan
i...@unseregedanken.de wrote:
> Hi Nick,
>
> Nick Upson wrote:
>> thanks, I now get
>>
>> openvpn[24699]: Options error: Unrecognized option or missing
>> parameter(s) in /var/etc/openvpn_server0.conf:22: tls_auth (2
Hi Nick,
Nick Upson wrote:
> thanks, I now get
>
> openvpn[24699]: Options error: Unrecognized option or missing
> parameter(s) in /var/etc/openvpn_server0.conf:22: tls_auth (2.0.6)
> when trying to start the server, the key was generated on our
> certificates machine if that makes any difference
Hey Nick,
Nick Upson wrote:
> I'm using 1.2-RELEASE and I'm trying to start using the openvpn
> capability. The problem I'm having is that there seems to be no way to
> use TLS (tls-auth), could someone either confirm that or let me know
> how to enable it please.
you could manually generate a ke
Hi Vinod,
Vinod Nadiadwala wrote:
> i would like to know does pfsense have support for Marvell Yukon
> 88E8057 NIC, as the NIC is not detected durning the installation of
> pfsense ?
just have a look on the hardware compatibility list from the respective
freebsd verison - at the moment the c
