Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 24074

Summary: pulse does not correctly assign netmask or broadcast addresses
Product: [Retired] Red Hat High Availability Server Reporter: Paul Lussier <pll>
Component: piranhaAssignee: Phil Copeland <copeland>
Status: CLOSED DEFERRED QA Contact: Jay Turner <jturner>
Severity: high Docs Contact:
Priority: high    
Version: 1.0CC: ddm, srevivo
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-05-11 21:22:10 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 Red Hat Bugzilla 2001-01-15 22:25:10 UTC 
The pulse code leaves the determination of netmask and broadcast
information up to the ifconfig program, which almost always uses the
wrong values unless the network in question is a natural Class C
network.

For anyone using Class A or Class B network address ranges subnetted
into smaller networks, ifconfig always uses the appropriate classes
natural netmask and determines the broadcast from a combination of the
IP address/netmask.  This results in netmasks of 255.0.0.0 for a class
A network and 255.255.0.0 for a class B network, and broadcasts of
X.255.255.255 and X.Y.255.255 respectively.

What is needed is a mechanism for setting the netmask within lvs.cf
so that the netmask and broadcast can be determined and subsequently
passed as arguments to ifconfig.
Comment 1 Red Hat Bugzilla 2001-01-16 17:11:23 UTC 
Forwarded to Phil for review
Comment 2 Red Hat Bugzilla 2001-05-11 21:22:05 UTC 
This is being worked on. You will be able to specify a network bas on all
virtual IP addresses, the net router, and the real server.