1 ################################################
3 # General configuration
5 # debug: Debug levels [0..3]
6 # map-request-retries: Additional Map-Requests to send per map cache miss
7 # log-file: Specifies log file used in daemon mode. If it is not specified,
8 # messages are written in syslog file
11 map-request-retries = 2
12 log-file = /var/log/oor.log
14 # Define the type of LISP device LISPmob will operate as
16 # operating-mode can be any of:
21 # For the rest of this file you can delete the sections that does not apply to
22 # the LISP device selected in operating-mode
25 ################################################
30 # Control messages are received and generated through this interface
31 # Only one interface is supported
35 # Define an allowed lisp-site to be registered into the Map Server. Several
36 # lisp-site can be defined.
38 # eid-prefix: Accepted EID prefix (IPvX/mask)
39 # key-type: Only 1 supported (HMAC-SHA-1-96)
40 # key: Password to authenticate the received Map-Registers
41 # iid: Instance ID associated with the lisp site [0-16777215]
42 # accept-more-specifics [true/false]: Accept more specific prefixes
43 # with same authentication information
46 eid-prefix = 192.168.16.11/32
50 accept-more-specifics = true
54 ###############################################
59 # List of interfaces to be used as outgoing interfaces for the packets sent
60 # by the RTR. Several rtr-ifaces can be defined.
61 # iface: interface containing the RLOCs to be used for outgoing traffic
62 # ip_version: 4 to use the IPv4 address of the interface and 6 to use the IPv6
63 # address of the interface
64 # priority [0-255]: Priority for the RLOC of the interface. Locators
65 # with lower values are more preferable. This is used for outgoing
66 # traffic policy management.
67 # weight [0-255]: When priorities are the same for multiple RLOCs, the weight
68 # indicates how to balance unicast traffic between them.
79 ###############################################
81 # xTR & MN configuration
84 # NAT Traversl configuration.
85 # nat_traversal_support: check if the node is behind NAT.
87 nat_traversal_support = off
89 # Map-Registers are sent to this Map-Server
90 # You can define several Map-Servers. Map-Register messages will be sent to all
92 # address: IPv4 or IPv6 address of the map-server
93 # key-type: Only 1 supported (HMAC-SHA-1-96)
94 # key: password to authenticate with the map-server
95 # proxy-reply [on/off]: Configure map-server to Map-Reply on behalf of the xTR
98 address = 192.168.16.11
104 # Packets addressed to non-LISP sites will be encapsulated to this Proxy-ETR
105 # You can define several Proxy-ETR. Traffic will be balanced according to the
106 # priority and weight.
107 # address: IPv4 or IPv6 address of the Proxy-ETR
108 # priority [0-255]: Proxy-ETR with lower values are more preferable.
109 # weight [0-255]: When priorities are the same for multiple Proxy-ETRs,
110 # the weight indicates how to balance unicast traffic between them.
113 address = 192.168.16.11
118 # IPv4 / IPv6 EID of the node.
119 # eid-prefix: EID prefix (ip-prefix/mask) of the mapping
120 # iid: Instance ID associated to the EID. When using VXLAN-GPE, iid configures
121 # the VNI of the mapping. [0-16777215]
122 # Two types of RLOCs can be defined:
123 # rloc-address: Specifies directly the RLOC of the interface
124 # address: It could be one of the following cases
125 # - IPv4 or IPv6 address of the RLOC. Address should exist and
126 # be assigned to an UP interface during startup process otherwise
129 # rloc-iface: Specifies the interface associated with the RLOC
130 # interface: interface containing the RLOCs associated to this mapping
131 # ip_version: 4 to use the IPv4 address of the interface and 6 to use the IPv6
132 # address of the interface
133 # Both types of RLOCs use priority and weight
134 # priority [0-255]: Priority for the RLOC of the interface. Locators
135 # with lower values are more preferable. This is used for both incoming
136 # policy announcements and outgoing traffic policy management.
137 # weight [0-255]: When priorities are the same for multiple RLOCs, the weight
138 # indicates how to balance unicast traffic between them.
141 eid-prefix = 2.2.2.2/32
144 address = 192.168.16.31
156 # Current LISP beta-network (lisp4.net/lisp6.net) PITR addresses
157 # Uncomment the IPv4 or IPv6 list based on your current locators and
158 # comment the previous 'proxy-itrs' section
162 # LISP beta-network IPv4 PITRs
163 # 69.31.31.98, # eqx-ash-pxtr
164 # 149.20.48.60, # isc-pxtr
165 # 198.6.255.37, # asp-pxtr
166 # 173.36.193.25, # sjc-pxtr
167 # 129.250.1.63, # ntt-amer-pxtr
168 # 217.8.98.33, # intouch-pxtr-1
169 # 217.8.98.35, # intouch-pxtr-2
170 # 193.162.145.46, # tdc-pxtr
171 # 158.38.1.92, # uninett-pxtr
172 # 203.181.249.172, # apan-pxtr
173 # 202.51.247.10 # sg-nus-pxtr
174 # LISP beta-network IPv6 PITRs
175 # 2001:590::451f:1f62, # eqx-ash-pxtr
176 # 2001:4f8:3:d::60, # isc-pxtr
177 # 2001:418:4:1:deaf:bebe::10d, # asp-pxtr
178 # 2001:418:0:1000::613, # ntt-amer-pxtr
179 # 2001:200:e000:17::17, # intouch-pxtr-1
180 # 2001:67C:21B4:108::b, # intouch-pxtr-2
181 # 2001:6c8:41:100:0:2:1:c, # tdc-pxtr
182 # 2001:700:0:52E::4, # uninett-pxtr
183 # 2001:67C:21B4:107::b # apan-pxtr