On Tue, Feb 24, 2026 at 03:51:50PM +0100, Renaud Allard wrote: > > > On 2/24/26 2:14 PM, Matthieu Herrb wrote: > > > Just to be sure, did you start/create vlan4 after neighbot was launched? > > > > > > No it's the main interface for this virtual machine, started at > > boot. It is a vlan interface over a trunk, but I fail to see how it > > would matter here. > > > > Also, I've since gotten messages that an host has moved between its > > IPv4 and IPv6 adresses, which is also pretty wrong on a dual-stack > > host. > > > > So neighbot fails to check my "able to handle IPv6 in a clever way" > > requirement for me so far. > > The bogon issue should be solved in 3.2. > > But I see what you mean about moving from IPv4 to IPv6 and the opposite. It > should be solved in 0.3.3 that I attached here. > > Feel free to report other issues. >
Thanks for the reactivity. with 0.3.3, I still have some 'moved' alerts from an IPv6 routable address to a Link Local one, and some 'moved' alerts from an IPv4 routable address to a IPv6 Link Local one. Also for one misconfigured machine which uses temporary IPv6 addresses I got 'new station' messages for each new temporary address. I don't know if this is by design or not. Our policy is to forbid this kind of obfuscation on that network segment, so I'd rather get a 'moved' notification in this case. -- Matthieu Herrb
