Actually, you can ignore the "-s1600" request, looks as if someone has
finally made tcpdumps default snap length somewhat bigger... It won't
hurt if you have done it using that option, but it also should no longer
(I have no idea for how long back into the past) be needed.
kre
Date:Thu, 22 Apr 2021 20:50:09 +0200
From:=?UTF-8?Q?J=C3=B6rn_Clausen?=
Message-ID:
| $ ifconfig -a
That all looks OK,
| I have configured the IPv4 part of vioif0 via /etc/ifconfig.vioif0:
Now I'm going to suggest that you (at least temporarily) configure
a
Hello Robert, Andy and everyone!
I hope I address all the questions...
As requested:
$ ifconfig -a
vioif0: flags=0x8843 mtu 1500
ec_capabilities=1
ec_enabled=0
address: 00:16:3e:b3:00:8a
inet 5.2.76.44/24 broadcast 5.2.76.255 flags 0x0
inet6
Date:Thu, 22 Apr 2021 11:06:04 +0200
From:=?UTF-8?Q?J=C3=B6rn_Clausen?=
Message-ID:
| BTW: This is all happening on the actual network interface,
| not the loopback interface.
Yes, I knew that, but the NetBSD network stack uses the loopback
interface for local
On Thu, Apr 22, 2021 at 2:10 AM Jörn Clausen wrote:
>
> Hello Robert!
>
> Thanks for the reply. As you suggested, I tried tcpdump. BTW: This is all
> happening on the actual network interface, not the loopback interface.
Yes but it's still useful to see ifconfig -a output as he asked for in
Hello Robert!
Thanks for the reply. As you suggested, I tried tcpdump. BTW: This is all
happening on the actual network interface, not the loopback interface.
I can see a constant stream of these packets:
10:31:46.504046 IP6 2a04:52c0:101:7b1::.5344 > ff15::efc0:988f.6771: UDP,
length 138
Date:Wed, 21 Apr 2021 22:50:40 +0200
From:=?UTF-8?Q?J=C3=B6rn_Clausen?=
Message-ID:
| I am mostly ignorant to everything IPv6, so I have no clue what that
| message means, and I was not able to find any enlightenment online.
IPv6 link local (and multicast, and