Bug 1475762

Summary: malformed address in route printed by 'ip route list' for RTN_MULTICAST type and AF_INET family
Product: Red Hat Enterprise Linux 7 Reporter: Stefano Brivio <sbrivio>
Component: iprouteAssignee: Stefano Brivio <sbrivio>
Status: CLOSED ERRATA QA Contact: Jaroslav Aster <jaster>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.4-AltCC: atragler, jaster, jishi, psutter
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: iproute-4.11.0-6.el7 Doc Type: Bug Fix
Doc Text:
Cause: Due to insufficient checks IPv4 multicast route addresses were incorrectly treated as IPv6 ones. Consequence: Listing IPv4 multicast routes showed malformed addresses. Fix: Affected code has been corrected. Result: Listing IPv4 multicast routes now correctly shows IPv4 addresses.
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 14:31:17 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:
Attachments:
Description Flags
Patch as submitted to maintainer none

Description Stefano Brivio 2017-07-27 09:33:56 UTC
Found in CI test run at:

    https://beaker.engineering.redhat.com/jobs/1973898

in test:

	Task: (Fail) /kernel/networking/route/route_func - STANDALONE, TEST_TYPE=netns, TEST_TOPO=default, ROUTE_MODE=local
	test: (Fail) Route-Selector-netns-default-local

---

Add a IPv4 multicast route:
    ip -4 route add multicast 172.111.1.1 dev veth1 table main

and list it:
    ip -4 route list type multicast table main

we get:
    multicast ac6f:101:800:400:400:0:3c00:0 dev veth1 scope link

instead of the expected:
    multicast 172.111.1.1 dev veth1 scope link

Comment 2 Stefano Brivio 2017-07-27 20:00:48 UTC
Created attachment 1305641 [details]
Patch as submitted to maintainer

Comment 3 Phil Sutter 2017-09-07 17:34:27 UTC
Postponing this to RHEL-7.5.

Comment 8 errata-xmlrpc 2018-04-10 14:31:17 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/RHEA-2018:0815