how to log iptables events
warning level:
iptables -A INPUT -j LOG --log-prefix "BAD_INPUT: " --log-level 4
iptables -A FORWARD -j LOG --log-prefix "BAD_FORWARD: " --log-level 4
iptables -A OUTPUT -j LOG --log-prefix "BAD_OUTPUT: " --log-level 4
commonly used examples
ip6tables -t raw -I PREROUTING -j LOG --log-prefix "prerouting-raw: " --log-level 4 ip6tables -t nat -I PREROUTING -j LOG --log-prefix "prerouting-nat: " --log-level 4 ip6tables -t mangle -I INPUT -j LOG --log-prefix "input-mangle: " --log-level 4 ip6tables -t filter -I INPUT -j LOG --log-prefix "input-filter: " --log-level 4 ip6tables -t mangle -I FORWARD -j LOG --log-prefix "forward-mangle: " --log-level 4 ip6tables -t filter -I OUTPUT -j LOG --log-prefix "output-filter: " --log-level 4 ip6tables -t nat -I POSTROUTING -j LOG --log-prefix "postrouting-nat: " --log-level 4 ip6tables -t mangle -I POSTROUTING -j LOG --log-prefix "postrouting-mangle: " --log-level 4 ip6tables -t mangle -A POSTROUTING -j LOG --log-prefix "postrouting-mangle-end: " --log-level 4
CentOS 7 uses systemd's journald as the default logs system, and with this the kernel logs (like the ones from iptables) are not directed to /var/log/messages
but to journald and should be displayed by passing the -k
(meaning kernel logs) to journalctl like this:
journalctl -k
日志如果太多, 可以清空再跑 (不太靠谱,经常搞死journal)
rm /run/log/journal/* -rf;systemctl restart systemd-journald
还是用这个参数:
-S --since=DATE Show entries not older than the specified date
Ref:
https://unix.stackexchange.com/questions/423778/log-iptables-events-on-centos-7
转载请注明出处 http://www.cnblogs.com/mashuai-191/
【推荐】国内首个AI IDE,深度理解中文开发场景,立即下载体验Trae
【推荐】编程新体验,更懂你的AI,立即体验豆包MarsCode编程助手
【推荐】抖音旗下AI助手豆包,你的智能百科全书,全免费不限次数
【推荐】轻量又高性能的 SSH 工具 IShell:AI 加持,快人一步
· 10年+ .NET Coder 心语 ── 封装的思维:从隐藏、稳定开始理解其本质意义
· 地球OL攻略 —— 某应届生求职总结
· 周边上新:园子的第一款马克杯温暖上架
· Open-Sora 2.0 重磅开源!
· 提示词工程——AI应用必不可少的技术