we encourage you to fill in the following tables in preparation for completing the rest of the installation process.
license keys
collect your license key certificates. your watchguard firebox system comes with a livesecurity service key that activates your one-year subscription to the livesecurity service. for more information on this service, see chapter 2, “service and support.” high availability and spamscreen are optional products, and you receive those license keys upon purchase. for more information on optional products, see chapter 1, “introduction.”

network addresses
one good way to set up your network is to create two worksheets: the first worksheet represents your network now–before deploying the firebox–and the second represents your network after the firebox is deployed. fill in the ip addresses in the worksheets below.

an example of a network before the firebox is installed appears in the following figure. in this example, the internet router performs network address translation (nat) for the internal network. the router has a public ip address of 208.15.15.1, and the private network has an address of 192.168.10.0/24. this network also has three public servers with the addresses 208.15.15.10, 208.15.15.15, and 208.15.15.17.

the following figure shows the same example network with a firebox deployed. the ip address of the internet router in the previous figure becomes the ip address of the firebox’s default gateway. this network uses drop-in configuration because the public servers will maintain their own ip addresses. drop-in configuration simplifies the setup of these devices. for more information on this type of configuration, see “drop-in configuration” on page 27.
by configuring the optional interface on the example network, the public servers can be connected directly to the firebox (because they are on the same subnet as the firebox).
in the example, the secondary network represents the local lan. because the trusted interface is being configured with the public ip address, a secondary network is added with an unassigned private ip address from the local lan: 192.168.10.1/24. this ip address then becomes the default gateway for devices on the local lan.