Bug 7438
Summary: | Network disconnects | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Viktor Steinmann <viktor.steinmann> |
Component: | kernel | Assignee: | Michael K. Johnson <johnsonm> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-08-08 17:39:42 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Viktor Steinmann
1999-11-30 10:25:44 UTC
Assigned to dledford I'm getting this problem almost exactly, except it's version 6.2. (Hmmmm, I wonder if it's the same thing? Maybe I should post a new bug...) The difference is that the server's keyboard is not physically accessable to me, as it is co-located. Here's the trick: if I log into one of the other co-located machines at the same site, I can then ssh from that box to the screwed-up box over the LAN! Then if I type "ping <machine on internet>" the network connection is restored for a few minutes, until it disappears again. My temporary fix is to have "ping yahoo.com > /dev/null &" running at all times. The first report looks like the a known problem with the intel stuff that should be mostly fixed in 2.2.16 but not 100% of cases. Please try the update kernel and let m eknow The second is the classic misconfigured bridge (probably 3com) which is not set to broadcast frames to an unknown mac address but instead drop them. Believed fixed in 6.2 errata kernel. Other problem appears to be non Linux Hi. I have same problem with network on a RedHat 6.0 2.2.5-22. Sometimes networks disconnects misteriously, and i have to reboot the machine..... With new 2.2.16-3 upgrade the problem was fixed? |