getting around SASL

[Carter Bullard]

Hey Russell,
The option should be "-M sasl_mech='none' ", not "-m ….".  The -m option is
to specify the flow aggregation key.

What error do you get with you don't specify anything on the command line?

Argus or radium dictate the protection strategy on the connection.
You need to satisfy them to get data from them.  If you can't get an algorithm
on the client end, you'll have to get the argus or radium configuration
changed.

Carter


On Mar 27, 2012, at 6:47 PM, Russell Fulton wrote:

> Hi Folks
> 
> I very rarely need to connect to a live server with any of the ra clients but I am now helping networks diagnose some problems in realtime.
> 
> When I try and use -S localhost I get:
> 
> [rful011 at mon263595 ~]$ ratop -S localhost -m sasl_mech='none'
> ArgusError: 11:42:02.985177 RaSaslNegotiate: error starting SASL negotiation SASL(-4): no mechanism available: No worthy mechs found
> 
> I tried to suppress sasl with the -m but that did not work.
> 
> Help! :)
> 
> Do I have to recompile everything without SASL support?
> 
> Russell
> 
> 

-------------- 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/20120327/9392db45/attachment.bin>