openoverlayrouter 1.2.0+ds1-2build1 / etc / oor.conf

This file is indexed.

/etc/oor.conf is in openoverlayrouter 1.2.0+ds1-2build1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below. 

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
################################################
#
# General configuration
#
# debug: Debug levels [0..3]
# map-request-retries: Additional Map-Requests to send per map cache miss
# log-file: Specifies log file used in daemon mode. If it is not specified,  
#   messages are written in syslog file

debug                  = 0 
map-request-retries    = 2
log-file               = /var/log/oor.log
 
# Define the type of LISP device LISPmob will operate as 
#
# operating-mode can be any of:
# xTR, RTR, MN, MS
#
operating-mode         = xTR

# For the rest of this file you can delete the sections that does not apply to 
# the LISP device selected in operating-mode


################################################
#
# MS configuration
#

# Control messages are received and generated through this interface
# Only one interface is supported

control-iface = <iface name>FIXME

# Define an allowed lisp-site to be registered into the Map Server. Several
# lisp-site can be defined.
# 
#   eid-prefix: Accepted EID prefix (IPvX/mask)
#   key-type: Only 1 supported (HMAC-SHA-1-96)
#   key: Password to authenticate the received Map-Registers
#   iid: Instance ID associated with the lisp site [0-16777215]
#   accept-more-specifics [true/false]: Accept more specific prefixes
#     with same authentication information 

lisp-site {
    eid-prefix            = <prefix>FIXME
    key-type              = 1
    key                   = <string>FIXME
    iid                   = 0
    accept-more-specifics = <bool>FIXME
}

# Define a static registered mapping. New Map-Registers overwrites
# the information of this mapping. You can define several eid-prefix.
#   eid-prefix: EID prefix (IPvX/mask) of the mapping
#   iid: Instance ID associated with the lisp site [0-16777215]
#   address: It could be one of the following cases
#      - IPv4 or IPv6 address of the RLOC
#      - ELP name
#   priority [0-255]: Priority for the RLOC of the interface. Locators
#     with lower values are more preferable. This is used for both incoming
#     policy announcements and outgoing traffic policy management
#   weight [0-255]: When priorities are the same for multiple RLOCs, the weight
#     indicates how to balance unicast traffic between them

ms-static-registered-site {
    eid-prefix          = <prefix>FIXME
    iid                 = 0
     rloc-address {
        address         = <string>FIXME
        priority        = <int>FIXME
        weight          = <int>FIXME
    }
}

###############################################
#
# Tunnel Router general configuration
# Common for xTR, RTR & MN
#

# encapsulation: Encapsulation that will use OOR in the data plane. Could be
#   LISP or VXLAN-GPE. LISP is selected by default

encapsulation          = <LISP/VXLAN-GPE>FIXME


# RLOC probing configuration
#   rloc-probe-interval: interval at which periodic RLOC probes are sent
#     (seconds). A value of 0 disables RLOC probing
#   rloc-probe-retries: RLOC probe retries before setting the locator with
#     status down. [0..5]
#   rloc-probe-retries-interval: interval at which RLOC probes retries are
#     sent (seconds) [1..rloc-probe-interval]

rloc-probing {
    rloc-probe-interval             = 30
    rloc-probe-retries              = 2
    rloc-probe-retries-interval     = 5
}

# Encapsulated Map-Requests are sent to this Map-Resolver
# You can define several Map-Resolvers, seprated by comma. Encapsulated 
# Map-Request messages will be sent to only one.
#   address: IPv4 or IPv6 address of the map-resolver  

map-resolver        = {
	<ip-address>FIXME
}

# Static Map Entry of the Map Cache. Several eid-prefix can be defined.
#   eid-prefix: EID prefix (ip-prefix/mask) of the mapping
#   iid: Instance ID associated to the EID. When using VXLAN-GPE, iid configures
#     the VNI of the mapping. [0-16777215]
#   address: It could be one of the following cases
#      - IPv4 or IPv6 address of the RLOC
#      - ELP name
#   priority [0-255]: Priority for the RLOC. Locators with
#     lower values are more preferable. This is used for both incoming
#     policy announcements and outgoing traffic policy management.
#   weight [0-255]: When priorities are the same for multiple RLOCs, the weight
#     indicates how to balance unicast traffic between them.

static-map-cache {
    eid-prefix          = <ip-prefix/mask>FIXME
    iid                 = 0
    rloc-address {
        address         = <string>FIXME
        priority        = <int>FIXME
        weight          = <int>FIXME
    }
}

###############################################
#
# RTR configuration
#

# List of interfaces to be used as outgoing interfaces for the packets sent
# by the RTR. Several rtr-ifaces can be defined. 
#   iface: interface containing the RLOCs to be used for outgoing traffic 
#   ip_version: 4 to use the IPv4 address of the interface and 6 to use the IPv6 
#     address of the interface
#   priority [0-255]: Priority for the RLOC of the interface. Locators
#     with lower values are more preferable. This is used for outgoing
#     traffic policy management.
#   weight [0-255]: When priorities are the same for multiple RLOCs, the weight
#     indicates how to balance unicast traffic between them.

rtr-ifaces {
    rtr-iface {
        iface           = <iface-name>FIXME
        ip_version      = <4/6>FIXME
        priority        = <int>FIXME
        weight          = <int>FIXME
    }
}

###############################################
#
# xTR & MN configuration
#

