Step 1. take the firewall out of the loop .. connect directly to the modem.
Use DHCP .. establish what IP addresses and masks and dns are issued ..
next step .. configure firewall with that information (I would start off
using DHCP)
if that doesn't fix it then the problem is your firewall configuration..
I'm afraid its RTM time there.
If you don't need a DMZ .. don't put one in .. at least not until you
have the basic config working
If you're using DHCP on your firewall I'd switch it off ..
Finally .. not all DNS servers will reply to Ping
Paul
Nick Rout wrote:
On Sunday 18 March 2007 16:22, Kerry Mayes wrote:
On 18/03/07, Steve Holdoway <[EMAIL PROTECTED]> wrote:
Don't worry about that. Can you ping 66.102.7.99 from the firewall? This
is what www.google.co.nz resolved to when I tried this just now.
Nope, 100% packet loss.
If you can, then it's a problem with dns, not routing.
If not, can you post the output from route -n on the firewall ( you might
have to put in /sbin/route -n ).
re typing this so hopefully no typos:
Kernel IP Routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0
eth2 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0
eth1 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
eth0 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0
eth3 0.0.0.0 10.0.0.138 0.0.0.0 UG 0 0 0
eth2
eth1 is orange, eth3 is blue both unused so far.
what does ifconfig on the firewall tell you?
