Applications such as OSPF and BFD need the original ingress device not
the VRF device; the latter can be derived from the former. To that end
add the skb_iif to inet_skb_parm and set it in ipv4 code after clearing
the skb control buffer similar to IPv6. From there the pktinfo can just
pull it from
Applications such as OSPF and BFD need the original ingress device not
the VRF device; the latter can be derived from the former. To that end
add the skb_iif to inet_skb_parm and set it in ipv4 code after clearing
the skb control buffer similar to IPv6. From there the pktinfo can just
pull it from
Hi,
On Sat, 7 May 2016 08:53:44 -0600 David Ahern wrote:
> >> @@ -1193,7 +1193,12 @@ void ipv4_pktinfo_prepare(const struct sock *sk,
> >> struct sk_buff *skb)
> >> ipv6_sk_rxinfo(sk);
> >>
> >>if (prepare && skb_rtable(skb)) {
> >> - pktinfo->ipi_ifindex = inet_ii
On 5/7/16 2:41 AM, Shmulik Ladkani wrote:
Hi David,
On Fri, 6 May 2016 18:49:41 -0700 David Ahern wrote:
Applications such as OSPF and BFD need the original ingress device not
the VRF device;
Would you consider this true for any IP_PKTINFO users in VRF setups?
yes. I was just giving speci
Hi David,
On Fri, 6 May 2016 18:49:41 -0700 David Ahern wrote:
> Applications such as OSPF and BFD need the original ingress device not
> the VRF device;
Would you consider this true for any IP_PKTINFO users in VRF setups?
> @@ -1193,7 +1193,12 @@ void ipv4_pktinfo_prepare(const struct sock *s
Applications such as OSPF and BFD need the original ingress device not
the VRF device; the latter can be derived from the former. To that end
add the skb_iif to inet_skb_parm and set it in ipv4 code after clearing
the skb control buffer similar to IPv6. From there the pktinfo can just
pull it from
Applications such as OSPF and BFD need the original ingress device not
the VRF device; the latter can be derived from the former. To that end
add the skb_iif to inet_skb_parm and set it in ipv4 code after clearing
the skb control buffer similar to IPv6. From there the pktinfo can just
pull it from
