*BSD News Article 51818


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!wabbit.cc.uow.edu.au!news.ci.com.au!usenet
From: Ferry Winarta <ferryw@softplus.com.au>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: IPFORWARDING on FreeBSD2.0, Help Please
Date: 28 Sep 1995 22:38:53 GMT
Organization: Software Plus (Aust) Pty Ltd
Lines: 64
Message-ID: <44f85t$kkg@mippet.ci.com.au>
References: <43ip24$as@mippet.ci.com.au> <Pine.SCO.3.91.950921124240.15219B-100000@conger.softplus.com.au> <43v9a3$ccj@uriah.heep.sax.de> <Pine.SCO.3.91.950925100403.20864A-100000@conger.softplus.com.au> <445o0a$6st@uriah.heep.sax.de>
NNTP-Posting-Host: spgate.softplus.com.au
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 1.1N (Windows; I; 16bit)

Hi,

j@uriah.heep.sax.de (J Wunsch) wrote:
>Ferry Winarta  <ferryw@softplus.com.au> wrote:
>
>>> >X.Y.Z.85 |--| X.Y.Z.65  X.Y.Z.33 |--| X.Y.Z.42  A.B.C.D |--| A.B.C.*
>>> >(INTERNAL)        (GATEWAY)                (ROUTER)            (External)
>
>>> What does the routing table on INTERNAL say for A.B.C.4?
>>
>>netstat -nr on X.Y.Z.85 :
>
>Please, try "netstat -ran" (immediately after an attempt to telnet
>A.B.C.4).  Do the same for GATEWAY then.  The routes to A.B.C.4 should
>appear as clone routes in the table.
>

I did this, it seems that it took the right route (from increasing number 
of packet ?, am I correct here ?)

>>> Does ROUTER forward the entire X.Y.Z network (netmask 255.255.255.0)
>>> to X.Y.Z.33?
>>
>>It is external router (CISCO), which I think should have no effect,
>>because I can telnet from gateway (X.Y.Z.33) to A.B.C.4 and vice versa.
>
>But there's still the question which netmask the router is using.  I
>admit that it's not very likely the reason though.
>
>Can you ping the router from INTERNAL?
>-- 

NO, 

I did try another PPP connection to the Internet (from the same gateway), 
and I can telnet from internal to external directly. 

So I think the problem is in the router. I'll contact the router's system
administrator to confirm this.

I have another question, regarding ipfw...

1. Does it need IPFORWARDING to be turned on, to use it ?
2. Or, if you turned on IPFORWARDING, than you control it by ipfw addb , 
   and if you turned off IPFORWARDING, than you can enable it by ipfw    
addf. I did try to read man ipfw, and the samples (I still couldn't
   figure out how to use it).

Thanks for all of your help

and
 
thanks for other people who already spent their time to help...

Regards,
ferry


>cheers, J"org
>
>joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/
>Never trust an operating system you don't have sources for. ;-)