2.5 Gbe USB Ethernet

Hi,

I am running a pi5 and as I have just upgraded my internet and network I have a USB 2.5 Gbe that I would like to use.

Can anyone sign post me in the right direction on how I can use this instead on the onboard NIC.

I have a had good and browse of the forum and cannot find anything.

Thanks

welcome to the dietpi forums! uh are you using this as a pc thats why you need 2.5gbe? if your just using this to watch movies over a network you dont really need 2.5gbe. have you tried a usb adapter? i tried a few usb adapters that used 2.5gbe here is one i use for dietpi on a pc and on a nas. Amazon.com: 2.5G USB to Ethernet Adapter, USB 3.0 to RJ45 Ethernet Adapter, Gigabit LAN Adapter for Xbox 360, Laptop, Computer, Mac, Chromebook, Microsoft Surface : Electronics

**I havent tested this using a raspberry only with a full desktop using dietpi and a network storage with dietpi and the qnap software.

I am using my pi as a download client so I would like it to benefit from the faster internet connection.

I am using this adapter UGREEN USB Ethernet Adapter, 2.5Gbps High-Speed Network Adapter for Gaming, USB 3.2 Gen 1 RJ45 Gigabit LAN Adaptor, Compatible with Laptop, PC, Switch, Xbox, Router, Surface Pro, Steam Deck : Amazon.co.uk: Computers & Accessories

It is listed in the USB devices but I cannot see a way to use it instead of the onboard NIC. I am looking where I can config the adapter set IP etc.

Can you share following

ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether d8:3a:dd:e7:67:78 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.254/24 brd 192.168.0.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 xxxx:xxx:xxxx:x:xxxx:xxxx:xxxx:xxxx/64 scope global dynamic mngtmpaddr
       valid_lft 47752sec preferred_lft 47752sec
    inet6 fe80::da3a:ddff:fee7:6778/64 scope link
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 6c:1f:f7:1b:a2:0f brd ff:ff:ff:ff:ff:ff

I masked my IPv6 address.

that is one of the other adapters i tried out and returned as it didnt work for me. it would constantly disconnect… probably due to defects though. it looks like its showing up but not as 2.5gbs.

It’s eth1. Unfortunately our tools did not support 2 ethernet adapter directly. Therefore you would need to configure the eth1 adapter manuall, using a drop in configuration file at /etc/network/interfaces.d/

I have not done this before, I create a file with something like:

auto eth1
iface eth1 inet static
        address 192.168.40.112
        netmask 255.255.255.0
        gateway 192.168.40.1

Do I need to call the file something in particular? I’m guessing eth1

The name should not matter. You can try to bring the adapter up using

ifup eth1

I created the file and I can ping on the IP address but when I unplug the onboard NIC I dont get a connection and when I unplug the USB NIC I can still ping it.

It seems that the IP address is on the onboard NIC.

ip a shows:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether d8:3a:dd:e7:67:78 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.254/24 brd 192.168.0.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 xxxx:xxx:xxxx:x:xxxx:xxxx:xxxx:xxxx/64 scope global dynamic mngtmpaddr
       valid_lft 46388sec preferred_lft 46388sec
    inet6 fe80::da3a:ddff:fee7:6778/64 scope link
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 6c:1f:f7:1b:a2:0f brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.249/24 brd 192.168.0.255 scope global eth1
       valid_lft forever preferred_lft forever
    inet6 xxxx:xxx:xxxx:x:xxxx:xxxx:xxxx:xxxx/64scope global dynamic mngtmpaddr
       valid_lft 46388sec preferred_lft 46388sec
    inet6 fe80::6e1f:f7ff:fe1b:a20f/64 scope link
       valid_lft forever preferred_lft forever

and the file my config file as below:

auto eth1
iface eth1 inet static
        address 192.168.0.249
        netmask 255.255.255.0
        gateway 192.168.0.1

You can identify the nic by its mac address. Simply connect the onboard nic only and check which mac address/adapter has an ip adress assigned.

I did an arp -a and the IP the IP addess I set for the USB is using the onboard NIC for some reason:

arp -a 192.168.0.149
Interface: 192.168.0.81 --- 0x4
  Internet Address      Physical Address      Type
  192.168.0.249         d8-3a-dd-e7-67-78     dynamic
arp -a 192.168.0.254
Interface: 192.168.0.81 --- 0x4
  Internet Address      Physical Address      Type
  192.168.0.254         d8-3a-dd-e7-67-78     dynamic

I’m not quite sure on this. Maybe @trendy has an idea

your gateway has a weird number you sure you set it right?

what’s weird about it?

This one seems to be strange. Or has this be done on a different device?

“0.254” in your gateway part is weird to me i dunno. :slight_smile: just funny ip “picks” i guess.

Thats the arp-a command from Windows with the IP 192.168.0.81. I used ARP to find the MAC addresses of the NIC of the IP set for eth1

Are you able to paste or screen shot where you are seeing this? 192.168.0.254 is the IP of eth0 I dont see any gateways shown in the “ip a” command output.

Did you had both connected at this moment?

What about enabling wifi and connecting via WiFi. Afterwards go to disabled onboard ethernet. This should allow your usb nic to become eth0