Description of problem:
ifcfg-eth0-range0 does not inherit network mask from parent config
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.configure ifcfg-eth0 with desired netmask (in my case 255.255.255.224)
2.configure ifcfg-eth0-range0 with no netmask entry
Netmask from parent config ignored (resulting netmask 255.255.255.0)
Netmask from parent config inherited (in my case 255.255.255.224)
This seemed to work OK on the 7.x series. The documentation within
ifup-aliases also specifically states that "Range files also inherit
configuration from the ifcfg-$DEV file just like normal."
This is a result of the problem described in bug 65415. You can work
around it by making sure that the range filenames match the egrep -v
that's shown in that bug (and thus are excluded from the list of
interfaces); for example, you can name them "-range:0" rather than
just "-range0", since a colon is one of the exception strings listed
in the egrep -v.
Bill Nottingham closed bug 65415, and in response to a query I sent
him regarding RHEL3, he replied: "It's fixed on the RHEL branch as
well, should be in the next scheduled update (update 4)." Bill, feel
free to add any more info...for example, it would be useful to know
approximately when RHEL3 update 4 is expected to be released.
U4 came out some time ago :-)
Yes, this should be fixed in 7.31.18.EL-1.