On 5/26/15, 2:48 PM, Eric W. Biederman wrote:
Roopa Prabhu <ro...@cumulusnetworks.com> writes:
From: Roopa Prabhu <ro...@cumulusnetworks.com>
This patch fixes incorrect -EINVAL error due to invalid
scope and type for mpls route deletes.
Well this is embarrassing apparently I did not exercise this code path
in iproute.
Looking through my tests the closest I came was:
ip -M route flush table all
iproute2 route modify code does not set protocol/scope/type
for RTM_DELROUTE msgs. mpls code can skip checking for
these too.
I am really not certain that is the case. I expect if you check
you will find that rtm_scope is set to 0 aka RT_SCOPE_UNIVERSE.
For scope I don't much care. The mpls concepts and the ip concepts
don't match. With mpls packets can be sent from anywhere in the
universe to an address that is valid only on one link.
For rtm_type I think we do care. IPv4 and IPv6 are a disaster when it
comes to interfaces for setting up multicast routes, and I don't see any
reason why we would need to replicate that disaster for mpls.
As such I would like rtm_type to actually mean something, as for mpls
the lookup for multicast packets and the lookup for unicast packets is
completely different. Unicast packet addresses are defined by the
receiver, and multicast packet addresses are defined by the sender.
So can we instead fix iproute to set rtm_type == RTN_UNICAST?
At least for mpls.
yes sure. I started with handling this in iproute2. So, i do have an
iproute2 patch for this.
Will post it later today.
thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
