Skip to contentSkip to conversation

IPtables hang system when loading over 254 IP Addresses

DISCUSSION Russell "Elik" Rademacher 2 participants 2 messages Dec 9, 2003 – Dec 11, 2003

lore
Share & tools
lore
#0 lore raw

Hello linux-kernel,

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.

Reason I asking is that I have quite a few servers with 256 to 300 IP addresses on it, which is mainly for the SSL or anonymous access. So..don't flame me for the gross IP misallocation on single server. :)

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?

This is on 2.4.x series kernel.

Signature · 3 lines
Best regards,
Russell "Elik" Rademacher
Freelance Remote System Adminstrator/Tech Support    
#1 lore raw
Quoted 1 line · Russell Elik Rademacher

Hello linux-kernel,

Hi Russell!

Quoted 5 lines

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, [email protected] and/or [email protected] are the ones you might want to contact
(http://netfilter.org/contact.html).

Quoted 10 lines

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.

Signature · 5 lines
- Harald Welte <[email protected]>             http://www.netfilter.org/
============================================================================
  "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