# NAT Traversl configuration. 
#   nat_traversal_support: check if the node is behind NAT.

nat_traversal_support  = off

# Map-Registers are sent to this Map-Server
# You can define several Map-Servers. Map-Register messages will be sent to all
# of them.
#   address: IPv4 or IPv6 address of the map-server
#   key-type: Only 1 supported (HMAC-SHA-1-96)
#   key: password to authenticate with the map-server
#   proxy-reply [on/off]: Configure map-server to Map-Reply on behalf of the xTR

map-server {
        address        = <ip-address>FIXME
        key-type       = 1
        key            = <password>FIXME
        proxy-reply    = <on/off>FIXME
}

# Packets addressed to non-LISP sites will be encapsulated to this Proxy-ETR
# You can define several Proxy-ETR. Traffic will be balanced according to the
# priority and weight.
#   address: IPv4 or IPv6 address of the Proxy-ETR
#   priority [0-255]: Proxy-ETR with lower values are more preferable.
#   weight [0-255]: When priorities are the same for multiple Proxy-ETRs,
#     the weight indicates how to balance unicast traffic between them.

proxy-etr {
        address     = <ip-address>FIXME
        priority    = <int>FIXME
        weight      = <int>FIXME
}

# IPv4 / IPv6 EID of the node.
#   eid-prefix: EID prefix (ip-prefix/mask) of the mapping
#   iid: Instance ID associated to the EID. When using VXLAN-GPE, iid configures
#     the VNI of the mapping. [0-16777215]
# Two types of RLOCs can be defined:
#   rloc-address: Specifies directly the RLOC of the interface
#     address: It could be one of the following cases
#       - IPv4 or IPv6 address of the RLOC. Address should exist and
#        be assigned to an UP interface during startup process otherwise
#        it is discarded.
#       - ELP name
#   rloc-iface: Specifies the interface associated with the RLOC
#     interface: interface containing the RLOCs associated to this mapping 
#     ip_version: 4 to use the IPv4 address of the interface and 6 to use the IPv6 
#       address of the interface
# Both types of RLOCs use priority and weight
#   priority [0-255]: Priority for the RLOC of the interface. Locators
#     with lower values are more preferable. This is used for both incoming
#     policy announcements and outgoing traffic policy management.
#   weight [0-255]: When priorities are the same for multiple RLOCs, the weight
#     indicates how to balance unicast traffic between them.

database-mapping {
    eid-prefix          = <ip-prefix/mask>FIXME
    iid                 = 0
    rloc-address {
        address         = <string>FIXME
        priority        = <int>FIXME
        weight          = <int>FIXME
    }
    rloc-iface{
        interface       = <string>FIXME
        ip_version      = <4/6>FIXME
        priority        = <int>FIXME
        weight          = <int>FIXME
    }
}

# Current LISP beta-network (lisp4.net/lisp6.net) PITR addresses
# Uncomment the IPv4 or IPv6 list based on your current locators and
# comment the previous 'proxy-itrs' section


#proxy-itrs = {
# LISP beta-network IPv4 PITRs
#        69.31.31.98,                 # eqx-ash-pxtr
#        149.20.48.60,                # isc-pxtr
#        198.6.255.37,                # asp-pxtr
#        173.36.193.25,               # sjc-pxtr
#        129.250.1.63,                # ntt-amer-pxtr
#        217.8.98.33,                 # intouch-pxtr-1
#        217.8.98.35,                 # intouch-pxtr-2
#        193.162.145.46,              # tdc-pxtr
#        158.38.1.92,                 # uninett-pxtr
#        203.181.249.172,             # apan-pxtr
#        202.51.247.10                # sg-nus-pxtr
# LISP beta-network IPv6 PITRs 
#        2001:590::451f:1f62,         # eqx-ash-pxtr
#        2001:4f8:3:d::60,            # isc-pxtr
#        2001:418:4:1:deaf:bebe::10d, # asp-pxtr
#        2001:418:0:1000::613,        # ntt-amer-pxtr
#        2001:200:e000:17::17,        # intouch-pxtr-1
#        2001:67C:21B4:108::b,        # intouch-pxtr-2
#        2001:6c8:41:100:0:2:1:c,     # tdc-pxtr
#        2001:700:0:52E::4,           # uninett-pxtr
#        2001:67C:21B4:107::b         # apan-pxtr
#}

###############################################
#
# Miscellaneous configuration
#

# Structure to define a path involving multiple hops
#   elp-name: Name to define the ELP used as a reference in the rest of the 
#     configuration
#   elp-node: Defines each of the hops of the ELP. Several ones can be defined.
#     In most cases, the last elp-node would be the local RLOC of an xTR
#   address: IPv4 or IPv6 address of the RLOC. The address of the last elp-node 
#     should exist and be assigned to an UP interface during startup process 
#     otherwise it is discarded.
#   strict [true/false]: Not yet implemented. Use false
#   probe [true/false]: Not yet implemented. Use false
#   lookup [true/false]: Not yet implemented. Use false

explicit-locator-path {
    elp-name        = <string>FIXME
    elp-node {
        address     = <ip-address>FIXME
        strict      = <bool>FIXME
        probe       = <bool>FIXME
        lookup      = <bool>FIXME
    }
    elp-node {
        address     = <ip-address>FIXME
        strict      = <bool>FIXME
        probe       = <bool>FIXME
        lookup      = <bool>FIXME
    } 
}

APT Browse - Built by Thomas Orozco.