Bystrykha commented 1 year ago

hello, I'm having a problem registering a dynamic prefix. This is the xTR1 configuration: #

-----------------------------------------------------------------------------

lisp enable { itr = yes etr = yes rtr = no map-server = no map-resolver = no ddt-node = no } lisp debug { core = yes itr = yes etr = yes rtr = no map-server = no map-resolver = no ddt-node = no } lisp user-account { username = root password = =b9e5c39708999f844a3c864e863c12618bf8a3f5 super-user = yes } lisp xtr-parameters { rloc-probing = no data-plane-security = no nat-traversal = no decentralized-nat = no nonce-echoing = no checkpoint-map-cache = no ipc-data-plane = no decentralized-push-xtr = no register-reachable-rtrs = no frame-logging = no flow-logging = no data-plane-logging = yes } lisp database-mapping { prefix { mr-name = my-mr ms-name = my-ms eid-prefix = 192.168.113.0/24 } prefix { mr-name = my-mr ms-name = my-ms eid-prefix = 192.168.113.5/32 dynamic-eid = yes } rloc { address = 192.168.56.111 } } lisp map-resolver { mr-name = my-mr address = 192.168.56.109 } lisp map-server { ms-name = my-ms address = 192.168.56.109 authentication-key = any-key want-map-notify = yes } lisp interface { interface-name = rloc device = enp0s8 } lisp interface { interface-name = eid device = enp0s9 dynamic-eid = 192.168.113.5/32 }

-----------------------------------------------------------------------------

This is the xTR2 configuration:

-----------------------------------------------------------------------------

lisp enable { itr = yes etr = yes rtr = no map-server = no map-resolver = no ddt-node = no } lisp debug { core = yes itr = yes etr = yes rtr = no map-server = no map-resolver = no ddt-node = no } lisp user-account { username = root password = =b9e5c39708999f844a3c864e863c12618bf8a3f5 super-user = yes } lisp xtr-parameters { rloc-probing = no data-plane-security = no nat-traversal = no decentralized-nat = no nonce-echoing = no checkpoint-map-cache = no ipc-data-plane = no decentralized-push-xtr = no register-reachable-rtrs = no frame-logging = no flow-logging = no data-plane-logging = yes } lisp database-mapping { prefix { mr-name = my-mr ms-name = my-ms eid-prefix = 192.168.129.0/24 } prefix { mr-name = my-mr ms-name = my-ms eid-prefix = 192.168.113.5/32 dynamic-eid = yes } rloc { address = 192.168.56.102 } } lisp map-resolver { mr-name = my-mr address = 192.168.56.109 } lisp map-server { ms-name = my-ms address = 192.168.56.109 authentication-key = any-key want-map-notify = yes } lisp interface { interface-name = eid device = enp0s9 dynamic-eid = 192.168.113.5/32 }

-----------------------------------------------------------------------------

MSMR config: #

-----------------------------------------------------------------------------

