[OOR-Users] xTR mode with NAT Traversal | non-icml traffic issue's --> assistance needed
Niek van der Ven
niekvanderven at hotmail.com
Fri Sep 23 14:07:50 CEST 2016
Dear Albert,
I can see the change of the RTR to: 217.8.98.33 but now i also lost ICMP packetise both directions for some reason: startup log below.
I was testing with http://www.cogentco.com/fr/network/looking-glass
traceroute to 153.16.57.129 (153.16.57.129), 30 hops max, 60 byte packets
1 gi0-0-0-19.6.agr11.vie01.atlas.cogentco.com<http://agr11.vie01.atlas.cogentco.com> (130.117.254.97) 1.354 ms 1.383 ms
2 te0-6-0-15.ccr21.vie01.atlas.cogentco.com<http://ccr21.vie01.atlas.cogentco.com> (154.54.56.117) 0.738 ms 0.751 ms
3 be2974.ccr21.muc03.atlas.cogentco.com<http://ccr21.muc03.atlas.cogentco.com> (154.54.58.5) 6.791 ms 6.649 ms
4 be2959.ccr41.fra03.atlas.cogentco.com<http://ccr41.fra03.atlas.cogentco.com> (154.54.36.53) 12.223 ms be2960.ccr42.fra03.atlas.cogentco.com<http://ccr42.fra03.atlas.cogentco.com> (154.54.36.253) 12.290 ms
5 be2813.ccr41.ams03.atlas.cogentco.com<http://ccr41.ams03.atlas.cogentco.com> (130.117.0.121) 18.695 ms be2814.ccr42.ams03.atlas.cogentco.com<http://ccr42.ams03.atlas.cogentco.com> (130.117.0.141) 18.714 ms
6 be2311.ccr21.ams04.atlas.cogentco.com<http://ccr21.ams04.atlas.cogentco.com> (154.54.74.90) 43.877 ms 45.777 ms
7 149.11.38.18 (149.11.38.18) 18.855 ms 18.870 ms
8 217.8.98.33 (217.8.98.33) 19.477 ms 19.793 ms —> which is the RTR but no packets sent into the tunnel for my net 153.16.57.129 and 153.16.57.130
9 * *
10 * *
sudo tcpdump -i lispTun0 -vvv
sudo: unable to resolve host niek-xtr
tcpdump: WARNING: lispTun0: no IPv4 address assigned
tcpdump: listening on lispTun0, link-type RAW (Raw IP), capture size 65535 bytes
12:04:12.415124 IP (tos 0xc0, ttl 249, id 19141, offset 0, flags [none], proto UDP (17), length 132)
217.8.98.33.4342 > 10.1.1.145.4342: [udp sum ok] UDP, length 104
12:05:12.478001 IP (tos 0xc0, ttl 249, id 36266, offset 0, flags [none], proto UDP (17), length 132)
217.8.98.33.4342 > 10.1.1.145.4342: [udp sum ok] UDP, length 104
12:06:12.415471 IP (tos 0xc0, ttl 249, id 52765, offset 0, flags [none], proto UDP (17), length 132)
217.8.98.33.4342 > 10.1.1.145.4342: [udp sum ok] UDP, length 104
oor -f /etc/oor.conf
[2016/9/23 11:59:12] INFO: Open Overlay Router v1.1 compiled for Linux
[2016/9/23 11:59:12] WARNING: Rights: Effective [4294967295] Permitted [4294967295]
[2016/9/23 11:59:12] INFO: Building address to interface hash table
[2016/9/23 11:59:12] INFO: Control created!
[2016/9/23 11:59:12] INFO: Log level: High Debug
[2016/9/23 11:59:12] DEBUG: Creating map cache and local mapping database
[2016/9/23 11:59:12] DEBUG-3: Creating mdb...
[2016/9/23 11:59:12] DEBUG-3: Creating mdb...
[2016/9/23 11:59:12] DEBUG-2: lisp_addr_get_ip_pref_addr: Not applicable to ip addressess
[2016/9/23 11:59:12] DEBUG: Finished Constructing xTR
[2016/9/23 11:59:12] INFO: Device working in mode xTR registering with control
[2016/9/23 11:59:12] DEBUG-2: nat_set_xTR_ID: xTR_ID initialiazed with value: 94da00000000922952a79b884226a158
[2016/9/23 11:59:12] DEBUG: NAT support enabled. Set defaul RLOC to IPv4 family
[2016/9/23 11:59:12] DEBUG: Configuration file: RLOC probing not defined. Setting default values: RLOC Probing Interval: 30 sec.
[2016/9/23 11:59:12] DEBUG-3: The server 217.8.98.42 has been added to the list
[2016/9/23 11:59:12] DEBUG: Added 217.8.98.42 to map-resolver list
[2016/9/23 11:59:12] DEBUG: Added 217.8.98.42 to map-server list
[2016/9/23 11:59:12] DEBUG-2: mapping_get_locators_with_afi: List for OOR AFI 1 and afi 2 not yet created
[2016/9/23 11:59:12] DEBUG-2: mapping_add_locator: Added locator 217.8.98.42 to the mapping with EID 0.0.0.0/32.
[2016/9/23 11:59:12] DEBUG: Added 217.8.98.42 to proxy-etr list
[2016/9/23 11:59:12] DEBUG-2: mapping_add_locator: Added locator 193.162.145.46 to the mapping with EID 0.0.0.0/32.
[2016/9/23 11:59:12] DEBUG: Added 193.162.145.46 to proxy-etr list
[2016/9/23 11:59:12] DEBUG: Balancing locator vector for 0.0.0.0/32:
[2016/9/23 11:59:12] DEBUG: IPv4 locators vector (2 locators): 217.8.98.42 193.162.145.46
[2016/9/23 11:59:12] DEBUG: IPv6 locators vector (0 locators):
[2016/9/23 11:59:12] DEBUG: IPv4 & IPv6 locators vector (0 locators):
[2016/9/23 11:59:12] DEBUG-3: The server 217.8.98.33 has been added to the list
[2016/9/23 11:59:12] DEBUG: Added 217.8.98.33 to proxy-itr list
[2016/9/23 11:59:12] DEBUG-2: Adding interface eth0 with index 2 to iface list
[2016/9/23 11:59:12] DEBUG-2: Interface eth0 with index 2 added to interfaces lists
[2016/9/23 11:59:12] DEBUG-3: open_ip_raw_socket: open socket 5 with afi: 2
[2016/9/23 11:59:12] DEBUG: bind_socket: Binded socket 5 to source address 10.1.1.145 and port 0 with afi 2
[2016/9/23 11:59:12] DEBUG: add_rule: Add rule -> Send packets with source address 10.1.1.145 and destination address _NULL_ to the table 2 with priority 2.
[2016/9/23 11:59:12] DEBUG-2: parse_rloc_address: Locator stucture created:
10.1.1.145, Up, 0/0, 255/0
[2016/9/23 11:59:12] DEBUG-2: mapping_get_locators_with_afi: List for OOR AFI 1 and afi 2 not yet created
[2016/9/23 11:59:12] DEBUG-2: mapping_get_locators_with_afi: List for OOR AFI 1 and afi 2 not yet created
[2016/9/23 11:59:12] DEBUG-2: mapping_add_locator: Added locator 10.1.1.145 to the mapping with EID 153.16.57.128/28.
[2016/9/23 11:59:12] DEBUG: Balancing locator vector for 153.16.57.128/28:
[2016/9/23 11:59:12] DEBUG: IPv4 locators vector (1 locators): 10.1.1.145
[2016/9/23 11:59:12] DEBUG: IPv6 locators vector (0 locators):
[2016/9/23 11:59:12] DEBUG: IPv4 & IPv6 locators vector (0 locators):
[2016/9/23 11:59:12] DEBUG-3: Couldn't find mapping for EID 153.16.57.128/28 in local mappings database
[2016/9/23 11:59:12] DEBUG-3: _add_ippref_entry: Added map cache data for 153.16.57.128/28
[2016/9/23 11:59:12] DEBUG-3: mdb_add_entry: inserted 153.16.57.128/28
[2016/9/23 11:59:12] DEBUG: Added EID prefix 153.16.57.128/28 in the database.
[2016/9/23 11:59:12] DEBUG-2: Configuring data plane
[2016/9/23 11:59:12] DEBUG-3: TUN/TAP ifindex is: 15
[2016/9/23 11:59:12] DEBUG: TUN/TAP mtu set to 1440
[2016/9/23 11:59:12] DEBUG-2: Tunnel fd at creation is 6
[2016/9/23 11:59:12] DEBUG: TUN interface UP.
[2016/9/23 11:59:12] DEBUG: add_route: added route to the system: src addr: -, dst prefix:-, gw: -, table: 100
[2016/9/23 11:59:12] DEBUG: add_route: added route to the system: src addr: -, dst prefix:-, gw: -, table: 100
[2016/9/23 11:59:12] DEBUG-3: open_udp_raw_socket: Created socket 7 associated to IPv4 addresses
[2016/9/23 11:59:12] DEBUG-3: open_udp_datagram_socket: Created socket 8 associated to IPv4 addresses
[2016/9/23 11:59:12] DEBUG: bind_socket: Binded socket 8 to source address _NULL_ and port 4341 with afi 2
[2016/9/23 11:59:12] DEBUG-2: Default IPv4 data iface eth0: 10.1.1.145
[2016/9/23 11:59:12] DEBUG: Data plane initialized
[2016/9/23 11:59:12] DEBUG-3: open_udp_datagram_socket: Created socket 9 associated to IPv4 addresses
[2016/9/23 11:59:12] DEBUG: bind_socket: Binded socket 9 to source address _NULL_ and port 4342 with afi 2
[2016/9/23 11:59:12] DEBUG-2: Default IPv4 control iface eth0: 10.1.1.145
[2016/9/23 11:59:12] DEBUG: Control initialized
[2016/9/23 11:59:12] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/23 11:59:12] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/23 11:59:12] DEBUG: tun_update_route: Process new gateway associated to the interface eth0: 10.1.1.1
[2016/9/23 11:59:12] DEBUG: add_route: added route to the system: src addr: -, dst prefix:-, gw: 10.1.1.1, table: 2
[2016/9/23 11:59:12] DEBUG-2: xtr_if_event: Reconfiguring Info Request process for locator 10.1.1.145 of the mapping 153.16.57.128/28.
[2016/9/23 11:59:12] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/23 11:59:12] DEBUG-2: xtr_if_event: Reconfiguring Info Request process for locator 10.1.1.145 of the mapping 153.16.57.128/28.
[2016/9/23 11:59:12] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/23 11:59:12] DEBUG-3: process_nl_new_unicast_route: the netlink message is not for any interface associated with RLOCs (eth1)
[2016/9/23 11:59:12] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/23 11:59:12] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/23 11:59:12] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/23 11:59:12] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/23 11:59:12] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/23 11:59:12] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/23 11:59:12] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/23 11:59:12] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/23 11:59:12] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/23 11:59:12] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/23 11:59:12] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/23 11:59:12] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/23 11:59:12] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/23 11:59:12] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/23 11:59:12] DEBUG-3: process_nl_new_unicast_route: the netlink message is not for any interface associated with RLOCs (eth1)
[2016/9/23 11:59:12] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/23 11:59:12] DEBUG: process_nl_new_unicast_route: Default RLOC afi defined (-a #): Skipped route with destination address IPv6 in iface eth0
[2016/9/23 11:59:12] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/23 11:59:12] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/23 11:59:12] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/23 11:59:12] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/23 11:59:12] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/23 11:59:12] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/23 11:59:12] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/23 11:59:12] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/23 11:59:12] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/23 11:59:12] DEBUG:
Starting xTR ...
[2016/9/23 11:59:12] DEBUG: Balancing locator vector for 0.0.0.0/32:
[2016/9/23 11:59:12] DEBUG: IPv4 locators vector (2 locators): 217.8.98.42 193.162.145.46
[2016/9/23 11:59:12] DEBUG: IPv6 locators vector (0 locators):
[2016/9/23 11:59:12] DEBUG: IPv4 & IPv6 locators vector (0 locators):
[2016/9/23 11:59:12] INFO: NAT aware on -> No Map Resolver will be used.
[2016/9/23 11:59:12] INFO: NAT aware on -> disabling RLOC Probing
[2016/9/23 11:59:12] DEBUG-3: locators_classify_in_4_6: No locators to classify for mapping with eid 0.0.0.0/32
[2016/9/23 11:59:12] DEBUG: Balancing locator vector for 0.0.0.0/32:
[2016/9/23 11:59:12] DEBUG: IPv4 locators vector (0 locators):
[2016/9/23 11:59:12] DEBUG: IPv6 locators vector (0 locators):
[2016/9/23 11:59:12] DEBUG: IPv4 & IPv6 locators vector (0 locators):
[2016/9/23 11:59:12] DEBUG: ****** Summary of the xTR configuration ******
[2016/9/23 11:59:12] DEBUG: ****************** LISP Local Mappings ****************
[2016/9/23 11:59:12] DEBUG: EID: 153.16.57.128/28, ttl: 10, loc-count: 1, action: no-action, auth: 1
RLOC: 10.1.1.145, Up, 0/0, 255/0
[2016/9/23 11:59:12] DEBUG: *******************************************************
[2016/9/23 11:59:12] DEBUG: **************** LISP Mapping Cache ******************
[2016/9/23 11:59:12] DEBUG: *******************************************************
[2016/9/23 11:59:12] DEBUG: ******************* Map-Servers list ********************************
[2016/9/23 11:59:12] DEBUG: | Locator (RLOC) | Key Type |
[2016/9/23 11:59:12] DEBUG: | 217.8.98.42 | HMAC-SHA-1-96 |
[2016/9/23 11:59:12] DEBUG: ************* Map Resolvers ***************
[2016/9/23 11:59:12] DEBUG: ************************* Proxy ETRs List ****************************
[2016/9/23 11:59:12] DEBUG: | Locator (RLOC) | Status | Priority/Weight |
[2016/9/23 11:59:12] DEBUG: ************* Proxy-ITRs ***************
[2016/9/23 11:59:12] DEBUG: [1] => 217.8.98.33
[2016/9/23 11:59:12] DEBUG: add_rule: Add rule -> Send packets with source address 153.16.57.128/28 and destination address _NULL_ to the table 100 with priority 100.
[2016/9/23 11:59:12] DEBUG: add_rule: Add rule -> Send packets with source address _NULL_ and destination address 153.16.57.128/28 to the table 254 with priority 99.
[2016/9/23 11:59:12] DEBUG: Balancing locator vector for 153.16.57.128/28:
[2016/9/23 11:59:12] DEBUG: IPv4 locators vector (1 locators): 10.1.1.145
[2016/9/23 11:59:12] DEBUG: IPv6 locators vector (0 locators):
[2016/9/23 11:59:12] DEBUG: IPv4 & IPv6 locators vector (0 locators):
[2016/9/23 11:59:12] DEBUG: Sent Info Request for mapping 153.16.57.128/28 to 217.8.98.42 from locator 10.1.1.145
[2016/9/23 11:59:12] DEBUG: Info Request -> nonce bd627fac5fef7bbd, EID: 153.16.57.128/28, MS: 217.8.98.42
[2016/9/23 11:59:12] DEBUG: Sent control message IP: 10.1.1.145 -> 217.8.98.42 UDP: 4342 -> 4342
[2016/9/23 11:59:12] INFO:
Open Overlay Router (v1.1): started...
[2016/9/23 11:59:12] DEBUG-3: OOR_API: zmq_ctx_new errno: Success
[2016/9/23 11:59:12] DEBUG-3: OOR_API: zmq_socket: Success
[2016/9/23 11:59:12] DEBUG-2: OOR_API: API server initiated using ZMQ
[2016/9/23 11:59:12] DEBUG: Received Info Reply -> nonce bd627fac5fef7bbd, IP: 217.8.98.42 -> 10.1.1.145, UDP: 4342 -> 4342
[2016/9/23 11:59:12] DEBUG-2: mapping_add_locator: Added locator 217.8.98.33 to the mapping with EID 153.16.57.128/28.
[2016/9/23 11:59:12] DEBUG: Balancing locator vector for 153.16.57.128/28:
[2016/9/23 11:59:12] DEBUG: IPv4 locators vector (1 locators): 10.1.1.145
[2016/9/23 11:59:12] DEBUG: IPv6 locators vector (0 locators):
[2016/9/23 11:59:12] DEBUG: IPv4 & IPv6 locators vector (0 locators):
[2016/9/23 11:59:12] DEBUG-2: mapping_get_locators_with_afi: List for OOR AFI 1 and afi 2 not yet created
[2016/9/23 11:59:12] DEBUG-2: mapping_add_locator: Added locator 217.8.98.33 to the mapping with EID 0.0.0.0/32.
[2016/9/23 11:59:12] DEBUG: Balancing locator vector for 0.0.0.0/32:
[2016/9/23 11:59:12] DEBUG: IPv4 locators vector (1 locators): 217.8.98.33
[2016/9/23 11:59:12] DEBUG: IPv6 locators vector (0 locators):
[2016/9/23 11:59:12] DEBUG: IPv4 & IPv6 locators vector (0 locators):
[2016/9/23 11:59:12] DEBUG: ECM -> flags:s, inner IP: 10.1.1.145 -> 217.8.98.42, inner UDP: 4342 -> 4342
[2016/9/23 11:59:12] DEBUG: Map-Register -> flags:PIRM record-count: 1 nonce 3b8df0ac5fe59d3b, Inner IP: 10.1.1.145 -> 217.8.98.42, EID: 153.16.57.128/28, RTR: 217.8.98.33
[2016/9/23 11:59:12] DEBUG: Sent control message IP: 10.1.1.145 -> 217.8.98.33 UDP: 4341 -> 4342
[2016/9/23 11:59:12] DEBUG: Sent Encap Map-Register for mapping 153.16.57.128/28 to MS 217.8.98.42 from RLOC 10.1.1.145 through RTR 217.8.98.33
[2016/9/23 11:59:12] DEBUG: Info Request of 153.16.57.128/28 to 217.8.98.42 from locator 10.1.1.145 programmed in 30 minutes.
[2016/9/23 11:59:12] DEBUG-3: xTR: Completed processing of LISP control message
[2016/9/23 11:59:12] DEBUG-3: INPUT (4341): Inner IP: 217.8.98.33 -> 10.1.1.145
[2016/9/23 11:59:12] DEBUG: Received Map-Notify-> flags:IR, record-count: 1, nonce 3B8DF0AC5FE59D3B, IP: 217.8.98.33 -> 10.1.1.145, UDP: 4342 -> 4342
[2016/9/23 11:59:12] DEBUG: Received Data Map Notify
[2016/9/23 11:59:12] DEBUG: Mapping-record -> ttl: 10 loc-count: 2 action: no-action auth: 0 map-version: 0 eid: 153.16.57.128/28
[2016/9/23 11:59:12] DEBUG: Locator-record -> flags: L=0,p=0,R=0, p/w: 0/0 255/0, addr: 10.1.1.145
[2016/9/23 11:59:12] DEBUG: Locator-record -> flags: L=0,p=0,R=1, p/w: 1/100 255/0, addr: 217.8.98.33
[2016/9/23 11:59:12] DEBUG-2: mapping_get_locators_with_afi: List for OOR AFI 1 and afi 2 not yet created
[2016/9/23 11:59:12] DEBUG-2: mapping_add_locator: Added locator 217.8.98.33 to the mapping with EID 153.16.57.128/28.
[2016/9/23 11:59:12] DEBUG-2: mapping_add_locator: Added locator 10.1.1.145 to the mapping with EID 153.16.57.128/28.
[2016/9/23 11:59:12] DEBUG: Map-Notify message confirms correct registration of 153.16.57.128/28.Programing next Map-Register in 60 seconds
[2016/9/23 11:59:12] DEBUG-3: xTR: Completed processing of LISP control message
[2016/9/23 12:0:12] DEBUG: ECM -> flags:s, inner IP: 10.1.1.145 -> 217.8.98.42, inner UDP: 4342 -> 4342
[2016/9/23 12:0:12] DEBUG: Map-Register -> flags:PIRM record-count: 1 nonce 6be6cee657ffff6f, Inner IP: 10.1.1.145 -> 217.8.98.42, EID: 153.16.57.128/28, RTR: 217.8.98.33
[2016/9/23 12:0:12] DEBUG: Sent control message IP: 10.1.1.145 -> 217.8.98.33 UDP: 4341 -> 4342
[2016/9/23 12:0:12] DEBUG: Sent Encap Map-Register for mapping 153.16.57.128/28 to MS 217.8.98.42 from RLOC 10.1.1.145 through RTR 217.8.98.33
[2016/9/23 12:0:12] DEBUG-3: INPUT (4341): Inner IP: 217.8.98.33 -> 10.1.1.145
[2016/9/23 12:0:12] DEBUG: Received Map-Notify-> flags:IR, record-count: 1, nonce 6BE6CEE657FFFF6F, IP: 217.8.98.33 -> 10.1.1.145, UDP: 4342 -> 4342
[2016/9/23 12:0:12] DEBUG: Received Data Map Notify
[2016/9/23 12:0:12] DEBUG: Mapping-record -> ttl: 10 loc-count: 2 action: no-action auth: 0 map-version: 0 eid: 153.16.57.128/28
[2016/9/23 12:0:12] DEBUG: Locator-record -> flags: L=0,p=0,R=0, p/w: 0/0 255/0, addr: 10.1.1.145
[2016/9/23 12:0:12] DEBUG: Locator-record -> flags: L=0,p=0,R=1, p/w: 1/100 255/0, addr: 217.8.98.33
[2016/9/23 12:0:12] DEBUG-2: mapping_get_locators_with_afi: List for OOR AFI 1 and afi 2 not yet created
[2016/9/23 12:0:12] DEBUG-2: mapping_add_locator: Added locator 217.8.98.33 to the mapping with EID 153.16.57.128/28.
[2016/9/23 12:0:12] DEBUG-2: mapping_add_locator: Added locator 10.1.1.145 to the mapping with EID 153.16.57.128/28.
[2016/9/23 12:0:12] DEBUG: Map-Notify message confirms correct registration of 153.16.57.128/28.Programing next Map-Register in 60 seconds
[2016/9/23 12:0:12] DEBUG-3: xTR: Completed processing of LISP control message
[2016/9/23 12:1:12] DEBUG: ECM -> flags:s, inner IP: 10.1.1.145 -> 217.8.98.42, inner UDP: 4342 -> 4342
[2016/9/23 12:1:12] DEBUG: Map-Register -> flags:PIRM record-count: 1 nonce ee54ca3a57fd5dee, Inner IP: 10.1.1.145 -> 217.8.98.42, EID: 153.16.57.128/28, RTR: 217.8.98.33
[2016/9/23 12:1:12] DEBUG: Sent control message IP: 10.1.1.145 -> 217.8.98.33 UDP: 4341 -> 4342
[2016/9/23 12:1:12] DEBUG: Sent Encap Map-Register for mapping 153.16.57.128/28 to MS 217.8.98.42 from RLOC 10.1.1.145 through RTR 217.8.98.33
[2016/9/23 12:1:12] DEBUG-3: INPUT (4341): Inner IP: 217.8.98.33 -> 10.1.1.145
[2016/9/23 12:1:12] DEBUG: Received Map-Notify-> flags:IR, record-count: 1, nonce EE54CA3A57FD5DEE, IP: 217.8.98.33 -> 10.1.1.145, UDP: 4342 -> 4342
[2016/9/23 12:1:12] DEBUG: Received Data Map Notify
[2016/9/23 12:1:12] DEBUG: Mapping-record -> ttl: 10 loc-count: 2 action: no-action auth: 0 map-version: 0 eid: 153.16.57.128/28
[2016/9/23 12:1:12] DEBUG: Locator-record -> flags: L=0,p=0,R=0, p/w: 0/0 255/0, addr: 10.1.1.145
[2016/9/23 12:1:12] DEBUG: Locator-record -> flags: L=0,p=0,R=1, p/w: 1/100 255/0, addr: 217.8.98.33
[2016/9/23 12:1:12] DEBUG-2: mapping_get_locators_with_afi: List for OOR AFI 1 and afi 2 not yet created
[2016/9/23 12:1:12] DEBUG-2: mapping_add_locator: Added locator 217.8.98.33 to the mapping with EID 153.16.57.128/28.
[2016/9/23 12:1:12] DEBUG-2: mapping_add_locator: Added locator 10.1.1.145 to the mapping with EID 153.16.57.128/28.
[2016/9/23 12:1:12] DEBUG: Map-Notify message confirms correct registration of 153.16.57.128/28.Programing next Map-Register in 60 seconds
[2016/9/23 12:1:12] DEBUG-3: xTR: Completed processing of LISP control message
On 23 Sep 2016, at 13:18, Albert López <alopez at ac.upc.edu<mailto:alopez at ac.upc.edu>> wrote:
Hi
When nat-traversal support is enabled the proxy-etrs are not used. A part from this, your configuration looks good. I have reconfigured beta network to use another RTR and I think that know it will work, at least it worked for me :-). Please, let me know if it is working for you too.
Best regards
Albert
On 23/09/16 10:17, Niek van der Ven wrote:
Dear Albert,
Thanx for ur reply, i’am using only one xTR and this one is connected via the same NAT.
I tried different DNS servers but no luck, i see the DNS request destined for the LISP tunnel but no reply coming back except icmp, not wget, curl (tcp), or DNS NTP (ump)
So the below config should work fine with the proxy 217.8.98.42, 193.162.145.46?
Or maybe better question which devices do support NAT traversal and can i use the with my account ?
many thanx again for ur support!
niek
###############
Lisp config:
################
debug = 3
map-request-retries = 3
log-file = /var/log/oor.log
operating-mode = xTR
encapsulation = LISP
rloc-probing {
rloc-probe-interval = 30
rloc-probe-retries = 2
rloc-probe-retries-interval = 5
}
map-resolver = {
217.8.98.42
}
nat_traversal_support = on
map-server {
address = 217.8.98.42
key-type = 1
key = <ommitted>
proxy-reply = on
}
proxy-etr {
address = 217.8.98.42
priority = 0
weight = 0
}
proxy-etr {
address = 193.162.145.46
priority = 0
weight = 0
}
database-mapping {
eid-prefix = 153.16.57.128/28
iid = 0
rloc-address {
address = 10.1.1.145
priority = 0
weight = 0
}
}
proxy-itrs = {
217.8.98.33
}
###############################################
On 23 Sep 2016, at 09:44, Albert López <alopez at ac.upc.edu<mailto:alopez at ac.upc.edu>> wrote:
Dear Niek,
Are you using more than one xTR/MN connected behind the same NAT? NAT support is in experimental status and the current implementation of the control plane (MS / RTRs) only supports one xTR behind the same NAT. Have you tried to use another DNS?
Best regards
Albert
On 22/09/16 14:21, Niek van der Ven wrote:
Hi,
Currently trying to get the xTR mode working with NAT Traversal but i have issues with non icmp traffic for both in and out-bound.
The icmp for both in and outbound is working on ipv4, also the registration appears to be fine (153.16.57.130 on a Linux machine connected via a dedicated Vnic):
niek-xtr intouch-ams-mr-ms-1 yes yes 00:10:00 0 153.16.57.128/28 10.1.1.145 (down)
158.38.1.92 (up) 158.38.1.92
Can somebody help me with a “Working” config so i can compare and find the error in my setup?
Running Ubuntu Linux 14.04.4
Open Overlay Router v1.1 compiled for Linux
Many thanx in advance for the support!!!
The testing results, config and debug info is below:
###############
netstat -nr
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 10.1.1.1 0.0.0.0 UG 0 0 0 eth0
10.1.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
153.16.57.128 0.0.0.0 255.255.255.240 U 0 0 0 eth1
route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default fw01.nalwventur 0.0.0.0 UG 0 0 0 eth0
10.1.1.0 * 255.255.255.0 U 0 0 0 eth0
153.16.57.128 * 255.255.255.240 U 0 0 0 eth1
ip rule list
0: from all lookup local
2: from 10.1.1.145 lookup 2
99: from all to 153.16.57.128/28 lookup main
100: from 153.16.57.128/28 lookup 100
32766: from all lookup main
32767: from all lookup default
ip route show table 100
default dev lispTun0 proto static metric 100
ip route show table 99
ip route show table 2
default via 10.1.1.1 dev eth0 proto static metric 100
ip route show table 0
default via 10.1.1.1 dev eth0 table 2 proto static metric 100
default dev lispTun0 table 100 proto static metric 100
default via 10.1.1.1 dev eth0
10.1.1.0/24 dev eth0 proto kernel scope link src 10.1.1.145
153.16.57.128/28 dev eth1 proto kernel scope link src 153.16.57.129
broadcast 10.1.1.0 dev eth0 table local proto kernel scope link src 10.1.1.145
local 10.1.1.145 dev eth0 table local proto kernel scope host src 10.1.1.145
broadcast 10.1.1.255 dev eth0 table local proto kernel scope link src 10.1.1.145
broadcast 127.0.0.0 dev lo table local proto kernel scope link src 127.0.0.1
local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1
local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1
broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1
broadcast 153.16.57.128 dev eth1 table local proto kernel scope link src 153.16.57.129
local 153.16.57.129 dev eth1 table local proto kernel scope host src 153.16.57.129
broadcast 153.16.57.143 dev eth1 table local proto kernel scope link src 153.16.57.129
default dev lispTun0 table 100 proto static metric 100
unreachable default dev lo table unspec proto kernel metric 4294967295 error -101
fe80::/64 dev eth1 proto kernel metric 256
fe80::/64 dev eth0 proto kernel metric 256
unreachable default dev lo table unspec proto kernel metric 4294967295 error -101
local ::1 dev lo table local proto none metric 0
local fe80:: dev lo table local proto none metric 0
local fe80:: dev lo table local proto none metric 0
local fe80::4026:a1ff:fe58:94da dev lo table local proto none metric 0
local fe80::9029:52ff:fea7:9b88 dev lo table local proto none metric 0
ff00::/8 dev eth1 table local metric 256
ff00::/8 dev eth0 table local metric 256
unreachable default dev lo table unspec proto kernel metric 4294967295 error -101
ip route show table 32766
ip route show table 32767
########################
Ping to google dns ok:
########################
ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=43 time=50.5 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=43 time=49.1 ms
^C
--- 8.8.8.8 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 49.181/49.885/50.590/0.739 ms
11:51:43.050728 IP 153.16.57.130 > google-public-dns-a.google.com<http://google-public-dns-a.google.com/>: ICMP echo request, id 23371, seq 2, length 64
11:51:43.099555 IP google-public-dns-a.google.com<http://google-public-dns-a.google.com/> > 153.16.57.130: ICMP echo reply, id 23371, seq 2, length 64
########################
Ping to nu.nl<http://nu.nl/> not ok:
########################
ping nu.nl<http://nu.nl/>
^C
11:51:45.762500 IP 153.16.57.130.51762 > resolver2-fs.opendns.com.domain: 7138+ A? nu.nl<http://nu.nl/>. (23)
########################
! Ping to ip of nu.nl<http://nu.nl/> (174.129.25.170) ok:
########################
ping 174.129.25.170
PING 174.129.25.170 (174.129.25.170) 56(84) bytes of data.
64 bytes from 174.129.25.170: icmp_seq=1 ttl=24 time=151 ms
64 bytes from 174.129.25.170: icmp_seq=2 ttl=24 time=151 ms
^C
--- 174.129.25.170 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 151.331/151.424/151.518/0.400 ms
11:52:04.737695 IP 153.16.57.130 > wwwizer.com<http://wwwizer.com/>: ICMP echo request, id 23374, seq 2, length 64
11:52:04.888827 IP wwwizer.com<http://wwwizer.com/> > 153.16.57.130: ICMP echo reply, id 23374, seq 2, length 64
##############
Lisp debug level 3:
#####################
[2016/9/22 11:51:42] DEBUG-3: OUTPUT: Received EID 153.16.57.130 -> 8.8.8.8, Proto: 1, Port: 0 -> 0
[2016/9/22 11:51:42] DEBUG-3: select_locs_from_maps: EID: 153.16.57.130 -> 8.8.8.8, protocol: 1, port: 0 -> 0 --> RLOC: 10.1.1.145 -> 158.38.1.92
[2016/9/22 11:51:42] DEBUG-3: ttable_insert: Inserted tupla: Src_addr: 153.16.57.130, Dst addr: 8.8.8.8, Proto: ICMP, Src Port: 0, Dst Port: 0 IID|VNI: 0
[2016/9/22 11:51:42] DEBUG-3: OUTPUT: Sending encapsulated packet: RLOC 10.1.1.145 -> 158.38.1.92
[2016/9/22 11:51:42] DEBUG-3: INPUT (4341): Inner IP: 8.8.8.8 -> 153.16.57.130
[2016/9/22 11:51:42] DEBUG: ECM -> flags:s, inner IP: 10.1.1.145 -> 217.8.98.42, inner UDP: 4342 -> 4342
[2016/9/22 11:51:42] DEBUG: Map-Register -> flags:PIRM record-count: 1 nonce f0ffdd6f5ffffffe, Inner IP: 10.1.1.145 -> 217.8.98.42, EID: 153.16.57.128/28, RTR: 158.38.1.92
[2016/9/22 11:51:42] DEBUG: Sent control message IP: 10.1.1.145 -> 158.38.1.92 UDP: 4341 -> 4342
[2016/9/22 11:51:42] DEBUG: Sent Encap Map-Register for mapping 153.16.57.128/28 to MS 217.8.98.42 from RLOC 10.1.1.145 through RTR 158.38.1.92
[2016/9/22 11:51:42] DEBUG-3: INPUT (4341): Inner IP: 158.38.1.92 -> 10.1.1.145
[2016/9/22 11:51:42] DEBUG: Received Map-Notify-> flags:IR, record-count: 1, nonce F0FFDD6F5FFFFFFE, IP: 158.38.1.92 -> 10.1.1.145, UDP: 4342 -> 4342
[2016/9/22 11:51:42] DEBUG: Received Data Map Notify
[2016/9/22 11:51:42] DEBUG: Mapping-record -> ttl: 10 loc-count: 2 action: no-action auth: 0 map-version: 0 eid: 153.16.57.128/28
[2016/9/22 11:51:42] DEBUG: Locator-record -> flags: L=0,p=0,R=0, p/w: 0/0 255/0, addr: 10.1.1.145
[2016/9/22 11:51:42] DEBUG: Locator-record -> flags: L=0,p=0,R=1, p/w: 1/100 255/0, addr: 158.38.1.92
[2016/9/22 11:51:42] DEBUG-2: mapping_get_locators_with_afi: List for OOR AFI 1 and afi 2 not yet created
[2016/9/22 11:51:42] DEBUG-2: mapping_add_locator: Added locator 158.38.1.92 to the mapping with EID 153.16.57.128/28.
[2016/9/22 11:51:42] DEBUG-2: mapping_add_locator: Added locator 10.1.1.145 to the mapping with EID 153.16.57.128/28.
[2016/9/22 11:51:42] DEBUG: Map-Notify message confirms correct registration of 153.16.57.128/28.Programing next Map-Register in 60 seconds
[2016/9/22 11:51:42] DEBUG-3: xTR: Completed processing of LISP control message
[2016/9/22 11:51:42] DEBUG-3: INPUT (4341): Inner IP: 93.174.93.164 -> 153.16.57.137
[2016/9/22 11:51:43] DEBUG-3: OUTPUT: Received EID 153.16.57.130 -> 8.8.8.8, Proto: 1, Port: 0 -> 0
[2016/9/22 11:51:43] DEBUG-3: OUTPUT: Sending encapsulated packet: RLOC 10.1.1.145 -> 158.38.1.92
[2016/9/22 11:51:43] DEBUG-3: INPUT (4341): Inner IP: 8.8.8.8 -> 153.16.57.130
[2016/9/22 11:51:43] DEBUG-3: INPUT (4341): Inner IP: 93.174.93.164 -> 153.16.57.136
[2016/9/22 11:51:45] DEBUG-3: OUTPUT: Received EID 153.16.57.130 -> 208.67.220.123, Proto: 17, Port: 51762 -> 53
[2016/9/22 11:51:45] DEBUG-3: select_locs_from_maps: EID: 153.16.57.130 -> 208.67.220.123, protocol: 17, port: 51762 -> 53
--> RLOC: 10.1.1.145 -> 158.38.1.92
[2016/9/22 11:51:45] DEBUG-3: ttable_insert: Inserted tupla: Src_addr: 153.16.57.130, Dst addr: 208.67.220.123, Proto: UDP, Src Port: 51762, Dst Port: 53 IID|VNI: 0
[2016/9/22 11:51:45] DEBUG-3: OUTPUT: Sending encapsulated packet: RLOC 10.1.1.145 -> 158.38.1.92
[2016/9/22 11:51:45] DEBUG-3: INPUT (4341): Inner IP: 93.174.93.164 -> 153.16.57.132
[2016/9/22 11:51:50] DEBUG-3: OUTPUT: Received EID 153.16.57.130 -> 208.67.222.123, Proto: 17, Port: 57620 -> 53
[2016/9/22 11:51:50] DEBUG-3: select_locs_from_maps: EID: 153.16.57.130 -> 208.67.222.123, protocol: 17, port: 57620 -> 53
--> RLOC: 10.1.1.145 -> 158.38.1.92
[2016/9/22 11:51:50] DEBUG-3: ttable_insert: Inserted tupla: Src_addr: 153.16.57.130, Dst addr: 208.67.222.123, Proto: UDP, Src Port: 57620, Dst Port: 53 IID|VNI: 0
[2016/9/22 11:51:50] DEBUG-3: OUTPUT: Sending encapsulated packet: RLOC 10.1.1.145 -> 158.38.1.92
[2016/9/22 11:51:52] DEBUG-3: INPUT (4341): Inner IP: 77.252.153.82 -> 153.16.57.139
[2016/9/22 11:51:55] DEBUG-3: OUTPUT: Received EID 153.16.57.130 -> 208.67.220.123, Proto: 17, Port: 51762 -> 53
[2016/9/22 11:51:55] DEBUG-3: ttable_remove_with_khiter: Remove tupla: Src_addr: 153.16.57.130, Dst addr: 208.67.220.123, Proto: UDP, Src Port: 51762, Dst Port: 53 IID|VNI: 0
[2016/9/22 11:51:55] DEBUG-3: select_locs_from_maps: EID: 153.16.57.130 -> 208.67.220.123, protocol: 17, port: 51762 -> 53
--> RLOC: 10.1.1.145 -> 158.38.1.92
[2016/9/22 11:51:55] DEBUG-3: ttable_insert: Inserted tupla: Src_addr: 153.16.57.130, Dst addr: 208.67.220.123, Proto: UDP, Src Port: 51762, Dst Port: 53 IID|VNI: 0
[2016/9/22 11:51:55] DEBUG-3: OUTPUT: Sending encapsulated packet: RLOC 10.1.1.145 -> 158.38.1.92
[2016/9/22 11:51:59] DEBUG-3: INPUT (4341): Inner IP: 93.174.93.164 -> 153.16.57.140
[2016/9/22 11:52:2] DEBUG-3: INPUT (4341): Inner IP: 93.174.93.164 -> 153.16.57.135
[2016/9/22 11:52:3] DEBUG-3: OUTPUT: Received EID 153.16.57.130 -> 174.129.25.170, Proto: 1, Port: 0 -> 0
[2016/9/22 11:52:3] DEBUG-3: select_locs_from_maps: EID: 153.16.57.130 -> 174.129.25.170, protocol: 1, port: 0 -> 0
--> RLOC: 10.1.1.145 -> 158.38.1.92
[2016/9/22 11:52:3] DEBUG-3: ttable_insert: Inserted tupla: Src_addr: 153.16.57.130, Dst addr: 174.129.25.170, Proto: ICMP, Src Port: 0, Dst Port: 0 IID|VNI: 0
[2016/9/22 11:52:3] DEBUG-3: OUTPUT: Sending encapsulated packet: RLOC 10.1.1.145 -> 158.38.1.92
[2016/9/22 11:52:3] DEBUG-3: INPUT (4341): Inner IP: 174.129.25.170 -> 153.16.57.130
[2016/9/22 11:52:4] DEBUG-3: OUTPUT: Received EID 153.16.57.130 -> 174.129.25.170, Proto: 1, Port: 0 -> 0
[2016/9/22 11:52:4] DEBUG-3: OUTPUT: Sending encapsulated packet: RLOC 10.1.1.145 -> 158.38.1.92
[2016/9/22 11:52:4] DEBUG-3: INPUT (4341): Inner IP: 174.129.25.170 -> 153.16.57.130
[2016/9/22 11:52:4] DEBUG-3: INPUT (4341): Inner IP: 104.20.2.47 -> 153.16.57.135
^C[2016/9/22 11:52:11] DEBUG: Terminal interrupt. Cleaning up...
[2016/9/22 11:52:11] DEBUG-2: Exit Cleanup
[2016/9/22 11:52:11] DEBUG: del_rule: Removed rule for source routing of src addr: 153.16.57.128/28
[2016/9/22 11:52:11] DEBUG: del_rule: Removed rule for source routing of src addr: _NULL_
[2016/9/22 11:52:11] DEBUG: xTR device destroyed
[2016/9/22 11:52:11] DEBUG: Freed xTR ...
[2016/9/22 11:52:11] DEBUG: Lisp controler destroyed
[2016/9/22 11:52:11] DEBUG: del_route: deleted route from the system: src addr: -, dst prefix:-, gw: 10.1.1.1, table: 2
[2016/9/22 11:52:11] DEBUG: del_rule: Removed rule for source routing of src addr: 10.1.1.145
[2016/9/22 11:52:11] DEBUG: Sockets closed
[2016/9/22 11:52:11] DEBUG: Destroying lmtimers ...
[2016/9/22 11:52:11] INFO: Exiting ...
###############
Lisp config:
################
niekvanderven at niek-xtr:~$ cat /etc/oor.conf
debug = 3
map-request-retries = 3
log-file = /var/log/oor.log
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
###############################################
#
# 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
# 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
}
map-resolver = {
217.8.98.42
}
###############################################
#
# xTR & MN configuration
#
# NAT Traversl configuration.
# nat_traversal_support: check if the node is behind NAT.
nat_traversal_support = on
# 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
# Only one map-server supported in NAT mode! (193.162.145.50 not replying !)
#map-server {
# address = 193.162.145.50
# key-type = 1
# key = <ommitted>
# proxy-reply = on
#}
map-server {
address = 217.8.98.42
key-type = 1
key = <ommitted>
proxy-reply = on
}
#map-server {
# address = 217.8.98.46
# key-type = 1
# key = <ommitted>
# proxy-reply = on
# }
# 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 = 217.8.98.42
priority = 0
weight = 0
}
proxy-etr {
address = 193.162.145.46
priority = 0
weight = 0
}
# 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 = 153.16.57.128/28
iid = 0
rloc-address {
address = 10.1.1.145
priority = 0
weight = 0
}
# rloc-iface{
# interface = eth0
# ip_version = 4
# priority = 1
# weight = 1
# }
}
# Current LISP beta-network (lisp4.net/lisp6.net<http://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
}
###############################################
#################
lisp startup in debug 3
#########################
oor
[2016/9/22 12:4:56] INFO: Open Overlay Router v1.1 compiled for Linux
[2016/9/22 12:4:56] WARNING: Rights: Effective [12288] Permitted [12288]
[2016/9/22 12:4:56] CRIT: pid_file_create: Error creating PID file: Permission denied
[2016/9/22 12:4:56] INFO: Building address to interface hash table
[2016/9/22 12:4:56] INFO: Control created!
[2016/9/22 12:4:56] INFO: Log level: High Debug
[2016/9/22 12:4:56] DEBUG: Creating map cache and local mapping database
[2016/9/22 12:4:56] DEBUG-3: Creating mdb...
[2016/9/22 12:4:56] DEBUG-3: Creating mdb...
[2016/9/22 12:4:56] DEBUG-2: lisp_addr_get_ip_pref_addr: Not applicable to ip addressess
[2016/9/22 12:4:56] DEBUG: Finished Constructing xTR
[2016/9/22 12:4:56] INFO: Device working in mode xTR registering with control
[2016/9/22 12:4:56] DEBUG-2: nat_set_xTR_ID: xTR_ID initialiazed with value: 94da00000000922952a79b884226a158
[2016/9/22 12:4:56] DEBUG: NAT support enabled. Set defaul RLOC to IPv4 family
[2016/9/22 12:4:56] DEBUG: RLOC Probing Interval: 30
[2016/9/22 12:4:56] DEBUG-3: The server 217.8.98.42 has been added to the list
[2016/9/22 12:4:56] DEBUG: Added 217.8.98.42 to map-resolver list
[2016/9/22 12:4:56] DEBUG: Added 217.8.98.42 to map-server list
[2016/9/22 12:4:56] DEBUG-2: mapping_get_locators_with_afi: List for OOR AFI 1 and afi 2 not yet created
[2016/9/22 12:4:56] DEBUG-2: mapping_add_locator: Added locator 217.8.98.42 to the mapping with EID 0.0.0.0/32.
[2016/9/22 12:4:56] DEBUG: Added 217.8.98.42 to proxy-etr list
[2016/9/22 12:4:56] DEBUG-2: mapping_add_locator: Added locator 193.162.145.46 to the mapping with EID 0.0.0.0/32.
[2016/9/22 12:4:56] DEBUG: Added 193.162.145.46 to proxy-etr list
[2016/9/22 12:4:56] DEBUG: Balancing locator vector for 0.0.0.0/32:
[2016/9/22 12:4:56] DEBUG: IPv4 locators vector (2 locators): 217.8.98.42 193.162.145.46
[2016/9/22 12:4:56] DEBUG: IPv6 locators vector (0 locators):
[2016/9/22 12:4:56] DEBUG: IPv4 & IPv6 locators vector (0 locators):
[2016/9/22 12:4:56] DEBUG-3: The server 217.8.98.33 has been added to the list
[2016/9/22 12:4:56] DEBUG: Added 217.8.98.33 to proxy-itr list
[2016/9/22 12:4:56] DEBUG-2: Adding interface eth0 with index 2 to iface list
[2016/9/22 12:4:56] DEBUG-2: Interface eth0 with index 2 added to interfaces lists
[2016/9/22 12:4:56] DEBUG-3: open_ip_raw_socket: open socket 5 with afi: 2
[2016/9/22 12:4:56] DEBUG: bind_socket: Binded socket 5 to source address 10.1.1.145 and port 0 with afi 2
[2016/9/22 12:4:56] DEBUG: add_rule: Add rule -> Send packets with source address 10.1.1.145 and destination address _NULL_ to the table 2 with priority 2.
[2016/9/22 12:4:56] DEBUG-2: parse_rloc_address: Locator stucture created:
10.1.1.145, Up, 0/0, 255/0
[2016/9/22 12:4:56] DEBUG-2: mapping_get_locators_with_afi: List for OOR AFI 1 and afi 2 not yet created
[2016/9/22 12:4:56] DEBUG-2: mapping_get_locators_with_afi: List for OOR AFI 1 and afi 2 not yet created
[2016/9/22 12:4:56] DEBUG-2: mapping_add_locator: Added locator 10.1.1.145 to the mapping with EID 153.16.57.128/28.
[2016/9/22 12:4:56] DEBUG: Balancing locator vector for 153.16.57.128/28:
[2016/9/22 12:4:56] DEBUG: IPv4 locators vector (1 locators): 10.1.1.145
[2016/9/22 12:4:56] DEBUG: IPv6 locators vector (0 locators):
[2016/9/22 12:4:56] DEBUG: IPv4 & IPv6 locators vector (0 locators):
[2016/9/22 12:4:56] DEBUG-3: Couldn't find mapping for EID 153.16.57.128/28 in local mappings database
[2016/9/22 12:4:56] DEBUG-3: _add_ippref_entry: Added map cache data for 153.16.57.128/28
[2016/9/22 12:4:56] DEBUG-3: mdb_add_entry: inserted 153.16.57.128/28
[2016/9/22 12:4:56] DEBUG: Added EID prefix 153.16.57.128/28 in the database.
[2016/9/22 12:4:56] DEBUG-2: Configuring data plane
[2016/9/22 12:4:56] DEBUG-3: TUN/TAP ifindex is: 6
[2016/9/22 12:4:56] DEBUG: TUN/TAP mtu set to 1440
[2016/9/22 12:4:56] DEBUG-2: Tunnel fd at creation is 6
[2016/9/22 12:4:56] DEBUG: TUN interface UP.
[2016/9/22 12:4:56] DEBUG: add_route: added route to the system: src addr: -, dst prefix:-, gw: -, table: 100
[2016/9/22 12:4:56] DEBUG: add_route: added route to the system: src addr: -, dst prefix:-, gw: -, table: 100
[2016/9/22 12:4:56] DEBUG-3: open_udp_raw_socket: Created socket 7 associated to IPv4 addresses
[2016/9/22 12:4:56] DEBUG-3: open_udp_datagram_socket: Created socket 8 associated to IPv4 addresses
[2016/9/22 12:4:56] DEBUG: bind_socket: Binded socket 8 to source address _NULL_ and port 4341 with afi 2
[2016/9/22 12:4:56] DEBUG-2: Default IPv4 data iface eth0: 10.1.1.145
[2016/9/22 12:4:56] DEBUG: Data plane initialized
[2016/9/22 12:4:56] DEBUG-3: open_udp_datagram_socket: Created socket 9 associated to IPv4 addresses
[2016/9/22 12:4:56] DEBUG: bind_socket: Binded socket 9 to source address _NULL_ and port 4342 with afi 2
[2016/9/22 12:4:56] DEBUG-2: Default IPv4 control iface eth0: 10.1.1.145
[2016/9/22 12:4:56] DEBUG: Control initialized
[2016/9/22 12:4:56] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/22 12:4:56] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/22 12:4:56] DEBUG: tun_update_route: Process new gateway associated to the interface eth0: 10.1.1.1
[2016/9/22 12:4:56] DEBUG: add_route: added route to the system: src addr: -, dst prefix:-, gw: 10.1.1.1, table: 2
[2016/9/22 12:4:56] DEBUG-2: xtr_if_event: Reconfiguring Info Request process for locator 10.1.1.145 of the mapping 153.16.57.128/28.
[2016/9/22 12:4:56] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/22 12:4:56] DEBUG-2: xtr_if_event: Reconfiguring Info Request process for locator 10.1.1.145 of the mapping 153.16.57.128/28.
[2016/9/22 12:4:56] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/22 12:4:56] DEBUG-3: process_nl_new_unicast_route: the netlink message is not for any interface associated with RLOCs (eth1)
[2016/9/22 12:4:56] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/22 12:4:56] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/22 12:4:56] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/22 12:4:56] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/22 12:4:56] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/22 12:4:56] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/22 12:4:56] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/22 12:4:56] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/22 12:4:56] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/22 12:4:56] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/22 12:4:56] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/22 12:4:56] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/22 12:4:56] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/22 12:4:56] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/22 12:4:56] DEBUG-3: process_nl_new_unicast_route: the netlink message is not for any interface associated with RLOCs (eth1)
[2016/9/22 12:4:56] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/22 12:4:56] DEBUG: process_nl_new_unicast_route: Default RLOC afi defined (-a #): Skipped route with destination address IPv6 in iface eth0
[2016/9/22 12:4:56] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/22 12:4:56] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/22 12:4:56] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/22 12:4:56] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/22 12:4:56] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/22 12:4:56] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/22 12:4:56] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/22 12:4:56] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/22 12:4:56] DEBUG-3: =>process_netlink_msg: Received new route message
[2016/9/22 12:4:56] DEBUG:
Starting xTR ...
[2016/9/22 12:4:56] DEBUG: Balancing locator vector for 0.0.0.0/32:
[2016/9/22 12:4:56] DEBUG: IPv4 locators vector (2 locators): 217.8.98.42 193.162.145.46
[2016/9/22 12:4:56] DEBUG: IPv6 locators vector (0 locators):
[2016/9/22 12:4:56] DEBUG: IPv4 & IPv6 locators vector (0 locators):
[2016/9/22 12:4:56] INFO: NAT aware on -> No Map Resolver will be used.
[2016/9/22 12:4:56] INFO: NAT aware on -> disabling RLOC Probing
[2016/9/22 12:4:56] DEBUG-3: locators_classify_in_4_6: No locators to classify for mapping with eid 0.0.0.0/32
[2016/9/22 12:4:56] DEBUG: Balancing locator vector for 0.0.0.0/32:
[2016/9/22 12:4:56] DEBUG: IPv4 locators vector (0 locators):
[2016/9/22 12:4:56] DEBUG: IPv6 locators vector (0 locators):
[2016/9/22 12:4:56] DEBUG: IPv4 & IPv6 locators vector (0 locators):
[2016/9/22 12:4:56] DEBUG: ****** Summary of the xTR configuration ******
[2016/9/22 12:4:56] DEBUG: ****************** LISP Local Mappings ****************
[2016/9/22 12:4:56] DEBUG: EID: 153.16.57.128/28, ttl: 10, loc-count: 1, action: no-action, auth: 1
RLOC: 10.1.1.145, Up, 0/0, 255/0
[2016/9/22 12:4:56] DEBUG: *******************************************************
[2016/9/22 12:4:56] DEBUG: **************** LISP Mapping Cache ******************
[2016/9/22 12:4:56] DEBUG: *******************************************************
[2016/9/22 12:4:56] DEBUG: ******************* Map-Servers list ********************************
[2016/9/22 12:4:56] DEBUG: | Locator (RLOC) | Key Type |
[2016/9/22 12:4:56] DEBUG: | 217.8.98.42 | HMAC-SHA-1-96 |
[2016/9/22 12:4:56] DEBUG: ************* Map Resolvers ***************
[2016/9/22 12:4:56] DEBUG: ************************* Proxy ETRs List ****************************
[2016/9/22 12:4:56] DEBUG: | Locator (RLOC) | Status | Priority/Weight |
[2016/9/22 12:4:56] DEBUG: ************* Proxy-ITRs ***************
[2016/9/22 12:4:56] DEBUG: [1] => 217.8.98.33
[2016/9/22 12:4:56] DEBUG: add_rule: Add rule -> Send packets with source address 153.16.57.128/28 and destination address _NULL_ to the table 100 with priority 100.
[2016/9/22 12:4:56] DEBUG: add_rule: Add rule -> Send packets with source address _NULL_ and destination address 153.16.57.128/28 to the table 254 with priority 99.
[2016/9/22 12:4:56] DEBUG: Balancing locator vector for 153.16.57.128/28:
[2016/9/22 12:4:56] DEBUG: IPv4 locators vector (1 locators): 10.1.1.145
[2016/9/22 12:4:56] DEBUG: IPv6 locators vector (0 locators):
[2016/9/22 12:4:56] DEBUG: IPv4 & IPv6 locators vector (0 locators):
[2016/9/22 12:4:56] DEBUG: Sent Info Request for mapping 153.16.57.128/28 to 217.8.98.42 from locator 10.1.1.145
[2016/9/22 12:4:56] DEBUG: Info Request -> nonce c47694a07ff3feec, EID: 153.16.57.128/28, MS: 217.8.98.42
[2016/9/22 12:4:56] DEBUG: Sent control message IP: 10.1.1.145 -> 217.8.98.42 UDP: 4342 -> 4342
[2016/9/22 12:4:56] INFO:
Open Overlay Router (v1.1): started...
[2016/9/22 12:4:56] DEBUG-3: OOR_API: zmq_ctx_new errno: Success
[2016/9/22 12:4:56] DEBUG-3: OOR_API: zmq_socket: Success
[2016/9/22 12:4:56] DEBUG-2: OOR_API: API server initiated using ZMQ
[2016/9/22 12:4:56] DEBUG: Received Info Reply -> nonce c47694a07ff3feec, IP: 217.8.98.42 -> 10.1.1.145, UDP: 4342 -> 4342
[2016/9/22 12:4:56] DEBUG-2: mapping_add_locator: Added locator 158.38.1.92 to the mapping with EID 153.16.57.128/28.
[2016/9/22 12:4:56] DEBUG: Balancing locator vector for 153.16.57.128/28:
[2016/9/22 12:4:56] DEBUG: IPv4 locators vector (1 locators): 10.1.1.145
[2016/9/22 12:4:56] DEBUG: IPv6 locators vector (0 locators):
[2016/9/22 12:4:56] DEBUG: IPv4 & IPv6 locators vector (0 locators):
[2016/9/22 12:4:56] DEBUG-2: mapping_get_locators_with_afi: List for OOR AFI 1 and afi 2 not yet created
[2016/9/22 12:4:56] DEBUG-2: mapping_add_locator: Added locator 158.38.1.92 to the mapping with EID 0.0.0.0/32.
[2016/9/22 12:4:56] DEBUG: Balancing locator vector for 0.0.0.0/32:
[2016/9/22 12:4:56] DEBUG: IPv4 locators vector (1 locators): 158.38.1.92
[2016/9/22 12:4:56] DEBUG: IPv6 locators vector (0 locators):
[2016/9/22 12:4:56] DEBUG: IPv4 & IPv6 locators vector (0 locators):
[2016/9/22 12:4:56] DEBUG: ECM -> flags:s, inner IP: 10.1.1.145 -> 217.8.98.42, inner UDP: 4342 -> 4342
[2016/9/22 12:4:56] DEBUG: Map-Register -> flags:PIRM record-count: 1 nonce 552eaa07fefdaed, Inner IP: 10.1.1.145 -> 217.8.98.42, EID: 153.16.57.128/28, RTR: 158.38.1.92
[2016/9/22 12:4:56] DEBUG: Sent control message IP: 10.1.1.145 -> 158.38.1.92 UDP: 4341 -> 4342
[2016/9/22 12:4:56] DEBUG: Sent Encap Map-Register for mapping 153.16.57.128/28 to MS 217.8.98.42 from RLOC 10.1.1.145 through RTR 158.38.1.92
[2016/9/22 12:4:56] DEBUG: Info Request of 153.16.57.128/28 to 217.8.98.42 from locator 10.1.1.145 programmed in 30 minutes.
[2016/9/22 12:4:56] DEBUG-3: xTR: Completed processing of LISP control message
[2016/9/22 12:4:56] DEBUG-3: INPUT (4341): Inner IP: 158.38.1.92 -> 10.1.1.145
[2016/9/22 12:4:56] DEBUG: Received Map-Notify-> flags:IR, record-count: 1, nonce 552EAA07FEFDAED, IP: 158.38.1.92 -> 10.1.1.145, UDP: 4342 -> 4342
[2016/9/22 12:4:56] DEBUG: Received Data Map Notify
[2016/9/22 12:4:56] DEBUG: Mapping-record -> ttl: 10 loc-count: 2 action: no-action auth: 0 map-version: 0 eid: 153.16.57.128/28
[2016/9/22 12:4:56] DEBUG: Locator-record -> flags: L=0,p=0,R=0, p/w: 0/0 255/0, addr: 10.1.1.145
[2016/9/22 12:4:56] DEBUG: Locator-record -> flags: L=0,p=0,R=1, p/w: 1/100 255/0, addr: 158.38.1.92
[2016/9/22 12:4:56] DEBUG-2: mapping_get_locators_with_afi: List for OOR AFI 1 and afi 2 not yet created
[2016/9/22 12:4:56] DEBUG-2: mapping_add_locator: Added locator 158.38.1.92 to the mapping with EID 153.16.57.128/28.
[2016/9/22 12:4:56] DEBUG-2: mapping_add_locator: Added locator 10.1.1.145 to the mapping with EID 153.16.57.128/28.
[2016/9/22 12:4:56] DEBUG: Map-Notify message confirms correct registration of 153.16.57.128/28.Programing next Map-Register in 60 seconds
[2016/9/22 12:4:56] DEBUG-3: xTR: Completed processing of LISP control message
^C[2016/9/22 12:4:58] DEBUG: Terminal interrupt. Cleaning up...
[2016/9/22 12:4:58] DEBUG-2: Exit Cleanup
[2016/9/22 12:4:58] DEBUG: del_rule: Removed rule for source routing of src addr: 153.16.57.128/28
[2016/9/22 12:4:58] DEBUG: del_rule: Removed rule for source routing of src addr: _NULL_
[2016/9/22 12:4:58] DEBUG: xTR device destroyed
[2016/9/22 12:4:58] DEBUG: Freed xTR ...
[2016/9/22 12:4:58] DEBUG: Lisp controler destroyed
[2016/9/22 12:4:58] DEBUG: del_route: deleted route from the system: src addr: -, dst prefix:-, gw: 10.1.1.1, table: 2
[2016/9/22 12:4:58] DEBUG: del_rule: Removed rule for source routing of src addr: 10.1.1.145
[2016/9/22 12:4:58] DEBUG: Sockets closed
[2016/9/22 12:4:58] DEBUG: Destroying lmtimers ...
[2016/9/22 12:4:58] INFO: Exiting ...
_______________________________________________
Users mailing list
Users at openoverlayrouter.org<mailto:Users at openoverlayrouter.org>
http://mail.openoverlayrouter.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users at openoverlayrouter.org<mailto:Users at openoverlayrouter.org>
http://mail.openoverlayrouter.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openoverlayrouter.org/pipermail/users/attachments/20160923/0ed2b5a2/attachment-0001.html>
More information about the Users
mailing list