The following reply was made to PR port-vax/58002; it has been noted by GNATS.
From: "Fege, Marc Daniel" <marc.fege%uni-bonn.de@localhost>
To: gnats-bugs%netbsd.org@localhost, port-vax-maintainer%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
Cc:
Subject: Re: port-vax/58002: NetBSD-VAX network stack or drivers broken since NetBSD 10?
Date: Wed, 6 Mar 2024 16:15:31 +0100
--b1=_carnOWI32t2ojiKliBQwWt2kut4EQPbGUOHIupdQE
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Hello Jonathan,
many thanks for your quick reply!
All of those MAC or IPv6 addresses in the presented logs were masked
by me for privacy reasons, if that is it, what you mean. The emulated
hardware MAC is recognised by the OS/drivers as it should be as it did
with NetBSD 9 before. Thus were the IPv6 addresses calculated ind
given accordingly. Even the site-local 'fd00:....' and global
'2003:...' addresses could be obtained somehow.
However: now neither IPv6 traffic is possible through that device,
even if being able automatically set appropriate IPv6 addresses to
that port. Nor is it even possible to set the preset IPv4 address to
the network device "de0" at boot. Should I do so manually with
"ifconfig 10.0.0.90 255.255.255.0" after logon, ifconfig set it so as
requested, but no traffic will be transmitted through the port.
Neither IPv6, nor IPv4. Not even pings.
What I miss in checking the ethernet port with a simple "ifconfig"
command within the emulated/guest NetBSD-10 machine are some lines in
ifconfig's output such as the following that I have for my NetBSD 9
host machine, where the emulated port is connected to and which works
fine as desired. That could be a hint:
"
media: Ethernet autoselect (1000baseT full-duplex)
status: active
"
Neither of those are present since the change from NetBSD 9.3 to
NetBSD 10RC5 of the guest. It seems to be, that the driver is unable
to determin the used medium and thus does not recognize the medium as
"active.
– Marc.
Am Mittwoch, den 06.03.2024 um 15:10 schrieb Jonathan A. Kollasch:
The following reply was made to PR port-vax/58002; it has been noted
by GNATS.
From: "Jonathan A. Kollasch"
To: gnats-bugs%netbsd.org@localhost
Cc:
Subject: Re: port-vax/58002: NetBSD-VAX network stack or drivers
broken since
NetBSD 10?
Date: Wed, 6 Mar 2024 08:04:58 -0600
It looks like you have a layer 2 multicast address in place of a layer
2 unicast
MAC address. Can you try again with say fe:ff:ff:ff:ff:ff
instead? Or
is this real hardware?
--b1=_carnOWI32t2ojiKliBQwWt2kut4EQPbGUOHIupdQE
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<style type=3D"text/css" id=3D"groupoffice-email-style">
/*
* Convert transparent color to hex value by given background
*/
h6 {
font-size: 11px;
line-height: 14px;
font-weight: bold;
color: rgba(0, 0, 0, 0.64);
}
h4 {
font-size: 14px;
line-height: 21px;
letter-spacing: 0.4px;
color: rgba(0, 0, 0, 0.87);
font-weight: normal;
}
h5 {
font-size: 12px;
color: rgba(0, 0, 0, 0.64);
font-weight: normal;
}
h3 {
font-size: 16px;
line-height: 21px;
font-weight: normal;
letter-spacing: 0.6px;
color: black;
}
h2 {
font-size: 21px;
line-height: 28px;
font-weight: normal;
letter-spacing: 0.6px;
color: black;
}
h1 {
font-size: 30px;
line-height: 35px;
font-weight: normal;
letter-spacing: 0.6px;
color: black;
}
body, p, span, div {
font-family: Helvetica, Arial, sans-serif;
font-size: 14px;
color: rgba(0, 0, 0, 0.87);
font-weight: normal;
line-height: 21px;
}
code {
border: 1px solid rgba(0, 0, 0, 0.12);
background-color: #fafafa;
padding: 7px;
margin: 14px 0;
display: block;
font-family: "Courier New", Courier, monospace;
color: black;
border-radius: 3.5px;
}
p {
margin: 0;
}
ul {
display: block;
list-style-type: disc;
list-style-position: outside;
margin: 0;
padding: 0 0 0 2em;
}
ol {
display: block;
list-style-type: decimal;
list-style-position: outside;
margin: 0;
padding: 0 0 0 2em;
}
ol > ol {
list-style-type: lower-alpha;
}
ol > ol > ol {
list-style-type: lower-roman;
}
@media (max-device-width: 1200px) {
/*
* Convert transparent color to hex value by given background
*/
h6 {
font-size: 13px;
line-height: 16px;
}
h4 {
font-size: 16px;
line-height: 24px;
}
h5 {
font-size: 14px;
}
h3 {
font-size: 18px;
line-height: 24px;
}
h2 {
font-size: 27px;
line-height: 32px;
}
h1 {
font-size: 24px;
line-height: 40px;
}
body, p, span, div {
font-size: 16px;
}
code {
padding: 8px;
margin: 16px 0;
display: block;
border-radius: 4px;
}
}
</style>
</head>
<body><div>Hello Jonathan,</div><div><br></div><div>many thanks for your qu=
ick reply!<br></div><div><br></div><div>All of those MAC or IPv6 addresses =
in the presented logs were masked by me for privacy reasons, if that is it,=
what you mean. The emulated hardware MAC is recognised by the OS/drivers a=
s it should be as it did with NetBSD 9 before. Thus were the IPv6 addresses=
<style></style>calculated ind given accordingly. Even the site-local 'fd00=
:....' and global '2003:...' addresses could be obtained somehow.</div><div=
>However: now neither IPv6 traffic is possible through that device, even if=
being able automatically set appropriate IPv6 addresses to that port. Nor =
is it even possible to set the preset IPv4 address to the network device "d=
e0" at boot. Should I do so manually with "ifconfig 10.0.0.90 255.255.255.0=
" after logon, ifconfig set it so as requested, but no traffic will be tran=
smitted through the port. Neither IPv6, nor IPv4. Not even pings.</div><div=
><br></div><div>What I miss in checking the ethernet port with a simple "if=
config" command within the emulated/guest NetBSD-10 machine are some lines =
in ifconfig's output such as the following that I have for my NetBSD 9 host=
machine, where the emulated port is connected to and which works fine as d=
esired. That could be a hint:</div><div><style></style></div><div>"</div><d=
iv> media: Ethernet autoselect (1000baseT full-duplex)<br=
> status: active<br></div><div>"<br></div><div><style></s=
tyle></div><div>Neither of those are present since the change from NetBSD 9=
.3 to NetBSD 10RC5 of the guest. It seems to be, that the driver is u=
nable to determin the used medium and thus does not recognize the medium as=
"active.</div><div><br></div><div>=E2=80=93 Marc.<br></div>
<br><br><br>Am Mittwoch, den 06.03.2024 um 15:10 schrieb Jonathan A. Kollas=
ch:<br><blockquote style=3D"border:0;border-left: 2px solid #22437f; paddin=
g:0px; margin:0px; padding-left:5px; margin-left: 5px; "><div class=3D"msg"=
>The following reply was made to PR port-vax/58002; it has been noted by GN=
ATS.<br>
<br>
From: "Jonathan A. Kollasch" <<a href="" href="mailto:jakllsch%kollasch.net@localhost" class="normal-link normal-link-email" target="_blank" rel="noopener noreferrer">jakllsch%kollasch.net@localhost" c=
lass=3D"normal-link normal-link-email" target=3D"_blank" rel=3D"noopener no=
referrer">jakllsch%kollasch.net@localhost</a>><br>
To: <a class=3D"normal-link" href="" href="mailto:gnats-bugs%netbsd.org@localhost" class="normal-link normal-link-email" target="_blank" rel="noopener noreferrer">gnats-bugs%netbsd.org@localhost">gnats-bu=
gs%netbsd.org@localhost</a><br>
Cc: <br>
Subject: Re: port-vax/58002: NetBSD-VAX network stack or drivers broken sin=
ce<br>
NetBSD 10?<br>
Date: Wed, 6 Mar 2024 08:04:58 -0600<br>
<br>
It looks like you have a layer 2 multicast address in place of a layer 2 u=
nicast<br>
MAC address. Can you try again with say fe:ff:ff:ff:ff:ff inste=
ad? Or<br>
is this real hardware?</div></blockquote></body></html>
--b1=_carnOWI32t2ojiKliBQwWt2kut4EQPbGUOHIupdQE--