From b1be87bff618a1375fc70c8057e1b39e539cb78c Mon Sep 17 00:00:00 2001 From: Jan Siwiec <jan.siwiec@vsb.cz> Date: Thu, 30 Mar 2023 09:46:25 +0200 Subject: [PATCH] proofread --- .../openstack/docs/additional-information/security-groups.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/topics/compute/openstack/docs/additional-information/security-groups.md b/topics/compute/openstack/docs/additional-information/security-groups.md index 0d3f1fb2..bc6b5e33 100644 --- a/topics/compute/openstack/docs/additional-information/security-groups.md +++ b/topics/compute/openstack/docs/additional-information/security-groups.md @@ -9,7 +9,7 @@ search: Security groups are a collection of security rules that are applied on specific VM. -Security rules in OpenStack serve as a Firewall. They are applied directly on VM ports and therefore proper configuration is necessary. Ingress as well as egress rules can be configured using Horizon and CLI. If you can't connect via ssh or ping your instance, chances are it is because of security rules. +Security rules in OpenStack serve as a Firewall. They are applied directly on VM ports and therefore proper configuration is necessary. Ingress as well as egress rules can be configured using Horizon and CLI. If you can't connect via SSH or ping your instance, chances are it is because of security rules. If you delete default egress rules, your virtual machine will not be able to send outgoing communication. To fix this, add a new egress rule with *any* IP protocol and port range, set Remote IP prefix to *0.0.0.0/0* (IPv4) or *::/0* (IPv6). -- GitLab