On 8/20/2015 5:11 PM, [email protected] wrote: > This looks like there's already a problem on my LOCAL-ROUTER, and maybe I'm > looking in the wrong places. > > Just testing different combinations I noticed this from a shell on > LOCAL-ROUTER > > ip -6 addr > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 > inet6 ::1/128 scope host > valid_lft forever preferred_lft forever > 5: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000 > inet6 2600:####:####:4d09::1/64 scope global > valid_lft forever preferred_lft forever > inet6 fe80::dc32:12af:fe11:fcf2/64 scope link > valid_lft forever preferred_lft forever > 8: tun1@NONE: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu > 1500 qlen 100 > inet6 2600:####:####:4dff::2/64 scope global > valid_lft forever preferred_lft forever > > And like before the ping to the REMOTE-SERVER side of the tunnel works > > ping6 -v -c 1 2600:####:####:4dff::1 > PING 2600:####:####:4dff::1(2600:####:####:4dff::1) 56 data > bytes > 64 bytes from 2600:####:####:4dff::1: icmp_seq=1 ttl=64 > time=27.4 ms > > --- 2600:####:####:4dff::1 ping statistics --- > 1 packets transmitted, 1 received, 0% packet loss, time 0ms > rtt min/avg/max/mdev = 27.480/27.480/27.480/0.000 ms > > as long as I don't give it the IP address of the eth1 interface. > > But when I do it doesn't get through, just like from the LAN-PC > > ping6 -v -c 1 -I 2600:####:####:4d09::1 2600:####:####:4dff::1 > PING 2600:####:####:4dff::1(2600:####:####:4dff::1) from > 2600:####:####:4d09::1 : 56 data bytes > > --- 2600:####:####:4dff::1 ping statistics --- > 1 packets transmitted, 0 received, 100% packet loss, time 0ms > > And it also fails on the LOCAL-ROUTER side of the OpenVpn tunnel when I > include the IP address. > > ping6 -v -c 1 -I 2600:####:####:4d09::1 2600:####:####:4dff::2 > PING 2600:####:####:4dff::2(2600:####:####:4dff::2) from > 2600:####:####:4d09::1 : 56 data bytes > 64 bytes from 2600:####:####:4dff::2: icmp_seq=1 ttl=64 > time=0.154 ms > > --- 2600:####:####:4dff::2 ping statistics --- > 1 packets transmitted, 1 received, 0% packet loss, time 0ms > rtt min/avg/max/mdev = 0.154/0.154/0.154/0.000 ms > > It's acting like there's a broken connection between the network the LAN is > on (2600:####:####:4d09::/64) and the network the OpenVPN tunnel is on > (2600:####:####:4dff::/64). > > Is that something related to 'neighbor discovery'? >
John, Why don't you simply get your own IPv6 tunnel from he.net? That's what the majority of Shorewall Users have done. -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
