I did it with 192.168.10.3 for ethernet and 192.168.10.3 & also 192.168.10.4 
for USRP2 but that doesn't help either!?


    On Thursday, October 18, 2018, 4:21:58 PM EDT, Marcus D. Leech 
<[email protected]> wrote:  
 
  On 10/18/2018 04:14 PM, Farhad Mirkazemi wrote:
  
   
  Hi Marcus, 
  Thanks for your reply;
  I have only one ethernet interface on my PC but I connect my usrp's on and 
off, first one works pretty ok for a long time now but the problem occurs when 
I try to connect the second usrp when the first one is not (can not be) 
connected (I don't have ethernet switch either). Any idea? 
  
   
    
  
      On Thursday, October 18, 2018, 4:06:20 PM EDT, Marcus D. Leech via 
USRP-users <[email protected]> wrote:  
  
      On 10/18/2018 02:51 PM, Farhad Mirkazemi via USRP-users wrote:
  
   Hi,  
  I have set up my first usrp2 on Ubuntu with its default ip address 
(192.168.10.2), with the ethernet ip address 192.168.10.1 and subnet mask 
255.255.255.0 and working with UHD fine; for some reasons, I need to use a 
second usrp2 which is with the same image and firmware update as the first one 
but when I set a second network with ethernet ip address 192.168.20.1 and same 
subnet mask as previous one and then set the second usrp address to a new one 
as 192.168.20.2, I receive the error like no device found ---> empty device 
address. When I use ping command, it operates ok with both ethernet networks 
but unable to recognize the device. Can you please help!? 
  Thanks,   
 
  So, you have two different ethernet interfaces on your host PC, with the two 
USRP2s on them, or a different configuration?
 
 
   _______________________________________________
 USRP-users mailing list
     
 Well, since a given interface can only be on a single subnet, I suggest 
changing the address of your 2nd USRP2 to 192.168.10.3, and using that
   address for your 2nd USRP2.
 
 
   
_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Reply via email to