* managing another network route, can't connect to it! Pls see!
@ 2003-02-26 11:14 louie miranda
2003-02-26 14:04 ` Arnt Karlsen
0 siblings, 1 reply; 6+ messages in thread
From: louie miranda @ 2003-02-26 11:14 UTC (permalink / raw)
To: netfilter
[-- 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
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: managing another network route, can't connect to it! Pls see! 2003-02-26 11:14 managing another network route, can't connect to it! Pls see! louie miranda @ 2003-02-26 14:04 ` Arnt Karlsen 2003-02-27 1:20 ` louie miranda 0 siblings, 1 reply; 6+ messages in thread From: Arnt Karlsen @ 2003-02-26 14:04 UTC (permalink / raw) To: netfilter ..'info ifconfig', you wanna do 'ifconfig eth1:0 192.168.129.254 up' or somesuch, on your gw. The new boxes on that net needs to know where to go, too. -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: managing another network route, can't connect to it! Pls see! 2003-02-26 14:04 ` Arnt Karlsen @ 2003-02-27 1:20 ` louie miranda 2003-02-27 7:20 ` louie miranda 0 siblings, 1 reply; 6+ messages in thread From: louie miranda @ 2003-02-27 1:20 UTC (permalink / raw) To: Arnt Karlsen, netfilter Arnt, Hi.. I already add another ip over my gw w/c is 192.168.129.50 and point the route to 10.0.0.2. On my WS there's still no response when i go to 192.168.129.x block. But i can ping 192.168.129.50 ip. What else could be possibly be missing? -- thanks, louie miranda ----- Original Message ----- From: "Arnt Karlsen" <arnt@c2i.net> To: <netfilter@lists.netfilter.org> Sent: Wednesday, February 26, 2003 10:04 PM Subject: Re: managing another network route, can't connect to it! Pls see! > > ..'info ifconfig', you wanna do 'ifconfig eth1:0 192.168.129.254 up' > or somesuch, on your gw. The new boxes on that net needs to know > where to go, too. > > -- > ..med vennlig hilsen = with Kind Regards from Arnt... ;-) > ...with a number of polar bear hunters in his ancestry... > Scenarios always come in sets of three: > best case, worst case, and just in case. > > > > ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: managing another network route, can't connect to it! Pls see! 2003-02-27 1:20 ` louie miranda @ 2003-02-27 7:20 ` louie miranda 2003-02-27 12:23 ` Arnt Karlsen 0 siblings, 1 reply; 6+ messages in thread From: louie miranda @ 2003-02-27 7:20 UTC (permalink / raw) To: louie miranda, Arnt Karlsen, netfilter hi thanks 2 everyone! :) all is working now.. -- thanks, louie miranda ----- Original Message ----- From: "louie miranda" <lmiranda@Chikka.com> To: "Arnt Karlsen" <arnt@c2i.net>; <netfilter@lists.netfilter.org> Sent: Thursday, February 27, 2003 9:20 AM Subject: Re: managing another network route, can't connect to it! Pls see! > Arnt, > > Hi.. > > I already add another ip over my gw w/c is 192.168.129.50 and point the > route to 10.0.0.2. On my WS there's still no response when i go to > 192.168.129.x block. But i can ping 192.168.129.50 ip. > > What else could be possibly be missing? > > > -- > thanks, > louie miranda > > > > ----- Original Message ----- > From: "Arnt Karlsen" <arnt@c2i.net> > To: <netfilter@lists.netfilter.org> > Sent: Wednesday, February 26, 2003 10:04 PM > Subject: Re: managing another network route, can't connect to it! Pls see! > > > > > > ..'info ifconfig', you wanna do 'ifconfig eth1:0 192.168.129.254 up' > > or somesuch, on your gw. The new boxes on that net needs to know > > where to go, too. > > > > -- > > ..med vennlig hilsen = with Kind Regards from Arnt... ;-) > > ...with a number of polar bear hunters in his ancestry... > > Scenarios always come in sets of three: > > best case, worst case, and just in case. > > > > > > > > > > > ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: managing another network route, can't connect to it! Pls see! 2003-02-27 7:20 ` louie miranda @ 2003-02-27 12:23 ` Arnt Karlsen 2003-02-28 3:24 ` louie miranda 0 siblings, 1 reply; 6+ messages in thread From: Arnt Karlsen @ 2003-02-27 12:23 UTC (permalink / raw) To: louie miranda; +Cc: netfilter On Thu, 27 Feb 2003 15:20:44 +0800, "louie miranda" <lmiranda@chikka.com> top posted, _and_ mailed, in message <01ce01c2de30$be8a3400$0b00000a@nocpc3>: > ----- Original Message ----- > From: "louie miranda" <lmiranda@Chikka.com> > To: "Arnt Karlsen" <arnt@c2i.net>; <netfilter@lists.netfilter.org> > Sent: Thursday, February 27, 2003 9:20 AM > Subject: Re: managing another network route, can't connect to it! Pls > see! > > > ----- Original Message ----- > > From: "Arnt Karlsen" <arnt@c2i.net> > > To: <netfilter@lists.netfilter.org> > > Sent: Wednesday, February 26, 2003 10:04 PM > > Subject: Re: managing another network route, can't connect to it! > > Pls see! > > > > > > > > > > ..'info ifconfig', you wanna do 'ifconfig eth1:0 192.168.129.254 > > > up' or somesuch, on your gw. The new boxes on that net needs to > > > know where to go, too. > > > > Arnt, > > > > Hi.. > > > > I already add another ip over my gw w/c is 192.168.129.50 and point > > the route to 10.0.0.2. On my WS there's still no response when i go > > to 192.168.129.x block. But i can ping 192.168.129.50 ip. > > > > What else could be possibly be missing? > > ..Louie, what _was_ missing? (I like to know whether I missed something in advicing you, etc, also toss in "Solved" in the subject of the thank-you message when you explain _how_ it was fixed, etc, more people might need this info.) -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: managing another network route, can't connect to it! Pls see! 2003-02-27 12:23 ` Arnt Karlsen @ 2003-02-28 3:24 ` louie miranda 0 siblings, 0 replies; 6+ messages in thread From: louie miranda @ 2003-02-28 3:24 UTC (permalink / raw) To: Arnt Karlsen, netfilter oh, yeah sorry i was too excited! :) I actually re-check my cisco router that is 10.0.0.2 (which is connected on my hub, it was configured to access straight 192.168.129.x/24 block). Now 10.0.0.2's subnet is actually set wrong, subnet was a /24 (255.255.255.0) i just remember im using /16 (255.255.0.0). I re-change the mask and re-add another route to 192.168.129.x via 10.0.0.2 on the linuxgw /sbin/route add -net 192.168.129.0 netmask 255.255.255.0 gw 10.0.0.2 now again i can ping 192.168.129.x from my linuxgw and still no respond from the ws (work stations). I add another rule that will forwarded all 10.0.0/16 (workstations) /sbin/iptables -A FORWARD -s 10.0.0.0/16 -i eth1 -j ACCEPT and test it. It worked! :) -- thanks, louie miranda ----- Original Message ----- From: "Arnt Karlsen" <arnt@c2i.net> To: "louie miranda" <lmiranda@chikka.com> Cc: <netfilter@lists.netfilter.org> Sent: Thursday, February 27, 2003 8:23 PM Subject: Re: managing another network route, can't connect to it! Pls see! > On Thu, 27 Feb 2003 15:20:44 +0800, > "louie miranda" <lmiranda@chikka.com> top posted, _and_ mailed, > in message <01ce01c2de30$be8a3400$0b00000a@nocpc3>: > > > ----- Original Message ----- > > From: "louie miranda" <lmiranda@Chikka.com> > > To: "Arnt Karlsen" <arnt@c2i.net>; <netfilter@lists.netfilter.org> > > Sent: Thursday, February 27, 2003 9:20 AM > > Subject: Re: managing another network route, can't connect to it! Pls > > see! > > > > > ----- Original Message ----- > > > From: "Arnt Karlsen" <arnt@c2i.net> > > > To: <netfilter@lists.netfilter.org> > > > Sent: Wednesday, February 26, 2003 10:04 PM > > > Subject: Re: managing another network route, can't connect to it! > > > Pls see! > > > > > > > > > > > > > > ..'info ifconfig', you wanna do 'ifconfig eth1:0 192.168.129.254 > > > > up' or somesuch, on your gw. The new boxes on that net needs to > > > > know where to go, too. > > > > > > Arnt, > > > > > > Hi.. > > > > > > I already add another ip over my gw w/c is 192.168.129.50 and point > > > the route to 10.0.0.2. On my WS there's still no response when i go > > > to 192.168.129.x block. But i can ping 192.168.129.50 ip. > > > > > > What else could be possibly be missing? > > > > > ..Louie, what _was_ missing? (I like to know whether I missed > something in advicing you, etc, also toss in "Solved" in the > subject of the thank-you message when you explain _how_ it was > fixed, etc, more people might need this info.) > > > -- > ..med vennlig hilsen = with Kind Regards from Arnt... ;-) > ...with a number of polar bear hunters in his ancestry... > Scenarios always come in sets of three: > best case, worst case, and just in case. > > > ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2003-02-28 3:24 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2003-02-26 11:14 managing another network route, can't connect to it! Pls see! louie miranda 2003-02-26 14:04 ` 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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox