argus-clients failing to listen using argus-udp after 3.0.5.11

[Carter Bullard]

Hey Terry,
Any additional information on this issue?
Hope all is most excellent,
Carter


On Feb 20, 2012, at 12:24 PM, Terry Burton wrote:

> On 20 February 2012 17:00, Carter Bullard <carter at qosient.com> wrote:
>> If you were to use "any" instead of 0.0.0.0, does that work?
> 
> Hi,
> 
> It turns out that I'm wrong about the client not binding to the UDP
> socket. The ra process does in fact bind, however the socket is closed
> as soon as data arrives at the port. I will now have to resume my
> investigations tomorrow.
> 
> For reference, any vs 0.0.0.0 both appear to be equivalent and work as
> far as binding is concerned but thanks for the pointer.
> 
> 
> Thanks,
> 
> Terry
> 
> 
>> On Feb 20, 2012, at 11:20 AM, Terry Burton <tez at terryburton.co.uk> wrote:
>> 
>>> Hi,
>>> 
>>> The netflow-related changes introduced in argus-clients between
>>> 3.0.5.10 and 3.0.5.11 appear to have broken argus-udp functionality by
>>> causing them to fail to bind to a local UDP socket when invoked as
>>> follows:
>>> 
>>> ./ra -X -S argus-udp://0.0.0.0:1234
>>> 
>>> 
>>> Thanks again,
>>> 
>>> Terry

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20120304/f13a4535/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4367 bytes
Desc: not available
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20120304/f13a4535/attachment.bin>