May I Delete Unknown msk0 Network Interface?

[Busthead]

Running latest update of v11.3. What is the purpose of the UNKNOWN msk0 network interface and may I delete it? It's IP addr is the same as bge0.

 

[Patrick M. Hausen]

It looks like your hardware features a second network port:

Code:

MSK(4)                 FreeBSD Kernel Interfaces Manual                 MSK(4)

NAME
     msk – Marvell/SysKonnect Yukon II Gigabit Ethernet adapter driver

SYNOPSIS
     To compile this driver into the kernel, place the following lines in your
     kernel configuration file:

           device miibus
           device msk

     Alternatively, to load the driver as a module at boot time, place the
     following line in loader.conf(5):

           if_msk_load="YES"

DESCRIPTION
     The msk device driver provides support for various NICs based on the
     Marvell/SysKonnect Yukon II Gigabit Ethernet controller chip.
[...]

 

[Busthead]

The card doesn't have two physical ports.

Is there a way to disable it or remove it from the dashboard?

 

[Hellione]

he does not mean one card with two ports, he means two different cards / chips in the system.
maybe an onboard card? your active network uses
bge = Broadcom BCM57xx/BCM590x Gigabit/Fast Ethernet driver
and the second, as patrick posted, is a
msk – Marvell/SysKonnect Yukon II Gigabit Ethernet adapter driver
maybe you can disable bge in bios, or remove the card if there is one installed

 

[Busthead]

The system uses an Intel X38 Express chipset with an integrated Broadcom 5755 or 5751 NetXtreme Gigabit NIC. No other network card is present.

Is it possible that that msk0 NIC is a remnant from previous hardware from which I used the config file?

Regardless, if I delete msk0 from Network-Interfaces, I loose connectivity to the system. So how to I delete this NIC and not loose access to my NAS?

 

[Hellione]

Strange. First I would try to fix this on the console.
2) configure link aggregation, delete if there is an entry 1) configure network interfaces, select both, delete, and setup your bge again

 

[Patrick M. Hausen]

Additionally maybe the contents of /var/run/dmesg.boot and the output of pciconf -lv might give some clues about your hardware. I suggest adding the files as attachments instead of copy&paste, they are rather long.