Bug 116328

Summary: /bin/ipcalc --prefix 203.3.43.087 255.255.255.224 ipcalc: bad ip address 203.3.43.087
Product: [Retired] Red Hat Linux Reporter: Geoff Horner <geoffrey.horner>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 9CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-02-20 03:34:23 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 Geoff Horner 2004-02-20 03:14:14 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET 
CLR 1.1.4322)

Description of problem:
This fails :-
/bin/ipcalc --prefix 203.3.43.087 255.255.255.224 
responding with :-
ipcalc: bad ip address 203.3.43.087

This works :-
/bin/ipcalc --prefix 203.3.43.87 255.255.255.224
response :-
PREFIX=27

Other addresses with a leading 0 in the 4th octet don't fail
eg :-
/bin/ipcalc --prefix 203.3.43.055 255.255.255.224 
works.



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

How reproducible:
Always

Steps to Reproduce:
1./bin/ipcalc --prefix 203.3.43.087 255.255.255.224 
2.
3.
    

Actual Results:  ipcalc: bad ip address 203.3.43.087

Expected Results:  PREFIX=27

Additional info:

This problem caused probelms with redhat-config-network where I 
couldn't activate an ethernet device.

Comment 1 Bill Nottingham 2004-02-20 03:34:23 UTC
Octets of the form '0xx' are interpreted as octal, as the standard
specifies.

Hence, in an octal number, you can't have the digit 8.