6.2.5. H.323
1.
Go to Rules > IP Rules > Add > IPRule
2.
Now enter:
•
Name: H323In
•
Action: Allow
•
Service: H323-Gatekeeper
•
Source Interface: any
•
Destination Interface: core
•
Source Network: 0.0.0.0/0 (all-nets)
•
Destination Network: wan_ip (external IP of the firewall)
•
Comment: Allow incoming communication with the Gatekeeper
3.
Click OK
1.
Go to Rules > IP Rules > Add > IPRule
2.
Now enter:
•
Name: H323In
•
Action: Allow
•
Service: Gatekeeper
•
Source Interface: lan
•
Destination Interface: dmz
•
Source Network: lannet
•
Destination Network: ip-gatekeeper (IP address of the gatekeeper)
•
Comment: Allow incoming communication with the Gatekeeper
3.
Click OK
Example 6.9. H.323 with Gatekeeper and two D-Link Firewalls
This scenario is quite similar to scenario 3, with the difference that the D-Link Firewall is protecting the "external"
phones. The D-Link Firewall with the Gatekeeper connected to the DMZ should be configured exactly as in scen-
ario 3 The other D-Link Firewall should be configured as below. The rules need to be added to the rule listings,
and it should be make sure there are no rules disallowing or allowing the same kind of ports/traffic before these
rules.
Note
There is no need to specify a specific rule for outgoing calls. NetDefendOS monitors
the communication between "external" phones and the Gatekeeper to make sure that it
is possible for internal phones to call the external phones that are registered with the
gatekeeper.
119
Chapter 6. Security Mechanisms