On Wed, Feb 12, 2020 at 11:45 AM Witold Tosta <witold.to...@gmail.com> wrote: > > In my opinion, the xt_geoip modules from xtables-addons have nothing to do > with your error. I would rather bet on the cooperation of the > e1000e network card driver with the tcpip stack.
No, if you take a look at the link I posted (that particular message, not the rest of the forum topic or related bug report), you will se that the same exact thing occurs on a system without this Intel driver. I now have a system without e1000, but it's still behaving the same way. In fact, it's currently using the bnxt driver. I'm ready to bet that if I use another NIC with a different driver, the same kernel traces will show up. I'm not saying xt_geoip is the culprit. I just need to get it out of the way for now so the kernel isn't tainted. Thanks, Vieri _______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
