timed_out: yes while traversing a firewall

[adityagawade27]

Hello,
We are using Arachne to test our network health. It works perfectly fine in our lab environment which has hosts in different vlans . However, on deploying it on a fire-walled environment I can see timed_out: yes on all the separated hosts. The tcpdump capture does not show any issues and the behavior is same as on a lab environment. The firewall seems to block repeated new connections on the same ports and filter out ACK packets. Is there any recommended method to deploy Arachne in an environment where the hosts are firewall separated. Please let me know. Thank you.

[henridevieux]

Hi,
This is an interesting problem. Currently, I think the only solution would be to reconfigure the firewall to allow the connections that it is currently blocking (perhaps whitelisting the port that connection attempts are made to).

We don't currently support multiple or randomized destination ports, only the source port range can be configured.