/netbsd-src/external/bsd/ipf/dist/perl/ |
H A D | ipf-mrtg.pl | 5 my $firewall = "IP Filter v3.3.3"; 22 "$firewall\n";
|
/netbsd-src/external/bsd/ipf/dist/rules/ |
H A D | firewall | 1 Configuring IP Filter for firewall usage. 19 want each host that is part of your firewall to be allowed to do, including 30 * "int-a" is the internal interface of the firewall. That is, it is the
|
H A D | nat-setup | 21 [firewall]
|
/netbsd-src/external/mpl/bind/dist/doc/arm/ |
H A D | rpz.inc.rst | 19 A DNS firewall examines DNS traffic and allows some responses to pass 24 DNS firewall can be configured to discard, modify, or replace the original 28 DNS Response Policy Zones (RPZ) are a form of DNS firewall in which the 29 firewall rules are expressed within the DNS itself - encoded in an open, 34 This allows a DNS operator to maintain their own firewall policies and 36 external firewall policies such as commercial or cooperative "threat 64 The most common use of a DNS firewall is to "poison" a domain name, IP 69 by adding a firewall policy into the recursive DNS server, with a trigger 91 firewalling. A DNS firewall can selectively intercept DNS queries for 105 that special handling is. For a DNS firewall, th [all...] |
/netbsd-src/external/bsd/unbound/dist/pythonmod/doc/ |
H A D | usecase.rst | 12 Control firewall (e.g. enable incoming SSH connection) with DNS query signed with private key. 13 So firewall can blocks every service during normal operation.
|
/netbsd-src/external/bsd/ipf/dist/FWTK/ |
H A D | fwtk_transparent.diff | 153 + IPFPATH=/src/unpacked/firewall/ip_fil3.1.5 190 diff -cr ../TIS.orig/fwtk/firewall.h fwtk/firewall.h 191 *** ../TIS.orig/fwtk/firewall.h Sun Sep 8 05:55:26 1996 192 --- fwtk/firewall.h Sun Feb 2 05:23:33 1997 213 /* Choose a system logging facility for the firewall toolkit. */ 221 /* Choose a system logging facility for the firewall toolkit. */ 590 #include "firewall.h"
|
H A D | fwtkp | 9 ! #include "firewall.h" 20 + #include "firewall.h" 420 #include "firewall.h"
|
H A D | ftp-gw.diff | 41 #include "firewall.h"
|
/netbsd-src/external/bsd/ipf/rules/ |
H A D | Makefile | 12 firewall ftp-proxy ftppxy nat-setup \
|
/netbsd-src/external/bsd/openldap/dist/doc/guide/admin/ |
H A D | security.sdf | 38 {{TERM:IP}} firewall capabilities of the server system can be used 46 As specifics of how to configure IP firewall are dependent on the 47 particular kind of IP firewall used, no examples are provided here. 48 See the document associated with your IP firewall. 68 it is generally advised that IP firewall protection be used instead
|
H A D | install.sdf | 136 filters (such as those provided by an IP-level firewall) is recommended
|
/netbsd-src/crypto/dist/ipsec-tools/src/racoon/rfc/ |
H A D | draft-ietf-ipsec-isakmp-hybrid-auth-05.txt | 47 entity, typically an Edge Device (e.g. firewall), authenticates using 159 (e.g. firewall), it is not always possible to preserve symmetric 162 OmniGuard/Defender authentication challenge to the firewall, since 163 she cannot check the firewall's response. 248 Edge Device - Gateway, router or firewall protecting a corporate
|
H A D | draft-beaulieu-ike-xauth-02.txt | 147 firewall, or network access server to offload the user 153 gateway/firewall), they cannot be used by themselves, but must be 159 the gateway/firewall (edge device) in a secured ISAKMP message. The 751 firewall/gateway), the methods described can also be used for edge
|
H A D | rfc2407.txt | 255 Some notion of proxy firewall addresses may also be required. 262 firewall address. The wildcard DNS name would be used to match 265 direction, and the optional firewall address would be used to 267 target system though an intermediate firewall.
|
H A D | rfc2367.txt | 2624 "firewall" configuration in which an intermediate system provides 2645 B "firewall" that implements IPsec 2652 system C. B is a "firewall" between C and the outside world that 2697 B "firewall" for net 1 that supports IPsec. 2698 C "firewall" for net 2 that supports IPsec.
|
/netbsd-src/external/mpl/dhcp/dist/ |
H A D | README | 208 acting as a firewall, you must be sure to allow DHCP packets through 209 the firewall. In particular, your firewall rules _must_ allow packets 212 firewall's IP address and UDP port 67 through to any address your DHCP 218 filter, if you set up a firewall that blocks UDP port 67 and 68 225 firewall rules as described above.
|
/netbsd-src/crypto/dist/ipsec-tools/src/racoon/samples/ |
H A D | racoon.conf.sample-natt | 12 # traffic. Don't forget to open these ports on your firewall!
|
/netbsd-src/sys/external/gpl2/dts/dist/arch/arm/boot/dts/ |
H A D | omap3-n900.dts | 13 * Default secure signed bootloader (Nokia X-Loader) does not enable L3 firewall 18 * There is "unofficial" version of bootloader which enables AES in L3 firewall 20 * There is also no runtime detection code if AES is disabled in L3 firewall...
|
/netbsd-src/usr.sbin/faithd/ |
H A D | README | 11 firewall-oriented gateway does, but between IPv6 and IPv4 with address
|
/netbsd-src/sys/arch/amd64/conf/ |
H A D | MODULAR | 127 -no pseudo-device ipfilter # IP filter (firewall) and NAT
|
/netbsd-src/external/mpl/bind/dist/doc/dnssec-guide/ |
H A D | getting-started.rst | 111 may mean updating firewall policies or Access Control Lists (ACL) on
|
H A D | validation.rst | 824 Some network equipment, such as a firewall, may make assumptions about 826 is. When a firewall sees a larger DNS packet than it expects, it may either 827 reject the large packet or drop its fragments because the firewall
|
/netbsd-src/dist/pf/etc/ |
H A D | pf.os | 163 # the case that X is a NAT firewall. While nmap is talking to the 164 # device itself, p0f is fingerprinting the guy behind the firewall 184 # system (and probably not quite to the firewall either).
|
/netbsd-src/external/ibm-public/postfix/dist/ |
H A D | RELEASE_NOTES-1.1 | 216 for a bug in old versions of the CISCO PIX firewall software that 420 LMTP, with virus scanning, and with firewall relays that forward
|
H A D | RELEASE_NOTES-2.1 | 269 information with a logfile watching program that updates a firewall
|