Guyz,

I m stuck in a problem. I have made a test network to test one of my application. A linux(say "LxNAT") machine having 2 ethernet card is supposed to serve NATING. The senarios is :

LxNAT ----- Having Two interface cards eth0 , eth1
eth1 = connected to main switch with ip address 192.168.1.190. On this switch we have alots of other system with in ip pool of 192.168.1.x.

eth0 = connected to a separte isolated switch and having ip address of 10.1.0.1 .On this isolated switch i have another windows machine connected with ip address 10.1.0.10. and default gateway 10.1.0.1

Now what i want is to access this internal windows machine at 10.1.0.10 from any of my external machines 192.168.1.x . For this purpose i need to do static NATing at LxNAT machine via iptables.

More clearly what i want is to assign an ip address from 192.168.1.x pool say 192.168.1.211 to my internal windows machine (10.1.0.10). So that when i ping from let say 192.168.1.20 to 192.168.1.211 the request is routed from LxNAT to internal windows machine 10.1.0.10.
and vice versa.

I need IPTABLE rules ?

Thanks in advance.

I want to do it with IPTABLES. I know that SHOREWALL can do that for me but i want to stick with IPTABLE rules.

You can actually do it in many ways.

If 192.168.1.190 can act as the default gateway for its class (like the way 10.1.0.1 is) then you dont even need NATing. Switching ON the ip_forwarding at kernel will do the needful.

Or otherwise you can make 192.168.1.x class default router to re-route packets destined for 10.1.0.10 to 192.168.1.190. (if you have access & rights to configure it)

If you precisely want to achieve this, then you got to give your linux box a virtual ip of .211 & then forward all or desired packets over to 10.1.0.10 with You can still achieve the same without placing that virtual ip as well.

p.s : Also make sure that switch on the ip-forwarding at kernel level prior to this.

Thanks amit, Yes precicely i want to do that. Now by applying your suggestion can i access both networks from both ends.

Means Ping from External to Internal and from Internal to external network will work ?

One more thing how can i add virtual ip to my box. i m using fedora 5 ?

amit i check this solution. It worked well but from one side . Means i can ping from my external network of 192.168.1.X to my windows machine at 10.1.0.1 but not the other way round. Wht i want to ask is wht shud i do to make it work other way round, so that i will be able to ping from internal to external network.

Thanks,

We did not create any ruleset for the other way round. Look until now; whenever any box from 192.168.1.x subnet connect/browse/use-any-other-service to 192.168.1.211 (virtual ip) it's being forwarded to 10.1.0.10. We are able to do it succesfully. So now when you ask to do it the other way... please specify it precisely with example ip schema (like to whom you want to connect to & from where ?) & then we got to create another iptables ruleset for it to bring it in effect. Our present ruleset doesnt do anything fancy other than we have asked it to.