natd.cf.sample revision 50476
1#
2# $FreeBSD: head/sbin/natd/samples/natd.cf.sample 50476 1999-08-28 00:22:10Z peter $
3#
4#
5# Configuration file for natd.
6#
7#
8# Enable logging to file /var/log/alias.log
9#
10log		no
11#
12# Incoming connections.  Should NEVER be set to "yes" if redirect_port,
13# redirect_address, or permanent_link statements are activated in this file!
14#
15# Setting to yes provides additional anti-crack protection
16#
17deny_incoming	no
18#
19# Use sockets to avoid port clashes.  Uses additional system resources, but
20# guarantees successful connections when port numbers conflict
21#
22use_sockets	no
23#
24# Avoid port changes if possible when altering outbound packets. Makes rlogin
25# work in most cases.
26#
27same_ports	yes
28#
29# Verbose mode. Enables dumping of packets and disables
30# forking to background.  Only set to yes for debugging.
31#
32verbose		no
33#
34# Divert port. Can be a name in /etc/services or numeric value.
35#
36port		32000
37#
38# Interface name or address being aliased. Either one,
39# not both is required.
40#
41# Obtain interface name from the command output of "ifconfig -a"
42#
43# alias_address	192.168.0.1
44interface	ep0
45#
46# Alias unregistered addresses or all addresses.  Set this to yes if
47# the inside network is all RFC1918 addresses. 
48#
49unregistered_only	no
50#
51# Configure permanent links. If you use host names instead
52# of addresses here, be sure that name server works BEFORE
53# natd is up - this is usually not the case. So either use
54# numeric addresses or hosts that are in /etc/hosts.
55#
56# Note:  Current versions of FreeBSD all call /etc/rc.firewall
57# BEFORE running named, so if the DNS server and NAT are on the same 
58# machine, the nameserver won't be up if natd is called from /etc/rc.firewall
59#
60# Map connections coming to port 30000 to telnet in my_private_host.
61# Remember to allow the connection /etc/rc.firewall also.
62#
63#  The following permanent_link and redirect_port statements are equivalent
64#permanent_link		tcp my_private_host:telnet 0.0.0.0:0 30000
65#redirect_port		tcp my_private_host:telnet 30000
66#
67# Map connections coming from host.xyz.com to port 30001 to 
68# telnet in another_host.
69#permanent_link		tcp another_host:telnet host.xyz.com:0 30001
70#
71# Static NAT address mapping:
72#
73#  ipconfig must apply any legal IP numbers that inside hosts
74# will be known by to the outside interface.  These are sometimes known as
75# virtual IP numbers.  It's suggested to use the "interface" directive
76# instead of the "alias_address" directive to make it more clear what is
77# going on. (although both will work)
78#
79# DNS in this situation can get hairy.  For example, an inside host
80# named aweb.company.com is located at 192.168.1.56, and needs to be 
81# accessible through a legal IP number like 198.105.232.1.  If both
82# 192.168.1.56 and 198.105.232.1 are set up as address records in the DNS
83# for aweb.company.com, then external hosts attempting to access
84# aweb.company.com may use address 192.168.1.56 which is inaccessible to them.
85#
86# The obvious solution is to use only a single address for the name, the
87# outside address.  However, this creates needless traffic through the
88# NAT, because inside hosts will go through the NAT to get to the legal
89# number, even when the inside number is on the same subnet as they are!
90#
91# It's probably not a good idea to use DNS names in redirect_address statements
92#
93#The following mapping points outside address 198.105.232.1 to 192.168.1.56
94#redirect_address  192.168.1.56		198.105.232.1
95