Re: [PATCHv2 iproute2] utils: return default family when rtm_family is not RTNL_FAMILY_IPMR/IP6MR

2017-07-27 Thread Stephen Hemminger
On Thu, 27 Jul 2017 12:03:02 +0200 Phil Sutter wrote: > On Thu, Jul 27, 2017 at 05:44:15PM +0800, Hangbin Liu wrote: > > When we get a multicast route, the rtm_type is RTN_MULTICAST, but the > > rtm_family may be AF_INET. If we only check the type with RTNL_FAMILY_IPMR, > > we will

Re: [PATCHv2 iproute2] utils: return default family when rtm_family is not RTNL_FAMILY_IPMR/IP6MR

2017-07-27 Thread Phil Sutter
On Thu, Jul 27, 2017 at 05:44:15PM +0800, Hangbin Liu wrote: > When we get a multicast route, the rtm_type is RTN_MULTICAST, but the > rtm_family may be AF_INET. If we only check the type with RTNL_FAMILY_IPMR, > we will get malformed address. e.g. > > + ip -4 route add multicast 172.111.1.1 dev

[PATCHv2 iproute2] utils: return default family when rtm_family is not RTNL_FAMILY_IPMR/IP6MR

2017-07-27 Thread Hangbin Liu
When we get a multicast route, the rtm_type is RTN_MULTICAST, but the rtm_family may be AF_INET. If we only check the type with RTNL_FAMILY_IPMR, we will get malformed address. e.g. + ip -4 route add multicast 172.111.1.1 dev em1 table main Before fix: + ip route list type multicast table main