Am Mittwoch, 4. November 2015, 04:40:51 schrieb Eric Dumazet: > On Wed, 2015-11-04 at 13:19 +0100, Wolfgang Walter wrote: > > Today I found a problem: on a router forwarding GRE-packets (ipv4) (it is > > not the endpount) the interface (intel igb) stops sending packets after > > some time. I think this happens when an ISATAP packet is inside the > > GRE-packet.> > > gre packets arrives on eth0 > > eth1 stops sending (receiving still works) > > ethtool -r eth1 > > eth1 works again for some time > > > > Switching GRO off on eth0 "fixes" the problem. > > > > I didn't test vanilla 4.1.12 yet, though. Until today 4.1.11 has been > > running on the router. What I tested was your patch > > > > "gre_gso_segment() chokes if SIT frames were aggregated by GRO engine." > > > > but did not solve the problem. > > > > So I would not recommend to backport it to longterm 4.1. > > > > My plans are: > > > > * test vanilla 4.1.12 > > * test 4.3 > > > > I want to test 4.3 on another router first, though. > > If the NIC stops sending packets after some time, it might be an igb > issue.
Yes, maybe igb has a problem sending a gro-packet if it is an isatap in gre. igb has no problem sending gro-packets which are pure isatap or which are ipv4 (tcp/udp) in gre with 4.1.12 + these patches. And it had no problem with 4.1.11 with isatap in gre. Disabling gso for the interface does help. I'll test pure 4.1.12 soon. Regards, -- Wolfgang Walter Studentenwerk München Anstalt des öffentlichen Rechts -- 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
