Mercurial > hg > freeDiameter
view doc/test_netemul.conf.sample @ 1515:8430dabbc637
Add 3GPP TS 29.109 V15.0.0 (2017-06)
Add AVPs:
- GBA-UserSecSettings, OctetString, code 400, section 6.3.1.1
- Transaction-Identifier, OctetString, code 401, section 6.3.1.2
- NAF-Id, OctetString, code 402, section 6.3.1.3
- GAA-Service-Identifier, OctetString, code 403, section 6.3.1.4
- Key-ExpiryTime, Time, code 404, section 6.3.1.5
- ME-Key-Material, OctetString, code 405, section 6.3.1.6
- UICC-Key-Material, OctetString, code 406, section 6.3.1.7
- GBA-U-Awareness-Indicator, Enumerated, code 407, section 6.3.1.8
- BootstrapInfoCreationTime, Time, code 408, section 6.3.1.9
- GUSS-Timestamp, Time, code 409, section 6.3.1.10
- GBA-Type, Enumerated, code 410, section 6.3.1.11
- UE-Id, OctetString, code 411, section 6.3.1.12
- UE-Id-Type, Enumerated, code 412, section 6.3.1.13
- UICC-App-Label, OctetString, code 413, section 6.3.1.14
- UICC-ME, Enumerated, code 414, section 6.3.1.15
- Requested-Key-Lifetime, Time, code 415, section 6.3.1.16
- Private-Identity-Request, Enumerated, code 416, section 6.3.1.17
- GBA-Push-Info, OctetString, code 417, section 6.3.1.18
- NAF-SA-Identifier, OctetString, code 418, section 6.3.1.19
- Security-Feature-Request, OctetString, code 419, section 6.3.1.20
- Security-Feature-Response, OctetString, code 420, section 6.3.1.21
Note: 3GPP TS 29.109 table 6.1 row GBA_U-Awareness-Indicator (407)
has an underscore in the name (contrary to RFC 6733 section 4.1).
Fix: GBA_U-Awareness-Indicator (407) renamed to GBA-U-Awareness-Indicator (407).
author | Luke Mewburn <luke@mewburn.net> |
---|---|
date | Thu, 09 Apr 2020 00:34:15 +1000 |
parents | 083317a4e947 |
children |
line wrap: on
line source
# This file contains information for configuring the test_netemul extension. # To find how to have freeDiameter load this extension, please refer to the freeDiameter documentation. # # The test_netemul extension implements a Diameter proxy that behaves like simple forwarding agent, # with the exception that it can introduce delay in the forwarding of the messages and generate duplicates # of messages, as can be expected from a real Diameter network. It can also generate routing errors when # connected to more than 2 peers. # LATENCY: # Two parameters are used to control the delay introduced in the messages. # - latency_average: # This is the average delay introduced in the packets. # Set to 0 to not add any latency (beyond the normal processing time). # The value is expressed as an integer followed by a unit which can # be 's' (seconds) or 'ms' (milliseconds). Example: # latency_average = 700 ms; # # - latency_deviation: # This parameter controls the variance in the latency. It is expressed # as a value between 0 % and 100 %. When set to 0 %, all messages will be delayed # by exactly latency_average. Otherwise, it represents the width of the interval # "around" the average where "most" of the latency will be chosen (the distribution # has a Gaussian shape). Example: # latency_deviation = 25 %; # # The default values give an added latency "mostly" between 0.4 and 0.6 seconds: # latency_average = 500 ms; # latency_deviation = 20 % ; # REORDERING: # There is no special control over the reordering of messages. It may simply happen # as a result of the latency. If you want to get a lot of reordering, set the # latency_variance to a high value. # DUPLICATES: # Duplicate messages are expected in the Diameter protocol by design, as a consequence # of the failover mechanism that provides the protocol's reliability. # - dupl_proba: # This value gives the probability of producing a duplicate of a forwarded message. # The value is comprized between 0 (no duplicates) and 1 (duplicate all messages). # Duplicates are created for requests, but may result in duplicate answers # received by your Diameter client(s), depending on your server(s)'s behavior. # In the case of freeDiameter client, the duplicate answer is automatically filtered out # because the hop-by-hop id has already been used. # Note that each duplicate copy is an independent message, # which receives a different latency, and might be routed to a different server if you # use for example load-balancing. # The parameter can take several forms: # dupl_proba = 0 ; # Disables the generation of duplicate messages completely. # dupl_proba = 1 / 10000 ; # dupl_proba = 0.0001 ; # Around 1 messages over ten thousands will be duplicated. # # Default value: # dupl_proba = 1 / 100 ;