+

Search Tips   |   Advanced Search


Use a firewall between the Controller and a Load Generator

To use a Controller and Load Generator either side of a firewall, it is necessary to open a TCP port on the Load Generator interface. This connection is established in the Controller-to-Load Generator direction.

Opening this port is sufficient to allow using the remote Load Generator. Other ports must be opened on the firewall to use the automatic discovery function in the Controller-to-Load Generator direction and in the Load Generator-to-Controller direction. When these ports are closed, the load generating machine host name must be declared manually on the Controller.

  1. The TCP port opened by the Load Generator Agent may be changed by editing the [Network]agent.server.port key in the <Load Generator>/conf/agent.properties file on the Load Generator side, and the [Network]agent.port key in the <Controller>/conf/controller.properties file on the Controller side.
  2. The TCP port opened by the Controller may be changed by editing the [Network]controller.server.port key in the <Controller>/conf/controller.properties file.
  3. The UDP port opened by the Load Generator Agent may be changed by editing the [Network]multicast.port key in the <Load Generator>/conf/agent.properties file on the Load Generator side, and the [Network]agent.multicast.port key in the <Controller>/conf/controller.properties file on the Controller. Note that all Load Generators must have the same port declared.


NeoLoad and Windows firewall

Windows features a built-in firewall that is activated by default. When manually running the Generator Agent with Agent.exe, the Windows firewall prompts the user to add the program to the exceptions. When running the program as a service, the firewall does not issue the prompt and automatically blocks the program. The firewall must be configured manually. It is necessary to add the ports to the list of exceptions.


Home