Bug 61275 - networking will not stay active after install on 7.3 Beta 2 (Hampton)
Summary: networking will not stay active after install on 7.3 Beta 2 (Hampton)
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: net-tools (Show other bugs)
(Show other bugs)
Version: 7.3
Hardware: i386 Linux
Target Milestone: ---
Assignee: Phil Knirsch
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2002-03-15 21:02 UTC by Issue Tracker
Modified: 2015-03-05 01:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-06-27 10:19:09 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Issue Tracker 2002-03-15 21:02:02 UTC
Description of Problem:
OS: 7.3 Beta 2 (Hampton) 

Seen so far on 320 and 330e 

Perform complete install w/o configuring networking during install.  After
install, configure nic (in KDE) w/ IP, gateway, start on boot, etc.  Now you
cannot ping network (netowrk is unreachable).  You can configure and up nic from
command line and then you can ping.  When you try to restart networking, the nic
will not restart.  Same result is found after a reboot.

Comment 1 Phil Knirsch 2002-03-18 15:04:16 UTC
Which tool was used for setting up networking? I also need a little more hw

Read ya, Phil

Comment 2 Norm Murray 2002-03-28 22:02:50 UTC
The network configuration tool in KDE was used to configure networking
(K>System>Network configuration). and as for the server details it was a stock
DL320 1.13ghz, 128mb ram, D05 9/10/01rom, ATA model w/ no extra cards installed.

Comment 3 Phil Knirsch 2003-05-23 08:28:16 UTC
Do you still see this problem?

If yes, could you attache the /etc/sysconfig/network-scripts/ifcfg-* files here?


Read ya, Phil

Comment 4 Phil Knirsch 2003-06-27 10:19:09 UTC
Closing due to inactivity and unreproducability.

Read ya, Phil

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