Basic Routing

[Dave]

This should be straightforward, but I must be having a
brain lapse.

The client PC has an internal IP address of
192.168.101.46 and a gateway of 192.168.101.45 (the
following server)

The server has an external address of 81.144.208.10 and a
gateway (a router) of 81.144.208.1

The internal card is 192.168.101.45 - but what does it's
gateway need to be and what do I need to do to setup the
routing to allow the client PC to connect to the internet
through the server (it will be running a checkpoint
firewall eventually to test some bits we want to play
with)

 

[Fritz]

You don't need to set the gateway on the internal NIC. Checkpoint should
handle the routing between the two NICs.

 

[Fritz]

....or you could set the gateway on the internal NIC to the IP External IP
(the other NIC).

 

[Dusty Harper {MS}]

You are moving from a private address space ( 192.168 ) to a public address
space ( 81 ). This requires NAT on the router. You only configure NIC with
a default gateway, which you have already done.

 

[Bill Grant]

router
81.144.208.1
|
81.144.208.10 dg 81.144.208.1
server
192.168.101.45 dg blank
|
client
192.168.101.46 dg 192.168.101.45

To see the router and anything beyond it from the 192.168.101 subnet,
the router must know where the 192.168.101 subnet is! If the server is
doing NAT, that will solve the problem, because all traffic reaching the
router will use the server's 81.144.208 address. You can't really connect a
private addressed machine to the Internet without NAT or proxy. The firewall
will provide that.

 

[Fritz]

Checkpoint will do NAT routing.

You are moving from a private address space ( 192.168 ) to a public
address
space ( 81 ). This requires NAT on the router. You only configure NIC
with
a default gateway, which you have already done.

--