I concur. As a matter of fact, opening the firewall has been the only fuss I've yet had with Jmeter Server ports.
Adding a route via 127.0.0.1 is wrong. Rather, the Jmeter Server should be made to believe its own IP was in fact 127.0.0.1, so it will tell the client to connect to that IP/Port. Is the 10.x.x.x subnet visible to your client node? If so, why are tunnels necessary. If not, am I correct to assume that the SSH tunnel is opened via some sort of NAT? Cheers, Felix On 07/22/2010 07:58 AM, chaitanya bhatt wrote: > Flik, > > Have you tried this without SSH tunneling(probably you might have to disable > firewall for 1099 and 4000 ports. Trust me, its worth giving a try). > The aim here is not the avoid using SSH but to determine if the problem is > with SSH tunneling or whether its with the basic jmeter client-server > communication itself. Once your sure that jmeter client-server communication > works without SSH, then you can start working towards nailing down the > problem with RMI over SSH process. Without which you would be trying to find > a needle in the haystack(or in the stack-trace ;) ) which is obviously > painful. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
