I have a Framework 16 laptop. I'm using a USB-C to Ethernet adapter to get wired networking going. It works briefly, but only if I force the link up repeatedly, and then shuts down within a minute or two, forgets its own IP, and quickly seems to get confused about whether or not the Ethernet cable is plugged in. Network stack restarts and trying to force the link back up generally get me nowhere and I have to reboot.
For those not familiar, on Framwork laptops there are small expansion cards that connect to the underside of the laptop. They're basically small squares that adapt Thunderbolt to anything else a user might want. In my case I got my hands on a USB-C Ethernet adapter while I sort out WiFi support. So, the device chain looks like this:
Thunderbolt device controller ↔ USB-C expansion card ↔ USB-C Ethernet adapter.
For clarity: this is not the official but unfortunately very janky looking Ethernet expansion card that goes directly from Thunderbolt to Ethernet... and sticks out of the laptop a fair bit.
I strongly suspect this setup is causing the underlying Ethernet driver to become very confused and eventually it just gives up on life. I'm a Gentoo Linux guy still getting the hang of BSD's differences from Linux. How do I collect the required information to file a bug for this? Would I file it with GhostBSD or upstream with FreeBSD?
On the one hand, explain it to me like I'm five, mainly because some commands and many device names are different between the Linux and FreeBSD ecosystems. On the other hand, don't be afraid to tell me to capture a Wireshark dump or something. Thanks!
