Flik, > 1. Jmeter client touches RMI server via tunnel. > 2. Jmeter client obtains information of jmeter server, like IP address, > Server Listening Port and etc. > 3. Jmeter client creates new socket directly to server according to IP > address and port obtained. > 4. If it is successful to create socket, test plan will be transferred to > jmeter server, if not error will be logged.
This sounds just right. > My real concern is whether jmeter server is reachable when it stay on > non-public IP address behind a firewall. 10.x.x.x is non-public, so I assume the server is just in another LAN of your company's, reachable via a router/firewall. > Which IP address Jmeter server registers itself in RMI server, its own one or > the firewall's? The server has no way of knowing the firewall's IP address. You *could* trick jmeter using an /etc/hosts entry, but then the firewall would positively need NAT rules. > It might be unreachable when it uses its own. SSH is reachable via the server's own address. You probably only need to ask your admin to open the Jmeter relevant ports for similar routing. Then SSH tunneling will be completely unnecessary. > Similarly, if I want keep information transition safe and using SSH tunnel, > it might not work. As stated previously, your Jmeter server must believe it was reachable via 127.0.0.1 (as per /etc/hosts), otherwise communication will certainly not work. > If anything is wrong, please correct me. There is some confusion about your actual topography. Can you ping the Jmeter server from your box? If so, please do a traceroute to your server and include the output (unless it's huge). Cheers, Felix --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
