From e31b664f2c36cd8e66677cb073c863eb77eec2a8 Mon Sep 17 00:00:00 2001
From: kostichs <45223018+kostichs@users.noreply.github.com>
Date: Tue, 14 Jan 2025 14:23:24 +0500
Subject: [PATCH] Update about-bare-metal-servers.md

---
 .../about-bare-metal-servers.md               | 20 +++++++++++++++++++
 1 file changed, 20 insertions(+)

diff --git a/documentation/cloud/bare-metal-servers/about-bare-metal-servers.md b/documentation/cloud/bare-metal-servers/about-bare-metal-servers.md
index 0b8d5b69..cd0c670d 100644
--- a/documentation/cloud/bare-metal-servers/about-bare-metal-servers.md
+++ b/documentation/cloud/bare-metal-servers/about-bare-metal-servers.md
@@ -113,3 +113,23 @@ The table below shows the key differences between our Bare Metal servers in <a h
 | Interaction with other Cloud services | Yes                                                                                                                                                                                                                                                    | No                                                                                                   |
 | Interaction with other Gcore services | Yes                                                                                                                                                                                                                                                    | No                                                                                                   |
 | Usability                             | Complex infrastructure, intensive workloads, possible traffic spikes, networks between Virtual and Bare Metal servers, interaction with other Cloud services (Load Balancers, Managed Kubernetes), internal virtualization and containers | Small- and medium-sized projects, simple web applications, predictable workloads, low budget |
+
+
+## ## Firewall feature not supported for Bare Metal servers
+
+Please note that the Firewall feature is not supported for Bare Metal servers. Unlike Virtual Machines or other cloud services that can easily integrate with cloud-native firewalls, Bare Metal servers operate directly on physical hardware and are not subject to the same level of firewall management.
+
+For network security, Bare Metal servers can use the following alternatives:
+*   You can manually configure network security using solutions like **iptables** or **nftables** (recommended) to protect your server at the network level. Other similar solutions can also be used to set up necessary firewall rules based on your security needs.
+
+```
+sudo iptables -A INPUT -p tcp --dport 22 -j ACCEPT
+sudo iptables -A INPUT -p tcp --dport 80 -j ACCEPT
+sudo iptables -A INPUT -p tcp --dport 443 -j ACCEPT
+sudo iptables -A INPUT -i lo -j ACCEPT
+sudo iptables -P INPUT DROP
+```
+
+*   For an additional layer of protection, opt for [Gcore DDoS Protection]([url](https://gcore.com/ddos-protection)) to keep your server available during attacks. DDoS Protection redirects traffic to the Threat Mitigation System (TMS), which performs filtering and threat detection, preventing service disruptions with its always-on mode.
+
+For more information, please [reach out to our support team]([url](https://gcore.com/contact-us)) for tailored DDoS Protection plans.