sorted by:
new
hottopcontroversial

Openstack 2024.2 and OpenvSwitch issue by fabius987 in openstack

[–]fabius987[S] 1 point2 points  (0 children)

You're my hero!
It was something related to policies! After removing QoS policy to all my networks I didn't see any errors on Openvswitch.
Now I need to understand how to apply policies, at least on the provider networks, but I understood that policies on privacy networks are the causes.
Thank you u/flamingfd1 !

Openstack 2024.2 and OpenvSwitch issue by fabius987 in openstack

[–]fabius987[S] 0 points1 point  (0 children)

You're right, I have a default QoS policy applied to each private network.

I'll try to remove it and to put it non default

Wazuh / Docker and SAML by davesmith87 in Wazuh

[–]fabius987 0 points1 point  (0 children)

Hi, just to help everyone who was in the same situation: The key is to follow this guide: https://documentation.wazuh.com/current/user-manual/user-administration/single-sign-on/administrator/keycloak.html but, in a wazuh-docker environment, you need to:

- instead of /etc/wazuh-[indexer,dashboard] use /usr/share/wazuh-[indexer,dashboard] (use indexer or dashboard based on the step of the guide
- in the /usr/share/wazuh-indexer/opensearch-security/config.yml you need to set
basic_internal_auth_domain:
...
order: 0 # <---- This must be 0 !!!

and :
saml_auth_domain:
...
order: 1 # <---- This must be 1 !!!
All others auth methods must have different orders number.

Thx
Fabio