Bug 1031217

Summary:	UCARP not abiding by --nomcast flag
Product:	[Fedora] Fedora EPEL	Reporter:	Aaron Russo <arusso>
Component:	ucarp	Assignee:	Gwyn Ciesla <gwync>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	el6	CC:	ask, gwync
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-30 15:00:40 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Aaron Russo 2013-11-15 22:39:01 UTC

Description of problem:

The ucarp binary provides a flag, '--nomcast' which is supposed to prevent ucarp from using multicast and instead use broadcast.

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

ucarp-1.5.2-8.el6

How reproducible:
Easily

Steps to Reproduce:
1. Setup a VIP configuration, passing --nomcast to the ucarp binary
2. start the ucarp service
3. start tcpdump with the following filter 'multicast and host 224.0.0.18'

Actual results:
Packets are seen being sent to the Multicast address 224.0.0.18 (VRRP)

Expected results:
Packets should be sent via the broadcast address instead of via multicast according to the 'ucarp --help'

Comment 1 Ben Cotton 2020-11-05 16:50:52 UTC

This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged  change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.

Comment 2 Ben Cotton 2020-11-30 15:00:40 UTC

EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
EPEL please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.