usrp-users@lists.ettus.com

Discussion and technical support related to USRP, UHD, RFNoC

View all threads

Connection to X310 fails but pinging works?

HD
Heinz, Dominik
Wed, Jan 29, 2025 2:35 PM

I have a system running Ubuntu 22.04, and a Ettus X310 is connected to said system via two SFP+ cables.
The latest uhd drivers are installed on the system.
The latest XG firmware image has been flashed onto the X310.

The main issue is that I can't seem to interact with the device, despite having the correct IP configurations set.
I assume it is a network configuration issue of some kind.

A few important notes for context:

  • The two SFP+ interfaces show up fine when running ip a\
  • I did set the MTU to 9000
  • I configured the IP address for both interfaces by manually adding an ethernet configuration via Ubuntu's network settings
  • I am successfully able to ping the device via 192.168.30.2 and via 192.168.40.2
  • I am NOT ABLE to interact with the X310. Both, uhd_find_devices and uhd_usrp_probe mention no device connected.
  • The green lights for the links on the back of the SDR light up (aka link is present)

I don't understand what I am missing to be able to interact with the device.
See the output below.

gnb@xgoss-host:~$ 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
valid_lft forever preferred_lft forever
2: enp77s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 9c:6b:00:56:a3:a5 brd ff:ff:ff:ff:ff:ff
3: enp1s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq state UP group default qlen 1000
link/ether f8:f2:1e:9b:f1:60 brd ff:ff:ff:ff:ff:ff
inet 192.168.30.2/24 brd 192.168.30.255 scope global noprefixroute enp1s0f0
valid_lft forever preferred_lft forever
inet6 fe80::a1a4:f18c:ce2c:bbf1/64 scope link noprefixroute
valid_lft forever preferred_lft forever
4: enp1s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq state UP group default qlen 1000
link/ether f8:f2:1e:9b:f1:61 brd ff:ff:ff:ff:ff:ff
inet 192.168.40.2/24 brd 192.168.40.255 scope global noprefixroute enp1s0f1
valid_lft forever preferred_lft forever
inet6 fe80::f167:b030:ddfa:a249/64 scope link noprefixroute
valid_lft forever preferred_lft forever
5: ogstun: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1400 qdisc fq_codel state UP group default qlen 500

gnb@xgoss-host:~$ uhd_usrp_probe
[INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~jammy1
Error: LookupError: KeyError: No devices found for ----->
Empty Device Address
gnb@xgoss-host:~$ uhd_find_devices
[INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~jammy1
No UHD Devices Found
gnb@xgoss-host:~$ uhd_usrp_probe --args addr=192.168.30.2
[INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~jammy1
Error: LookupError: KeyError: No devices found for ----->
Device Address:
addr: 192.168.30.2

gnb@xgoss-host:~$ uhd_usrp_probe --args addr=192.168.40.2
[INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~jammy1
Error: LookupError: KeyError: No devices found for ----->
Device Address:
addr: 192.168.40.2

gnb@xgoss-host:~$ ping 192.168.30.2 -c 1
PING 192.168.30.2 (192.168.30.2) 56(84) bytes of data.
64 bytes from 192.168.30.2: icmp_seq=1 ttl=64 time=0.039 ms

--- 192.168.30.2 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.039/0.039/0.039/0.000 ms
gnb@xgoss-host:~$ ping 192.168.40.2 -c 1
PING 192.168.40.2 (192.168.40.2) 56(84) bytes of data.
64 bytes from 192.168.40.2: icmp_seq=1 ttl=64 time=0.066 ms

--- 192.168.40.2 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.066/0.066/0.066/0.000 ms
gnb@xgoss-host:~$

I would like some information how I can interface with the X310.
I already checked the official documentation, but I don't see what I am missing/doing wrong.

I have a system running Ubuntu 22.04, and a Ettus X310 is connected to said system via two SFP+ cables. The latest uhd drivers are installed on the system. The latest XG firmware image has been flashed onto the X310. The main issue is that I can't seem to interact with the device, despite having the correct IP configurations set. I assume it is a network configuration issue of some kind. A few important notes for context: - The two SFP+ interfaces show up fine when running ip a\ - I did set the MTU to 9000 - I configured the IP address for both interfaces by manually adding an ethernet configuration via Ubuntu's network settings - I am successfully able to ping the device via 192.168.30.2 and via 192.168.40.2 - I am NOT ABLE to interact with the X310. Both, uhd_find_devices and uhd_usrp_probe mention no device connected. - The green lights for the links on the back of the SDR light up (aka link is present) I don't understand what I am missing to be able to interact with the device. See the output below. gnb@xgoss-host:~$ 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 valid_lft forever preferred_lft forever 2: enp77s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 9c:6b:00:56:a3:a5 brd ff:ff:ff:ff:ff:ff 3: enp1s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq state UP group default qlen 1000 link/ether f8:f2:1e:9b:f1:60 brd ff:ff:ff:ff:ff:ff inet 192.168.30.2/24 brd 192.168.30.255 scope global noprefixroute enp1s0f0 valid_lft forever preferred_lft forever inet6 fe80::a1a4:f18c:ce2c:bbf1/64 scope link noprefixroute valid_lft forever preferred_lft forever 4: enp1s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq state UP group default qlen 1000 link/ether f8:f2:1e:9b:f1:61 brd ff:ff:ff:ff:ff:ff inet 192.168.40.2/24 brd 192.168.40.255 scope global noprefixroute enp1s0f1 valid_lft forever preferred_lft forever inet6 fe80::f167:b030:ddfa:a249/64 scope link noprefixroute valid_lft forever preferred_lft forever 5: ogstun: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1400 qdisc fq_codel state UP group default qlen 500 gnb@xgoss-host:~$ uhd_usrp_probe [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~jammy1 Error: LookupError: KeyError: No devices found for -----> Empty Device Address gnb@xgoss-host:~$ uhd_find_devices [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~jammy1 No UHD Devices Found gnb@xgoss-host:~$ uhd_usrp_probe --args addr=192.168.30.2 [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~jammy1 Error: LookupError: KeyError: No devices found for -----> Device Address: addr: 192.168.30.2 gnb@xgoss-host:~$ uhd_usrp_probe --args addr=192.168.40.2 [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~jammy1 Error: LookupError: KeyError: No devices found for -----> Device Address: addr: 192.168.40.2 gnb@xgoss-host:~$ ping 192.168.30.2 -c 1 PING 192.168.30.2 (192.168.30.2) 56(84) bytes of data. 64 bytes from 192.168.30.2: icmp_seq=1 ttl=64 time=0.039 ms --- 192.168.30.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.039/0.039/0.039/0.000 ms gnb@xgoss-host:~$ ping 192.168.40.2 -c 1 PING 192.168.40.2 (192.168.40.2) 56(84) bytes of data. 64 bytes from 192.168.40.2: icmp_seq=1 ttl=64 time=0.066 ms --- 192.168.40.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.066/0.066/0.066/0.000 ms gnb@xgoss-host:~$ I would like some information how I can interface with the X310. I already checked the official documentation, but I don't see what I am missing/doing wrong.
WH
william.haftel@bluehalo.com
Wed, Jan 29, 2025 4:43 PM

I think your interfaces on the host should have IP addresses ending with .1 instead of .2 since the USRP has the .2 addresses.

The pings you are doing are just pinging yourself, not the USRP.

I think your interfaces on the host should have IP addresses ending with .1 instead of .2 since the USRP has the .2 addresses. The pings you are doing are just pinging yourself, not the USRP.