Multiport Gigabit Card?

[kuleszdl]

Well, I thought since this is a vendor-specific forum it seems a bit strange discussing other products. But to give you a pointer: You might be interested in looking at the NanoPI R2s if you want something with 2 NICs. The second NIC is attached via USB3 but seems to deliver GBe speeds. It has no onboard wifi but this could be added via USB 2.0 (if you want to have freedom-friendly wifi, I know of no chipset atm that needs more than USB 2 anyways).

Personally, I consider the Rockpro64's PCIe more flexible - in theory. In practice, I don't know of any Wifi+LAN combo card that has both on one PCIe card.

[Der Geist der Maschine]

But to give you a pointer: You might be interested in looking at the NanoPI R2s if you want something with 2 NICs.

I found there also the NanoPI R1. It does not only include 2 ethernet ports but also wifi! That's actually what I really want. So far I have found that only on the OrangePI R1.

Both are not perfect as neither provide 1GB ethernet nor the 5GHz wifi band. One can't have everything. I still need to look up their support by vanilla linux and if they overhead under load.

[kuleszdl]

If you want you can start a new thread in the "general" forum and we'll continue the discussion there.

=> I'd like to keep this thread ontopic regarding the use of multiport gigabit NICs on the rockpro64, especially in scenarios where you might want to have multiple ethernet ports.

[deVillon]

I tried genuine I350-T2 with 5.10.0-3-arm64 #1 SMP Debian 5.10.13-1 kernel.
Works like a dream.
The only problem I found is that Rock's build-in ethernet port changed its name all the time. It might be any of eth0, eth1, eth2.
After I created the /lib/udev/rules.d/70-persistent-net.rules
with the following contents

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", KERNELS=="fe300000.ethernet", NAME="eth2"

The problem stopped and the build-in port is always eth2.

[kuleszdl]

According to the Debian wiki, the 70-persistent-net.rules is deprecated. Instead, the proper way seems to be booting the kernel using the parameter

net.ifnames=0

See: https://wiki.debian.org/NetworkInterfaceNames