Empathy List Archives

AP

Ashton Palacios

Tue, May 30, 2023 10:17 PM

My research group recently got an Ettus X410. We are wanting to connect to
it through two MT27800 NICs on our server. We are able to set up the IP
addresses on the server and running uhd_find_devices shows the USRP having
the correct IP address that we are expecting. When we go to run the
benchmark_rate test we get the following error:

/usr/local/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6

[INFO] [UHD] linux; GNU C++ version 11.3.0; Boost_107400;
UHD_4.4.0.HEAD-0-g5fac246b
[00:00:00.000581] Creating the usrp device with: ...
[INFO] [MPMD] Initializing 1 device(s) in parallel with args:
mgmt_addr=192.168.13.2,type=x4xx,product=x410,serial=326B6ED,name=ni-x4xx-326B6ED,fpga=X4_200,claimed=False,addr=192.168.11.2
[INFO] [MPM.PeriphManager] init() called with device args
`fpga=X4_200,mgmt_addr=192.168.13.2,name=ni-x4xx-326B6ED,product=x410,clock_source=internal,time_source=internal'.
[ERROR] [RFNOC::MGMT] EnvironmentError: IOError: recv error on socket:
Connection refused
[ERROR] [RFNOC::GRAPH] IO Error during GSM initialization.
EnvironmentError: IOError: recv error on socket: Connection refused
[ERROR] [RFNOC::GRAPH] Caught exception while initializing graph:
EnvironmentError: IOError: recv error on socket: Connection refused
Error: RuntimeError: Failure to create rfnoc_graph.
alfor@sdr:/usr/local/lib/uhd/examples$ sudo !!
sudo ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6

[INFO] [UHD] linux; GNU C++ version 11.3.0; Boost_107400;
UHD_4.4.0.HEAD-0-g5fac246b
[00:00:00.000251] Creating the usrp device with: ...
[INFO] [MPMD] Initializing 1 device(s) in parallel with args:
mgmt_addr=192.168.13.2,type=x4xx,product=x410,serial=326B6ED,name=ni-x4xx-326B6ED,fpga=X4_200,claimed=False,addr=192.168.11.2
[INFO] [MPM.PeriphManager] init() called with device args
`fpga=X4_200,mgmt_addr=192.168.13.2,name=ni-x4xx-326B6ED,product=x410,clock_source=internal,time_source=internal'.
[ERROR] [RFNOC::MGMT] EnvironmentError: IOError: recv error on socket:
Connection refused
[ERROR] [RFNOC::GRAPH] IO Error during GSM initialization.
EnvironmentError: IOError: recv error on socket: Connection refused
[ERROR] [RFNOC::GRAPH] Caught exception while initializing graph:
EnvironmentError: IOError: recv error on socket: Connection refused
Error: RuntimeError: Failure to create rfnoc_graph.

Any suggestions on how to fix this?

My research group recently got an Ettus X410. We are wanting to connect to it through two MT27800 NICs on our server. We are able to set up the IP addresses on the server and running uhd_find_devices shows the USRP having the correct IP address that we are expecting. When we go to run the benchmark_rate test we get the following error: /usr/local/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 [INFO] [UHD] linux; GNU C++ version 11.3.0; Boost_107400; UHD_4.4.0.HEAD-0-g5fac246b [00:00:00.000581] Creating the usrp device with: ... [INFO] [MPMD] Initializing 1 device(s) in parallel with args: mgmt_addr=192.168.13.2,type=x4xx,product=x410,serial=326B6ED,name=ni-x4xx-326B6ED,fpga=X4_200,claimed=False,addr=192.168.11.2 [INFO] [MPM.PeriphManager] init() called with device args `fpga=X4_200,mgmt_addr=192.168.13.2,name=ni-x4xx-326B6ED,product=x410,clock_source=internal,time_source=internal'. [ERROR] [RFNOC::MGMT] EnvironmentError: IOError: recv error on socket: Connection refused [ERROR] [RFNOC::GRAPH] IO Error during GSM initialization. EnvironmentError: IOError: recv error on socket: Connection refused [ERROR] [RFNOC::GRAPH] Caught exception while initializing graph: EnvironmentError: IOError: recv error on socket: Connection refused Error: RuntimeError: Failure to create rfnoc_graph. alfor@sdr:/usr/local/lib/uhd/examples$ sudo !! sudo ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 [INFO] [UHD] linux; GNU C++ version 11.3.0; Boost_107400; UHD_4.4.0.HEAD-0-g5fac246b [00:00:00.000251] Creating the usrp device with: ... [INFO] [MPMD] Initializing 1 device(s) in parallel with args: mgmt_addr=192.168.13.2,type=x4xx,product=x410,serial=326B6ED,name=ni-x4xx-326B6ED,fpga=X4_200,claimed=False,addr=192.168.11.2 [INFO] [MPM.PeriphManager] init() called with device args `fpga=X4_200,mgmt_addr=192.168.13.2,name=ni-x4xx-326B6ED,product=x410,clock_source=internal,time_source=internal'. [ERROR] [RFNOC::MGMT] EnvironmentError: IOError: recv error on socket: Connection refused [ERROR] [RFNOC::GRAPH] IO Error during GSM initialization. EnvironmentError: IOError: recv error on socket: Connection refused [ERROR] [RFNOC::GRAPH] Caught exception while initializing graph: EnvironmentError: IOError: recv error on socket: Connection refused Error: RuntimeError: Failure to create rfnoc_graph. Any suggestions on how to fix this?

MD

Marcus D. Leech

Tue, May 30, 2023 11:47 PM

On 30/05/2023 18:17, Ashton Palacios wrote:

My research group recently got an Ettus X410. We are wanting to
connect to it through two MT27800 NICs on our server. We are able to
set up the IP addresses on the server and running uhd_find_devices
shows the USRP having the correct IP address that we are expecting.
When we go to run the benchmark_rate test we get the following error:

/usr/local/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate
10e6

