bug?

[Peter Van Epp]

	I can't seem to launch two copies of argus on different interfaces
anymore. I used to do this on 1.8.1. Is there the monitor port defaulting
to an interface (rather than the one on the -i) perhaps? 2.0.0i is running
looking at my backbone and I have an isolated test net on the other interface
where I can run tcpreplay against argus (except I currently can't get both
going at once, I expect command lining the port will fix that tomorrow though).
So far 2.0.0i hasn't seg faulted, but I am still seeing time stamp corruption.
When I get tcpreplay up I'll see if I can reproduce the time stamp corruption.

argus on interface rl0:

root     226  0.0 17.8 93628 92536  v0  S     6:32PM   0:28.92 argus_bpf -i rl0
-w argus.log
root     227  0.0  0.1  1904  716  v0  S     6:32PM   0:03.01 argus_bpf -i rl0 -
w argus.log
root     228  0.1  0.1  1908  692  v0  S     6:32PM   0:06.94 argus_bpf -i rl0 -
w argus.log

a new copy on xl0:

argus_bpf -ixl0 -w t
argus_bpf[326]: 970026160.039157 : ArgusError argus_bpf: ArgusEstablishListen: b
ind() error

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