- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Sep 9 2024
Sep 2 2024
Aug 31 2024
Aug 30 2024
Aug 26 2024
Aug 23 2024
Only worked:
- Reboot instance
- load /config/config.boot
- sudo podman rm suricata
- commit
Then it works
vyos@VyOS-Test01#
[edit]
vyos@VyOS-Test01# load /config/config.boot
[edit]
vyos@VyOS-Test01#
[edit]
vyos@VyOS-Test01# compare
+ container {
+ name suricata {
+ allow-host-networks
+ arguments "-q 1"
+ capability "net-admin"
+ capability "sys-admin"
+ capability "sys-nice"
+ image "jasonish/suricata:6.0.14"
+ memory "1024"
+ volume ETC {
+ destination "/etc/suricata"
+ source "/config/suricata/etc"
+ }
+ volume LOGS {
+ destination "/var/log/suricata"
+ source "/config/suricata/logs"
+ }
+ volume RULES {
+ destination "/var/lib/suricata/rules/"
+ source "/config/suricata/rules"
+ }
+ }
+ }If service is 'failed' state
vyos@VyOS-Test01:~$ systemctl status vyos-container-suricata.service
× vyos-container-suricata.service - VyOS Container suricata
Loaded: loaded (/run/systemd/system/vyos-container-suricata.service; static)
Active: failed (Result: exit-code) since Fri 2024-08-23 10:32:44 UTC; 43s ago
Duration: 4min 55.702s
Process: 2855 ExecStartPre=/bin/rm -f /run/vyos-container-suricata.service.pid /run/vyos-container-suricata.service.cid (code=exited, sta>
Process: 2856 ExecStart=/usr/bin/podman run --conmon-pidfile /run/vyos-container-suricata.service.pid --cidfile /run/vyos-container-suric>
Process: 2867 ExecStopPost=/usr/bin/podman rm --ignore -f --cidfile /run/vyos-container-suricata.service.cid (code=exited, status=0/SUCCE>
Process: 2873 ExecStopPost=/bin/rm -f /run/vyos-container-suricata.service.cid (code=exited, status=0/SUCCESS)
CPU: 129msIn T6673#198344, @a.hajiyev wrote:You are right there is an op-mode command to restart the container
restart container suricataBut I think there needs to be some checks/changes at least someone will execute the native Podman command to restart the container.
You are right there is an op-mode command to restart the container
restart container suricata
But I think there needs to be some checks/changes at least someone will execute the native Podman command to restart the container.
It fails because you do it in the wrong way
Aug 22 2024
PR https://github.com/vyos/vyos-1x/pull/4003
vyos@r14:~$ show ntp
.- Number of sample points in measurement set.
/ .- Number of residual runs with same sign.
| / .- Length of measurement set (time).
| | / .- Est. clock freq error (ppm).
| | | / .- Est. error in freq.
| | | | / .- Est. offset.
| | | | | | On the -.
| | | | | | samples. \
| | | | | | |
Name/IP Address NP NR Span Frequency Freq Skew Offset Std Dev
==============================================================================
ec2-34-206-168-146.compu> 31 15 70m +0.225 0.056 +1295us 112us
ec2-18-193-41-138.eu-cen> 31 13 70m -0.305 0.070 -968us 119us
ec2-122-248-201-177.ap-s> 6 3 52m -2.587 0.901 +109us 252us
vyos@r14:~$Aug 21 2024
Aug 15 2024
Aug 14 2024
Aug 12 2024
Aug 10 2024
Aug 6 2024
@Arc771 thanks for mentioning this, i now will close it
Aug 1 2024
Jul 26 2024
Jul 18 2024
Jul 15 2024
Jul 14 2024
pre-auth stage of the negotiation does not populate the Device, IPv4, _TX, and _RX values yet, that's why the command fails: the raw array doesn't contain these variables yet.
Jul 12 2024
@Viacheslav, Thank you for the hint. After further analysis, these are the findings from the tests done in the lab running 1.4.0 version on both sides with server/client setup.
Jul 11 2024
In T6545#194997, @SrividyaA wrote:@Viacheslav, For site-to-site or server/client mode, when used cipher option as none then also issue is noticed. When you commit, it gives this warning:
vyos@vyos# set int openvpn vtun1 encryption cipher none [edit] vyos@vyos# commit Warning: "encryption none" was specified! No encryption will be performed and data is transmitted in plain text over the network!Logs:
Jul 10 14:51:39 openvpn-vtun1[12357]: Cipher NONE not supported
Jul 10 2024
@Viacheslav, For site-to-site or server/client mode, when used cipher option as none then also issue is noticed. When you commit, it gives this warning:
Jul 8 2024
Jul 7 2024
Jul 4 2024
@SrividyaA what cipher should be selected instead if none is removed and migrated away?
@SrividyaA Does it work for site-to-site ciphers option?
Jul 3 2024
The critical issue was addressed in T5520, and the matter avoided with the move to revised image tools. No more to do on this at this point, and will close.
Jul 2 2024
Jun 28 2024
The correct pass options without "
set interfaces openvpn vtun20 encryption ncp-ciphers 'aes256' set interfaces openvpn vtun20 hash 'sha512' set interfaces openvpn vtun20 mode 'server' set interfaces openvpn vtun20 openvpn-option 'push keepalive 1 10' set interfaces openvpn vtun20 server subnet '10.10.2.0/24' set interfaces openvpn vtun20 server topology 'subnet' set interfaces openvpn vtun20 tls ca-certificate 'ca' set interfaces openvpn vtun20 tls certificate 'cert' set interfaces openvpn vtun20 tls dh-params 'dh'
Jun 27 2024
Which exectly config it generates?
Based on this code should work https://github.com/vyos/vyos-1x/blob/b3b1d59d86af510c454da446f013b514389f5c7f/src/conf_mode/interfaces_openvpn.py#L683
Jun 25 2024
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'
Jun 21 2024
@Viacheslav Fabse started working on it and I did have a look at the changes last week.
Jun 18 2024
Jun 13 2024
I tend to say that this is not necessary and very dangerous. These modules can easily destroy the VyOS filesystem when used improperly.
Jun 12 2024
I would have put it on my list. @Fabse if you get stuck or need some support just slack me.
Sure @Viacheslav! I'll try to add the PR. Also thanks for the documentation @nvollmar :)
@nvollmar Do you want to claim the task?
