|
Punch in a sniffer and see what is happening on
that outside interface.
Ping the webserver's outside IP address from the
router console (assuming you have rule to allow icmp-echo/reply).
View the sniffer data and see if you get an ARP
reply (make sure to clear the arp cache on the router first...hehe)
No ARP reply from the firewall, NO SOUP FOR YOU!!
Do not collect $200, go directly to....
If you had local.arp configured properly as well as
a rule to allow http to your DMZ bastion host, then
you SHOULD see some "accept" log entries with
xlated destination/source addresses.
If not, then your ARP settings might not be
working. (in CCSE/2000 class they hammered into us that
this file and many others are sensitive to
extraneous formatting and control characters)
I would verify that ARP and static routes are
working first.
Make sure your route 0.0.0.0 is for the outside
interface as well.
I generally have a stealth rule that prevents any
access to my firewall's real IP's.
The only ports that will ever be open are the ones
necessary via implied rules (AAA, log, mgmt etc)
|
Title: NAT and DMZ routing
- [FW1] NAT and DMZ routing Rob Michayluk
- Re: [FW1] NAT and DMZ routing Carl E. Mankinen
- RE: [FW1] NAT and DMZ routing Rob Michayluk
- RE: [FW1] NAT and DMZ routing Carl E. Mankinen
- RE: [FW1] NAT and DMZ routing Hal Dorsman
- RE: [FW1] NAT and DMZ routing Thomas . Poole
- RE: [FW1] NAT and DMZ routing Murphy, Paul
