Bug 63646 - RFE: Add profile support for redhat-config-network
RFE: Add profile support for redhat-config-network
Status: CLOSED DEFERRED
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-network (Show other bugs)
7.2
All Linux
medium Severity medium
: ---
: ---
Assigned To: Trond Eivind Glomsrxd
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-04-16 16:01 EDT by Forrest
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-04-16 16:02:04 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 Forrest 2002-04-16 16:01:59 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.5) Gecko/20011031

Description of problem:
I noticed in the redhat-config-network help section that using
/etc/sysconfig/networking/profiles is not yet implemented.  I just wanted to add
my comments for this component.  I would like to have the ability to create and
switch profiles using redhat-config-network, as well as switching using a
command line--something like:
service network restart home
where home is one of the profiles that I had already setup.

Another enhancement along a similar line is some sort of network probing, so
that when I go from my desk to a conference room on a different subnet (both
using DHCP), it will automatically sense that I am on a different subnet, and it
will restart the network for me.

One other thing pertaining to the network, is there any way to make the network
timeout shorter?  That way it won't wait for several minutes to timeout if the
computer is off the network.  Once autosensing of the network works, it would be
nice to have a very short timeout for the network at boot time, and then it will
start the network as soon as it senses that the network is attached.

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


How reproducible:
Always

Steps to Reproduce:
1.  Start the network
2.
3.
	

Additional info:
Comment 1 Trond Eivind Glomsrxd 2002-04-16 16:04:08 EDT
Try running with "-p" :) - more is in the works, though, including probing, of
some sort
Comment 2 Forrest 2002-04-16 16:18:01 EDT
Is there anything that I can do to help?
Comment 3 Trond Eivind Glomsrxd 2002-04-16 16:27:31 EDT
We'd need testing later, but not yet.

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