Dear iptables Team,

I found that iprange match module extension in iptables might not be working in
1.4.7 version. 

I was using the following rule in 1.4.0: 
-A fwd-acl -d 192.168.1.2/32 -i eth1 -p tcp -m iprange --src-range
10.0.0.1-10.0.0.2 -m tcp --sport 1024:65535 --dport 8585 -m state --state NEW
-j ACCEPT

Now I upgrade to 1.4.7 and found that altough this rule is accepted without an
error, what is in fact taking place is (rules were reloaded with
iptables-restore):

-A fwd-acl -d 192.168.1.2/32 -i eth1 -p tcp -m iprange --src-range
0.0.0.0-0.0.0.0 -m tcp --sport 1024:65535 --dport 8585 -m state --state NEW -j
ACCEPT

Thanks in advance.

After some additional testing, I have found that this only happens with a
somewhat old linux kernel version. I've tested iptables 1.4.0, 1.4.4, 1.4.5,
1.4.6 and 1.4.7 with linux kernel 2.6.20 (CONFIG_IP_NF_MATCH_IPRANGE) and linux
kernel 2.6.30 (CONFIG_NETFILTER_XT_MATCH_IPRANGE).
With linux kernel version 2.6.20, iprange works correctly up to and including
iptables version 1.4.5. iptables 1.4.6 and 1.4.7 failed to set iprange.
With linux kernel version 2.6.30 iprange works correctly from iptables 1.4.0 to
1.4.7.
So, I'm going to close this bug report.
Thx for your good work.