Re: Error when IPRANGE used on 2.4 Kernel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I agree with the stupid IP part...it was just for the mail. I did try
quite a few IP addresses.

But on the comment about it not being part of 2.4. I assumed that
iprange is patched when I received the following message:
Error: iprange: Bad IP Address ..... Pretty sure it entered
libipt_iprange: parse_iprange function.

-Karthik

On Thu, Nov 6, 2008 at 8:24 PM, Sven-Haegar Koch <haegar@xxxxxxxxx> wrote:
> On Thu, 6 Nov 2008, Karthik V wrote:
>
>> I am faced with a weird error for IPTABLES version 1.2.9 on 2.4
>> kernel. The following command:
>>
>> iptables -A INPUT -m iprange --src-range 192.168.0.0-192.168.0.0 -j ACCEPT
>>
>> - fails on 2.4 Kernel with Error: No chain/target/match by that name.
>>
>> - But the same command is working on other systems with 2.6 kernel
>> viz., Fedora Core 6 Desktop and OpenWRT router.
>
> I think kernel 2.4 just does not support -m iprange at all, unless you
> patched it to your kernel tree yourself.
>
> Also the range '192.168.0.0-192.168.0.0' looks quite stupid to me, as
> this is just one address.
>
> c'ya
> sven
>
> --
>
> The Internet treats censorship as a routing problem, and routes around
> it. (John Gilmore on http://www.cygnus.com/~gnu/)
>



-- 

Bill Vaughan  - "The tax collector must love poor people, he's
creating so many of them."
--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux