On Tue, Apr 7, 2015, at 20:56, Tom Herbert wrote:
> On Tue, Apr 7, 2015 at 8:45 AM, Hannes Frederic Sowa
> <hannes@xxxxxxxxxxxxxxxxxxx> wrote:
> >> > --- a/net/ipv6/ip6_tunnel.c
> >> > +++ b/net/ipv6/ip6_tunnel.c
> >> > @@ -1100,7 +1100,7 @@ static int ip6_tnl_xmit2(struct sk_buff *skb,
> >> > ipv6h->nexthdr = proto;
> >> > ipv6h->saddr = fl6->saddr;
> >> > ipv6h->daddr = fl6->daddr;
> >> > - ip6tunnel_xmit(skb, dev);
> >> > + ip6tunnel_xmit(NULL, skb, dev);
> >>
> >> By same should logic iptunnel_xmit call in ip_tunnel_xmit should take
> >> NULL arg for socket?
> >
> > Sure!
> >
> Actually, for consistency amongst all the IP encapsulation protocols
> and given Dave's comments on how this is supposed to work, maybe for
> the v4 and v6 tunnels we could have a raw AF_INET{6} socket opened for
> all the tunnels to use when ip_tunnel_xmit is called. If it makes a
> difference for UDP encapsulation, a UDP socket could also be opened.
Yes, agreed.
Currently the semantics seem fine to me. vxlan needs this because it is
communicating via multicast addresses and thus we depend on correct
mc_loop behaviour. Which other tunnel protocols could be affected by
this, too?
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
