On 2022-Feb-17, at 00:02, Mark Millard wrote:
> On 2022-Feb-16, at 15:18, bob prohaska wrote:
>
>> [changed subject to more clearly reflect the symptoms]
>>
>> On Mon, Feb 14, 2022 at 09:59:23PM -0800, Mark Millard wrote:
>>> Since I have a context working based on the kernel in:
>>>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233683
--- Comment #8 from Paul Webster ---
(In reply to Bjoern A. Zeeb from comment #7)
HOST:
# ifconfig | grep inet6
inet6 2a01:4f8:190:1183::1:1 prefixlen 64
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopei
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233683
Bjoern A. Zeeb changed:
What|Removed |Added
CC||k...@freebsd.org
--- Comment #7 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233683
--- Comment #6 from Paul Webster ---
Also: FreeBSD de1.paulwebster.org 13.0-STABLE FreeBSD 13.0-STABLE #2
stable/13-n249446-6488ea00aba4: Sun Feb 13 07:54:21 CET 2022
r...@de1.paulwebster.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC am
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233683
--- Comment #5 from Paul Webster ---
I forgot sysctl.conf for the host:
root@de1:~ # cat /etc/sysctl.conf
# $FreeBSD$
#
# This file is read when going to multi-user and its contents piped thru
# ``sysctl'' to adjust kernel values. ``man
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233683
--- Comment #4 from Paul Webster ---
Just to further add to the previous post, IPv4 and all other bridging is
operational, I have kept back information I felt irrellevent:
root@sitehost:/var # ping -c 3 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 d
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233683
Paul Webster changed:
What|Removed |Added
CC||paul.g.webster@googlemail.c
