possible communication problem with argus on 32 bit system, ra on 64 bit system

[Peter Van Epp]

	Argus isn't 64 bit clean in the current version which is likely your
problem. If you can build it as a 32 bit binary on the 64 bit machine then you
may be OK. For one time_t is assumed to be 32 bits and on a 64 machine it isn't.
Making argus 64 bit clean is one of the goals of argus-2.0.7 (although I don't
think 2.0.7 has even started yet).

Peter Van Epp / Operations and Technical Support 
Simon Fraser University, Burnaby, B.C. Canada


On Fri, Sep 16, 2005 at 06:20:59PM -0600, Richard Johnson wrote:
> I'm using a couple of machines to handle our flow data.  One listens on the
> network and runs argus.  The second runs ra to take the flow data via a
> crossover cable, and store it to an array for analysis.
> 
> When running OpenBSD 3.6 i386 (32 bit intel xeon) machines on each side,
> they communicate just fine.
> 
> When I swap the host running ra out for one based on OpenBSD 3.7 amd64 (64
> bit -- amd opteron) with an otherwise identical ra build to the original, I
> achieve only the following:
> 
> 	argus on 32 bit host sends no data
> 	ra on 64 bit host reports "no data available", and quits
> 
> Meanwhile, the hosts can communicate freely on the crossover cable with
> pings, netcat connections on various ports, ssh logins, etc.  Ergo, it's an
> application layer problem that's affecting only argus->ra.
> 
> Have any of you encountered similar difficulties?
> 
> Is it insane of me to be trying 32 bit and 64 bit machines together like
> this with argus 2.0.6fixes1?  If it's not totally insane, might it be
> possible to work around the structure incompatibilities (which I'm just
> guessing at here) by building and running a 32 bit ra on the 64 bit machine?
> 
> Your hints, guesses, and even brickbats will be greatly appreciated.
> 
> Thanks!
> 
> 
> Richard