Message: 4
Date: Sat, 28 Jan 2006 00:58:51 -0500
From: Binand Sethumadhavan <[EMAIL PROTECTED]>
Well, do you know which of these specifically allows machine B
to
access Internet? That would help is solving this. Or are all
three
required?
Well I think all three have a role to play. Shorewall allows or
disallows requests to and from the intranet to the internet, the
network itself is required because that is where the gateway is
configured and named resolves host names.
My first guess would be that named is where the problem is because
the client machines often complain of "server not found". If you
fire up firefox on Machine B, the answer is "www.google.com not
found".
However, attempting to restart named alone does not work. So, I
think the network needs time to get all interfaces going on top
gear and therefore needs a gap before other services which require
the network are started up. In rc5.d both shorewall and network
are set to S10 (S10network and S10shorewall) and are probably
falling over each other while starting up.
So where am I? And have I given you enough to help? Another
question is whether the eth0:0 business could be causing this
problem
Thanks in advance
Pramathesh
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
linux-india-help mailing list
linux-india-help@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-india-help
