E
ed
Hello,
At my office, we have an internal LAN (192.168.1.X). We have added a
networked cluster of 20 computers. We wish to have these 20 on a
separate subnet (192.168.2.X).
The 20 computers are connected to a switch. The switch is connected to
a D-Link router via one of the router LAN ports. The D-Link router is
connected to the 192.168.1.X network via the router's WAN port. So the
router has a static WAN IP (192.168.1.60) on the 192.168.1.X network.
On the cluster LAN side the router is 192.168.2.1. The 20 cluster
computers have IPs ranging from 192.168.2.51 to 192.168.2.70.
Any of the cluster computers can ping each other (e.g. 192.168.2.51
pings 192.168.2.52) and can also ping computers on the 192.168.1.X
network (e.g. 192.168.2.51 pings 192.168.1.53). However, computers on
the 192.168.1.X network cannot ping computers on the 192.168.2.X
network. Is this an expected result? My expectation was that I could
sit at one of the 192.168.1.X computers, add a route like so:
route add 192.168.2.0 mask 255.255.255.0 192.168.1.60
and then ping the 192.168.2.X computer using the cluster router as the
gateway. We have configured the cluster router firewall to allow all
types of traffic on all ports. Still, it doesn't work. I probably
have a conceptual issue here. Does NAT only work in the outgoing
direction?
Regards,
Ed.
At my office, we have an internal LAN (192.168.1.X). We have added a
networked cluster of 20 computers. We wish to have these 20 on a
separate subnet (192.168.2.X).
The 20 computers are connected to a switch. The switch is connected to
a D-Link router via one of the router LAN ports. The D-Link router is
connected to the 192.168.1.X network via the router's WAN port. So the
router has a static WAN IP (192.168.1.60) on the 192.168.1.X network.
On the cluster LAN side the router is 192.168.2.1. The 20 cluster
computers have IPs ranging from 192.168.2.51 to 192.168.2.70.
Any of the cluster computers can ping each other (e.g. 192.168.2.51
pings 192.168.2.52) and can also ping computers on the 192.168.1.X
network (e.g. 192.168.2.51 pings 192.168.1.53). However, computers on
the 192.168.1.X network cannot ping computers on the 192.168.2.X
network. Is this an expected result? My expectation was that I could
sit at one of the 192.168.1.X computers, add a route like so:
route add 192.168.2.0 mask 255.255.255.0 192.168.1.60
and then ping the 192.168.2.X computer using the cluster router as the
gateway. We have configured the cluster router firewall to allow all
types of traffic on all ports. Still, it doesn't work. I probably
have a conceptual issue here. Does NAT only work in the outgoing
direction?
Regards,
Ed.