MMCT TEAM
Server IP : 128.199.20.84  /  Your IP : 108.162.216.158
Web Server : Apache/2.4.41 (Ubuntu)
System : Linux competent-maruti 5.4.0-128-generic #144-Ubuntu SMP Tue Sep 20 11:00:04 UTC 2022 x86_64
User : www-data ( 33)
PHP Version : 8.0.20
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,pcntl_unshare,
MySQL : OFF  |  cURL : ON  |  WGET : ON  |  Perl : ON  |  Python : OFF
Directory (0755) :  /usr/share/doc/iptables/

[  Home  ][  C0mmand  ][  Upload File  ]

Current File : //usr/share/doc/iptables/INCOMPATIBILITIES
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.

MMCT - 2023