Compaq ProLiant 1000 Performance Analysis and Tuning of Raptor's Eagle NT 3.06 - Page 8

Machine, Hardware, Software

Page 8 highlights

278A/0497 WHITE PAPER (cont.) ... Table 4 shows the hardware and software makeup of the firewall for the base system. Machine Hardware OS Software firewall01 ProLiant 5000, 64 MB RAM, 1-Pentium PRO 200/512K cache, 2 EISA NetFlx-3 10/100 NICs, PCISmart-2 Ctrl, 1-2 GB Drive Windows NT 3.51 Server, Service Pack 5 Raptor's Eagle NT 3.06 firewall software and Hawk GUI. Table 4: Firewall Hardware and Software Makeup Firewall configuration with Eagle NT 3.06 starts with DNS setup. The network segments for Inside and Outside used the network addresses 10.10.10 and 11.11.11 respectively and the domain was set to testbed.com for both segments. This information was configured from the Gateway screen File->Set up DNS... menu option. Two files: HOSTS and HOSTS.PUB located in the %SYSTEMROOT%\SYSTEM32\DRIVERS\ETC directory are created with DNS changes when saved. The HOSTS and HOSTS.PUB files correspond to DNS names for inside and outside hosts respectively. Outside DNS queries are done on the HOSTS.PUB file and inside DNS queries are done on the HOSTS and HOSTS.PUB files. The HOSTS and HOSTS.PUB files for the firewall setup are listed in Appendix A. Since access is allowed from the DMZ/Hostile network to the private webserver for benchmark testing, configuration for the private webserver is done through the Gateway screen File>Set up HTTP... The physical server holds the address of 10.10.10.8 and is assigned the DNS names of server01 and server02 to create two virtual servers. Port 80 is used for both the inside port of the webserver daemon and the firewall gateway. Please refer to Screen 1, the HTTP Setup screen. Screen 1: Http Setup Names given to network segments, hosts, groups, etc. are configured in the Net Entities screen. Rules can be applied based on names, once the network entities are configured. Inside, Outside, Server1, Server2, and universe are names for network entities needed in the firewall configuration. Please refer to Screen 2 for configured network entities. 8

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27

W
HITE
P
APER
(cont.)
8
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
278A/0497
Table 4 shows the hardware and software makeup of the firewall for the base system.
Machine
Hardware
OS
Software
firewall01
ProLiant 5000, 64 MB
RAM,
1-Pentium PRO
200/512K cache, 2
EISA
NetFlx-3 10/100 NICs, PCI-
Smart-2 Ctrl, 1-2 GB Drive
Windows NT
3.51 Server,
Service Pack 5
Raptor’s Eagle NT
3.06 firewall software
and Hawk GUI.
Table 4:
Firewall Hardware and Software Makeup
Firewall configuration with Eagle NT 3.06 starts with DNS setup. The network segments for
Inside and Outside used the network addresses
10.10.10
and
11.11.11
respectively and the
domain was set to
testbed.com
for both segments.
This information was configured from the
Gateway
screen
File->Set up DNS... menu option.
Two files: HOSTS and HOSTS.PUB located in the
%SYSTEMROOT%\SYSTEM32\DRIVERS\ETC
directory are created with DNS changes when
saved. The HOSTS and HOSTS.PUB files correspond to DNS names for inside and outside hosts
respectively. Outside DNS queries are done on the HOSTS.PUB file and inside DNS queries are
done on the HOSTS and HOSTS.PUB files. The HOSTS and HOSTS.PUB files for the firewall
setup are listed in Appendix
A.
Since access is allowed from the DMZ/Hostile network to the private webserver for benchmark
testing, configuration for the private webserver is done through the
Gateway
screen
File-
>Set up HTTP...
The physical server holds the address of
10.10.10.8
and is assigned
the DNS names of server01 and server02 to create two virtual servers. Port 80 is used for both the
inside port of the webserver daemon and the firewall gateway.
Please refer to Screen 1, the
HTTP
Setup
screen.
Screen 1:
Http Setup
Names given to network segments, hosts, groups, etc. are configured in the
Net Entities
screen.
Rules can be applied based on names, once the network entities are configured. Inside,
Outside, Server1, Server2, and universe are names for network entities needed in the firewall
configuration. Please refer to Screen 2 for configured network entities.