> Victor Sudakov wrote:
> > Dear Colleagues,
> >
> > Why could it be that a FreeBSD 12.2 host does not reply to ICMPv6
> > Neighbor Solicitations from the router?
>
> Any ideas please?
Thank you for pointing this out.
I do have an similar effect, after upgrading, and you point me to a good
direct
On 4 Jan 2021, at 14:17, Lutz Donnerhacke wrote:
Victor Sudakov wrote:
Dear Colleagues,
Why could it be that a FreeBSD 12.2 host does not reply to ICMPv6
Neighbor Solicitations from the router?
Any ideas please?
Thank you for pointing this out.
I do have an similar effect, after upgrading,
> I’d start by checking netstat -s -p icmp6 and netstat -s -p ip6 for
> any suspicious counter updates.
Great idea. It points me tot he most stupid error I could make.
Instead of
ifconfig_lagg140_aliases="inet6 2a01:75c0:1000:140::/64 anycast"
I wrote
ifconfig_vlan140_aliases="inet6 2a01:75
Paul Mather wrote:
> Why could it be that a FreeBSD 12.2 host does not reply to ICMPv6
> Neighbor Solicitations from the router?
[dd]
> >
> > $ ifconfig re1
> > re1: flags=8843 metric 0 mtu 1500
> >
> > options=8209b
> >ether c4:12:f5:33:c9:7c
> >inet 192.168.17
Lutz Donnerhacke wrote:
> > Victor Sudakov wrote:
> > > Dear Colleagues,
> > >
> > > Why could it be that a FreeBSD 12.2 host does not reply to ICMPv6
> > > Neighbor Solicitations from the router?
> >
> > Any ideas please?
>
> Thank you for pointing this out.
> I do have an similar effect, after
Hello. I wrote a simple daemon called ZeroDNS which provides functionality
similar to multicast DNS, namely it discovers other participating machines
over the LAN and stores their hostname and IPv4 address pairs.
Here is a NSS module which allows the system to use information from that
daemon:
htt
