Re: Current AMD64 IPv6 broken

2016-09-22 Thread Heiko Zimmermann
I asked my Provider (Hetzner), this is the Gateway Router, Stuart is right. I want to help to solve the bug, I could provide an ssh access. Am 22.09.2016 um 11:01 schrieb Stuart Henderson: > It's a Juniper so probably the upstream router. > > $ maclookup 78:fe:3d:46:ed:9d > 78:fe:3d:46:ed:9d

Re: Current AMD64 IPv6 broken

2016-09-22 Thread Stuart Henderson
It's a Juniper so probably the upstream router. $ maclookup 78:fe:3d:46:ed:9d 78:fe:3d:46:ed:9d (Juniper Networks) On 22 September 2016 08:54:47 Martin Pieuchot wrote: On 21/09/16(Wed) 23:24, Heiko Zimmermann wrote: Hello Martin, the Infos you wanted: 176.9.157.65

Re: Current AMD64 IPv6 broken

2016-09-21 Thread Heiko Zimmermann
Hello Martin, the Infos you wanted: 176.9.157.65 78:fe:3d:46:ed:9dre0 4m54s ## # sysctl net.inet6.icmp6.nd6_debug=1 net.inet6.icmp6.nd6_debug: 0 -> 1 # route -n show -inet6 Routing tables Internet6:

Re: Current AMD64 IPv6 broken

2016-09-21 Thread Martin Pieuchot
On 21/09/16(Wed) 13:32, Heiko Zimmermann wrote: > Hello Martin, > > here are the requested outputs. > Thank you in advance. Who is '78:fe:3d:46:ed:9d' You can crank net.inet6.icmp6.nd6_debug to see if you get more information about why it can be resolved in -current. > > Heiko > > >

Re: Current AMD64 IPv6 broken

2016-09-21 Thread Martin Pieuchot
On 20/09/16(Tue) 19:17, Heiko Zimmermann wrote: > Hello Martin. > > I updated cvs. ipv6 from and to external is broken. > internal ping6 is ok. > > I stept back 5 days, but all the same. I built a 6.0 stable kernel and > bootet again, there is all ok. (to be sure that is not the Provider and >

Re: Current AMD64 IPv6 broken

2016-09-21 Thread Martin Pieuchot
On 20/09/16(Tue) 14:05, David Hill wrote: > Hello - > > So, I have kinda seen this for a little while but haven't had time to > debug. Sorry but there's no evidence that you're talking about the same problem. Your problem seem related to router advertisement. But you didn't include the

Re: Current AMD64 IPv6 broken

2016-09-20 Thread David Hill
Hello - So, I have kinda seen this for a little while but haven't had time to debug. A way I can reproduce this. I have a laptop with iwn0 and bge0, with trunk0 $ cat /etc/hostname.trunk0 trunkport bge0 trunkport iwn0 trunkproto failover up inet6 autoconfprivacy inet6 autoconf dhcp My router