PR https://github.com/vyos/vyos-1x/pull/3720
set service monitoring telegraf loki url 'http://localhost' set service monitoring telegraf loki metric-name-label 'r123'
PR https://github.com/vyos/vyos-1x/pull/3720
set service monitoring telegraf loki url 'http://localhost' set service monitoring telegraf loki metric-name-label 'r123'
@Vijayakumar This package is deprecated as per https://vyos.dev/T6507
The no-verify options exists
vyos@vyos# set load-balancing reverse-proxy backend bk01 ssl Possible completions: ca-certificate Certificate Authority in PKI configuration no-verify Do not attempt to verify SSL certificates for backend servers
Added in the T6242
Provide a minimal example of configuration (set commands) to reproduce.
Works fine:
set load-balancing reverse-proxy backend bk01 server srv01 address '192.168.122.16' set load-balancing reverse-proxy backend bk01 server srv01 port '22' set load-balancing reverse-proxy service ssh backend 'bk01' set load-balancing reverse-proxy service ssh mode 'tcp' set load-balancing reverse-proxy service ssh port '22' set service ssh disable-host-validation set service ssh port '2222'
@nvollmar Do you want to claim the task?
It will be easy to add; you need to generate a new CLI like with "prometheus-client" for example https://github.com/vyos/vyos-1x/blob/03d8c16a12d182a2fb2ab9f7acec5d8cb83937ba/interface-definitions/service_monitoring_telegraf.xml.in#L188-L250
And add template changes https://github.com/vyos/vyos-1x/blob/03d8c16a12d182a2fb2ab9f7acec5d8cb83937ba/data/templates/telegraf/telegraf.j2#L45-L58
@lclements0 Add a simple set of commands to reproduce.
PR https://github.com/vyos/vyos-1x/pull/3621
set nat cgnat log-allocation set nat cgnat pool external ext-01 external-port-range '1024-65535' set nat cgnat pool external ext-01 per-user-limit port '2000' set nat cgnat pool external ext-01 range 192.168.122.222/32 set nat cgnat pool internal int-01 range '100.64.0.0/28' set nat cgnat rule 10 source pool 'int-01' set nat cgnat rule 10 translation pool 'ext-01'
check logs:
Jun 10 14:10:02 r4 sudo[9057]: vyos : TTY=pts/0 ; PWD=/home/vyos ; USER=root ; COMMAND=/usr/bin/sh -c ' /usr/libexec/vyos/conf_mode/nat_cgnat.py' Jun 10 14:10:02 r4 sudo[9057]: pam_unix(sudo:session): session opened for user root(uid=0) by vyos(uid=1003) Jun 10 14:10:03 r4 cgnat[9059]: Internal host: 100.64.0.0, external host: 192.168.122.222, Port range: 1024-3023 Jun 10 14:10:03 r4 cgnat[9059]: Internal host: 100.64.0.1, external host: 192.168.122.222, Port range: 3024-5023 Jun 10 14:10:03 r4 cgnat[9059]: Internal host: 100.64.0.2, external host: 192.168.122.222, Port range: 5024-7023 Jun 10 14:10:03 r4 cgnat[9059]: Internal host: 100.64.0.3, external host: 192.168.122.222, Port range: 7024-9023 Jun 10 14:10:03 r4 cgnat[9059]: Internal host: 100.64.0.4, external host: 192.168.122.222, Port range: 9024-11023 Jun 10 14:10:03 r4 cgnat[9059]: Internal host: 100.64.0.5, external host: 192.168.122.222, Port range: 11024-13023 Jun 10 14:10:03 r4 cgnat[9059]: Internal host: 100.64.0.6, external host: 192.168.122.222, Port range: 13024-15023 Jun 10 14:10:03 r4 cgnat[9059]: Internal host: 100.64.0.7, external host: 192.168.122.222, Port range: 15024-17023 Jun 10 14:10:03 r4 cgnat[9059]: Internal host: 100.64.0.8, external host: 192.168.122.222, Port range: 17024-19023 Jun 10 14:10:03 r4 cgnat[9059]: Internal host: 100.64.0.9, external host: 192.168.122.222, Port range: 19024-21023 Jun 10 14:10:03 r4 cgnat[9059]: Internal host: 100.64.0.10, external host: 192.168.122.222, Port range: 21024-23023 Jun 10 14:10:03 r4 cgnat[9059]: Internal host: 100.64.0.11, external host: 192.168.122.222, Port range: 23024-25023 Jun 10 14:10:03 r4 cgnat[9059]: Internal host: 100.64.0.12, external host: 192.168.122.222, Port range: 25024-27023 Jun 10 14:10:03 r4 cgnat[9059]: Internal host: 100.64.0.13, external host: 192.168.122.222, Port range: 27024-29023 Jun 10 14:10:03 r4 cgnat[9059]: Internal host: 100.64.0.14, external host: 192.168.122.222, Port range: 29024-31023 Jun 10 14:10:03 r4 cgnat[9059]: Internal host: 100.64.0.15, external host: 192.168.122.222, Port range: 31024-33023 Jun 10 14:10:03 r4 sudo[9057]: pam_unix(sudo:session): session closed for user root
Accel-ppp does not work with VPP
At the meeting, we concluded that tables should not intersect with protocols static table x
This PR was just to make this use case when they intersect and have a more flexible configuration.
Without using the same tables, it makes no sense in this PR.
That's why it was closed
In T6448#191156, @HappyShr00m wrote:I have not used it since I thought it would delete even running instances or stop them. if it doesn't, then may I suggest adding a description to the command to indicate that it will not impact the running containers. thanks
In T6445#191083, @Apachez wrote:Yes but this is what the peer would do on its own - if the opposite device is lost in connectivity it can rollback to previous config which is enabled by default (that is history of configs).
It will delete all unused images
Did you try this command, as the command does not work?
@talmakion Good catch! Thanks for contributing!
In T6445#191034, @Apachez wrote:This can be handled just like "how others does it" as in if the peer is lost after a sync then the peer will automatically return to previous config.
Swap/change/hide config entries are not implemented.
It is not a bug but a feature request.
The config-sync is not a HA.
I don't think config-sync should save, reboot, or do something else.
Imagine if, due to config-sync, you lose access to the secondary node and if it was saved by config-sync.
If you add this config after the server is configured, it works as it requires a restart of the service
sudo systemctl restart accel-ppp@pppoe.service
Or reconfigure the service again
@L0crian Some TC combinations are affected by locks, so they are impossible to use with, for example, /16 networks.
Add the set of commands to reproduce.
Should be fixed in T6373
Duplicate