Package: iptables
Version: 1.3.3-1bpo1
Severity: important

Dear Maintainer,

Today I stumbled upon this stupifying bug with chain name lengths. 

It seems like the maximum chain name would be 30 characters. While shortening 
the chain name however, iptables would 
happily create a chain with a name that is 29 or 30 characters long, it would 
list the chain with iptables -L, but 
would fail to find the chain when I target it with -j. 28 characters works fine.

Please find a short self-explanatory script attached.

Regards,

Allard Hoeve


> [EMAIL PROTECTED] ~ # ~allard/iptables.lengthbug
> 
> Trying this_chain_name_is_32_chars_long, which is 32 characters long
> + iptables -t nat -N this_chain_name_is_32_chars_long
> iptables v1.3.3: chain name `this_chain_name_is_32_chars_long' too long (must 
> be under 30 chars)
> Try `iptables -h' or 'iptables --help' for more information.
> + set +x
> 
> Trying this_chain_name_is_30_longgggg, which is 30 characters long
> + iptables -t nat -N this_chain_name_is_30_longgggg
> + iptables -t nat -A POSTROUTING -j this_chain_name_is_30_longgggg
> iptables: No chain/target/match by that name
> + set +x
> 
> Trying this_chain_name_is_29_longggg, which is 29 characters long
> + iptables -t nat -N this_chain_name_is_29_longggg
> + iptables -t nat -A POSTROUTING -j this_chain_name_is_29_longggg
> iptables: No chain/target/match by that name
> + set +x
> 
> Trying this_chain_name_is_28_longgg, which is 28 characters long
> + iptables -t nat -N this_chain_name_is_28_longgg
> + iptables -t nat -A POSTROUTING -j this_chain_name_is_28_longgg
> + set +x
> [EMAIL PROTECTED] ~ # 




-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.17.7-fwsh-byte
Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF8)

Versions of packages iptables depends on:
ii  libc6                 2.3.2.ds1-22sarge6 GNU C Library: Shared libraries an

-- no debconf information

Attachment: iptables.lengthbug
Description: application/shellscript

Reply via email to