Hi Rob,
Often you can get around a complex solution with a little hack:
I presume you want a "thin connection, lesser CPU" computer ("Smarts") to
control the USRP, while you want a beefy machine ("Beef") to capture the stream.
At least for the X310, it works to use a static route on Smarts that declares
that the USRP can be reached through a secondary network interface on Beef.
That machine then gets ebtables or iptables rules to forward all traffic coming
from Smarts to the USRP and to forward all packets from the USRP to the Smarts,
_except_ for the CHDR sample packets on their dedicated port.
Those, you sniff up with a self-written program. Since you don't have to
support the full flexibility, reordering and feature set of UHD, that might be
a pretty efficient solution. If Beef's network card supports hardware sorting
packets for specific ports into separate RX ring buffers, you could possibly
even use a kernel bypass and just directly poll these buffers from userland;
but that would be deeper into the realm of performance optimization than you
might need to go.
Best regards,
Marcus
On 19 May 2018 20:34:46 GMT+02:00, Neel Pandeya via USRP-users
<[email protected]> wrote:
>Hello Rob:
>
>This capability is not supported with the multi_usrp API on the X300,
>X310,
>N310.
>
>It was supported on the N200/N210.
>
>https://files.ettus.com/manual/page_usrp2.html#usrp2_altstream
>
>However, this capability is supported for the X300, X310, N310 using
>the
>RFNoC API.
>
>--Neel Pandeya
>408-610-6370
>
>
>
>
>On 7 May 2018 at 15:55, Rob Kossler via USRP-users <
>[email protected]> wrote:
>
>> Hi,
>> I am using UHD from a custom c++ application and I would like to
>control
>> the USRP from one port and send the Rx streaming samples to a
>separate
>> application at a different IP address using the other USRP SFP port.
>I
>> found in the documentation for stream_args_t that there are "port"
>and
>> "addr" args that can be set to send the streaming to an alternate
>> destination.
>>
>> When I specify these args, I am not seeing traffic on the specified
>> addr/port. This occurs using an N310. I would like this
>functionality to
>> work for both X310 and N310. I am wondering if I am missing a step
>or
>> two. Please let me know.
>>
>> Rob
>>
>> _______________________________________________
>> USRP-users mailing list
>> [email protected]
>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>
>>
--
This was written on my cellular phone. whilst an impressive piece of
engineering, this might not be the perfect device to write emails on - please
excuse my brevity._______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
