[lkml]   [2003]   [Dec]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: IPtables hang system when loading over 254 IP Addresses
On Mon, Dec 08, 2003 at 05:18:10PM -0700, Russell Elik Rademacher wrote:
> Hello linux-kernel,

Hi Russell!

> I was wondering if anyone have fixed or knew the slightly broken
> issue about loading the IPTables with Ingress/Egress filtering on
> 254 IP addresses or more? It basically locks up the system in
> networking level but everything else works fine.

The netfilter/iptables project has seperate mailinglists, and/or
are the ones you might want to contact

> Basically, if you knew about the script, APF Firewall script, I uses
> it and it make extensive uses of the IPTables to make complex
> firewall rules. But when it reaches to around 254, it just locks up
> the network system, rendering the server unaccessible. It make
> extensive uses of Ingress/Egress and I only seen it locks up when I
> make use of Egress filtering. Ingress works fine up to 400 IP
> addresses and I haven't pushed it that far past it to see how far it
> can go. But Egress, it locks it up, when combined with Ingress.
> Dunno about Egress itself in general. So...anyone might have a clue
> on this?

Maybe you should then talk to the "APF Firewall Script" author. We are
not aware of any iptables-related issues with as little as 254 rules.

- Harald Welte <>
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[unhandled content-type:application/pgp-signature]
 \ /
  Last update: 2005-03-22 13:59    [W:0.029 / U:7.884 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site