view doc/acl_wl.conf.sample @ 1533:f8561a0f7ac1

Rename IPv6 AVPs per 3GPP TS 29.061 The following AVPs were renamed in 3GPP TS 29.061 V12.6.0 (2014-06) (where "IPv6" was globally changed to "Ipv6" in the standard): - 3GPP-CG-IPv6-Address (14) renamed to 3GPP-CG-Ipv6-Address (14). - 3GPP-SGSN-IPv6-Address (15) renamed to 3GPP-SGSN-Ipv6-Address (15). - 3GPP-GGSN-IPv6-Address (16) renamed to 3GPP-GGSN-Ipv6-Address (16). - 3GPP-IPv6-DNS-Servers (17) renamed to 3GPP-Ipv6-DNS-Servers (17). - MBMS-GGSN-IPv6-Address (917) renamed to MBMS-GGSN-Ipv6-Address (917). - MBMS-BMSC-SSM-IPv6-Address (919) renamed to MBMS-BMSC-SSM-Ipv6-Address (919).
author Luke Mewburn <luke@mewburn.net>
date Mon, 20 Apr 2020 11:44:56 +1000
parents 0dff6a604b0a
children
line wrap: on
line source

# Configuration file for the peer whitelist extension.
#
# This extension is meant to allow connection from remote peers, without actively
# maintaining this connection ourselves (as it would be the case by declaring the 
# peer in a ConnectPeer directive).
#
# This extension supports configuration reload at runtime. Send
# signal SIGUSR1 to the process to cause the process to reload its
# config.
#
# The format of this file is very simple. It contains a list of peer names
# separated by spaces or newlines. 
#
# The peer name must be a fqdn. We allow also a special "*" character as the
# first label of the fqdn, to allow all fqdn with the same domain name.
# Example: *.example.net will allow host1.example.net and host2.example.net
#
# At the beginning of a line, the following flags are allowed (case sensitive) -- either or both can appear:
# ALLOW_OLD_TLS : we accept unprotected CER/CEA exchange with Inband-Security-Id = TLS
# ALLOW_IPSEC   : we accept implicitly protected connection with with peer (Inband-Security-Id = IPSec)
# It is specified for example as:
# ALLOW_IPSEC vpn.example.net vpn2.example.net *.vpn.example.net
# These flag take effect from their position, until the end of the line.

"Welcome to our mercurial repository"