> On 5 Aug 2016, at 12:05, Juliusz Chroboczek <[email protected]> > wrote: > >> I would expect to be able to ping the ip address >> (2a02:c7d:1d31:a605::3c/64) on eth2 of (2) from (1). > > On each router, run > > ip6tables -I INPUT -j ACCEPT > ip6tables -I OUTPUT -j ACCEPT > ip6tables -I FORWARD -j ACCEPT > > and try again. (This is not a persistent configuration, it will go away > at next boot). > > — Juliusz
Thanks for the suggestion, but no change. I’ve also tried taking the firewalls down, and looking at the ip6tables -L -v at different points in time to identify dropped or rejected packets - neither DROPped nor REJECTed counts get above 0. So I do have a sane view of how the process should be working: packet received on (2), eth1 (as evidenced by tcpdump results on (2)) should be forwarded to the ip address on eth2 (which it doesn’t as tcpdump on that interface shows no packets) Tim _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
