OK, this is actually an E310 problem. The E310 always looks off device first. A coworker reminded me that we spent a couple days years back trying to figure out why the device was asking like it was working, but we weren't seeing any results. It was because it was actually talking to an N2xx on the network even with the IP address arg.
We never found a solution (using both the 127 and 192 address as an argument still causes issues). So, it would be nice to clean this up on the E310 at some point, but for now I will try not to mix the E310 and E320 on the same subnet. ________________________________ From: Jason Matusiak Sent: Friday, June 7, 2019 12:41 PM To: Nate Temple Cc: Marcus D Leech; Philip Balister; Ettus Mail List Subject: Re: [USRP-users] E320 hogging the network OK, maybe based on my last email (which crossed yours I think). The addr flag doesn't seem to work at all with the uhd_usrp_probe on the E310 (at least my version). ________________________________ From: Nate Temple <nate.tem...@ettus.com> Sent: Friday, June 7, 2019 12:37 PM To: Jason Matusiak Cc: Marcus D Leech; Philip Balister; Ettus Mail List Subject: Re: [USRP-users] E320 hogging the network Hi Jason, For what its worth, I haven't personally ran this exact combo (E310 w/ UHD 3.11 and E320 w/ 3.14) on the same subnet, but I have ran two N320's on the same subnet (192.168.10.2 and 192.168.10.3, both with 3.14). I did run into the issue where probing in embedded mode would pickup the other device first, but when providing a localhost addr, it worked as expected. I could use both devices from a common host in network mode. Trying the E320/E310 on different subnets would be worth a try. I'll open an internal issue on our bug tracker for this, there is likely improvements we can make to the device discovery. Regards, Nate Temple On Fri, Jun 7, 2019 at 9:22 AM Jason Matusiak <ja...@gardettoengineering.com<mailto:ja...@gardettoengineering.com>> wrote: Howdy. Nope, but it fails in a weird way. I disconnected the E320 to make sure this issue wasn't due to it, but it still acts the same. If I run: uhd_usrp_probe --args "addr=127.0.0.1" root@ettus-e3xx-sg3:~# uhd_usrp_probe --args "addr=127.0.0.1" [INFO] [UHD] linux; GNU C++ version 7.3.0; Boost_106400; UHD_3.11.0.1-0-unknown Error: i2c_zc_impl recv timeout Reading up on the USRP2, they specifically say that you need to be on different subnets if you are using more than on device. I wonder if this is the case here too? https://files.ettus.com/manual/page_usrp2.html#usrp2_network_multidev ________________________________ From: Nate Temple <nate.tem...@ettus.com<mailto:nate.tem...@ettus.com>> Sent: Friday, June 7, 2019 12:17 PM To: Jason Matusiak Cc: Marcus D Leech; Philip Balister; Ettus Mail List Subject: Re: [USRP-users] E320 hogging the network Hi Jason, On the E310, if you pass the device arg addr with 127.0.0.1 does it work as expected? uhd_usrp_probe --args "addr=127.0.0.1" Regards, Nate Temple On Fri, Jun 7, 2019 at 9:10 AM Jason Matusiak via USRP-users <usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com>> wrote: Darn, I was hoping that was it, but I don't think so. Here is the result from my E310: eth0 Link encap:Ethernet HWaddr 00:80:2F:25:44:46 and now the E320: sfp0 Link encap:Ethernet HWaddr 00:80:2F:24:C2:FB If I ping each device on my host, then run arp, I see this (the mac addresses match up correctly): Address HWtype HWaddress Flags Mask Iface 192.168.10.45 ether 00:80:2f:24:c2:fb C p4p1 192.168.10.95 ether 00:80:2f:25:44:46 C p4p1 I figured that that would be fine though because I have the same issue when I am running commands ON my E310. And if it was a routing issue, it would mean that both my machine and the E310 and the E320 were being screwed up. ________________________________ From: Marcus D Leech <patchvonbr...@gmail.com<mailto:patchvonbr...@gmail.com>> Sent: Friday, June 7, 2019 12:01 PM To: Jason Matusiak Cc: Philip Balister; Ettus Mail List Subject: Re: [USRP-users] E320 hogging the network Check the MAC addresses. I know that on some ARM platforms that has to be programmed in at boot and perhaps these system images have it set to the same value. Sent from my iPhone On Jun 7, 2019, at 11:52 AM, Jason Matusiak via USRP-users <usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com>> wrote: Philip, They have unique addresses (10.95 and 10.45). It is really weird that when I am on the E310, and set the ip-addr to himself, that he would even look off the device.... They both have hostnames and they are not similar to each other at all. ________________________________ From: Philip Balister <phi...@balister.org<mailto:phi...@balister.org>> Sent: Friday, June 7, 2019 11:10 AM To: Jason Matusiak; Ettus Mail List Subject: Re: [USRP-users] E320 hogging the network Check each ones ip address, likely by running ifconfig. In the back of my mind, I recall something like this in the E100 days. Do they have the same hostname? Philip On 06/07/2019 07:37 AM, Jason Matusiak via USRP-users wrote: > It looks like I am misunderstanding something with how the E320 handles the > network. > > > I have my E320 on my subnet with the sfp0 assigned to 10.45 (instead of the > default 10.2). I can ssh into it and things seem to run fine in embedded > mode. > > > Now, if I ssh onto an E312 that is on the same network (IP 10.95), it doesn't > work right as long as the E320 is plugged in. When I do a probe or run any > other UHD-type commands on the E310, it seems to always talk to the E320 > first and it screws everything up. It doesn't matter if I put the E310's > address into the command or not, the E320 responds. I also remember seeing > this occur when I was on my host machine running commands (the E320 bullied > its way into being the main attraction). > > > My current work-around is to unplug Ethernet from the E320, run my command on > the E310, plug back into the E320, then run its command. This seems to allow > things to work as I intended, but is obviously not ideal and is fairly > difficult to do when devices are remote. > > > So what am I missing here? > > > > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com<mailto:USRP-users@lists.ettus.com> > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com USRP-users Info Page - Ettus<http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com> lists.ettus.com<http://lists.ettus.com> To see the collection of prior postings to the list, visit the USRP-users Archives.. Using USRP-users: To post a message to all the list members, send email to usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com>. You can subscribe to the list, or change your existing subscription, in the sections below. > _______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com<mailto:USRP-users@lists.ettus.com> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com _______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com<mailto:USRP-users@lists.ettus.com> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
