Since the communication channel to the radio is not IP based, seems to me that the waters would be muddied by “faking” it.
Sent from my iPhone > On Jun 10, 2019, at 7:17 AM, Jason Matusiak <ja...@gardettoengineering.com> > wrote: > > Bingo, thanks. One note though, the type is e3x0 (not e300). > > Doesn't the e310 understand an IP address of 127.0.0.1 though? I would think > that something like that would be a perfect use-case for the localhost. > > > From: USRP-users <usrp-users-boun...@lists.ettus.com> on behalf of Marcus D. > Leech via USRP-users <usrp-users@lists.ettus.com> > Sent: Friday, June 7, 2019 5:34 PM > To: usrp-users@lists.ettus.com > Subject: Re: [USRP-users] E320 hogging the network > >> On 06/07/2019 03:05 PM, Jason Matusiak via USRP-users wrote: >> 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. >> > For the case of running E310 apps *on* the E310, just use "type=e300", radio > hardware on the E310 itself doesn't *have* an IP address, so using > addr= will simply cause UHD to go down the wrong device path when you're > running it ON the E31x itself. > >
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
