On Saturday October 15 2016 19:44, you wrote to Markus Reschke:
JD> Here is what I get with ping. I tried both ::1 and ::2
The ::2 you tried is not assigned to any interface.
JD> C:\Windows\system32>ping 2001:470:71:bf5::1
JD> Pinging 2001:470:71:bf5::1 with 32 bytes of data: JD> Reply from 2001:470:71:bf5::1: time=196ms JD> Reply from 2001:470:71:bf5::1: time=196ms JD> Reply from 2001:470:71:bf5::1: time=196ms JD> Reply from 2001:470:71:bf5::1: time=196ms
That is the address of his fido machine.
There are also 2001:470:70:bf5::1 and 2001:470:70:bf5::2. Note the '70' instead of the '71' in the third position. Those two addresses are the end points of his he.net tunnel. They both ping from here as well now. Since his tunnel does not end on his router, but on his fidonet system, his binkp server may also answer on the address of his tunnel end point.
His setup is a bit unusual. Most have the tunnel terminate on their router, so that IPv6 traffic can be routed to all devices on the LAN.
Andrew, why do you not have the tunnel terminate on your router? Does your router not support 6in4 tunneling?
