NAI wrote:
>
> Hi,
>
> I work for an IT company and I have been assigned the task of handling the
> Gauntlet Firewall. I setup a test lab which included 3 computers one as the
> firewall and the other two as two different networks. Working in this setup
> does not allow you to really work extensively and learn about the firewall.
> We already have a company firewall (Gauntlet) in place. Our company
> firewall has been configured with the default settings when it comes to the
> policies & proxies. It would be great if I could connect my test lab
> firewall to the company firewall.
>
> Can I have cascading firewalls?
Sure. There's quite a few big corporates who have internal firewalls at
the dept office level, and a major firewall at the internet link. From
what I understand it tends to be more for inforcing internal policy that
external security tho.
If you're running a private address space (192.168.x.x or similar)
configure one of your test firewall interfaces to be on your internal
network, and the other to be on a small subnet, put some machines on
either side and play. You can still do it if your using public
addresses, you just might find it harder to find acceptable/available IP
ranges...
> Why is a caching DNS required at the firewall?
Partly, speed, partly because allowing DNS, or anything, throught the
firewall should be avoided if you can.
> Could you specify some reading material that would be helpful?
Ummm... :-)
> Is there any software that could be used to test the firewall, some hacking
> software for example?
I'm a big fan of "nmap", with or without the gui, "nmapfe". It's a
portscanner for linux. A good packet sniffer is a must too, to see which
packets get through. A portscan from one side of the firewall, with a
packet sniffer on the other is a good way to do basic testing/checking.
--
Tristan Ball
System Adminstrator - Adelaide
Vision Systems
PH (08) 83004771
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
