Re: port-vax/58002: NetBSD-VAX network stack or drivers broken since NetBSD 10?

["Fege, Marc Daniel" <marc.fege%uni-bonn.de@localhost>]

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" <jakllsch%kollasch.net@localhost>
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?