[INFO] [UHD] linux; GNU C++ version 11.3.0; Boost_107400;
UHD_4.4.0.HEAD-0-g5fac246b
[00:00:00.000581] Creating the usrp device with: ...
[INFO] [MPMD] Initializing 1 device(s) in parallel with args:
mgmt_addr=192.168.13.2,type=x4xx,product=x410,serial=326B6ED,name=ni-x4xx-326B6ED,fpga=X4_200,claimed=False,addr=192.168.11.2
[INFO] [MPM.PeriphManager] init() called with device args
`fpga=X4_200,mgmt_addr=192.168.13.2,name=ni-x4xx-326B6ED,product=x410,clock_source=internal,time_source=internal'.
[ERROR] [RFNOC::MGMT] EnvironmentError: IOError: recv error on socket:
Connection refused
[ERROR] [RFNOC::GRAPH] IO Error during GSM initialization.
EnvironmentError: IOError: recv error on socket: Connection refused
[ERROR] [RFNOC::GRAPH] Caught exception while initializing graph:
EnvironmentError: IOError: recv error on socket: Connection refused
Error: RuntimeError: Failure to create rfnoc_graph.
alfor@sdr:/usr/local/lib/uhd/examples$ sudo !!
sudo ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6

[INFO] [UHD] linux; GNU C++ version 11.3.0; Boost_107400;
UHD_4.4.0.HEAD-0-g5fac246b
[00:00:00.000251] Creating the usrp device with: ...
[INFO] [MPMD] Initializing 1 device(s) in parallel with args:
mgmt_addr=192.168.13.2,type=x4xx,product=x410,serial=326B6ED,name=ni-x4xx-326B6ED,fpga=X4_200,claimed=False,addr=192.168.11.2
[INFO] [MPM.PeriphManager] init() called with device args
`fpga=X4_200,mgmt_addr=192.168.13.2,name=ni-x4xx-326B6ED,product=x410,clock_source=internal,time_source=internal'.
[ERROR] [RFNOC::MGMT] EnvironmentError: IOError: recv error on socket:
Connection refused
[ERROR] [RFNOC::GRAPH] IO Error during GSM initialization.
EnvironmentError: IOError: recv error on socket: Connection refused
[ERROR] [RFNOC::GRAPH] Caught exception while initializing graph:
EnvironmentError: IOError: recv error on socket: Connection refused
Error: RuntimeError: Failure to create rfnoc_graph.

Any suggestions on how to fix this?

USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-leave@lists.ettus.com

This looks like a simple networking issue.

First things first--can you "ping" the ip addresses of the device?

If you explicitly use the device address, instead of letting UHD "hunt"
for it, does it still do this?

benchmark_rate --args "addr=<ip address of device> type=x400"

On 30/05/2023 18:17, Ashton Palacios wrote: > My research group recently got an Ettus X410. We are wanting to > connect to it through two MT27800 NICs on our server. We are able to > set up the IP addresses on the server and running uhd_find_devices > shows the USRP having the correct IP address that we are expecting. > When we go to run the benchmark_rate test we get the following error: > > > /usr/local/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate > 10e6 > > [INFO] [UHD] linux; GNU C++ version 11.3.0; Boost_107400; > UHD_4.4.0.HEAD-0-g5fac246b > [00:00:00.000581] Creating the usrp device with: ... > [INFO] [MPMD] Initializing 1 device(s) in parallel with args: > mgmt_addr=192.168.13.2,type=x4xx,product=x410,serial=326B6ED,name=ni-x4xx-326B6ED,fpga=X4_200,claimed=False,addr=192.168.11.2 > [INFO] [MPM.PeriphManager] init() called with device args > `fpga=X4_200,mgmt_addr=192.168.13.2,name=ni-x4xx-326B6ED,product=x410,clock_source=internal,time_source=internal'. > [ERROR] [RFNOC::MGMT] EnvironmentError: IOError: recv error on socket: > Connection refused > [ERROR] [RFNOC::GRAPH] IO Error during GSM initialization. > EnvironmentError: IOError: recv error on socket: Connection refused > [ERROR] [RFNOC::GRAPH] Caught exception while initializing graph: > EnvironmentError: IOError: recv error on socket: Connection refused > Error: RuntimeError: Failure to create rfnoc_graph. > alfor@sdr:/usr/local/lib/uhd/examples$ sudo !! > sudo ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 > > [INFO] [UHD] linux; GNU C++ version 11.3.0; Boost_107400; > UHD_4.4.0.HEAD-0-g5fac246b > [00:00:00.000251] Creating the usrp device with: ... > [INFO] [MPMD] Initializing 1 device(s) in parallel with args: > mgmt_addr=192.168.13.2,type=x4xx,product=x410,serial=326B6ED,name=ni-x4xx-326B6ED,fpga=X4_200,claimed=False,addr=192.168.11.2 > [INFO] [MPM.PeriphManager] init() called with device args > `fpga=X4_200,mgmt_addr=192.168.13.2,name=ni-x4xx-326B6ED,product=x410,clock_source=internal,time_source=internal'. > [ERROR] [RFNOC::MGMT] EnvironmentError: IOError: recv error on socket: > Connection refused > [ERROR] [RFNOC::GRAPH] IO Error during GSM initialization. > EnvironmentError: IOError: recv error on socket: Connection refused > [ERROR] [RFNOC::GRAPH] Caught exception while initializing graph: > EnvironmentError: IOError: recv error on socket: Connection refused > Error: RuntimeError: Failure to create rfnoc_graph. > > Any suggestions on how to fix this? > > _______________________________________________ > USRP-users mailing list -- usrp-users@lists.ettus.com > To unsubscribe send an email to usrp-users-leave@lists.ettus.com This looks like a simple networking issue. First things first--can you "ping" the ip addresses of the device? If you explicitly use the device address, instead of letting UHD "hunt" for it, does it still do this? benchmark_rate --args "addr=<ip address of device> type=x400"

P

pistachio6981@gmail.com

Wed, May 31, 2023 2:35 PM

I agree that it is probably a simple networking thing. I can ping each of the addresses and the device pongs back. I did try to run the the benchmark program while specifying an IP address and USRP type and got the same error as shown below:

/usr/local/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --args "addr=192.168.10.2,type=x4xx"

[INFO] [UHD] linux; GNU C++ version 11.3.0; Boost_107400; UHD_4.4.0.HEAD-0-g5fac246b

[00:00:00.000281] Creating the usrp device with: addr=192.168.10.2,type=x4xx...

