Re: Public IPv6s fail on KVM bridge with "No buffer space available"

2017-05-25 Thread Alarig Le Lay
On mer. 24 mai 12:17:50 2017, William Gathoye wrote: > In this use case, you make the assumption that my gateway is actually > the first one to respond, this is why you select only the first answer > using -c1. But as you can see below, if I remove that argument, several > routers are answering to

Re: Public IPv6s fail on KVM bridge with "No buffer space available"

2017-05-24 Thread Bjoern A. Zeeb
On 24 May 2017, at 10:17, William Gathoye wrote: In this use case, you make the assumption that my gateway is actually the first one to respond, this is why you select only the first answer using -c1. But as you can see below, if I remove that argument, several routers are answering to me (seem

Re: Public IPv6s fail on KVM bridge with "No buffer space available"

2017-05-24 Thread William Gathoye
On 05/22/2017 02:13 PM, Alarig Le Lay wrote: > You can try to ping6 the IPv6 multicast address for all the routers on > the link: > > 14:07 alarig@mew ~ % ping6 -c1 ff02::2%vtnet0 > PING6(56=40+8+8 bytes) fe80::a800:ff:fe93:83a3%vtnet0 --> ff02::2%vtnet0 > 16 bytes from fe80::209%vtnet0, icmp_seq=

Re: Public IPv6s fail on KVM bridge with "No buffer space available"

2017-05-22 Thread Alarig Le Lay
On lun. 22 mai 14:03:54 2017, William Gathoye wrote: > Btw, if I wanted to use link local addresses to communicate with the > provider next hop gateway, how can I know the local link fe80 IPv6 > address of that gateway since my provider (OVH) doesn't disclose it? You can try to ping6 the IPv6 mult

Re: Public IPv6s fail on KVM bridge with "No buffer space available"

2017-05-22 Thread William Gathoye
Thanks all for your answers. Since I'm not subscribed to this list, please make sure I'm in your `To` field when replying. On 05/17/2017 09:45 AM, Andrey V. Elsukov wrote: >> Please note all my GWs are outside of my IP subnets. > > FreeBSD's IPv6 NDP implementation can not find GWs layer 2 addres

Re: Public IPv6s fail on KVM bridge with "No buffer space available"

2017-05-17 Thread Andrey V. Elsukov
On 17.05.2017 00:24, William Gathoye wrote: > Contrary to the other LXC/KVM, the latter cannot ping any IPv6 machines > outside those accessible directly from the bridge. As soon I try to ping > either the gateway of my hypervisor (still in IPv6), or any other far > away IPv6 hosts (e.g. google.com

Re: Public IPv6s fail on KVM bridge with "No buffer space available"

2017-05-16 Thread Alarig Le Lay
On mar. 16 mai 23:24:17 2017, William Gathoye wrote: > The FreeBSD host is configured like this: > > ifconfig vtnet0 /32 > route add -iface vtnet0 > route add default > > ifconfig vtnet0 inet6 prefixlen 64 > route add -inet6 -iface vtnet0 > route add -inet6 default D