You are currently browsing the tag archive for the ‘firewalls’ tag.

I had a set of applications deployed on a Process Server however they would not start as a remote server – a MQ server – was behind a firewall and was inaccessible.  This firewall allowed the SSH port (23) however, so, naturally, I employed SSH tunnelling.

I used a technique to avoid having to modify the applications to use localhost as the hostname in order to direct traffic to go via SSH tunnel instead of directly to the firewalled MQ server.  In /etc/hosts, I added “vm123.developer.ihost.com” (the MQ server) to the “127.0.0.1″ line.  This would trick the applications into using 127.0.0.1 for the MQ server.  The SSH tunnel command needed changing however to use IP address instead of the host name, for example:

ssh -f bjfletcher@vm123.developer.ihost.com -L 1414:vm123.developer.ihost.com:1414 -N

to:

ssh -f bjfletcher@123.45.67.89 -L 1414:123.45.67.89:1414 -N

This was to use the actual MQ server through the IP address for the SSH tunnel whereas the applications would use the SSH tunnel itself through the host name.  Nice and easy huh? :-)

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 3 other followers

Author

I work in IBM Software Services for WebSphere and Lotus (ISSW and ISSL respectively), who do specialist work for customers. Contact ISSW or ISSL for more details. I can also be contacted through email. Any views here are my own and don’t necessarily represent IBM’s positions, strategies or opinions.
Follow

Get every new post delivered to your Inbox.