User Details
- User Since
- Apr 17 2024, 11:00 AM (43 w, 6 d)
Mon, Jan 27
@Viacheslav I'd suggest to reopen this issue.
Jan 4 2025
Jan 2 2025
Dec 31 2024
Dec 24 2024
Dec 20 2024
Dec 18 2024
Dec 17 2024
Dec 16 2024
Dec 15 2024
Blackbox exporter requires a config file for modules that should be used (for example ping over IPv4 or IPv6, DNS for A or AAAA).
This feature is missing documentation: https://docs.vyos.io/en/latest/configuration/service/monitoring.html
Dec 12 2024
Dec 11 2024
Dec 9 2024
Dec 1 2024
Nov 19 2024
Nov 18 2024
Yes, I linked the article for background why the MTU setting is helpful, this applies to Podman as well as Docker.
Nov 17 2024
Nov 13 2024
Oct 22 2024
Oct 21 2024
In July Podman was upgraded from 4.3 (debian package) to 4.9 (custom built package)
Oct 14 2024
@Viacheslav I think this can be closed, I'm not aware of open issues regarding this.
will you add podman exporter as well?
Oct 1 2024
I got the drivers and vyos image built.
One thing I noticed some of the tools require mft to also be installed (https://network.nvidia.com/products/adapter-software/firmware-tools/).
Sep 24 2024
@Viacheslav I can try testing this on my test bench as I have a couple of spare ConnectX 4/5 to play around. Is this in 1.5 rolling?
Sep 20 2024
This task has been completed with https://github.com/vyos/vyos-documentation/pull/1548
Sep 17 2024
Sep 16 2024
Sep 12 2024
Sep 11 2024
Sep 6 2024
Aug 27 2024
Aug 6 2024
Thanks for verifying. Interesting, is it also using the custom Podman package?
Verified on my 1.4 install the policy.json is present, but missing in the latest rolling release
Aug 5 2024
Jun 21 2024
@Viacheslav Fabse started working on it and I did have a look at the changes last week.
Jun 12 2024
I would have put it on my list. @Fabse if you get stuck or need some support just slack me.
Relevant telegraf documentation: https://github.com/influxdata/telegraf/blob/release-1.31/plugins/outputs/loki/README.md
Jun 10 2024
Jun 9 2024
Jun 8 2024
Created a PR with a fix
Added an example how to reproduce it
Currently I'm not sure, might be related to changes from T4519
May 28 2024
May 27 2024
May 17 2024
May 16 2024
IMO it would make sense to show the DUID since that has to be passed for static mappings and is also configured on the client side
May 6 2024
Ok, that makes sense. Still need to place the tag.
May 4 2024
The format I started playing with looks like this:
set system config-management commit-archive 1 username 'xxx' set system config-management commit-archive 1 password 'xxx' set system config-management commit-archive 1 scheme 'scp' set system config-management commit-archive 1 location '192.0.2.1/backup'
I already looked a bit into it. What complicates it is the old location is a multi and one can add a list of locations.
May 1 2024
Thanks for the hints, that makes sense. Let's see how that can be implemented :)
Proposal:
set system config-management commit-archive uri "stor01z-cs.int.trae32566.org/cr01b-vyos" set system config-management commit-archive scheme "sftp" set system config-management commit-archive username "cr01b" set system config-management commit-archive password "$T3$TP@$$W0^%"
We could improve it by breaking up configuration, having the user providing a URI, Protocol and optional username/password as separate values.
Then we can properly encode username/password. This would also give more flexibility how username/password are handled and passed on.
In both cases it is kind of an user error, the password would have to be properly url encoded if provided in one (@ should be %40 in an URI, a ! should be %21).