From: "louie miranda" <lmiranda@chikka.com>
To: netfilter@lists.samba.org
Subject: managing another network route, can't connect to it! Pls see!
Date: Wed, 26 Feb 2003 19:14:06 +0800 [thread overview]
Message-ID: <030f01c2dd88$2f277140$0b00000a@nocpc3> (raw)
[-- Attachment #1: Type: text/plain, Size: 2282 bytes --]
i.e.
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.
My LAN is on a masq LinuxBOX. On my diagram i have added a network cable
that is on a different
subnet connect to a cisco router via 10.0.0.2 which is connected to another
network (diff story).
My kernel route diagram is below..
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
203.190.72.104 0.0.0.0 255.255.255.248 U 0 0 0 eth0
192.168.129.0 10.0.0.2 255.255.255.0 UG 0 0 0 eth1
<--- new route via 10.0.0.2
10.0.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1
0.0.0.0 203.190.72.110 0.0.0.0 UG 0 0 0 eth0
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?
---
thanks,
louie
[-- Attachment #2: networkdiag.txt --]
[-- Type: text/plain, Size: 1356 bytes --]
Consider the following network:
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
next reply other threads:[~2003-02-26 11:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 11:14 louie miranda [this message]
2003-02-26 14:04 ` managing another network route, can't connect to it! Pls see! Arnt Karlsen
2003-02-27 1:20 ` louie miranda
2003-02-27 7:20 ` louie miranda
2003-02-27 12:23 ` Arnt Karlsen
2003-02-28 3:24 ` louie miranda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='030f01c2dd88$2f277140$0b00000a@nocpc3' \
--to=lmiranda@chikka.com \
--cc=netfilter@lists.samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox