On 05/02/2024 13:38, Mathias Jeschke wrote:
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
On 05/02/2024 15:12, Bo Berglund wrote:
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
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 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
__
On Sat, 27 Jan 2024 13:38:37 +0100, Marc SCHAEFER wrote:
>Debian supports conffiles: they are handled specially, changes from maintainer
>are presented to the sysadmin at package upgrade or installation time
>(conffiles can stay even if you remove a package, if you don't --purge it) and
>you can
Hello,
On Sat, Jan 27, 2024 at 01:06:15PM +0100, Jochen Bern wrote:
> (Note that, back when I had to try to get rid of the parameterless
> "--daemon" in the unit file, I found that the unit file would get
> overwritten with every update - unlike "normal" config files, where a new
> packaged versio
On 27.01.24 10:37, Bo Berglund wrote:
It seems like there is a global conf file somewhere which is used by all
instances of the openvpn service, but I am confused by the various statements on
how to edit this file.
Please:
Exactly where is this file? ( /path/to/conffile )
If I may put words in
On Sat, 27 Jan 2024 09:45:10 +0100, Bo Berglund wrote:
>On Mon, 22 Jan 2024 12:27:52 +0100, Gert Doering wrote:
>
>>Hi,
>>
>>On Mon, Jan 22, 2024 at 11:27:41AM +0100, Jochen Bern wrote:
>>> .02) OpenVPN prioritizes command line parameters over statements in config
>>> files on the theory that so
On Mon, 22 Jan 2024 12:27:52 +0100, Gert Doering wrote:
>Hi,
>
>On Mon, Jan 22, 2024 at 11:27:41AM +0100, Jochen Bern wrote:
>> .02) OpenVPN prioritizes command line parameters over statements in config
>> files on the theory that someone probably typed them in for *this*
>> particular execution
Hi,
On Mon, Jan 22, 2024 at 11:27:41AM +0100, Jochen Bern wrote:
> .02) OpenVPN prioritizes command line parameters over statements in config
> files on the theory that someone probably typed them in for *this*
> particular execution of the openvpn binary
It doesn't. It depends on ordering
op
On 21.01.24 21:08, Bo Berglund wrote:
Inside the [systemd unit file for] openvpn server [...] this item is defined:
--suppress-timestamps
This means that *all* server instances will get this set even though it is not
in the instance's own conf file!
Now I wonder if there is anything at all one
On Sun, 21 Jan 2024 21:59:01 +, tincantech via Openvpn-users
wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA256
>
>Hi,
>
>On Sunday, January 21st, 2024 at 9:17 PM, Gert Doering
>wrote:
>
>> Hi,
>>
>> On Sun, Jan 21, 2024 at 09:08:01PM +0100, Bo Berglund wrote:
>>
>> > Now I wonder i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
On Sunday, January 21st, 2024 at 9:17 PM, Gert Doering
wrote:
> Hi,
>
> On Sun, Jan 21, 2024 at 09:08:01PM +0100, Bo Berglund wrote:
>
> > Now I wonder if there is anything at all one can do on a server instance
> > level
> > to disable th
Hi,
On Sun, Jan 21, 2024 at 09:08:01PM +0100, Bo Berglund wrote:
> Now I wonder if there is anything at all one can do on a server instance level
> to disable that setting such that the timestamps are returned to the logfiles?
> Like:
> "reset suppress-timestamps"
> or similar?
OpenVPN does not a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Sent with Proton Mail secure email.
On Sunday, January 21st, 2024 at 8:08 PM, Bo Berglund
wrote:
> This is a discussion that started in another unrelated thread titled:
> "Two questions about key generation for clients"
> but which does not
25 matches
Mail list logo