[INFO] [MPMD] Initializing 1 device(s) in parallel with args: mgmt_addr=192.168.10.2,type=x4xx,product=x410,serial=326B6ED,name=ni-x4xx-326B6ED,fpga=X4_200,claimed=False,addr=192.168.10.2

[INFO] [MPM.PeriphManager] init() called with device args `fpga=X4_200,mgmt_addr=192.168.10.2,name=ni-x4xx-326B6ED,product=x410,clock_source=internal,time_source=internal'.

[ERROR] [RFNOC::MGMT] EnvironmentError: IOError: recv error on socket: Connection refused

[ERROR] [RFNOC::GRAPH] IO Error during GSM initialization. EnvironmentError: IOError: recv error on socket: Connection refused

[ERROR] [RFNOC::GRAPH] Caught exception while initializing graph: EnvironmentError: IOError: recv error on socket: Connection refused

Error: RuntimeError: Failure to create rfnoc_graph.

Any other suggestions?

I agree that it is probably a simple networking thing. I can ping each of the addresses and the device pongs back. I did try to run the the benchmark program while specifying an IP address and USRP type and got the same error as shown below:\ \ /usr/local/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --args "addr=192.168.10.2,type=x4xx" \[INFO\] \[UHD\] linux; GNU C++ version 11.3.0; Boost_107400; UHD_4.4.0.HEAD-0-g5fac246b \[00:00:00.000281\] Creating the usrp device with: addr=192.168.10.2,type=x4xx... \[INFO\] \[MPMD\] Initializing 1 device(s) in parallel with args: mgmt_addr=192.168.10.2,type=x4xx,product=x410,serial=326B6ED,name=ni-x4xx-326B6ED,fpga=X4_200,claimed=False,addr=192.168.10.2 \[INFO\] \[MPM.PeriphManager\] init() called with device args \`fpga=X4_200,mgmt_addr=192.168.10.2,name=ni-x4xx-326B6ED,product=x410,clock_source=internal,time_source=internal'. \[ERROR\] \[RFNOC::MGMT\] EnvironmentError: IOError: recv error on socket: Connection refused \[ERROR\] \[RFNOC::GRAPH\] IO Error during GSM initialization. EnvironmentError: IOError: recv error on socket: Connection refused \[ERROR\] \[RFNOC::GRAPH\] Caught exception while initializing graph: EnvironmentError: IOError: recv error on socket: Connection refused Error: RuntimeError: Failure to create rfnoc_graph.\ \ Any other suggestions?

MD

Marcus D. Leech

Wed, May 31, 2023 3:30 PM

On 31/05/2023 10:35, pistachio6981@gmail.com wrote:

I agree that it is probably a simple networking thing. I can ping each
of the addresses and the device pongs back. I did try to run the the
benchmark program while specifying an IP address and USRP type and got
the same error as shown below:

/usr/local/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate
10e6 --args "addr=192.168.10.2,type=x4xx"

carboxymethylcellulose propylene glycol[INFO] [UHD] linux; GNU C++
version 11.3.0; Boost_107400; UHD_4.4.0.HEAD-0-g5fac246b

[00:00:00.000281] Creating the usrp device with:
addr=192.168.10.2,type=x4xx...

[INFO] [MPMD] Initializing 1 device(s) in parallel with args:
mgmt_addr=192.168.10.2,type=x4xx,product=x410,serial=326B6ED,name=ni-x4xx-326B6ED,fpga=X4_200,claimed=False,addr=192.168.10.2carboxymethylcellulose
propylene glycol

[INFO] [MPM.PeriphManager] init() called with device args
`fpga=X4_200,mgmt_addr=192.168.10.2,name=ni-x4xx-326B6ED,product=x410,clock_source=internal,time_source=internal'.

[ERROR] [RFNOC::MGMT] EnvironmentError: IOError: recv error on socket:
Connection refused

[ERROR] [RFNOC::GRAPH] IO Error during GSM initialization.
EnvironmentError: IOError: recv error on socket: Connection refused

[ERROR] [RFNOC::GRAPH] Caught exception while initializing graph:
EnvironmentError: IOError: recv error on socket: Connection refused

Error: RuntimeError: Failure to create rfnoc_graph.

Any other suggestions?

Do you get the same error when using: uhd_usrp_probe --args
"addr=192.168.10.2,type=x4xx"

On 31/05/2023 10:35, pistachio6981@gmail.com wrote: > > I agree that it is probably a simple networking thing. I can ping each > of the addresses and the device pongs back. I did try to run the the > benchmark program while specifying an IP address and USRP type and got > the same error as shown below: > > /usr/local/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate > 10e6 --args "addr=192.168.10.2,type=x4xx" > > carboxymethylcellulose propylene glycol[INFO] [UHD] linux; GNU C++ > version 11.3.0; Boost_107400; UHD_4.4.0.HEAD-0-g5fac246b > > [00:00:00.000281] Creating the usrp device with: > addr=192.168.10.2,type=x4xx... > > [INFO] [MPMD] Initializing 1 device(s) in parallel with args: > mgmt_addr=192.168.10.2,type=x4xx,product=x410,serial=326B6ED,name=ni-x4xx-326B6ED,fpga=X4_200,claimed=False,addr=192.168.10.2carboxymethylcellulose > propylene glycol > > [INFO] [MPM.PeriphManager] init() called with device args > `fpga=X4_200,mgmt_addr=192.168.10.2,name=ni-x4xx-326B6ED,product=x410,clock_source=internal,time_source=internal'. > > [ERROR] [RFNOC::MGMT] EnvironmentError: IOError: recv error on socket: > Connection refused > > [ERROR] [RFNOC::GRAPH] IO Error during GSM initialization. > EnvironmentError: IOError: recv error on socket: Connection refused > > [ERROR] [RFNOC::GRAPH] Caught exception while initializing graph: > EnvironmentError: IOError: recv error on socket: Connection refused > > Error: RuntimeError: Failure to create rfnoc_graph. > > Any other suggestions? > > Do you get the same error when using: uhd_usrp_probe --args "addr=192.168.10.2,type=x4xx"

P

pistachio6981@gmail.com

Wed, May 31, 2023 4:11 PM

Yes it does sadly.

/usr/local/lib/uhd/examples$ uhd_usrp_probe --args "addr=192.168.10.2,type=x4xx"

[INFO] [UHD] linux; GNU C++ version 11.3.0; Boost_107400; UHD_4.4.0.HEAD-0-g5fac246b

[INFO] [MPMD] Initializing 1 device(s) in parallel with args: mgmt_addr=192.168.10.2,type=x4xx,product=x410,serial=326B6ED,name=ni-x4xx-326B6ED,fpga=X4_200,claimed=False,addr=192.168.10.2

[INFO] [MPM.PeriphManager] init() called with device args `fpga=X4_200,mgmt_addr=192.168.10.2,name=ni-x4xx-326B6ED,product=x410,clock_source=internal,time_source=internal'.

