Bug 1398337

Summary:	dnsmasq lacks ra-param option
Product:	Red Hat Enterprise Linux 7	Reporter:	Neil Wilson <neil>
Component:	dnsmasq	Assignee:	Petr Menšík <pemensik>
Status:	CLOSED ERRATA	QA Contact:	Jan Ščotka <jscotka>
Severity:	medium	Docs Contact:	Ioanna Gkioka <igkioka>
Priority:	medium
Version:	7.2	CC:	psklenar, thozza, vdanek
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	dnsmasq-2.76-1.el7	Doc Type:	Enhancement
Doc Text:	_Dnsmasq_ now supports the ra-param option With this update, dnsmasq can change the default values of IPv6 Router Advertisement. As a result, the "ra-param" option is used to change the default priorities and time intervals of routes advertised by dnsmasq. See the dnsmasq(1) man page for more information.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 22:56:41 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:
Bug Depends On:	1375527
Bug Blocks:	1393869

Description Neil Wilson 2016-11-24 13:30:27 UTC

Description of problem:

dnsmasq lacks the ra-param option


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

Name        : dnsmasq
Arch        : x86_64
Version     : 2.66
Release     : 14.el7_2.1


Additional info:

The version of dnsmasq in RHEL7 lacks the ra-param option available in version 2.67 and above - which means that dnsmasq can't be used as a full replacement for radvd.

The particular use case here is when routers switch over and you want to lower the route priority/lifetime of one vs. the other.

Comment 10 errata-xmlrpc 2017-08-01 22:56:41 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2117