Re: managing another network route, can't connect to it! Pls see!

[jereme <jereme@rmcnet.cc>]

Hi Louie,

"louie miranda" <lmiranda@chikka.com> writes:
> Consider the following network: (kindly view the attached txt file for a
> nicer one)
> 
>                               inet
>                                 |
>                                 |
>                                 |203.190.72.108
>                       *-----------------*
>               10.0.0.1|       eth0      |none
>                  /----|eth1         eth2|------\               new network
> block pipe
>                  |    |     LINUX GW    |   line cut         *--------*
> 192.168.129.x/24 (network)
>                  |    *-----------------*                    |        |
> 10.0.0.2, gw for 192.168.129.x/24 block under LINUX GW
>                  |                                           | 192.x  |
>                  |                                           |        |
>                *HUB*-----------------------------------------*--------*
>                  |                                              cisco 2600
> router ip of this router is: 10.0.0.2
>                  |
>                  |
>            *--* *--* *--*
>            |  | |  | |  |
>            |  | |  | |  |
>            *--* *--* *--*
>             workstations
>           10.0.0.0/16 block
> 
> 
>     interface:
>      - eth0 = 203.190.72.108, default gw.
>      - eth1 = 10.0.0.0/16, local area network.
>      - eth2 = none
> 
> 
> 
> ===========
> 
> Right now im inside 10.0.0.0/16 block, my ip is 10.0.0.11 and my default gw
> is via 203.190.72.108.

I think that you mean your default gateway is 10.0.0.1, if your ws has
a /16 netmask, as you say.


> I can access ip block 192.168.129.x on my LINUX GW perfectly. But when im on
> my workstations on
> 10.0.0.11 block i cannot even ping 192.168.129.x block. Which could be
> possibly be wrong?

For the hosts on the 10.0.0.0/16 network, like your ws, you have to
add a route for the 192.168.129.0/24 network via 10.0.0.2, axactly as
you have done for the linux gateway.

As it stands now, if the 10.0.0.0/16 hosts have only a local route and
a default route, they are sending datagrams bound for the
192.168.129.0/24 network to their default gw.  Though this is not as
efficient as having those hosts use the 10.0.0.2 router, it does save
you the headache of setting static routes on each system.  To get this
to work, I would suspect the problem lies in the filtering and
mangallind rules on the gw.  You can post those rules, if you are
comfortable with that and you want more help.



hth,
jereme

-- 
+--------------------------------------------------------------+
Jereme Corrado <jereme@restorative-management.com>
System Administrator
Restorative Management Corp.

gpg: 1024D/9C39E1F0