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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.
>
>
>



[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux