Hi,
On Mon, Feb 05, 2024 at 03:12:01PM +0100, Bo Berglund wrote:
> >> $ openvpn --version
> >> OpenVPN 2.4.12 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL]
> >> [PKCS11]
> >Ah, yes. So that's a bit of an antique :-)
>
> $ apt policy openvpn
> openvpn:
> Installed: 2.4.12-0ubuntu0.20
On Mon, 5 Feb 2024 14:04:38 +0100, Gert Doering wrote:
>Hi,
>
>On Mon, Feb 05, 2024 at 12:25:51PM +0100, Bo Berglund wrote:
>> >How old is your OpenVPN?
>>
>> This is on the Ubuntu 20.04 LTS server:
>>
>> Aug 21 2023:
>>
>> $ openvpn --version
>> OpenVPN 2.4.12 x86_64-pc-linux-gnu [SSL (OpenSS
Hi,
On Mon, Feb 05, 2024 at 12:25:51PM +0100, Bo Berglund wrote:
> > https://community.openvpn.net/openvpn/ticket/719
> >
> >which says that from 2.5.0 on, there should be POSIX timestamps.
> >
> >How old is your OpenVPN?
>
> This is on the Ubuntu 20.04 LTS server:
>
> Aug 21 2023:
>
> $ openv
Bo Berglund wrote:
I mean the logs being produced from these server.conf lines:
status /etc(openvpn/log/openvpn-status.log
log /etc(openvpn/log/openvpn.log
verb 4
Why do you insist on using legacy file based logs? Systemd's journal has
much better options to filter/display log messages.
And
On Mon, 5 Feb 2024 12:15:53 +0100, Marc SCHAEFER wrote:
>On Mon, Feb 05, 2024 at 09:55:58AM +0100, Bo Berglund wrote:
>> I tried the service restart and it worked inasfar as the logs now look like
>> this
>> example:
>>
>> Mon Feb 5 09:42:42 2024 us=734354 succeeded -> ifconfig_pool_set()
>
>D
On Mon, 5 Feb 2024 10:52:22 +0100, Gert Doering wrote:
>Hi,
>
>On Mon, Feb 05, 2024 at 09:55:58AM +0100, Bo Berglund wrote:
>> I really wonder why it uses this terrible illogical display with the day name
>> first?
>>
>> So how can I change it to use the ISO 8601 format?
>
>Well. There's --mach
On Mon, Feb 05, 2024 at 09:55:58AM +0100, Bo Berglund wrote:
> I tried the service restart and it worked inasfar as the logs now look like
> this
> example:
>
> Mon Feb 5 09:42:42 2024 us=734354 succeeded -> ifconfig_pool_set()
Do you mean rsyslog logs?
Again, systemd changes everything: you c
On 04.02.24 16:32, Bo Berglund wrote:
It took a week after revoking him until I could no longer access the site myself
(I live about 6000 km away from the site and rely on OpenVPN for access).
We once apparently had someone think that it'd be "neat and tidy" to
have a root CA cert's validity e
On 05.02.24 09:55, Bo Berglund wrote:
I really wonder why it uses this terrible illogical display with the day name
first?
Because the need for global, *cross-OS* standards for a timestamp format
first arose with BBSes, USENET, E-Mails and the like, and the developers
of those wanted to have
Hi,
On Mon, Feb 05, 2024 at 09:55:58AM +0100, Bo Berglund wrote:
> I really wonder why it uses this terrible illogical display with the day name
> first?
>
> So how can I change it to use the ISO 8601 format?
Well. There's --machine-readable-output, I think, and also
https://community.openvp
Bo Berglund wrote:
I tried the service restart and it worked inasfar as the logs now look like this
example:
Mon Feb 5 09:42:42 2024 us=734354 succeeded -> ifconfig_pool_set()
Now I just need to get it to display as -mm-dd hh:mm:ss so it would be
useful for me.
I really wonder why it uses
On Mon, 5 Feb 2024 09:04:06 +0100, Marc SCHAEFER wrote:
>Hello,
>
>On Mon, Feb 05, 2024 at 12:06:13AM +0100, Bo Berglund wrote:
>> restart the specific services or do I have to restart the server computer
>> itself?
>
>I am no systemd specialist, however, most of the times you change a systemd
>c
Hello,
On Mon, Feb 05, 2024 at 12:06:13AM +0100, Bo Berglund wrote:
> restart the specific services or do I have to restart the server computer
> itself?
I am no systemd specialist, however, most of the times you change a systemd
config file you should do:
systemctl daemon-reload
__
13 matches
Mail list logo
