hiya dave

quick glance... and some guesswork

- a machine should always be able to ping itself 
        ( 10.32.32.x or 10.42.43.x 
        ( evben with the nic cable disconnected )

- c0n1 does not have a 10.42.42.0 routes
  and it has 10.42.43.* gateway ( wrong ?? )

- i think either eth1(43.*) or eth0(42.*) must go to the outside world
        lets say *.42.8 is internal

- if c0n1 and c0n3 has only one nic.. you have extra routes
  listed
        - i say change all of the cluster to be 10.42.42.*

- buster, if its the one to go tothe outside world needs
  to have one wire to the outside world
        gateway is the ip# of your router or isp
        10.42.43.1  lets say

and you should be all set
c ya
alvin

On Fri, 4 Oct 2002, dave mallery wrote:

> hi
> 
> now i believe myself to be a fairly experienced deb user.  this is
> humiliating:
> 
> i have a home network (10.42.42.0) which has a floppyfw gateway to the
> world at 10.42.42.254.  works.
> 
> i have been building a cluster (actually, resuscitating one, but that's
> another story).  the cluster network is 10.42.43.0.  its gateway is
> called buster and has 2 nics, 10.42.42.112 (eth0) and 10.42.43.254
> (eth1).
> 
> the cluster nodes (only 3 running now) are c0n1 c0n2 and c0n3. they are
> served their roots by buster (etherboot). works. that was hard. this is
> easy?
> 
> too bad i can't ping in or out.
> 
> from inside out:
> c0n1:/home/dmallery>> route -n
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric RefUse Iface
> 10.42.43.0      0.0.0.0         255.255.255.0   U     0      0     0 eth0
> 0.0.0.0         10.42.43.254    0.0.0.0         UG    0      0   0 eth0
> 
> cluster member c0n1 can ping buster, but no further.
> 
> next here's buster:
> buster:/etc/init.d>> route -n
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric RefUse Iface
> 10.42.43.0      0.0.0.0         255.255.255.0   U     0      0    0 eth1
> 10.42.42.0      0.0.0.0         255.255.255.0   U     0      0    0 eth0
> 0.0.0.0         10.42.42.254    0.0.0.0         UG    0      0    0 eth0

buster should be at 10.42.42.254 ( its ip# ) for talking to c0n1 and bilbo
buster should have another ip# say 10.42.43.254 as its other ip#

fix the gateway above to 10.42.43.1  of the real router from isp
---------------------

> buster can ping into the cluster and outwards into 10.42.42.0 land.
> buster is happy.  buster can even ping debian.org!
> 
> next (and last) here's bilbo, a sarge machine on the home front:
> 
> bilbo:/>> route -n
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref   Iface
> 10.42.43.0      10.42.42.112    255.255.255.0   UG    0      0     0 eth0
> 10.42.42.0      0.0.0.0         255.255.255.0   U     0      0     0 eth0
> 0.0.0.0         10.42.42.254    0.0.0.0         UG    0      0     0 eth0

remove 10.42.43 routes
------------------------

> bilbo can ping the world and buster but not into the cluster.
> 
> (i realize that i will have to add a route to the firewall to the cluster
> but that can wait till c0n1 can ping bilbo!)
> 
> is this a routing problem, or am i looking endlessly in the wrong place?
> i am at a dead stop.  i would so appreciate some pointers.
> 
> thanks in advance.
> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to