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.
Did you get any response to this query? > He found a neighbor discovery cleanup patch from way back > in 2014 that solved the problem for him. This would be most excellent to get one's hands on. > 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. So to be clear, where the problem is not getting ND responses on the local-LAN side of the shorewall gateway, "specifying the upstream router's link-local IP as the gateway" (where upstream means the Internet side of the shorewall gateway) was a solution? Specifying it as the gateway where though? Shorewall providers file? I typically have "-" as my gateway there for all providers except my HE tunnel. Is the suggestion to use the upstream router's link-local address instead of "-"? For the provider on my eth0.2 interface, the link-local address is fe80::10 given: # ip -6 neigh show dev eth0.2 fe80::10 lladdr 00:c1:b1:60:a4:19 router STALE I don't seem to get anything returning for that command for my pppoe- wan1 interface: # ip -6 neigh show dev pppoe-wan1 # so do I just continue to use "-"? FWIW, I am resurrecting this thread because I have just discovered that this ND "deafness" problem also causes android devices' WiFi connections to flap horribly because of it's IpReachabilityMonitor service. 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
