Bug 84403 - irc connection tracking module fails with more than 8 ports defined
irc connection tracking module fails with more than 8 ports defined
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: iptables (Show other bugs)
8.0
athlon Linux
medium Severity medium
: ---
: ---
Assigned To: Thomas Woerner
Ben Levenson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-02-15 14:56 EST by Brad Smith
Modified: 2007-04-18 12:51 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-08-16 12:16:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Brad Smith 2003-02-15 14:56:08 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021202

Description of problem:
I inadvertently configured irc connection tracking with more than 8 ports which
in turn caused some very strange system behavior. The first symptom was the lose
of the system mouse. When I rebooted the system, the next symptom was a failure
to boot. The system would hang as it was starting lpd, sendmail and other
services. I could always cntl-alt-del to reboot, but the system would not boot
correctly.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.define more than 8 irc ports in iptables
2.reinitialize iptables
3.reboot
    

Actual Results:  system hang during reboot.

Expected Results:  gracefull failure of the irc connection module should not
have affected any other component of the system

Additional info:


While trying to track down this bug, I ended up buying a new motherboard and CPU
and ddr ram..... Expensive bug. :)
Comment 1 Thomas Woerner 2004-08-16 12:16:46 EDT
Please verify this with a newer version of Red Hat Enterprise Linux or
Fedora Core and reopen it against the new version if it still occurs.

Closing as "not a bug" for now.

Note You need to log in before you can comment on or make changes to this bug.