Netgear DGND3300v2 DGND3300 User Manual - Page 48
Table 3-1., Adding or Editing Firewall Service Rules, Field, Outbound Rules, Address range, Start
View all Netgear DGND3300v2 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 48 highlights
RangeMax Dual Band Wireless-N Modem Router DGND3300 User Manual Table 3-1. Adding or Editing Firewall Service Rules Field Outbound Rules Inbound Rules Action • For Outbound rules, ALLOW rules are only useful if the traffic is already covered by a BLOCK rule. (That is, you want to allow a subset of traffic that is currently blocked by another rule.) • To define the schedule used in these selections, use the Schedule screen (see "Scheduling Blocking" on page 3-14). • For Inbound rules, BLOCK rules are only useful if the traffic is already covered by an ALLOW rule. (That is, you want to block a subset of traffic that is currently allowed by another rule.) • To define the schedule used in these selections, use the Schedule screen (see "Scheduling Blocking" on page 3-14). LAN users (Outbound Services only) These settings determine which computers on your network are affected by this rule, based on their source (LAN) IP address. Select the desired option: • Any. All local IP addresses are covered by this rule. • Address range. If this option is selected, you must enter the Start and Finish fields. • Single address. Enter the required address in the Start fields. Send to LAN Server (Inbound Services only) Enter the IP address of the PC or Server on your LAN that will receive the inbound traffic covered by this rule. WAN Servers These settings determine which Internet locations are covered by the rule, based on their destination (WAN) IP address. Select the desired option: • Any. All local IP addresses are covered by this rule. • Address range. If this option is selected, you must enter the Start and Finish fields. • Single address. Enter the required address in the Start fields. Log This determines whether packets covered by this rule are logged. Select the desired action: • Always. Always log traffic considered by this rule, whether it matches or not. This is useful when debugging your rules. • Never. Never log traffic considered by this rule, whether it matches or not. • Match. Log traffic only it matches this rule. (The action is determined by this rule.) • Not Match. Log traffic that is considered by this rule, but does not match (The action is NOT determined by this rule.) 3-8 Protecting Your Network v1.0, September 2009