lisp enable { itr = no etr = no rtr = no map-server = yes map-resolver = yes ddt-node = no } lisp debug { etr = no core = yes map-resolver = yes ddt-node = no rtr = no map-server = yes itr = no } lisp user-account { username = root password = =b9e5c39708999f844a3c864e863c12618bf8a3f5 super-user = yes } lisp site { site-name = site-1 authentication-key = any-key allowed-prefix { eid-prefix = 192.168.129.0/24 accept-more-specifics = yes

instance-id = 2

} lisp site { site-name = site-2 authentication-key = any-key allowed-prefix { eid-prefix = 192.168.3.0/24 accept-more-specifics = yes } } lisp site { site-name = site-3 authentication-key = any-key allowed-prefix { eid-prefix = 192.168.113.0/24 accept-more-specifics = yes

instance-id = 1

} lisp interface { interface-name = rloc device = enp0s8 }

-----------------------------------------------------------------------------

I don't see dynamic EID in Map_Register message, and when I try to ping this dynamic EID I see "Destination Net Unreachable" :( Tell me pleace, why xTR don't register it?

farinacci commented 1 year ago

Check to see if you see the dynamic-EID discovered on both the ITR and ETR sides. You should see it from the ITR and ETR displays from the web interface.

Your configuration looks fine to me.

Dino

On Mar 31, 2023, at 7:00 PM, Bystrykh Alexey @.***> wrote:

enp0s9

Bystrykha commented 1 year ago

The problem is in next: denamic EID is registered on both machinesm and when EID send ping on dynamic EID, dynamic EID's ITR drop it:

Logs:

Map-Register_1: 04/03/23 04:08:27.689: etr: Map-Register -> flags: psITrmnfe, record-count: 1, nonce: 0xaabbccdddfdfdf01, key/alg-id: 0/2, auth-len: 32, xtr-id: 0x79d5a7b0a0258f17, site-id: 0 04/03/23 04:08:27.689: etr: Send Map-Register to map-server [0]172.17.0.2, ms-name 'my-ms' 04/03/23 04:08:27.690: etr: Send 100 bytes to 172.17.0.2 4342, packet: 32000801 01dfdfdf ddccbbaa 00020020 c1744cce 63afacff 522312fe 38eb35fc e2e7254e fe8ee8b2 05dc87b9 b78282b0 00000003 01181000 00000001 c0a80100 0000ff00 00050001 ac110003 00000000 00000000 79d5a7b0 a0258f17 00000000 00000000 04/03/23 04:09:27.695: etr: Build Map-Register for 1 database-mapping entries 04/03/23 04:09:27.695: etr: EID-prefix [0]192.168.1.0/24 for ms-name 'my-ms' 04/03/23 04:09:27.695: etr: EID-record -> record-ttl: 3 mins, rloc-count: 1, action: no-action, auth, map-version: 0, afi: 1, [iid]eid/ml: [0]192.168.1.0/24
04/03/23 04:09:27.696: etr: RLOC-record -> flags: LpR, 0/0/255/0, afi: 1, rloc: 172.17.0.3

Map-Register_2: 04/03/23 04:08:35.777: etr: Map-Register -> flags: psITrmnfe, record-count: 1, nonce: 0xaabbccdddfdfdf01, key/alg-id: 0/2, auth-len: 32, xtr-id: 0x9a216233d3994fb0, site-id: 0 04/03/23 04:08:35.777: etr: Send Map-Register to map-server [0]172.17.0.2, ms-name 'my-ms' 04/03/23 04:08:35.777: etr: Send 100 bytes to 172.17.0.2 4342, packet: 32000801 01dfdfdf ddccbbaa 00020020 8c09bf9a 968b7a3e 19ed3c58 6a3cddbe 9edc3873 cc825c79 7b861e30 c73ae534 00000003 01181000 00000001 c0a80200 0000ff00 00050001 ac110004 00000000 00000000 9a216233 d3994fb0 00000000 00000000 04/03/23 04:09:35.782: etr: Build Map-Register for 1 database-mapping entries 04/03/23 04:09:35.782: etr: EID-prefix [0]192.168.2.0/24 for ms-name 'my-ms' 04/03/23 04:09:35.782: etr: EID-record -> record-ttl: 3 mins, rloc-count: 1, action: no-action, auth, map-version: 0, afi: 1, [iid]eid/ml: [0]192.168.2.0/24
04/03/23 04:09:35.783: etr: RLOC-record -> flags: LpR, 0/0/255/0, afi: 1, rloc: 172.17.0.4

ping xTR_1 -> xTR_2: 04/03/23 04:02:39.338: itr: Receive eth1, MACs: 0242-c0a8-0102 -> 0242-9080-f5f9, [0]192.168.1.3 -> [0]192.168.2.5 , tos/ttl: 0/63, length: 84, packet: 45000054 d41c4000 3f01e333 c0a80103 c0a80205 08002063 01d90020 b188241b 00000000 00000000 00000000 00000000 00000000 00000000 00000000 ... 04/03/23 04:02:39.338: itr: Lookup for EID [0]192.168.2.5 found map-cache entry [0]192.168.2.5/32
04/03/23 04:02:39.338: itr: Packet hash 0x4, index 0, best-rloc-list: [['172.17.0.4', 'up-state']]
04/03/23 04:02:39.339: itr: Send LISP packet, outer RLOCs: 172.17.0.3 -> 172.17.0.4 , outer tos/ttl: 0/62, outer UDP: 62215 -> 4341, inner EIDs: [0]192.168.1.3 -> [0]192.168.2.5 , inner tos/ttl: 0/62, length: 120, encap LISP-header -> flags: Nlevipkk, nonce: 62658e, iid/lsb: 00000000, packet: 45000078 dfdf4000 3e11046c ac110003 ac110004 f30710f5 00640000 8062658e 00000000 45000054 d41c4000 3e01e433 c0a80103 c0a80205 ...

receive ping on xTR_2: 04/03/23 04:02:46.426: etr: Receive LISP packet, outer RLOCs: 172.17.0.3 -> 172.17.0.4 , outer tos/ttl: 0/62, outer UDP: 62215 -> 4341, inner EIDs: [0]192.168.1.3 -> [0]192.168.2.5 , inner tos/ttl: 0/62, length: 120, decap LISP-header -> flags: Nlevipkk, nonce: ba9b32, iid/lsb: 00000000, packet: 45000078 dfdf4000 3e11046c ac110003 ac110004 f30710f5 00640000 80ba9b32 00000000 45000054 d7f24000 3e01e05d c0a80103 c0a80205 ... 04/03/23 04:02:46.427: etr: Forward packet for EIDs [0]192.168.1.3 -> [0]192.168.2.5 : 45000054 d7f24000 3d01e15d c0a80103 c0a80205 08001a84 01d90027 4c608f1b 00000000 00000000 00000000 00000000 00000000 00000000 00000000 ...

answer: 04/03/23 04:02:30.472: itr: Receive eth1, MACs: 0242-c0a8-0205 -> 0242-c0a8-0202, [0]192.168.2.5 -> [0]192.168.1.3 , tos/ttl: 0/64, length: 84, packet: 45000054 d7500000 40011f00 c0a80205 c0a80103 000058ce 01d90017 0a279b1a 00000000 00000000 00000000 00000000 00000000 00000000 00000000 ... 04/03/23 04:02:30.473: itr: Disallow dynamic-EID [0]192.168.2.5 on interface eth1

Pleace, tell me how can I solve this problem?

farinacci commented 1 year ago

answer: 04/03/23 04:02:30.472: itr: Receive eth1, MACs: 0242-c0a8-0205 -> 0242-c0a8-0202, [0]192.168.2.5 -> [0]192.168.1.3 , tos/ttl: 0/64, length: 84, packet: 45000054 d7500000 40011f00 c0a80205 c0a80103 000058ce 01d90017 0a279b1a 00000000 00000000 00000000 00000000 00000000 00000000 00000000 ... 04/03/23 04:02:30.473: itr: Disallow dynamic-EID [0]192.168.2.5 on interface eth1

Do yo have a "lisp interface" command to discover the EID 192.168.2.5 on eth1?

If you look at lisp-itr.log on xtr2, you will see what interface the EID was discovered on. It must have been discovered on some interface or it wouldn't have been registered.

Dino

Bystrykha commented 1 year ago

this is interface dir dynamic prefix: lisp interface { interface-name = eid_1 device = eth1 dynamic-eid = 192.168.2.5/32 }

May the interface for dynamic prefix discovery be the same as for static prefix discovery?

Also, in itr logs: 04/03/23 05:03:01.159: itr: Capturing packets for source-EIDs ['192.168.2.5/32', '192.168.2.0/24']

xTR_1: 04/03/23 05:03:12.635: itr: Capturing packets for source-EIDs ['192.168.2.5/32', '192.168.1.0/24']

farinacci commented 1 year ago

Okay, had to verify that. Can you find a "Discover" message in the lisp-itr.log file on xtr2 for 192.168.2.5. Look for it in the lisp-etr.log too. The one in the ETR would cause the registration. And make sure the 192.168.2.5 is being registered from the discovery of the dynamic-EID and not from the static "lisp database-mapping" command.

Dino

On Apr 2, 2023, at 10:08 PM, Bystrykh Alexey @.***> wrote:

this is interface dir dynamic prefix: lisp interface { interface-name = eid_1 device = eth1 dynamic-eid = 192.168.2.5/32 } May the interface for dynamic prefix discovery be the same as for static prefix discovery? Also, in itr logs: 04/03/23 05:03:01.159: itr: Capturing packets for source-EIDs ['192.168.2.5/32', '192.168.2.0/24'] xTR_1: 04/03/23 05:03:12.635: itr: Capturing packets for source-EIDs ['192.168.2.5/32', '192.168.1.0/24'] — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

Bystrykha commented 1 year ago

with such config I don't see discover message in ETR and ITR logs... what could be the error if not in the config file?

farinacci commented 1 year ago

I am not sure. I haven't tested this code in a long time, but I'll give it a try at the end of the week and get back to you.

Was the first time the .5 EID talk was on the ping reply?

Try pinging from it to the near side where xTR1 is an see if you get better results.

Dino

On Apr 3, 2023, at 3:18 AM, Bystrykh Alexey @.***> wrote:

with such config I don't see discover message in ETR and ITR logs... what could be the error if not in the config file? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

Bystrykha commented 1 year ago

I found that when pinging from a dynamic EID, the condition is not met (lisp.py)

therefore, the conditions are not met

farinacci commented 1 year ago

Yes, that was the code that inspired my questioning. the first return False would mean a dynamic-eid is not configured on the interface and the second means the source address of the packet isn't more specific.

Since you said it was configured (I didn't see the latest lisp.config on xTR2 so can't verify for sure), I assumed I would have to go off and try it.

Send me your lisp.config for xTR so we can see why 192.168.2.5 is not accepted. Also, check to see if you have instance-ID 0 configured and not using a different instance-ID, that could cause the problem as well.

Dino

On Apr 4, 2023, at 3:14 AM, Bystrykh Alexey @.***> wrote:

I found that when pinging from a dynamic EID, the condition is not met (lisp.py) therefore, the conditions are not met

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

Bystrykha commented 1 year ago

Unfortunately, I have a new problem that causes the static script to not work for me, more specifically: in Map-Repleay I do not observe the desired xTR i changed the config files like this: MSMR:

-----------------------------------------------------------------------------

lisp enable { itr = no etr = no rtr = no map-server = yes map-resolver = yes ddt-node = no } lisp debug { etr = no core = yes map-resolver = yes ddt-node = no rtr = no map-server = yes itr = no } lisp user-account { username = root password = =b9e5c39708999f844a3c864e863c12618bf8a3f5 super-user = yes } lisp site { site-name = site-1 authentication-key = any-key allowed-prefix { eid-prefix = 192.168.129.0/24 instance-id = 1 accept-more-specifics = yes } } lisp site { site-name = site-3 authentication-key = any-key allowed-prefix { eid-prefix = 192.168.113.0/24 accept-more-specifics = yes instance-id = 3 } } lisp interface { interface-name = rloc device = enp0s8 }

-----------------------------------------------------------------------------

xTR_1:

-----------------------------------------------------------------------------

lisp enable { itr = yes etr = yes rtr = no map-server = no map-resolver = no ddt-node = no } lisp debug { core = yes itr = yes etr = yes rtr = no map-server = no map-resolver = no ddt-node = no } lisp user-account { username = root password = =b9e5c39708999f844a3c864e863c12618bf8a3f5 super-user = yes } lisp xtr-parameters { rloc-probing = no data-plane-security = no nat-traversal = no decentralized-nat = no nonce-echoing = no checkpoint-map-cache = no ipc-data-plane = no decentralized-push-xtr = no register-reachable-rtrs = no frame-logging = no flow-logging = no data-plane-logging = yes } lisp database-mapping { prefix { mr-name = my-mr ms-name = my-ms eid-prefix = 192.168.129.0/24 instance-id = 1 } rloc { address = 192.168.56.102 } } lisp map-resolver { mr-name = my-mr address = 192.168.56.109 } lisp map-server { ms-name = my-ms address = 192.168.56.109 authentication-key = any-key want-map-notify = yes } lisp interface { interface-name = eid_stat device = enp0s9 instance-id = 1 } lisp interface { interface-name = rloc device = enp0s8 }

-----------------------------------------------------------------------------

xTR_2:

-----------------------------------------------------------------------------

lisp enable { itr = yes etr = yes rtr = no map-server = no map-resolver = no ddt-node = no } lisp debug { core = yes itr = yes etr = yes rtr = no map-server = no map-resolver = no ddt-node = no } lisp user-account { username = root password = =b9e5c39708999f844a3c864e863c12618bf8a3f5 super-user = yes } lisp xtr-parameters { rloc-probing = no data-plane-security = no nat-traversal = no decentralized-nat = no nonce-echoing = no checkpoint-map-cache = no ipc-data-plane = no decentralized-push-xtr = no register-reachable-rtrs = no frame-logging = no flow-logging = no data-plane-logging = yes } lisp database-mapping { prefix { mr-name = my-mr ms-name = my-ms eid-prefix = 192.168.113.0/24 instance-id = 3 } rloc { address = 192.168.56.111 } } lisp map-resolver { mr-name = my-mr address = 192.168.56.109 } lisp map-server { ms-name = my-ms address = 192.168.56.109 authentication-key = any-key want-map-notify = yes } lisp interface { interface-name = rloc device = enp0s8 } lisp interface { interface-name = eid_1 device = enp0s9 instance-id = 3 }

-----------------------------------------------------------------------------

This is dump from MSMR: Map-Request: Map-Reply:

This is 192.168.56.102 ITR's logs: 04/05/23 15:19:26.555: itr: <lisp.lisp_packet object at 0x7ff13124fe10> 04/05/23 15:19:26.555: itr: Receive enp0s9, MACs: 0800-2798-6e54 -> 0800-27a8-e3fe, [1]192.168.129.5 -> [1]192.168.113.8, tos/ttl: 0/64, length: 84, packet: 45000054 ef36400 0 4001d813 c0a88105 c0a87108 08007aa0 00170001 0e2f2d64 00000000 7be10700 00000000 10111213 1415 1617 18191a1b 1c1d1e1f ... 04/05/23 15:19:26.555: itr: Lookup for EID [1]192.168.113.8 not found in map-cache 04/05/23 15:19:26.555: itr: No Rate-Limit Mode for another 37 secs 04/05/23 15:19:26.555: itr: Map-Request -> flags: adrspimxnld, itr-rloc-count: 0 (+1), rec ord-count: 1, nonce: 0x9f6b3f4c1140337b, source-eid: afi 1, [1]192.168.129.5, targe t-eid: afi 1, [1]192.168.113.8/32, ITR-RLOCs: 04/05/23 15:19:26.556: itr: itr-rloc: afi 1 192.168.56.102 04/05/23 15:19:26.556: itr: ECM -> flags: sdem, inner IP: [1]192.168.129.5 -> [1]192.168.113.8, inner UDP: 42493 -> 4342 04/05/23 15:19:26.556: itr: Send Encapsulated-Control-Message to 192.168.56.109 04/05/23 15:19:26.556: itr: Send 88 bytes to ::ffff:192.168.56.109 4342, packet: 800 00000 45000054 00000000 8011c73a c0a88105 c0a87108 a5fd10f6 00400000 10000001 7b334011 4c3f6b9f 40030000 0200000a 00000001 0001c0a8 81050001 c0a83866 00204003 00000200 000a0000 00010001 c0a87108

04/05/23 15:19:26.559: itr: 4Receive 40 bytes from 192.168.56.109 4342, packet: 2000 0001 7b334011 4c3f6b9f 0000000f 00202000 00004003 00000200 000a0000 00010001 c0a87108
04/05/23 15:19:26.559: itr: Map-Reply -> flags: res, hop-count: 0, record-count: 1, nonce: 0x9f6b3f4c1140337b 04/05/23 15:19:26.559: itr: EID-record -> record-ttl: 15 mins, rloc-count: 0, action: nativ e-forward, non-auth, map-version: 0, afi: 1, [iid]eid/ml: [1]192.168.113.8/32 04/05/23 15:19:26.559: itr: Add [1]192.168.113.8/32 map-cache with 0 RLOCs

04/05/23 15:19:27.594: itr: <lisp.lisp_packet object at 0x7ff13124f5d0> 04/05/23 15:19:27.594: itr: Receive enp0s9, MACs: 0800-2798-6e54 -> 0800-27a8-e3fe, [1]192.168.129.5 -> [1]192.168.113.8, tos/ttl: 0/64, length: 84, packet: 45000054 ef4b400 0 4001d7fe c0a88105 c0a87108 08005738 00170002 0f2f2d64 00000000 9d480800 00000000 10111213 1415 1617 18191a1b 1c1d1e1f ... 04/05/23 15:19:27.595: itr: Lookup for EID [1]192.168.113.8 found map-cache entry [1]192.168.113.8/32 04/05/23 15:19:27.595: itr: Natively forwarding 04/05/23 15:19:27.595: itr: socket.sendto() failed: [Errno 101] Network is unreachable

how do i change the config file to make the static script work?

Bystrykha commented 1 year ago

I removed all "instance-id = *" lines from the configuration files and the ping started, why was there an error with iid?

farinacci commented 1 year ago

I removed all "instance-id = *" lines from the configuration files and the ping started, why was there an error with iid?

Yep, note that an instance-id concatenated with an EID is an "extended-EID" so it looks like a completely differnet address so you have to be consistent.

Great job debugging this and glad you fixed it.

I'm here if you need anything else. Please report progress. Thanks.

And send me your email address so I can cache it.

Thanks! Dino

Bystrykha commented 1 year ago

I found out, that dynamic scenario works only with using "instance-id" parameter, but if I use it, even static scenario not working. How can I feel config file for detection of dynamic-EID worked? Now my config look like this (without "instance-id" parameters): https://github.com/farinacci/lispers.net/issues/21#issuecomment-1497120207 This is my email: tri_de@inbox.ru Thanks for the help!

farinacci commented 1 year ago

Okay, I will look at that. And fix any bugs I find. Thanks!

Dino

On Apr 6, 2023, at 9:00 PM, Bystrykh Alexey @.***> wrote:

I found out, that dynamic scenario works only with using "instance-id" parameter, but if I use it, even static scenario not working. How can I feel config file for detection of dynamic-EID worked? Now my config look like this (without "instance-id" parameters): #21 (comment) This is my email: @. Рhanks for the help! — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.>

farinacci commented 1 year ago

Even when you configure "instance-id = 0"? It should default to that.

Dino

On Apr 6, 2023, at 9:00 PM, Bystrykh Alexey @.***> wrote:

I found out, that dynamic scenario works only with using "instance-id" parameter, but if I use it, even static scenario not working. How can I feel config file for detection of dynamic-EID worked? Now my config look like this (without "instance-id" parameters): #21 (comment) This is my email: @. Рhanks for the help! — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.>

Bystrykha commented 1 year ago

When "instance-id = 0" for all lisp sites, dynamic and static scenaries are work. Config files are:

xTR_1:

-----------------------------------------------------------------------------

lisp enable { itr = yes etr = yes rtr = no map-server = no map-resolver = no ddt-node = no } lisp debug { etr = yes core = yes map-resolver = no ddt-node = no rtr = no map-server = no itr = yes } lisp user-account { username = root password = =b9e5c39708999f844a3c864e863c12618bf8a3f5 super-user = yes } lisp xtr-parameters { rloc-probing = no data-plane-security = no

nat-traversal = yes

nat-traversal = no
nonce-echoing = no
data-plane-logging = yes
flow-logging = no

} lisp map-resolver { mr-name = my-mr address = 172.17.0.4 } lisp map-server { ms-name = my-ms address = 172.17.0.4 authentication-key = any-key } lisp database-mapping { prefix { ms-name = my-ms mr-name = my-mr eid-prefix = 192.168.1.0/24 instance-id = 0 } rloc { address = 172.17.0.2 } } lisp interface { interface-name = eid_1 device = eth0 instance-id = 0 } lisp interface { interface-name = rloc_1 device = eth1 }

-----------------------------------------------------------------------------

MSMR:

-----------------------------------------------------------------------------

lisp enable { itr = no etr = no rtr = no map-server = yes map-resolver = yes ddt-node = no } lisp debug { etr = no core = no map-resolver = yes ddt-node = no rtr = no map-server = yes itr = no } lisp user-account { username = root password = =b9e5c39708999f844a3c864e863c12618bf8a3f5 super-user = yes } lisp site { site-name = site-1 authentication-key = any-key allowed-prefix { eid-prefix = 192.168.1.0/24 accept-more-specifics = yes instance-id = 0 } } lisp site { site-name = site-2 authentication-key = some-key allowed-prefix { eid-prefix = 192.168.2.0/24 accept-more-specifics = yes instance-id = 0 } }

-----------------------------------------------------------------------------

xTR_2:

-----------------------------------------------------------------------------

lisp enable { itr = yes etr = yes rtr = no map-server = no map-resolver = no ddt-node = no } lisp debug { etr = yes core = yes map-resolver = no ddt-node = no rtr = no map-server = no itr = yes } lisp user-account { username = root password = =b9e5c39708999f844a3c864e863c12618bf8a3f5 super-user = yes } lisp xtr-parameters { rloc-probing = no data-plane-security = no

nat-traversal = yes

nat-traversal = no
nonce-echoing = no
data-plane-logging = yes
flow-logging = no

} lisp map-resolver { mr-name = my-mr address = 172.17.0.4 } lisp map-server { ms-name = my-ms address = 172.17.0.4 authentication-key = some-key } lisp database-mapping { prefix { eid-prefix = 192.168.2.5/32 dynamic-eid = yes mr-name = my-mr ms-name = my-ms instance-id = 0 } prefix { mr-name = my-mr ms-name = my-ms eid-prefix = 192.168.2.0/24 instance-id = 0 } rloc { address = 172.17.0.3 } } lisp interface { interface-name = eid2 device = eth0 dynamic-eid = 192.168.2.5/32 instance-id = 0 } lisp interface { interface-name = rloc device = eth1 }

-----------------------------------------------------------------------------

farinacci commented 1 year ago

Right but don’t include the command to see if it defaults the right way and still works. lisp interface { interface-name = eid_1 device = eth0 instance-id = 0}Remove instance-id above. And you also don’t need it on the map-server in the lisp site command FYI Thanks for verifying,DinoOn Apr 6, 2023, at 11:20 PM, Bystrykh Alexey @.***> wrote: When "instance-id = 0" for all lisp sites, dynamic and static scenaries are work. Config files are: xTR_1:

lispers.net lisp.config file, last changed: Fri Apr 7 06:03:58 UTC 2023

(1) Only commands between the first pair of dotted lines will be processed.

(2) Any lines you find prepended with "#>>>" are errors found during command processing.

(3) You may comment out lines by placing a "#" in the first column of any line between the section between the first pair of dotted lines.

(4) Note the modification timestamp above is auto generated after you have saved this file and it has been processed.

(5) Deleting configuration can be achieved by deleting lines and restarting the LISP component or by use of the LISP API.

(6) The landing web page on any device provides detailed Command and API documentation.

(7) Any name references must follow their definitions. Examples are elp-names and rle-names when referred to in static map-cache entries.

DO NOT WRITE TO ANY OTHER PART OF THIS FILE. YOU MUST ONLY ADD, CHANGE, OR REMOVE LINES BETWEEN THE FIRST PAIR OF DOTTED LINES SECTION.

-----------------------------------------------------------------------------

lisp enable { itr = yes etr = yes rtr = no map-server = no map-resolver = no ddt-node = no } lisp debug { etr = yes core = yes map-resolver = no ddt-node = no rtr = no map-server = no itr = yes } lisp user-account { username = root password = =b9e5c39708999f844a3c864e863c12618bf8a3f5 super-user = yes } lisp xtr-parameters { rloc-probing = no data-plane-security = no nat-traversal = yes nat-traversal = no nonce-echoing = no data-plane-logging = yes flow-logging = no

} lisp map-resolver { mr-name = my-mr address = 172.17.0.4 } lisp map-server { ms-name = my-ms address = 172.17.0.4 authentication-key = any-key } lisp database-mapping { prefix { ms-name = my-ms mr-name = my-mr eid-prefix = 192.168.1.0/24 instance-id = 0 } rloc { address = 172.17.0.2 } } lisp interface { interface-name = eid_1 device = eth0 instance-id = 0 } lisp interface { interface-name = rloc_1 device = eth1 }

-----------------------------------------------------------------------------

MSMR:

lispers.net lisp.config file, last changed: Fri Apr 7 05:19:04 UTC 2023