On 2021-09-24 5:06 a.m., Thangaraj Mukara Dhakshinamoorthy wrote:

Hallo Markus,

The VM is not recognizing the Ettus N320, but the windows host can see and ping successfully!

*_In Windows Host OS:_*

C:\Program Files\UHD\bin>ipconfig

Windows-IP-Konfiguration

Unbekannter Adapter Management:

Verbindungsspezifisches DNS-Suffix:

IPv4-Adresse  . . . . . . . . . . : 10.2.35.84

Subnetzmaske  . . . . . . . . . . : 255.255.255.255

Standardgateway . . . . . . . . . :

Ethernet-Adapter Ethernet:

Verbindungsspezifisches DNS-Suffix: fritz.box

Verbindungslokale IPv6-Adresse  . : fe80::e868:6c6:349a:434e%14

IPv4-Adresse  . . . . . . . . . . : 192.168.178.43

Subnetzmaske  . . . . . . . . . . : 255.255.255.0

Standardgateway . . . . . . . . . : 192.168.178.1

Ethernet-Adapter VirtualBox Host-Only Network:

Verbindungsspezifisches DNS-Suffix:

Verbindungslokale IPv6-Adresse  . : fe80::68b9:4e91:4875:8e30%9

IPv4-Adresse  . . . . . . . . . . : 192.168.56.1

Subnetzmaske  . . . . . . . . . . : 255.255.255.0

Standardgateway . . . . . . . . . :

Ethernet-Adapter Ethernet 2:

Verbindungsspezifisches DNS-Suffix:

Verbindungslokale IPv6-Adresse  . : fe80::ec39:375b:1411:4ebb%4

IPv4-Adresse (Auto. Konfiguration): *169.254.78.187*

Subnetzmaske  . . . . . . . . . . : 255.255.0.0

Standardgateway . . . . . . . . . :

C:\Program Files\UHD\bin>ping 169.254.78.187

Ping wird ausgeführt für 169.254.78.187 mit 32 Bytes Daten:

Antwort von 169.254.78.187: Bytes=32 Zeit<1ms TTL=128

Antwort von 169.254.78.187: Bytes=32 Zeit<1ms TTL=128

Antwort von 169.254.78.187: Bytes=32 Zeit<1ms TTL=128

Antwort von 169.254.78.187: Bytes=32 Zeit<1ms TTL=128

Ping-Statistik für 169.254.78.187:

Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0

(0% Verlust),

Ca. Zeitangaben in Millisek.:

Minimum = 0ms, Maximum = 0ms, Mittelwert = 0ms

C:\Program Files\UHD\bin>uhd_find_devices.exe

[INFO] [UHD] Win32; Microsoft Visual C++ version 14.1; Boost_107000; UHD_4.1.0.1-release

[ERROR] [X300] X300 Network discovery error receive_from: Eine vorhandene Verbindung wurde vom Remotehost geschlossen

[ERROR] [UHD] Device discovery error: receive_from: Eine vorhandene Verbindung wurde vom Remotehost geschlossen

[ERROR] [UHD] Device discovery error: receive_from: Eine vorhandene Verbindung wurde vom Remotehost geschlossen

No UHD Devices Found

[ERROR] [UHD] Device discovery error: receive_from: Eine vorhandene Verbindung wurde vom Remotehost geschlossen

C:\Program Files\UHD\bin>uhd_usrp_probe.exe

[INFO] [UHD] Win32; Microsoft Visual C++ version 14.1; Boost_107000; UHD_4.1.0.1-release

Error: LookupError: KeyError: No devices found for ----->

Empty Device Address

*_In Virtualbox Ubuntu Guest OS:_*

*__*

thangz@thangz-VirtualBox:~/Desktop$ ifconfig

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

inet 10.0.2.15  netmask 255.255.255.0  broadcast 10.0.2.255

inet6 fe80::99d7:4c84:8bab:2aff  prefixlen 64  scopeid 0x20<link>

ether 08:00:27:89:05:93  txqueuelen 1000  (Ethernet)

RX packets 1179  bytes 1293603 (1.2 MB)

RX errors 0  dropped 0  overruns 0  frame 0

TX packets 757  bytes 79260 (79.2 KB)

TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536

inet 127.0.0.1  netmask 255.0.0.0

inet6 ::1  prefixlen 128  scopeid 0x10<host>

loop  txqueuelen 1000  (Local Loopback)

RX packets 250  bytes 22074 (22.0 KB)

RX errors 0  dropped 0  overruns 0  frame 0

TX packets 250  bytes 22074 (22.0 KB)

      TX errors 0  dropped 0 overruns 0  carrier 0 collisions 0

Apparently, the Virtualbox is not recognizing the Ettus N320!

Looking forward to your kind advice.

Regards,

Thangaraj

*Von:*[email protected] <[email protected]>
*Gesendet:* Freitag, 24. September 2021 07:47
*An:* [email protected]
*Betreff:* [USRP-users] Re: Help_Failed to build UHD in Ubuntu 20.04

Hello Thangaraj,

you need to check the  IP-Address of the virtual machine. There’s two different addresses for each SFP on the USRP device. They are depending on both the port and the speed. On mine (X310) they are 192.168.10.2 for the 1GBit/s and 192.168.30.2 or 192.168.40.2.  I guess it is the same with yours. You can first try to ping the device both on the host and the VM.

Best Markus


_______________________________________________
USRP-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Your PING example is pinging the IP address of the host, NOT the USRP N320.  This will always succeed.

You'll need to change the IP address of that network interface to 192.168.10.1, so that it is on the same subnet as the USRP N320 default address for the SFP0 port
  of 192.168.10.2.

Please read:

https://kb.ettus.com/USRP_N300/N310/N320/N321_Getting_Started_Guide#Probe_the_USRP


_______________________________________________
USRP-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to