Bug 984857 - complete server isolation; can ping, but cannot telnet; Only by a directly connected local terminal.
Summary: complete server isolation; can ping, but cannot telnet; Only by a directly co...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: iptables
Version: 5.5
Hardware: athlon
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Thomas Woerner
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-16 08:12 UTC by John
Modified: 2013-08-01 12:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-01 12:46:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description John 2013-07-16 08:12:11 UTC
Description of problem:
There was a complete server isolation (in the network). Ping was there but telnet was not working and there were no indications of slowdown or any of the other normal identifiers that something was about to fail.

Version-Release number of selected component (if applicable):
RHEL 5.x
Linux localhost.localdomain 2.6.9-78.ELsmp 
i686 athlon i386 GNU/Linux

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
I am not a linux expert (Unix is OK) I was not able to clearly determine what was happening. But as a guess, the ip stack was down but the NIC still retains it's ip configuration, so ping works but nothing else. Looking for a reason of isolation and how can such isolations can be avoided? /var/log/messages attached.

Comment 1 Kamil Dudka 2013-07-16 11:20:47 UTC
I cannot see any connection to the acl package.  I suspect your firewall is improperly configured.  I am switching the component to iptables...

Comment 2 John 2013-07-16 12:33:27 UTC
Does connection with ACL package is a MUST?
This has anything to do with the Server Isolation.
I am looking for the reason of server isolation. Please let me know what other logs are required?

Thanks

Comment 3 John 2013-07-18 06:21:51 UTC
The Bug is more or less related to 491432.

Bug No. 984857 can be closed.

Comment 4 Thomas Woerner 2013-08-01 12:46:22 UTC
Closing as NOT A BUG due to comment 3.


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