I've been scratching my head over this, FW on the client looks ok to me.
[root@www-stage ~]# /sbin/iptables -L | grep curie
ACCEPT udp -- curieb.wadsworth.org anywhereudp spts:932:948
dpt:amanda
ACCEPT tcp -- curieb.wadsworth.org anywheretcp
3.146: received ACK pkt:
amandad: time 33.146: stream_accept: timeout after 30 seconds
amandad: time 33.146: stream 0 accept failed: bad SECURITY line: ''
amandad: time 63.146: stream_accept: timeout after 30 seconds
amandad: time 63.146: stream 1 accept failed: bad SECURITY line: ''
amandad
On 04/12/2013 11:52 AM, Brian Cuttler wrote:
amandad: try_socksize: send buffer size is 65536
amandad: try_socksize: receive buffer size is 65536
amandad: time 3.128: bind_portrange2: trying port=831
amandad: time 3.129: stream_server: waiting for connection: 0.0.0.0.36507
amandad:
Jean-Louis,
Yes, the ability to hit the socket makes sense, especially as
amcheck is ok and amdump, which uses many more network resources,
does not.
I'm not seeing the failures I'd expect to see, which may simply
mean I don't actually know what I'm looking for.
The failure bad security is
