Bping on LTP bench demo seems to give erroneous RTT values

[Xploror]

Hello ION team,

I have been using the demo/bench-ltp/ example to play around with couple of scenarios. I can normally start node 2 and node 3 individually on different terminals and then I run bpecho on node 3 and bping at node 2 as shown below:

On node 3

bpecho ipn:3.1

On node 2

bping -c 5 -i 1 -q 0 ipn:2.1 ipn:3.1 > bpingoutput1

My egress plan is as shown below. Since the one-way light time (OWLT) between 2 and 3 is set to be 7 seconds (arbitrary), I expect RTT to be atleast no less than 14.

m horizon  +0
a range    +0 +600		2 3   7
a contact  +0 +32		2 3   10000000000
a contact  +90 +420		2 3   10000000000
a contact  +0 +600		3 2   10000000000

When the bping runs it creates an output file as shown below. This output file was run exactly 12 seconds after the first call to the ./ionstart. I have also ran it multiple times to crosscheck if the values were infact outliers but thats not the case, all the RTT values are around 1 sec. From my understanding, if the OWLT is 7 between nodes 2 and 3, then shouldn't the bping values should have a minimum of 14 seconds recorded as RTT? It feels like it almost instantaneously is able to send the bundles to node 3 even though the range specifies 7 seconds separation.

read interval of 1 ad 1.000000
64 bytes from ipn:3.1  seq=0 time=0.959325 s
64 bytes from ipn:3.1  seq=1 time=0.958316 s
64 bytes from ipn:3.1  seq=2 time=0.958316 s
64 bytes from ipn:3.1  seq=3 time=0.958481 s
64 bytes from ipn:3.1  seq=4 time=0.961887 s
5 bundles transmitted, 5 bundles received, 0.00% bundle loss, time 4.963728 s
rtt min/avg/max/sdev = 958.316/959.265/961.887/1.363 ms

Please guide me if I'm doing anything wrong or I should expect bping to not reflect the propagation delay?