Re: your mail
On Fri, Oct 04, 2002 at 09:57:23PM -0700, Alvin Oga wrote:
> hi ya kourosh..
> i dont know your config of your lan etc.. :-)>
Unless you have psychic powers I wouldn't think so ;-)
> - if buster was NOT forwarding, am thinking none of the machines
> in the cluster would NOT a "ping www.yahoo.com" replies
> - but since one does work.. and another does not
> ( its an ip# problem forwarding for that other private net
> ( its the different ip# problem
> - you will get one that can ping and another that cannot ping
> if the routing or gateway is wrong... thus our delima in here
> - or possibly other issues ... including "forwarding" but
> i think that is unlikely since one(other than buster) works
I agree, except it's my understanding that bilbo, the machine that can
ping the Internet, is not on the cluster side of the network, but on
the other, or as Dave calls it, the "home" side. So if that's correct,
then the only machines that can't ping the Internet are on the cluster
network, behind buster. Since buster can ping the "home" network, the
"cluster" network, and the Internet, that led me to believe that only
forwarding is the problem with that machine.
Of course, I could still be wrong =)
> - funny part... i think we can both fix it in a jippy if we could
> fiddle with the boxes.. :-)
> "tech support via email"... humm .. what a novel concept... :-)
> ssh into the problem box is easier..
Much easier! =)
> have fun
> On Fri, 4 Oct 2002, Kourosh Ghassemieh wrote:
> > firstname.lastname@example.org
> > Cc:
> > Bcc:
> > Subject: Re: routing problem
> > Reply-To:
> > In-Reply-To: <Pine.LNX.3.96.1021004195839.12812A-100000@Maggie.Linux-Consulting.com>
> > Alvin,
> > I'm not sure I see that the gw is misconfigured. The routing table on my
> > firewall looks the same as buster, with the exception of the IP's.
> > Buster only needs to know about the cluster's network, the home network,
> > and where to send everything else. Buster has a route for the cluster network
> > on interface eth1, the home network on interface eth0, and the default route
> > is the gw on the home side.
> > My thinking is that buster is simply not forwarding packets because it can
> > ping everywhere itself, yet nothing gets past it. Dave can try checking to see
> > if forwading is on with 'cat /proc/sys/net/ipv4/ip_forward'. If it's 1 then
> > forwarding is on. If it's 0 then forwarding is off and it can be turned on
> > by 'echo 1 > /proc/sys/net/ipv4/ip_forward'.
> > Again, Dave, the cluster doesn't need a route to the firewall as thet's buster's
> > job.
> > Oh, and if iptables or ipchains is enabled on buster they mau also be causing
> > problems unless there are rules to forward packets.
> > Hope this doesn't cause any more confusion =)