d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

`permanent_link' is obsolete; update examples.

Browse Source
This commit is contained in:
Ruslan Ermilov 1999-09-13 18:18:33 +00:00
parent 73d10c7f63
commit 578d29dd12
1 changed files with 7 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
sbin/natd/samples/natd.cf.sample
View File

@ -9,8 +9,8 @@
#
log no
#
# Incoming connections. Should NEVER be set to "yes" if redirect_port,
# redirect_address, or permanent_link statements are activated in this file!
# Incoming connections. Should NEVER be set to "yes" if redirect_port
# or redirect_address statements are activated in this file!
#
# Setting to yes provides additional anti-crack protection
#
@ -44,7 +44,7 @@ port 32000
interface ep0
#
# Alias unregistered addresses or all addresses. Set this to yes if
# the inside network is all RFC1918 addresses.
# the inside network is all RFC1918 addresses.
#
unregistered_only no
#
@ -54,19 +54,17 @@ unregistered_only no
# numeric addresses or hosts that are in /etc/hosts.
#
# Note: Current versions of FreeBSD all call /etc/rc.firewall
# BEFORE running named, so if the DNS server and NAT are on the same
# BEFORE running named, so if the DNS server and NAT are on the same
# machine, the nameserver won't be up if natd is called from /etc/rc.firewall
#
# Map connections coming to port 30000 to telnet in my_private_host.
# Remember to allow the connection /etc/rc.firewall also.
#
# The following permanent_link and redirect_port statements are equivalent
#permanent_link tcp my_private_host:telnet 0.0.0.0:0 30000
#redirect_port tcp my_private_host:telnet 30000
#
# Map connections coming from host.xyz.com to port 30001 to
# Map connections coming from host.xyz.com to port 30001 to
# telnet in another_host.
#permanent_link tcp another_host:telnet host.xyz.com:0 30001
#redirect_port tcp another_host:telnet 30001 host.xyz.com
#
# Static NAT address mapping:
#
@ -77,7 +75,7 @@ unregistered_only no
# going on. (although both will work)
#
# DNS in this situation can get hairy. For example, an inside host
# named aweb.company.com is located at 192.168.1.56, and needs to be
# named aweb.company.com is located at 192.168.1.56, and needs to be
# accessible through a legal IP number like 198.105.232.1. If both
# 192.168.1.56 and 198.105.232.1 are set up as address records in the DNS
# for aweb.company.com, then external hosts attempting to access