On Fri, 16 Jan 2015, Jamie Landeg-Jones wrote: > Bernhard Fröhlich <decke_at_bluelife.at> wrote: > > I don't know what's unusual with the DO virtualisation, but vultr just > works like a normal server (though they do restrict to virtio devices > where applicable rather than emulated harware) They use Avahi for autodisovery of the IPv4 "link layer" address to further boostrap the configuration. Unfortuately avahi-autoipd seems to needs lots of dependencies, including gobject-introspection. bsd-cloudinit is written in Python and they use it to get a proper IPv4 addresses. This configuration gets sucked into rc. On Fri, 16 Jan 2015, Nikolay Denev wrote: > On Fri, Jan 16, 2015 at 7:13 AM, Lyndon Nerenberg <lyndon_at_orthanc.ca> wrote: > > > Beware that they (DO) do not at all grok ipv6. They hand out /124s, or > > something equally silly. > > > > My DO instance has /64 and I have no problems with using ipv6 to login. It's /64 formally here, but I am told only to use 16 (sixteen) addresses xxxx:2000 ... xxxx:200f Sounds like neighbour discovery scalability issues? //MarcinReceived on Fri Jan 16 2015 - 08:38:45 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:54 UTC