On Wed, Nov 11, 2015 at 6:47 AM, Or Gerlitz <ogerl...@mellanox.com> wrote: > Hi Joe/Jesse, > > We've noticed that VXLAN decap rules set by OVS in the below trivial VXLAN > config contain full match on TTL=64 for the outer headers, can you explain > the reasoning behind it? is that justa typo in dumping the flow?
Looking at the code, this does indeed seem to be the case. To the best of my knowledge, there was no particular reasoning behind it - it simply was never an issue so the wildcard generation wasn't improved. > I also noticed that on my systems (upstream kernel 4.3.0-rc6+, veth > emulating a VM network 192.168.52/24 and host network 192.168.31/24, ovs > user-space 2.3.2) something is broken in the encap rule reporting, traffic > goes fine (below) That is pretty strange, I have never seen that before. It seems that the key to be set is being reported as UNSPEC, which is weird if traffic is flowing normally. I guess you could try a newer version of userspace but I'm not aware of any patches that went in that would have fixed a bug in this area. -- 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
