Releases: iptsh/system_tools
Releases · iptsh/system_tools
system_tools.sh_v2.4
【v2.4】 Fourteenth Edition, fixed three critical errors when creating new ssh and docker ip scripts, including errors in network name retrieval, container name retrieval, and the ipset address set service. The script author has migrated to the new iptsh.com website. Fixed issues with invalid display colors in several details. (2025.05.06 PM)
【v2.4】 第十四版，修复新建 ssh 脚本以及 docker ip 脚本时的三处核心关键错误，分别是网络名称获取的错误、获取容器名称的错误、ipset地址集合服务的错误。脚本作者迁移至新的 iptsh.com 网址。修复几处细节的显示颜色无效问题。（2025.05.06午）
system_tools.sh_v2.3
【v2.3】 Thirteenth Edition, Removed the code for displaying the IP address set after the initial creation and modification of the SSH rule due to display failure, rendering it invalid. (2025.04.23 PM)
【v2.3】 第十三版，删除首次创建以及修改ssh规则之后显示ip地址集相关的代码，原因是无法显示，属于无效代码。（2025.04.23午）
system_tools.sh_v2.2
【v2.2】 Twelfth Edition, Corrected the error in the script for creating new SSH firewall rules. The original script did not define a drop rule, which constitutes a critical functional flaw. Defining only allow rules without a corresponding drop rule renders the configuration meaningless. (2025.04.21 PM)
【v2.2】 第十二版，修正新建ssh防火墙规则脚本内容错误，原脚本没有定义丢弃规则，这属于严重功能错误，如果仅仅定义允许的规则，将毫无意义。（2025.04.21午）
system_tools.sh_v2.1
【v2.1】 Eleventh Edition, In the new version, both the Nezha monitoring server and the monitored client share the same port. This script updates the method for matching IP address firewall rules while retaining compatibility with both the new and old port matching methods. (2025.04.18 PM)
【v2.1】 第十一版，新版本哪吒监控服务端和被监控端共用相同的端口，本脚本设置的IP地址防火墙规则更新匹配方法，同时保留新旧版本的端口匹配。（2025.04.18午）
system_tools.sh_v2.0
【v2.0】 Tenth Edition, In the latest version of Debian, it is no longer possible to view detailed port NAT forwarding information through POSTROUTING when checking iptables IPv4 Docker NAT rules and ip6tables IPv6 Docker NAT rules. This version adds DOCKER details to display the forwarding information. (2025.04.17 Noon)
【v2.0】 第十版，查看 iptables IPv4 Docker NAT 规则和查看 ip6tables IPv6 Docker NAT 规则，在最新的Debian版本中，无法通过POSTROUTING显示端口NAT转发明细，此版本增加DOCKER明细以显示转发。（2025.04.17午）
system_tools.sh_v1.9
【v1.9】 Ninth Version, This version fixes the issue where the script did not check if ipset was already installed before creating Docker firewall configuration files. It optimizes and changes the terminal interaction logic when managing SSH firewall rules and Docker firewall rules.When a user chooses not to create a configuration file, the script will first check if the configuration file already exists in the system. This approach introduces a validation logic to prevent mistakenly proceeding directly to the file creation step, which may not be the best user experience. Similarly, when the user chooses to modify an existing configuration file, the script will also first check if the corresponding configuration file already exists in the system, applying the same validation logic.In previous versions, the script only checked if the configuration file existed right before actually creating it. Now, this check has been moved up to the interaction inquiry phase. This change ensures that before any configuration file is created, the system confirms the absence of the corresponding configuration file, avoiding any blind file creation. All actions are carried out under a transparent logical environment for the script's sensitive operations. The previous detection step is now converted into corresponding prompt messages.(2024.08.25 Night)
【v1.9】 第九版，修正创建 Docker 防火墙配置文件时，未判断 ipset 是否已经安装的问题，优化以及变更管理 SSH 防火墙规则以及管理 Docker 防火墙和规则时终端交互的逻辑层次，当选择未创建配置时会首先判断系统中是否已经存在配置文件，这是一种质疑逻辑，避免选择失误进而造成直接进入创建配置文件的环节，显然直接进入下一环节并不是最佳的终端交互体验方式，另外，当选择修改相应的配置文件时，也会首先判断系统中是否已经存在对应的配置文件，同样也是质疑性质的逻辑，之前的版本中，在最终创建配置文件的之前才会检测系统是否已经存在配置文件，现在这种检测被提前到交互询问的环节，这一切都时为了在创建任何配置文件之前，都能确保系统中确实没有相应的配置文件，而不是直接盲目的创建任何文件，一切都需要在透明的逻辑环境下进行脚本的敏感操作，至于之前的检测环节，变更为相应的提示语。（2024.08.25夜）
system_tools.sh_v1.8
【v1.8】 Eighth Edition, Changed the container status in Docker container information display to white, in order to avoid visual confusion with container names when the code automatically wraps on mobile clients.Modified the script so that when Docker container information is not retrieved, it displays the character "N/A" to represent missing information, preventing potential misalignment of information columns. (2024.08.23 PM)
【v1.8】 第八版，变更 Docker 容器信息显示的容器状态内容为白色，以避免手机客户端代码自动换行后，视觉上与容器名称不好区分，变更 Docker 容器信息获取的内容为空时，能够显示字符 N/A ，以代表未获取到任何信息，防止可能会造成的信息列的错乱。（2024.08.23午）
system_tools.sh_v1.7
【v1.7】 Seventh Edition, Fixed logical errors in Docker firewall management options.Added a prompt to ask whether to create a configuration file.Added a submenu for common system commands.Added an option to the main menu for displaying Docker container information, which includes container name, network name, IPv4 address, IPv6 address, container status, and port mapping information.Improved the readability and aesthetic presentation of Docker container information display. (2024.08.22 Night)
【v1.7】 第七版，修正 Docker 防火墙管理选项逻辑错误，增加询问是否创建配置文件的判断环节，增加常用系统命令子菜单，主菜单增加显示 Docker 容器信息选项，显示容器名称、容器所在网络名称、IPv4地址、IPv6地址、容器运行状态、容器端口映射信息，优化 Docker 容器信息显示的可读性以及信息输出的美观性。（2024.08.22夜）
system_tools.sh_v1.6
【v1.6】 Sixth Edition, Managed Docker firewall rules.Managed Docker services that support only IPv4 access and those that support both IPv4 and IPv6 access.For services supporting both, the script requires enabling Docker custom networks and configuring IPv6 forwarding and access. The script does not force users to complete these configurations in a specific way, but currently, using the Docker project robbertkl/ipv6nat to achieve IPv6 forwarding and access in Docker networks is a recommended approach, though other methods can also be used.The Docker service firewall management function in this script was the original purpose of creating the script and is considered by the author to be a crucial part of automating Docker maintenance strategies.Two very important tasks: restricting external access to Docker services and enabling IPv6 access for Docker services.(2024.08.21 Noon)
【v1.6】 第六版，管理 Docker 防火墙规则，管理单纯支持 IPv4 访问的 Docker 服务，管理同时支持 IPv4 访问和 IPv6 访问的 Docker 服务，如果是后者，需要开启 Docker 自定义网络，并且配置 IPv6 转发和访问，本脚本不会强制去要求用户如何去完成这些配置，不过就目前来看，通过 Docker 项目 robbertkl/ipv6nat 实现 Docker 网络的 IPv6 转发和访问，是比较推荐的做法，当然也可以采取别的方法。这个脚本的 Docker 服务防火墙管理功能，其实也是作者制作这个脚本的最初目的，同时也是作者认为非常有必要实现脚本化的 Docker 维护策略。两个非常重要的事情，一个是限制外界对 Docker 搭建服务的访问，另一个是实现 Docker 服务的 IPv6 访问。（2024.08.21午）
system_tools.sh_v1.5
