On 26 May 2015 at 12:56, Jim Rippon jim@rippon.me.uk wrote:
It sounds like what you'll need to create is a DNAT on your linux machine. That will require a couple of things to be set up. I'm doing this from memory, so I'd recommend reading up on your distributions forums how to implement NAT forwarding as well, since I may have missed things or suggest something that will get undone automatically for you :)
Thanks for this and sorry for the tardy response.
I tried the commands as you wrote them, which were all accepted except: iptables -t nat -A POSTROUTING -s 192.168.2.100 -j SNAT --to-destination 192.168.1.11 .. which I had to change to: iptables -t nat -A POSTROUTING -s 192.168.2.100 -j SNAT --to 192.168.1.11
But I couldn't get it to actually work. I spent a while with Google before I received a call from the people who wrote the Windows software who gave me an alternative workaround, so the original need went away.
I'd still like to get this working though. In order that I can research this more fruitfully, what's the technical term for what I am actually trying to do? Is "creating a DNAT" sufficient or is that too broad?
A good (albeit slightly dated) grounding in IPTables and networking can be found in the Linux Advanced Routing and Traffic Control HOWTO at http://www.lartc.org, also the Linux-IP documentation site at http://linux-ip.net has lots of relevant information and examples.
I will spend some time here too, thanks.