Hi Brian [and all the others who helped], 

Thanks very much to all who gave me advice the last 
couple of days.

The problems turned out to be mostly 'bad hardware'...
2 bad Nics and a bad cable. 

Routing seems to work ok on two of the machines but I'm 
having problems pinging between BOX-1 and BOX-2.

My Goal here is to use a 
WIN-95 machine
[ with a 'server' s/w pkg & Dual Phone Line Modem] 
'BOX-1' to dialup the ISP 
and pass the packets to... 'BOX-2'
a RH-5.2 Linux Machine [ IP Masqueraded Firewall Box] 
which is used to protect my local network[ just 'BOX-3' now]. 

I am doing it this way because I don't have access to 
DSL or ISDN but I do have access to  Dual Phone Line technology. 

Eventually I will be able to get high speed service and will 
eliminate Box-1 and connect Box-2 directly to the ISP.

I do not yet have the  'server s/w package' installed on the 
WIN-95 Machine-BOX-1.

The following is 
my current system...   

---------------------------------------------------------------
 MY ISP
 |
 |
 |
 >------|== SupraSonic Dual Line/ 56k Modem  '106k down'           
        |
        |--Box-1   A WIN-95 MACHINE  [w/ a 'server s/w package']
        |
        | THE GATEWAY for This Box is 0.0.0.0 [is set by ppp process]
        |       
        |                  WIN-95
        |
 >------|---eth0   IP= 10.0.0.1  Mask= 255.0.0.0
 |
 |
 |
 >------|---eth1   IP= 10.0.0.2  Mask= 255.0.0.0
        |
        |==Box-2  RH-5.2 [an IP-Masqueraded[IPFWADM]firewall Machine]
        |
        |   THE GATEWAY for This Box is 10.0.0.1 
        |                  LINUX[ RH-5.2]
  >-----|---eth0   IP= 192.168.127.65  Mask= 255.255.255.0
  |
  |
  >--|              
     |==LynkSys HUB, 10BT, 5 ports
  >--|
  |   
  >--|---eth0    IP=192.168.127.68 Mask= 255.255.255.0
     | 
     |--Box-3  a DUAL BOOTED Machine-WIN-95 & LINUX[RH-6.1]
     |             
     |   THE GATEWAY IP#  for This Box is 192.168.127.65


---------------------------------------------------------------
My /etc/hosts  [on all machines]  contains....

127.0.0.1            localhost         localhost.localdomain

10.0.0.1             in.domain.name    in  #[BOX-1 eth0]

10.0.0.2             nut.domain.name   nut #[BOX-2 eth1]
192.168.127.65       gw.domain.name    gw  #[BOX-2 eth0]

192.168.127.68       luk.domain.name   luk #[BOX-3 eth0]
---------------------------------------------------------------
On BOX-2...  'gw.domain.name'   [non-public domain name & IP#s]

'netstat -nr   shows....

192.168.127.0 0.0.0.0   255.255.255.0 U  1500 0 0 eth0
127.0.0.0     0.0.0.0   255.0.0.0     U  3584 0 0 lo
10.0.0.0      0.0.0.0   255.0.0.0     U  1500 0 0 eth1
0.0.0.0       10.0.0.1  0.0.0.0       UG 1500 0 0 eth1

---------------------------------------------------------------
On BOX-2...  'gw.domain.name'   [non-public domain name & IP#s]

my /etc/rc.d/rc.local file has...

ipfwadm -F -p deny
ipfwadm -F -a -m -S 192.168.127.0/24 -D 10.0.0.0/8
---------------------------------------------------------------
On BOX-3...  'luk.domain.name'  [non-public domain name & IP#s]

a WIN-95 Box - dual booted with RH-6.1

I am able to ping from Box-2 to Box-3...

I am able to ping from Box-3 to Box-2 
to 
10.0.0.2             nut.domain.name   nut  [ eth1 ] on BOX-2
192.168.127.65       gw.domain.name    gw  [ eth0 ]  on BOX-2 

BUT... 
I cannot ping to '10.0.0.1  in.domain.name'  [eth0]  on BOX-1 
from either BOX-2 or BOX-3. 

I also cannot ping from BOX-1 to anything on BOX-2 or BOX-3 

I'm hoping someone can tell me whether I should expect to be 
able to ping from the local network [BOXES-2 & 3] to BOX-1 
prior to installing the 'server s/w package'[ on BOX-1] ? 

My guess is that since I have no server-s/w on BOX-1 that 
that is the reason I cannot ping there yet.  

OR what else might I need to do next?

Many thanks in advance to you all 
for your assistance.

Johnny

[EMAIL PROTECTED]



Brian wrote:

> >
> > However the 2nd machine has an old [but I thought functioning NIC]
> > nic which does not have any lights.
> >
> > Do you think I should replace the nic on the second machine and
> > test it all again?
> 
> possibly.................
>


-- 
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.

Reply via email to