HI!

Someone pl. help me on this;

Description:
I want to communicate/bridge/NAT with 2 diff. subnets 192.168.0.0 (network0) and 192.168.1.0 (network1)which are connected with a debian pc having 2 NICs as follows;

Debina (Server) with 2 NICs

(Network1)
eth1
IP : 192.168.1.1
Subnet: 255.255.255.0
GW: 192.168.0.1
DNS: 192.168.1.1

(Network0)
eth0
IP: 192.168.0.1
Subnet: 255.255.255.0
GW: 192.168.1.1
DNS: 192.168.0.1

Client Side Settings of (Network0)
IP: 192.168.0.2
Subnet: 255.255.255.0
GW: 192.168.0.5
DNS: 192.168.0.5

Client Side Settings of (Network1)
IP: 192.168.1.2
Subnet: 255.255.255.0
GW: 192.168.1.2
DNS: 192.168.1.2

Both the networks are having diff. Gateways which are the IPs of the ADSL modems which are serving internet independently...so the Gateways cudn't be changed. If we change, the browsing cut offs accordingly.

IP_Fwarding is enabled on debian server and I can see both networks on the Debian Server (2NICs) but not able to communicate/see on client PCs from 0 to 1 and vice versa.

Pl. let me know how is it possible to get both networks to see each other PCs both networks are having windows XP PCs & i don't have any cisco router etc.

will really appreciate your help...am stuck-up into it from last 2 months

Azam

well on that box all you need to do is enable ip forwarding (echo 1 > /proc/sys/net/ipv4/ip_forward) but the problem is how to get the traffic to hit that box in the first place. either add routes on *ALL* your clients to route to the destination subnet via that machine, or you*might* be able to put a static route on the ADSL routers to redirect on behalf of the whole network

Appreciate your effort, but the thing is 1's ADSL modem having the multiple static GWs facility but the 0's network ADSL don't have multirouting facility.

secondly I have already enabled the ip fwrding so there's no problem at the linux box server, however the XP clients can't access 0 to 1 and vice versa.

Azam

Upgrade the lame gateway device that doesn't support adding routes.. if you need to route traffic and it doesn't support routing it should not be in that environment, or a device that DOES support routing should be in front of it.