On Tue, 2018-03-27 at 12:44 -0700, Tom Eastep wrote: > > I've asked the maintainer of Foobar Linux, a RHEL-based distribution, > for details. He found a neighbor discovery cleanup patch from way > back > in 2014 that solved the problem for him.
Do we have a copy of this patch or know where it is hiding? > The problem symptoms vary, > depending on the NIC and how protocols are stacked (bond, vlan, > etc.). Yuck. > Also, some cases only show up when Shorewall Multi-ISP is configured. I do have Multi-ISP configured. > I experienced the problem on Debian 8 for a while. Did you do anything specific to resolve it or did it just go away with a regular kernel upgrade? > One user who had the problem recently, found that specifying the > upstream router's link-local IP as the gateway (rather than its > global > IP) solved the problem for him. How do you discover the link-local address for the upstream router? This issue makes for a very unstable IPv6 network. Nodes expecting responses to RA requests get in a tizzy when they time out. Part of trying to get upstream support for this problem is going to be that it only exhibits itself when shorewall6[-lite] is running. I guess I am going to have to try to break down my shorewall6 config to see if I can figure out exactly what is tickling it. Cheers, b.
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
