From: "louie miranda" <lmiranda@chikka.com>
To: Arnt Karlsen <arnt@c2i.net>, netfilter@lists.netfilter.org
Subject: Re: managing another network route, can't connect to it! Pls see!
Date: Fri, 28 Feb 2003 11:24:18 +0800 [thread overview]
Message-ID: <00c601c2ded8$e0eaed70$2200000a@nocpc3> (raw)
In-Reply-To: 20030227132347.03d3dc58.arnt@c2i.net
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.
>
>
>
prev parent reply other threads:[~2003-02-28 3:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
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='00c601c2ded8$e0eaed70$2200000a@nocpc3' \
--to=lmiranda@chikka.com \
--cc=arnt@c2i.net \
--cc=netfilter@lists.netfilter.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