argus_output_stream
Carter Bullard
carter at qosient.com
Wed Nov 1 17:13:39 EDT 2017
Hey Phillip,
Its suppose to be:
ra -S argus-udp://x.y.z.w:port
At least that was what we intended ????
Carter
Carter Bullard • CTO
150 E 57th Street Suite 12D
New York, New York 10022-2795
Phone +1.212.588.9133 • Mobile +1.917.497.9494
> On Nov 1, 2017, at 4:28 PM, Phillip Deneault <deneaulp at bc.edu> wrote:
>
> I've got a use-case which would be perfect to use argus to push data via argus_output_stream. Instead of going to a multicast address, it would be great if it could simply go to a single address. If I do point argus-udp to a unicast address, it _seems_ to work, as packets are sent to the other destination on udp/561. Huzzah!
>
> However... what do I set up on the other side to listen for this traffic? Argus listens on TCP port, as does all the other ra* services according to the docs.
>
> I can't just change argus-udp to argus-tcp in Argus... as it throws this error...
>
> argus: ArgusError: 01 Nov 17 16:24:29.706660 ArgusInitOutput: open argus-tcp://<ip>:561: No such file or directory
>
> Thoughts? I'm thinking(hoping) there's already a feature somewhere that's just not documented well enough for me to understand.
>
> Thanks,
> Phil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20171101/299d97fc/attachment.html>
More information about the argus
mailing list