You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/blog/CentOS8-firewalld-tips/index.md
+8-11Lines changed: 8 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,23 +9,20 @@ enableTocContent: false
9
9
tocPosition: outer
10
10
tocLevels: ["h2", "h3", "h4"]
11
11
tags:
12
-
- Firewall
13
-
- Security
14
-
- Sysadmin
15
-
- Troubleshooting
16
-
series:
17
-
-
18
-
categories:
19
-
-
20
-
image:
12
+
- Firewall
13
+
- Security
14
+
- Sysadmin
15
+
- Troubleshooting
21
16
---
22
17
23
18
When configuring firewall rules to be as strict as required, you may have some troubles understanding why something you thought was allowed is, actually, not. And to track down this kind of issues, some logs might help. Here is a small copy-pasta to enable `firewalld` logging.
24
19
25
-
## Enable "*Access Denied*"
20
+
## Enable "_Access Denied_"
26
21
27
22
{{<expand "References">}}
28
-
*[How to enable firewalld logging for denied packets on Linux](https://www.cyberciti.biz/faq/enable-firewalld-logging-for-denied-packets-on-linux/)
23
+
24
+
-[How to enable firewalld logging for denied packets on Linux](https://www.cyberciti.biz/faq/enable-firewalld-logging-for-denied-packets-on-linux/)
25
+
29
26
{{</expand>}}
30
27
31
28
`firewalld` can log events to `rsyslog`, the events journal in most linux distribution. This can be enable either at runtime (that won't persist across service restarts) or by configuration to keep it enabled for longer periods.
0 commit comments