Mercurial > hg > freeDiameter
view doc/acl_wl.conf.sample @ 1520:5aa6d237b306
Add 3GPP TS 29.561 V16.3.0 (2020-03)
Add AVPs:
- 3GPP-Notification, OctetString, code 110, section 11.3.1
- 3GPP-UE-MAC-Address, OctetString, code 111, section 11.3.1
- 3GPP-Authorization-Reference, OctetString, code 112, section 11.3.1
- 3GPP-Policy-Reference, OctetString, code 113, section 11.3.1
- 3GPP-Session-AMBR, OctetString, code 114, section 11.3.1
- 3GPP-NAI, OctetString, code 115, section 11.3.1
- 3GPP-Session-AMBR-v2, OctetString, code 116, section 11.3.1
- 3GPP-IP-Address-Pool-Id, OctetString, code 118, section 11.3.1
- 3GPP-S-NSSAI, UTF8String, code 200, section 16.3.1
author | Luke Mewburn <luke@mewburn.net> |
---|---|
date | Thu, 09 Apr 2020 13:24:42 +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.