[ERROR] [RFNOC::MGMT] EnvironmentError: IOError: recv error on socket: Connection refused

[ERROR] [RFNOC::GRAPH] IO Error during GSM initialization. EnvironmentError: IOError: recv error on socket: Connection refused

[ERROR] [RFNOC::GRAPH] Caught exception while initializing graph: EnvironmentError: IOError: recv error on socket: Connection refused

Error: RuntimeError: Failure to create rfnoc_graph.

Yes it does sadly.\ \ /usr/local/lib/uhd/examples$ uhd_usrp_probe --args "addr=192.168.10.2,type=x4xx" \[INFO\] \[UHD\] linux; GNU C++ version 11.3.0; Boost_107400; UHD_4.4.0.HEAD-0-g5fac246b \[INFO\] \[MPMD\] Initializing 1 device(s) in parallel with args: mgmt_addr=192.168.10.2,type=x4xx,product=x410,serial=326B6ED,name=ni-x4xx-326B6ED,fpga=X4_200,claimed=False,addr=192.168.10.2 \[INFO\] \[MPM.PeriphManager\] init() called with device args \`fpga=X4_200,mgmt_addr=192.168.10.2,name=ni-x4xx-326B6ED,product=x410,clock_source=internal,time_source=internal'. \[ERROR\] \[RFNOC::MGMT\] EnvironmentError: IOError: recv error on socket: Connection refused \[ERROR\] \[RFNOC::GRAPH\] IO Error during GSM initialization. EnvironmentError: IOError: recv error on socket: Connection refused \[ERROR\] \[RFNOC::GRAPH\] Caught exception while initializing graph: EnvironmentError: IOError: recv error on socket: Connection refused Error: RuntimeError: Failure to create rfnoc_graph.

P

pistachio6981@gmail.com

Wed, May 31, 2023 4:13 PM

running the the probe on the ethernet cable interface completes successfully, it is just the MT cards that are causing problems.

MD

Marcus D. Leech

Wed, May 31, 2023 4:15 PM

On 31/05/2023 12:11, pistachio6981@gmail.com wrote:

Yes it does sadly.

/usr/local/lib/uhd/examples$ uhd_usrp_probe --args
"addr=192.168.10.2,type=x4xx"

[INFO] [UHD] linux; GNU C++ version 11.3.0; Boost_107400;
UHD_4.4.0.HEAD-0-g5fac246b

[INFO] [MPMD] Initializing 1 device(s) in parallel with args:
mgmt_addr=192.168.10.2,type=x4xx,product=x410,serial=326B6ED,name=ni-x4xx-326B6ED,fpga=X4_200,claimed=False,addr=192.168.10.2

[INFO] [MPM.PeriphManager] init() called with device args
`fpga=X4_200,mgmt_addr=192.168.10.2,name=ni-x4xx-326B6ED,product=x410,clock_source=internal,time_source=internal'.

[ERROR] [RFNOC::MGMT] EnvironmentError: IOError: recv error on socket:
Connection refused

[ERROR] [RFNOC::GRAPH] IO Error during GSM initialization.
EnvironmentError: IOError: recv error on socket: Connection refused

[ERROR] [RFNOC::GRAPH] Caught exception while initializing graph:
EnvironmentError: IOError: recv error on socket: Connection refused

Error: RuntimeError: Failure to create rfnoc_graph.

USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-leave@lists.ettus.com

A few things to check:

Are you running a system image on the X410 that is up-to-date with
your host UHD version?

   What are the IP addresses of all the network interfaces on your
system? Is it possible the routing machinery
   is sending packets out the wrong interface because you've duplicated
the IP address/subnet on two of your
   network cards?

Is there some other (non-USRP X410) device that is reachable from
your computer, with the same IP address?

