[LARTC] RE: IP routing

["Bau, Flavien" <fbau@us.infogrames.com>]

[-- Attachment #1: Type: text/plain, Size: 1403 bytes --]

 

Hi all,

 

1- I have a CIPE Linux Box (10.73.0.254) which is in the LAN 

(10.73/16) and which has access to other LANs (10.78/16 , 10.60/16 

etc..) thru tunnels I built with CIPE tool.

2- My users on the LAN 10.73/16 have 10.73.0.1 as the default gateway, 

In this default gateway, I have setup routes to go 10.78/16, 10.60.16 

network using the CIPE box (10.73.0.254). This default gateway has 

also other routes for others internal network (198.162... etc...)

 

The pb:

 

When users from remote LANs try to reach a windows server in 10.73 

they cannot because, the IP packet is forwarded by the CIPE Box 

directly to the windows server without going thru 10.73.0.1.  To reply 

the server will try to use it s default gateway: 10.73.0.1 and not the 

10.73.0.254.

  

Of course I could add a static route on my desktops and servers but, 

it as painful process.

 

The funny thing is that when from my windows server, I ping a remote 

LAN desktop, it creates a dynamic route and starting from here the 

remote desktop will be able to ping my windows server

  

Is there any way to avoid that using IP routing: For instance on my 

CIPE box I would like to say: For source packet which are not from 

10.73/16 and which want to reach 10.73/16 the go thru 10.73.0.1

  

 ??? Any suggestions

  

Enclosed a little drawing to explain.

  

  

NB: I use Linux 7.0 and Linux 7.1

 


[-- Attachment #2: Type: text/html, Size: 8714 bytes --]