Bug 77082 - Not able to configure the 'scope' of an address assigned to an interface
Not able to configure the 'scope' of an address assigned to an interface
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
8.0
All Linux
low Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-10-31 17:13 EST by Iustin Pop
Modified: 2014-03-16 22:32 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-10-31 17:14:05 EST
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 Iustin Pop 2002-10-31 17:13:57 EST
Description of Problem:
The /sbin/ifup script which activates and configures network devices in RedHat
Linux is forcing the 'scope' property of addresses added to devices to 'host'
for the loopback device and to default (global) for all other devices.

It would be useful to be able to customize the scope field, since this allow a
finer selection of source addresses of network connection from the machine
(among others).

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

Simple diff -u:
--- ifup.orig   2002-11-01 00:09:49.000000000 +0200
+++ ifup        2002-11-01 00:14:29.000000000 +0200
@@ -235,7 +235,7 @@
     if [ "${DEVICE}" = "lo" ]; then
        SCOPE="scope host"
     else
-        SCOPE=
+        SCOPE=${SCOPE:-}
     fi

     if [ -n "$SRCADDR" ]; then
Comment 1 Bill Nottingham 2002-11-11 23:58:57 EST
Added in CVS, will be in 6.96-1 or later.

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