On 31/05/2023 12:11, pistachio6981@gmail.com wrote: > > Yes it does sadly. > > /usr/local/lib/uhd/examples$ uhd_usrp_probe --args > "addr=192.168.10.2,type=x4xx" > > [INFO] [UHD] linux; GNU C++ version 11.3.0; Boost_107400; > UHD_4.4.0.HEAD-0-g5fac246b > > [INFO] [MPMD] Initializing 1 device(s) in parallel with args: > mgmt_addr=192.168.10.2,type=x4xx,product=x410,serial=326B6ED,name=ni-x4xx-326B6ED,fpga=X4_200,claimed=False,addr=192.168.10.2 > > [INFO] [MPM.PeriphManager] init() called with device args > `fpga=X4_200,mgmt_addr=192.168.10.2,name=ni-x4xx-326B6ED,product=x410,clock_source=internal,time_source=internal'. > > [ERROR] [RFNOC::MGMT] EnvironmentError: IOError: recv error on socket: > Connection refused > > [ERROR] [RFNOC::GRAPH] IO Error during GSM initialization. > EnvironmentError: IOError: recv error on socket: Connection refused > > [ERROR] [RFNOC::GRAPH] Caught exception while initializing graph: > EnvironmentError: IOError: recv error on socket: Connection refused > > Error: RuntimeError: Failure to create rfnoc_graph. > > > _______________________________________________ > USRP-users mailing list -- usrp-users@lists.ettus.com > To unsubscribe send an email to usrp-users-leave@lists.ettus.com A few things to check: Are you running a system image on the X410 that is up-to-date with your host UHD version? What are the IP addresses of all the network interfaces on your system? Is it possible the routing machinery is sending packets out the wrong interface because you've duplicated the IP address/subnet on two of your network cards? Is there some *other* (non-USRP X410) device that is reachable from your computer, with the same IP address?

P

pistachio6981@gmail.com

Wed, May 31, 2023 4:41 PM

the image should be just fine, there are no other devices that are on the same subnet as the sdr interfaces are on. Here are interfaces on the server that is trying to connect to the x410:

ens18: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

    inet 192.168.0.148  netmask 255.255.255.0  broadcast 192.168.0.255

    inet6 fe80::d75b:dde7:bb0d:bf0e  prefixlen 64  scopeid 0x20<link>

    ether 22:73:df:f4:97:21  txqueuelen 1000  (Ethernet)

    RX packets 1766  bytes 402332 (402.3 KB)

    RX errors 0  dropped 119  overruns 0  frame 0

    TX packets 1444  bytes 2596987 (2.5 MB)

    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ens17f0np0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

    inet 192.168.10.3  netmask 255.255.255.0  broadcast 192.168.10.255

    inet6 fe80::eaeb:d3ff:fe43:3ec8  prefixlen 64  scopeid 0x20<link>

    ether e8:eb:d3:43:3e:c8  txqueuelen 1000  (Ethernet)

    RX packets 0  bytes 0 (0.0 B)

    RX errors 0  dropped 0  overruns 0  frame 0

    TX packets 51  bytes 6608 (6.6 KB)

    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ens17f1np1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

    inet 192.168.11.3  netmask 255.255.255.0  broadcast 192.168.11.255

    inet6 fe80::eaeb:d3ff:fe43:3ec9  prefixlen 64  scopeid 0x20<link>

    ether e8:eb:d3:43:3e:c9  txqueuelen 1000  (Ethernet)

    RX packets 0  bytes 0 (0.0 B)

    RX errors 0  dropped 0  overruns 0  frame 0

    TX packets 51  bytes 6617 (6.6 KB)

    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ens27f0np0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

    inet 192.168.12.3  netmask 255.255.255.0  broadcast 192.168.12.255

    inet6 fe80::eaeb:d3ff:fe55:dc00  prefixlen 64  scopeid 0x20<link>

    ether e8:eb:d3:55:dc:00  txqueuelen 1000  (Ethernet)

    RX packets 0  bytes 0 (0.0 B)

    RX errors 0  dropped 0  overruns 0  frame 0

    TX packets 51  bytes 6633 (6.6 KB)

    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ens27f1np1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

    inet 192.168.13.3  netmask 255.255.255.0  broadcast 192.168.13.255

    inet6 fe80::eaeb:d3ff:fe55:dc01  prefixlen 64  scopeid 0x20<link>

    ether e8:eb:d3:55:dc:01  txqueuelen 1000  (Ethernet)

    RX packets 0  bytes 0 (0.0 B)

    RX errors 0  dropped 0  overruns 0  frame 0

    TX packets 51  bytes 6612 (6.6 KB)

    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0\

Here are the interfaces on the x410:

eth0 Link encap:Ethernet HWaddr 00:80:2F:36:2B:C6

      inet addr:192.168.0.165  Bcast:192.168.0.255  Mask:255.255.255.0

      inet6 addr: fe80::280:2fff:fe36:2bc6/64 Scope:Link

      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

      RX packets:4232 errors:0 dropped:988 overruns:0 frame:0

      TX packets:335 errors:0 dropped:0 overruns:0 carrier:0

      collisions:0 txqueuelen:1000 

      RX bytes:440934 (430.5 KiB)  TX bytes:37656 (36.7 KiB)

      Interrupt:19

int0 Link encap:Ethernet HWaddr AE:4A:B9:D0:0B:25

      inet addr:169.254.0.1  Bcast:169.254.0.255  Mask:255.255.255.0

      inet6 addr: fe80::ac4a:b9ff:fed0:b25/64 Scope:Link

      UP BROADCAST RUNNING MULTICAST  MTU:9000  Metric:1

      RX packets:17079 errors:0 dropped:0 overruns:0 frame:0

      TX packets:17134 errors:0 dropped:0 overruns:0 carrier:0

      collisions:0 txqueuelen:1000 

      RX bytes:1127294 (1.0 MiB)  TX bytes:1136890 (1.0 MiB)

lo Link encap:Local Loopback

      inet addr:127.0.0.1  Mask:255.0.0.0

      inet6 addr: ::1/128 Scope:Host

      UP LOOPBACK RUNNING  MTU:65536  Metric:1

      RX packets:973 errors:0 dropped:0 overruns:0 frame:0

      TX packets:973 errors:0 dropped:0 overruns:0 carrier:0

      collisions:0 txqueuelen:1000 

      RX bytes:73015 (71.3 KiB)  TX bytes:73015 (71.3 KiB)

sfp0 Link encap:Ethernet HWaddr 00:80:2F:36:2B:C7

      inet addr:192.168.10.2  Bcast:192.168.10.255  Mask:255.255.255.0

      inet6 addr: fe80::280:2fff:fe36:2bc7/64 Scope:Link

      UP BROADCAST RUNNING MULTICAST  MTU:9000  Metric:1

      RX packets:288 errors:0 dropped:0 overruns:0 frame:0

      TX packets:560 errors:0 dropped:0 overruns:0 carrier:0

      collisions:0 txqueuelen:1000 

      RX bytes:38774 (37.8 KiB)  TX bytes:137733 (134.5 KiB)

sfp0_1 Link encap:Ethernet HWaddr 00:80:2F:36:2B:C8

      inet addr:192.168.11.2  Bcast:192.168.11.255  Mask:255.255.255.0

      inet6 addr: fe80::280:2fff:fe36:2bc8/64 Scope:Link

      UP BROADCAST RUNNING MULTICAST  MTU:9000  Metric:1

      RX packets:335 errors:0 dropped:0 overruns:0 frame:0

      TX packets:94 errors:0 dropped:0 overruns:0 carrier:0

      collisions:0 txqueuelen:1000 

      RX bytes:45298 (44.2 KiB)  TX bytes:14410 (14.0 KiB)

sfp0_2 Link encap:Ethernet HWaddr 00:80:2F:36:2B:C9

      inet addr:192.168.12.2  Bcast:192.168.12.255  Mask:255.255.255.0

      inet6 addr: fe80::280:2fff:fe36:2bc9/64 Scope:Link

      UP BROADCAST RUNNING MULTICAST  MTU:9000  Metric:1

      RX packets:657 errors:0 dropped:0 overruns:0 frame:0

      TX packets:66 errors:0 dropped:0 overruns:0 carrier:0

      collisions:0 txqueuelen:1000 

      RX bytes:162231 (158.4 KiB)  TX bytes:10541 (10.2 KiB)

sfp0_3 Link encap:Ethernet HWaddr 00:80:2F:36:2B:CA

      inet addr:192.168.13.2  Bcast:192.168.13.255  Mask:255.255.255.0

      inet6 addr: fe80::280:2fff:fe36:2bca/64 Scope:Link

      UP BROADCAST RUNNING MULTICAST  MTU:9000  Metric:1

      RX packets:325 errors:0 dropped:0 overruns:0 frame:0

      TX packets:168 errors:0 dropped:0 overruns:0 carrier:0

      collisions:0 txqueuelen:1000 

      RX bytes:41365 (40.3 KiB)  TX bytes:22845 (22.3 KiB)\

Maybe we set up our netplan rules wrong, here is an example of what we currently have for one of the interfaces:

network:

version: 2

renderer: NetworkManager

ethernets:

ens17f0np0:

  dhcp4: no

  dhcp6: no

  addresses: \[192.168.10.3/24\]

  nameservers:

    addresses: \[8.8.8.8,8.8.4.4\]\

Thank you so much for your time and help.

the image should be just fine, there are no other devices that are on the same subnet as the sdr interfaces are on. Here are interfaces on the server that is trying to connect to the x410:\ \ ens18: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.148 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::d75b:dde7:bb0d:bf0e prefixlen 64 scopeid 0x20<link> ether 22:73:df:f4:97:21 txqueuelen 1000 (Ethernet) RX packets 1766 bytes 402332 (402.3 KB) RX errors 0 dropped 119 overruns 0 frame 0 TX packets 1444 bytes 2596987 (2.5 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ens17f0np0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.10.3 netmask 255.255.255.0 broadcast 192.168.10.255 inet6 fe80::eaeb:d3ff:fe43:3ec8 prefixlen 64 scopeid 0x20<link> ether e8:eb:d3:43:3e:c8 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 51 bytes 6608 (6.6 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ens17f1np1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.11.3 netmask 255.255.255.0 broadcast 192.168.11.255 inet6 fe80::eaeb:d3ff:fe43:3ec9 prefixlen 64 scopeid 0x20<link> ether e8:eb:d3:43:3e:c9 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 51 bytes 6617 (6.6 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ens27f0np0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.12.3 netmask 255.255.255.0 broadcast 192.168.12.255 inet6 fe80::eaeb:d3ff:fe55:dc00 prefixlen 64 scopeid 0x20<link> ether e8:eb:d3:55:dc:00 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 51 bytes 6633 (6.6 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ens27f1np1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.13.3 netmask 255.255.255.0 broadcast 192.168.13.255 inet6 fe80::eaeb:d3ff:fe55:dc01 prefixlen 64 scopeid 0x20<link> ether e8:eb:d3:55:dc:01 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 51 bytes 6612 (6.6 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0\ \ Here are the interfaces on the x410:\ \ eth0 Link encap:Ethernet HWaddr 00:80:2F:36:2B:C6 inet addr:192.168.0.165 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::280:2fff:fe36:2bc6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4232 errors:0 dropped:988 overruns:0 frame:0 TX packets:335 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:440934 (430.5 KiB) TX bytes:37656 (36.7 KiB) Interrupt:19 int0 Link encap:Ethernet HWaddr AE:4A:B9:D0:0B:25 inet addr:169.254.0.1 Bcast:169.254.0.255 Mask:255.255.255.0 inet6 addr: fe80::ac4a:b9ff:fed0:b25/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 RX packets:17079 errors:0 dropped:0 overruns:0 frame:0 TX packets:17134 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1127294 (1.0 MiB) TX bytes:1136890 (1.0 MiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:973 errors:0 dropped:0 overruns:0 frame:0 TX packets:973 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:73015 (71.3 KiB) TX bytes:73015 (71.3 KiB) sfp0 Link encap:Ethernet HWaddr 00:80:2F:36:2B:C7 inet addr:192.168.10.2 Bcast:192.168.10.255 Mask:255.255.255.0 inet6 addr: fe80::280:2fff:fe36:2bc7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 RX packets:288 errors:0 dropped:0 overruns:0 frame:0 TX packets:560 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:38774 (37.8 KiB) TX bytes:137733 (134.5 KiB) sfp0_1 Link encap:Ethernet HWaddr 00:80:2F:36:2B:C8 inet addr:192.168.11.2 Bcast:192.168.11.255 Mask:255.255.255.0 inet6 addr: fe80::280:2fff:fe36:2bc8/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 RX packets:335 errors:0 dropped:0 overruns:0 frame:0 TX packets:94 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:45298 (44.2 KiB) TX bytes:14410 (14.0 KiB) sfp0_2 Link encap:Ethernet HWaddr 00:80:2F:36:2B:C9 inet addr:192.168.12.2 Bcast:192.168.12.255 Mask:255.255.255.0 inet6 addr: fe80::280:2fff:fe36:2bc9/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 RX packets:657 errors:0 dropped:0 overruns:0 frame:0 TX packets:66 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:162231 (158.4 KiB) TX bytes:10541 (10.2 KiB) sfp0_3 Link encap:Ethernet HWaddr 00:80:2F:36:2B:CA inet addr:192.168.13.2 Bcast:192.168.13.255 Mask:255.255.255.0 inet6 addr: fe80::280:2fff:fe36:2bca/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 RX packets:325 errors:0 dropped:0 overruns:0 frame:0 TX packets:168 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:41365 (40.3 KiB) TX bytes:22845 (22.3 KiB)\ \ Maybe we set up our netplan rules wrong, here is an example of what we currently have for one of the interfaces:\ \ network: version: 2 renderer: NetworkManager ethernets: ens17f0np0: dhcp4: no dhcp6: no addresses: \[192.168.10.3/24\] nameservers: addresses: \[8.8.8.8,8.8.4.4\]\ \ Thank you so much for your time and help.

MD

Marcus D. Leech

Wed, May 31, 2023 4:54 PM

On 31/05/2023 12:41, pistachio6981@gmail.com wrote:

the image should be just fine, there are no other devices that are on
the same subnet as the sdr interfaces are on. Here are interfaces on
the server that is trying to connect to the x410:

ens18: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

inet 192.168.0.148 netmask 255.255.255.0 broadcast 192.168.0.255

inet6 fe80::d75b:dde7:bb0d:bf0e prefixlen 64 scopeid 0x20<link>

ether 22:73:df:f4:97:21 txqueuelen 1000 (Ethernet)

RX packets 1766 bytes 402332 (402.3 KB)

RX errors 0 dropped 119 overruns 0 frame 0

TX packets 1444 bytes 2596987 (2.5 MB)

TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

ens17f0np0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

inet 192.168.10.3 netmask 255.255.255.0 broadcast 192.168.10.255

inet6 fe80::eaeb:d3ff:fe43:3ec8 prefixlen 64 scopeid 0x20<link>

ether e8:eb:d3:43:3e:c8 txqueuelen 1000 (Ethernet)

RX packets 0 bytes 0 (0.0 B)

RX errors 0 dropped 0 overruns 0 frame 0

TX packets 51 bytes 6608 (6.6 KB)

TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

ens17f1np1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

inet 192.168.11.3 netmask 255.255.255.0 broadcast 192.168.11.255

inet6 fe80::eaeb:d3ff:fe43:3ec9 prefixlen 64 scopeid 0x20<link>

ether e8:eb:d3:43:3e:c9 txqueuelen 1000 (Ethernet)

RX packets 0 bytes 0 (0.0 B)

RX errors 0 dropped 0 overruns 0 frame 0

TX packets 51 bytes 6617 (6.6 KB)

TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

ens27f0np0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

inet 192.168.12.3 netmask 255.255.255.0 broadcast 192.168.12.255

inet6 fe80::eaeb:d3ff:fe55:dc00 prefixlen 64 scopeid 0x20<link>

ether e8:eb:d3:55:dc:00 txqueuelen 1000 (Ethernet)

RX packets 0 bytes 0 (0.0 B)

RX errors 0 dropped 0 overruns 0 frame 0

TX packets 51 bytes 6633 (6.6 KB)

TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

ens27f1np1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

inet 192.168.13.3 netmask 255.255.255.0 broadcast 192.168.13.255

inet6 fe80::eaeb:d3ff:fe55:dc01 prefixlen 64 scopeid 0x20<link>

ether e8:eb:d3:55:dc:01 txqueuelen 1000 (Ethernet)

RX packets 0 bytes 0 (0.0 B)

RX errors 0 dropped 0 overruns 0 frame 0

TX packets 51 bytes 6612 (6.6 KB)

TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Here are the interfaces on the x410:

eth0 Link encap:Ethernet HWaddr 00:80:2F:36:2B:C6

inet addr:192.168.0.165 Bcast:192.168.0.255 Mask:255.255.255.0

inet6 addr: fe80::280:2fff:fe36:2bc6/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:4232 errors:0 dropped:988 overruns:0 frame:0

TX packets:335 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:440934 (430.5 KiB) TX bytes:37656 (36.7 KiB)

Interrupt:19

int0 Link encap:Ethernet HWaddr AE:4A:B9:D0:0B:25

inet addr:169.254.0.1 Bcast:169.254.0.255 Mask:255.255.255.0

inet6 addr: fe80::ac4a:b9ff:fed0:b25/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1

RX packets:17079 errors:0 dropped:0 overruns:0 frame:0

TX packets:17134 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:1127294 (1.0 MiB) TX bytes:1136890 (1.0 MiB)

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING MTU:65536 Metric:1

RX packets:973 errors:0 dropped:0 overruns:0 frame:0

TX packets:973 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:73015 (71.3 KiB) TX bytes:73015 (71.3 KiB)

sfp0 Link encap:Ethernet HWaddr 00:80:2F:36:2B:C7

inet addr:192.168.10.2 Bcast:192.168.10.255 Mask:255.255.255.0

inet6 addr: fe80::280:2fff:fe36:2bc7/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1

RX packets:288 errors:0 dropped:0 overruns:0 frame:0

TX packets:560 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:38774 (37.8 KiB) TX bytes:137733 (134.5 KiB)

sfp0_1 Link encap:Ethernet HWaddr 00:80:2F:36:2B:C8

inet addr:192.168.11.2 Bcast:192.168.11.255 Mask:255.255.255.0

inet6 addr: fe80::280:2fff:fe36:2bc8/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1

RX packets:335 errors:0 dropped:0 overruns:0 frame:0

TX packets:94 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:45298 (44.2 KiB) TX bytes:14410 (14.0 KiB)

sfp0_2 Link encap:Ethernet HWaddr 00:80:2F:36:2B:C9

inet addr:192.168.12.2 Bcast:192.168.12.255 Mask:255.255.255.0

inet6 addr: fe80::280:2fff:fe36:2bc9/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1

RX packets:657 errors:0 dropped:0 overruns:0 frame:0

TX packets:66 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:162231 (158.4 KiB) TX bytes:10541 (10.2 KiB)

sfp0_3 Link encap:Ethernet HWaddr 00:80:2F:36:2B:CA

inet addr:192.168.13.2 Bcast:192.168.13.255 Mask:255.255.255.0

inet6 addr: fe80::280:2fff:fe36:2bca/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1

RX packets:325 errors:0 dropped:0 overruns:0 frame:0

TX packets:168 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:41365 (40.3 KiB) TX bytes:22845 (22.3 KiB)

Maybe we set up our netplan rules wrong, here is an example of what we
currently have for one of the interfaces:

network:

version: 2

renderer: NetworkManager

ethernets:

ens17f0np0:

dhcp4: no

dhcp6: no

addresses: [192.168.10.3/24]

nameservers:

addresses: [8.8.8.8,8.8.4.4]

Thank you so much for your time and help.

USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-leave@lists.ettus.com

I've reached out to the other members of the Ettus support organization
-- I'm hampered by not having an X410 in my collection,
so I'm unfortunately running a bit "blind". Some patience may be
required--a goodly fraction of the support team are at
a conference for the next two days.

On 31/05/2023 12:41, pistachio6981@gmail.com wrote: > > the image should be just fine, there are no other devices that are on > the same subnet as the sdr interfaces are on. Here are interfaces on > the server that is trying to connect to the x410: > > ens18: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > > inet 192.168.0.148 netmask 255.255.255.0 broadcast 192.168.0.255 > > inet6 fe80::d75b:dde7:bb0d:bf0e prefixlen 64 scopeid 0x20<link> > > ether 22:73:df:f4:97:21 txqueuelen 1000 (Ethernet) > > RX packets 1766 bytes 402332 (402.3 KB) > > RX errors 0 dropped 119 overruns 0 frame 0 > > TX packets 1444 bytes 2596987 (2.5 MB) > > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > ens17f0np0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > > inet 192.168.10.3 netmask 255.255.255.0 broadcast 192.168.10.255 > > inet6 fe80::eaeb:d3ff:fe43:3ec8 prefixlen 64 scopeid 0x20<link> > > ether e8:eb:d3:43:3e:c8 txqueuelen 1000 (Ethernet) > > RX packets 0 bytes 0 (0.0 B) > > RX errors 0 dropped 0 overruns 0 frame 0 > > TX packets 51 bytes 6608 (6.6 KB) > > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > ens17f1np1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > > inet 192.168.11.3 netmask 255.255.255.0 broadcast 192.168.11.255 > > inet6 fe80::eaeb:d3ff:fe43:3ec9 prefixlen 64 scopeid 0x20<link> > > ether e8:eb:d3:43:3e:c9 txqueuelen 1000 (Ethernet) > > RX packets 0 bytes 0 (0.0 B) > > RX errors 0 dropped 0 overruns 0 frame 0 > > TX packets 51 bytes 6617 (6.6 KB) > > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > ens27f0np0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > > inet 192.168.12.3 netmask 255.255.255.0 broadcast 192.168.12.255 > > inet6 fe80::eaeb:d3ff:fe55:dc00 prefixlen 64 scopeid 0x20<link> > > ether e8:eb:d3:55:dc:00 txqueuelen 1000 (Ethernet) > > RX packets 0 bytes 0 (0.0 B) > > RX errors 0 dropped 0 overruns 0 frame 0 > > TX packets 51 bytes 6633 (6.6 KB) > > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > ens27f1np1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > > inet 192.168.13.3 netmask 255.255.255.0 broadcast 192.168.13.255 > > inet6 fe80::eaeb:d3ff:fe55:dc01 prefixlen 64 scopeid 0x20<link> > > ether e8:eb:d3:55:dc:01 txqueuelen 1000 (Ethernet) > > RX packets 0 bytes 0 (0.0 B) > > RX errors 0 dropped 0 overruns 0 frame 0 > > TX packets 51 bytes 6612 (6.6 KB) > > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > Here are the interfaces on the x410: > > eth0 Link encap:Ethernet HWaddr 00:80:2F:36:2B:C6 > > inet addr:192.168.0.165 Bcast:192.168.0.255 Mask:255.255.255.0 > > inet6 addr: fe80::280:2fff:fe36:2bc6/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:4232 errors:0 dropped:988 overruns:0 frame:0 > > TX packets:335 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:440934 (430.5 KiB) TX bytes:37656 (36.7 KiB) > > Interrupt:19 > > int0 Link encap:Ethernet HWaddr AE:4A:B9:D0:0B:25 > > inet addr:169.254.0.1 Bcast:169.254.0.255 Mask:255.255.255.0 > > inet6 addr: fe80::ac4a:b9ff:fed0:b25/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 > > RX packets:17079 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:17134 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:1127294 (1.0 MiB) TX bytes:1136890 (1.0 MiB) > > lo Link encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > inet6 addr: ::1/128 Scope:Host > > UP LOOPBACK RUNNING MTU:65536 Metric:1 > > RX packets:973 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:973 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:73015 (71.3 KiB) TX bytes:73015 (71.3 KiB) > > sfp0 Link encap:Ethernet HWaddr 00:80:2F:36:2B:C7 > > inet addr:192.168.10.2 Bcast:192.168.10.255 Mask:255.255.255.0 > > inet6 addr: fe80::280:2fff:fe36:2bc7/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 > > RX packets:288 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:560 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:38774 (37.8 KiB) TX bytes:137733 (134.5 KiB) > > sfp0_1 Link encap:Ethernet HWaddr 00:80:2F:36:2B:C8 > > inet addr:192.168.11.2 Bcast:192.168.11.255 Mask:255.255.255.0 > > inet6 addr: fe80::280:2fff:fe36:2bc8/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 > > RX packets:335 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:94 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:45298 (44.2 KiB) TX bytes:14410 (14.0 KiB) > > sfp0_2 Link encap:Ethernet HWaddr 00:80:2F:36:2B:C9 > > inet addr:192.168.12.2 Bcast:192.168.12.255 Mask:255.255.255.0 > > inet6 addr: fe80::280:2fff:fe36:2bc9/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 > > RX packets:657 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:66 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:162231 (158.4 KiB) TX bytes:10541 (10.2 KiB) > > sfp0_3 Link encap:Ethernet HWaddr 00:80:2F:36:2B:CA > > inet addr:192.168.13.2 Bcast:192.168.13.255 Mask:255.255.255.0 > > inet6 addr: fe80::280:2fff:fe36:2bca/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 > > RX packets:325 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:168 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:41365 (40.3 KiB) TX bytes:22845 (22.3 KiB) > > Maybe we set up our netplan rules wrong, here is an example of what we > currently have for one of the interfaces: > > network: > > version: 2 > > renderer: NetworkManager > > ethernets: > > ens17f0np0: > > dhcp4: no > > dhcp6: no > > addresses: [192.168.10.3/24] > > nameservers: > > addresses: [8.8.8.8,8.8.4.4] > > Thank you so much for your time and help. > > > _______________________________________________ > USRP-users mailing list -- usrp-users@lists.ettus.com > To unsubscribe send an email to usrp-users-leave@lists.ettus.com I've reached out to the other members of the Ettus support organization -- I'm hampered by not having an X410 in my collection, so I'm unfortunately running a bit "blind". Some patience may be required--a goodly fraction of the support team are at a conference for the next two days.

P

pistachio6981@gmail.com

Tue, Jun 6, 2023 2:47 PM

Sorry to bother again, but was there any other suggestions give by any other members of the Ettus support organization on this issue?

usrp-users@lists.ettus.com

x410 help