WIP: Ping interop in py-libp2p and rust-libp2p #620

lla-dane · 2025-05-20T19:13:04Z

Description

This is a work-progress pull request for establishing interoperability between py-libp2p and rust-libp2p.

Changes

The directory structure is similar to ./interop-tests in rust-libp2p.

interop/exec/native_ping.py
interop/exec/config: env variables for ping test
interop/arch.py: RedisClient and SwarmBuilder utilities
interop/lib.py: handle_ping, send_ping and run_test(SwarmRunner) utilities

Current Status

Ping test is successful for 2 py-libp2p nodes with insecure, secio and mplex.

Logs

Listener

❯ transport=tcp ip=0.0.0.0 is_dialer=false port=8000 redis_addr=6379 test_timeout_seconds=180 security=insecure muxer=mplex python3 native_ping.py

2025-05-18 22:29:13.035 | INFO     | interop.lib:run_test:69 - Starting run_test
2025-05-18 22:29:13.161 | INFO     | interop.lib:run_test:75 - Running ping test local_peer=Qmd5TtD5cr5sWfJsgexK6ESZr2FhvuzgLwPMVFyikKpWCB
2025-05-18 22:29:13.164 | INFO     | interop.lib:run_test:83 - Test instance, listening: /ip4/0.0.0.0/tcp/8000/p2p/Qmd5TtD5cr5sWfJsgexK6ESZr2FhvuzgLwPMVFyikKpWCB
received ping from QmcwusXZydtSbD9evrcHyaXEwMN8GjnTXHBsT67iYcm9yN
responded with pong to QmcwusXZydtSbD9evrcHyaXEwMN8GjnTXHBsT67iYcm9yN

Dialer

❯ transport=tcp ip=0.0.0.0 is_dialer=true port=8001 redis_addr=6379 test_timeout_seconds=180 security=insecure muxer=mplex python3 native_ping.py

2025-05-18 22:29:16.488 | INFO     | interop.lib:run_test:69 - Starting run_test
2025-05-18 22:29:16.572 | INFO     | interop.lib:run_test:75 - Running ping test local_peer=QmcwusXZydtSbD9evrcHyaXEwMN8GjnTXHBsT67iYcm9yN
2025-05-18 22:29:16.585 | INFO     | interop.lib:run_test:95 - Remote conection established
2025-05-18 22:29:16.585 | INFO     | interop.lib:run_test:100 - handshake time: 9.33ms
sending ping to Qmd5TtD5cr5sWfJsgexK6ESZr2FhvuzgLwPMVFyikKpWCB
received pong from Qmd5TtD5cr5sWfJsgexK6ESZr2FhvuzgLwPMVFyikKpWCB

Next Steps

Extend the support for Noise and Yamux, to test interoperability with rust-libp2p.

@seetadev

seetadev · 2025-05-22T21:06:48Z

@lla-dane : Hi Abhinav. Great progress.

Wish to share that yamux has been merged today. Looking forward to an early resolution to CI/CD fixes.

seetadev · 2025-05-23T14:50:19Z

@lla-dane : Great progress. Please use yamux for interop tests now.

This would resolve most of the CI/CD issues. Rust-libp2p has deprecated mplex and are using yamux.

Yamux PR got merged yesterday by @pacrob. Please keep @acul71 and me in the loop as you share code commits using yamux as the multiplexer.

lla-dane · 2025-05-23T15:16:39Z

Yes, sure. Stuck with a few errors right now, but will post an update soon!!

lla-dane · 2025-05-24T12:11:50Z

What is happening currently is, after the security and muxer negotiation happens, the protocol negotiation fails. I will explain the case for py-dialer and rust-listener.

Starting up py-dialer and rust-listener with the following commands:

# ./interop/exec: py-dialer
transport=tcp ip=127.0.0.1 is_dialer=true redis_addr=6379 port=8001 test_timeout_seconds=180 security=noise  muxer=yamux  python3 native_ping.py 

# ./rust-libp2p: rust-listener
RUST_LOG=debug redis_addr=localhost:6379 ip="0.0.0.0" transport=tcp security=noise muxer=yamux is_dialer="false" cargo run --bin native_ping

py-dialer logs

Logs

2025-05-24 22:59:05.534 | INFO     | interop.lib:run_test:69 - Starting run_test
2025-05-24 22:59:05.736 | INFO     | interop.lib:run_test:75 - Running ping test local_peer=QmYG1F2byD3M4eRs2E46k32NseJffaQxj85GAnFkHRAvrf
2025-05-24 22:59:05.743 | INFO     | interop.lib:run_test:126 - GETTING READY FOR CONNECTION
2025-05-24 22:59:05.743 | DEBUG    | libp2p.network.swarm:dial_peer:139 - attempting to dial peer %s
2025-05-24 22:59:05.743 | INFO     | libp2p.network.swarm:dial_peer:155 - HANDSHAKE GOING TO HAPPEN
2025-05-24 22:59:05.744 | DEBUG    | libp2p.network.swarm:dial_addr:191 - dialed peer %s over base transport
2025-05-24 22:59:05.744 | INFO     | libp2p.protocol_muxer.multiselect_client:select_one_of:70 - TRYING TO GET THE HANDSHAKE HAPPENED
2025-05-24 22:59:05.744 | INFO     | libp2p.protocol_muxer.multiselect_client:handshake:46 - WROTE SUC, /multistream/1.0.0
2025-05-24 22:59:05.747 | INFO     | libp2p.protocol_muxer.multiselect_client:handshake:49 - READ SUC, /multistream/1.0.0
2025-05-24 22:59:05.748 | INFO     | libp2p.protocol_muxer.multiselect_client:select_one_of:72 - HANDSHAKE HAPPENED
2025-05-24 22:59:05.748 | INFO     | libp2p.protocol_muxer.multiselect_client:select_one_of:75 - /noise
2025-05-24 22:59:05.748 | INFO     | libp2p.protocol_muxer.multiselect_client:try_select:101 - /noise
2025-05-24 22:59:05.748 | INFO     | libp2p.protocol_muxer.multiselect_client:try_select:107 - Response: 
2025-05-24 22:59:05.757 | DEBUG    | libp2p.network.swarm:dial_addr:204 - upgraded security for peer %s
2025-05-24 22:59:05.757 | INFO     | libp2p.protocol_muxer.multiselect_client:select_one_of:70 - TRYING TO GET THE HANDSHAKE HAPPENED
2025-05-24 22:59:05.757 | INFO     | libp2p.protocol_muxer.multiselect_client:handshake:46 - WROTE SUC, /multistream/1.0.0
2025-05-24 22:59:05.759 | INFO     | libp2p.protocol_muxer.multiselect_client:handshake:49 - READ SUC, /multistream/1.0.0
2025-05-24 22:59:05.759 | INFO     | libp2p.protocol_muxer.multiselect_client:select_one_of:72 - HANDSHAKE HAPPENED
2025-05-24 22:59:05.759 | INFO     | libp2p.protocol_muxer.multiselect_client:select_one_of:75 - /yamux/1.0.0
2025-05-24 22:59:05.759 | INFO     | libp2p.protocol_muxer.multiselect_client:try_select:101 - /yamux/1.0.0
2025-05-24 22:59:05.759 | INFO     | libp2p.protocol_muxer.multiselect_client:try_select:107 - Response: 
2025-05-24 22:59:05.759 | DEBUG    | libp2p.network.swarm:dial_addr:213 - upgraded mux for peer %s
2025-05-24 22:59:05.760 | DEBUG    | libp2p.network.swarm:dial_addr:217 - successfully dialed peer %s
2025-05-24 22:59:05.760 | INFO     | interop.lib:run_test:128 - HOST CONNECTED
2025-05-24 22:59:05.760 | DEBUG    | libp2p.network.swarm:new_stream:227 - attempting to open a stream to peer %s
2025-05-24 22:59:05.760 | INFO     | libp2p.network.swarm:dial_peer:134 - WE ARE RETURNING, PEER ALREADAY EXISTS
2025-05-24 22:59:05.760 | INFO     | libp2p.network.swarm:new_stream:230 - INETCONN CREATED
2025-05-24 22:59:05.760 | INFO     | libp2p.network.swarm:new_stream:233 - INETSTREAM CREATED
2025-05-24 22:59:05.760 | DEBUG    | libp2p.network.swarm:new_stream:235 - successfully opened a stream to peer %s
2025-05-24 22:59:05.760 | INFO     | libp2p.host.basic_host:new_stream:186 - INETSTREAM CHECKING IN
2025-05-24 22:59:05.760 | INFO     | libp2p.host.basic_host:new_stream:187 - ['/ipfs/ping/1.0.0']
2025-05-24 22:59:05.760 | DEBUG    | libp2p.host.basic_host:new_stream:190 - PROTOCOLS TRYING TO GET SENT
2025-05-24 22:59:05.760 | INFO     | libp2p.protocol_muxer.multiselect_client:select_one_of:70 - TRYING TO GET THE HANDSHAKE HAPPENED
2025-05-24 22:59:05.760 | INFO     | libp2p.protocol_muxer.multiselect_client:handshake:46 - WROTE SUC, /multistream/1.0.0
2025-05-24 22:59:05.762 | DEBUG    | libp2p.host.basic_host:_swarm_stream_handler:237 - failed to accept a stream from peer %s, error=%s
2025-05-24 22:59:05.762 | ERROR    | libp2p.protocol_muxer.multiselect_client:handshake:51 - READ FAIL, fail to read from multiselect communicator
2025-05-24 22:59:05.762 | DEBUG    | libp2p.host.basic_host:new_stream:196 - fail to open a stream to peer %s, error=%s

rust-listener logs

Logs

2025-05-24T17:29:03.063081Z  INFO libp2p_swarm: local_peer_id=12D3KooWBjkD7G113HB1RgaU36kRYWsfqQKXKuKT23cBas1W3DYZ
2025-05-24T17:29:03.063232Z  INFO interop_tests: Running ping test local_peer=12D3KooWBjkD7G113HB1RgaU36kRYWsfqQKXKuKT23cBas1W3DYZ
2025-05-24T17:29:03.063387Z DEBUG libp2p_tcp: listening on 0.0.0.0:0
2025-05-24T17:29:03.065175Z  INFO interop_tests: Test instance, listening for incoming connections on address address=/ip4/0.0.0.0/tcp/0
2025-05-24T17:29:03.076315Z DEBUG Swarm::poll: libp2p_tcp: New listen address address=/ip4/127.0.0.1/tcp/40449
2025-05-24T17:29:03.076491Z DEBUG Swarm::poll: libp2p_swarm: New listener address listener=ListenerId(1) address=/ip4/127.0.0.1/tcp/40449
2025-05-24T17:29:03.076796Z DEBUG Swarm::poll: libp2p_tcp: New listen address address=/ip4/192.168.31.130/tcp/40449
2025-05-24T17:29:03.076880Z DEBUG Swarm::poll: libp2p_swarm: New listener address listener=ListenerId(1) address=/ip4/192.168.31.130/tcp/40449
2025-05-24T17:29:03.111888Z DEBUG Swarm::poll: libp2p_tcp: New listen address address=/ip4/172.19.0.1/tcp/40449
2025-05-24T17:29:03.111976Z DEBUG Swarm::poll: libp2p_swarm: New listener address listener=ListenerId(1) address=/ip4/172.19.0.1/tcp/40449
2025-05-24T17:29:03.112045Z DEBUG interop_tests: NewListenAddr { listener_id: ListenerId(1), address: /ip4/172.19.0.1/tcp/40449 }
2025-05-24T17:29:03.112124Z DEBUG Swarm::poll: libp2p_tcp: New listen address address=/ip4/172.17.0.1/tcp/40449
2025-05-24T17:29:03.112171Z DEBUG Swarm::poll: libp2p_swarm: New listener address listener=ListenerId(1) address=/ip4/172.17.0.1/tcp/40449
2025-05-24T17:29:03.112218Z DEBUG interop_tests: NewListenAddr { listener_id: ListenerId(1), address: /ip4/172.17.0.1/tcp/40449 }
2025-05-24T17:29:03.112303Z DEBUG Swarm::poll: libp2p_tcp: New listen address address=/ip4/172.18.0.1/tcp/40449
2025-05-24T17:29:03.112351Z DEBUG Swarm::poll: libp2p_swarm: New listener address listener=ListenerId(1) address=/ip4/172.18.0.1/tcp/40449
2025-05-24T17:29:03.112401Z DEBUG interop_tests: NewListenAddr { listener_id: ListenerId(1), address: /ip4/172.18.0.1/tcp/40449 }
2025-05-24T17:29:05.744517Z DEBUG Swarm::poll: libp2p_tcp: Incoming connection from remote at local remote_address=/ip4/192.168.31.130/tcp/33746 local_address=/ip4/192.168.31.130/tcp/40449
2025-05-24T17:29:05.745833Z DEBUG interop_tests: IncomingConnection { connection_id: ConnectionId(1), local_addr: /ip4/192.168.31.130/tcp/40449, send_back_addr: /ip4/192.168.31.130/tcp/33746 }
2025-05-24T17:29:05.748791Z DEBUG new_incoming_connection{remote_addr=/ip4/192.168.31.130/tcp/33746 id=1}: multistream_select::listener_select: Listener: confirming protocol protocol=/noise
2025-05-24T17:29:05.748877Z DEBUG new_incoming_connection{remote_addr=/ip4/192.168.31.130/tcp/33746 id=1}: multistream_select::listener_select: Listener: sent confirmed protocol protocol=/noise
2025-05-24T17:29:05.759486Z DEBUG new_incoming_connection{remote_addr=/ip4/192.168.31.130/tcp/33746 id=1}: multistream_select::listener_select: Listener: confirming protocol protocol=/yamux/1.0.0
2025-05-24T17:29:05.759564Z DEBUG new_incoming_connection{remote_addr=/ip4/192.168.31.130/tcp/33746 id=1}: multistream_select::listener_select: Listener: sent confirmed protocol protocol=/yamux/1.0.0
2025-05-24T17:29:05.759922Z DEBUG new_incoming_connection{remote_addr=/ip4/192.168.31.130/tcp/33746 id=1}: yamux::connection: new connection: bdb5a808 (Server)    
2025-05-24T17:29:05.760482Z DEBUG Swarm::poll: libp2p_swarm: Connection established peer=QmYG1F2byD3M4eRs2E46k32NseJffaQxj85GAnFkHRAvrf endpoint=Listener { local_addr: /ip4/192.168.31.130/tcp/40449, send_back_addr: /ip4/192.168.31.130/tcp/33746 } total_peers=1
2025-05-24T17:29:05.760548Z DEBUG interop_tests: ConnectionEstablished { peer_id: PeerId("QmYG1F2byD3M4eRs2E46k32NseJffaQxj85GAnFkHRAvrf"), connection_id: ConnectionId(1), endpoint: Listener { local_addr: /ip4/192.168.31.130/tcp/40449, send_back_addr: /ip4/192.168.31.130/tcp/33746 }, num_established: 1, concurrent_dial_errors: None, established_in: 14.499266ms }
2025-05-24T17:29:05.760591Z DEBUG new_established_connection{remote_addr=/ip4/192.168.31.130/tcp/33746 id=1 peer=QmYG1F2byD3M4eRs2E46k32NseJffaQxj85GAnFkHRAvrf}:Connection::poll: yamux::connection::rtt: sending ping 3065193300    
2025-05-24T17:29:05.761599Z DEBUG new_established_connection{remote_addr=/ip4/192.168.31.130/tcp/33746 id=1 peer=QmYG1F2byD3M4eRs2E46k32NseJffaQxj85GAnFkHRAvrf}:Connection::poll: yamux::connection: bdb5a808: new outbound (Stream bdb5a808/2) of (Connection bdb5a808 Server (streams 1))    
2025-05-24T17:29:05.761880Z DEBUG new_established_connection{remote_addr=/ip4/192.168.31.130/tcp/33746 id=1 peer=QmYG1F2byD3M4eRs2E46k32NseJffaQxj85GAnFkHRAvrf}:Connection::poll: multistream_select::dialer_select: Dialer: Proposed protocol protocol=/ipfs/ping/1.0.0
2025-05-24T17:29:05.762018Z DEBUG new_established_connection{remote_addr=/ip4/192.168.31.130/tcp/33746 id=1 peer=QmYG1F2byD3M4eRs2E46k32NseJffaQxj85GAnFkHRAvrf}:Connection::poll: yamux::connection::rtt: received pong 3065193300, estimated round-trip-time 1.428048ms    
2025-05-24T17:29:05.762630Z DEBUG Swarm::poll: libp2p_swarm: Connection closed with error IO(Custom { kind: Other, error: Error(Right(Decode(Io(Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" })))) }): Connected { endpoint: Listener { local_addr: /ip4/192.168.31.130/tcp/40449, send_back_addr: /ip4/192.168.31.130/tcp/33746 }, peer_id: PeerId("QmYG1F2byD3M4eRs2E46k32NseJffaQxj85GAnFkHRAvrf") } total_peers=0
2025-05-24T17:29:05.762710Z DEBUG interop_tests: ConnectionClosed { peer_id: PeerId("QmYG1F2byD3M4eRs2E46k32NseJffaQxj85GAnFkHRAvrf"), connection_id: ConnectionId(1), endpoint: Listener { local_addr: /ip4/192.168.31.130/tcp/40449, send_back_addr: /ip4/192.168.31.130/tcp/33746 }, num_established: 0, cause: Some(IO(Custom { kind: Other, error: Error(Right(Decode(Io(Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" })))) })) }

So what's happening is:

The dialer successfully negotiates noise and muxer for stream, at ConnectionEstablished in the rust logs.
But after that when the /ipfs/ping/1.0.0 protocol negotiation starts to happen, the dialer write /multistream/1.0.0 in stream for handshake, but cannot read from the stream, visible in the py-logs in this line:

2025-05-24 22:59:05.760 | INFO     | libp2p.protocol_muxer.multiselect_client:handshake:46 - WROTE SUC, /multistream/1.0.0

I think for some reason during protocol negotiation the stream get reset or something.
But this issue does not happens when the same implementations are used.

So I can't figure out why this is happening, what I am missing. @acul71 @paschal533 .

paschal533 · 2025-05-24T14:00:29Z

Hey @lla-dane, thanks for the detailed breakdown and logs. It looks like the Noise and Yamux negotiations are working fine, but the protocol negotiation for /ipfs/ping/1.0.0 is failing because the Python dialer can’t read the response after writing /multistream/1.0.0. I suspect this is either a multistream-select mismatch or a ping protocol incompatibility between py-libp2p and rust-libp2p. Here’s what I think we should try next:

Debug Multistream-Select:
Let’s add more logging to the Rust listener to see how it handles the /multistream/1.0.0 handshake. Run the listener with:

RUST_LOG=debug,libp2p::multistream_select=debug redis_addr=localhost:6379 ip="127.0.0.1" transport=tcp security=noise muxer=yamux is_dialer="false" cargo run --bin native_ping

This should show if the Rust side is responding correctly or resetting the stream. Also, can you check the libp2p.protocol_muxer.multiselect_client.handshake function in Python to see if it’s reading the response correctly? Maybe add some debug prints like:

print(f"DEBUG: Writing /multistream/1.0.0 to stream")
await stream.write(b"/multistream/1.0.0\n")
print(f"DEBUG: Reading response from stream")
response = await stream.read(1024)
print(f"DEBUG: Received response: {response}")

Could you share the updated Rust and Python logs after trying these? Also, let’s keep @acul71 and @seetadev in the loop for any new commits. If you’re still stuck, I can help test this locally with the same setup. Thanks for driving this forward

paschal533 · 2025-05-24T14:23:51Z

Hi @lla-dane , @acul71, @seetadev ,

Just a quick update on the ping example in py-libp2p/examples/ping/ping.py. I’ve confirmed that the current version uses Plaintext as the security protocol since it calls new_host() without a custom sec_opt configuration. This means it’s not yet aligned with rust-libp2p’s default Noise protocol for our interop tests.

I’m actively working on updating ping.py to include Noise support by adding NoiseTransport and X25519 keypair configurations, similar to what we discussed earlier. However, I’m still hitting the ModuleNotFoundError: No module named 'libp2p.crypto.x25519' despite x25519.py being in libp2p/crypto/ and updating libp2p/crypto/__init__.py with from .x25519 import create_new_key_pair as create_new_x25519_key_pair. The tests in tests/crypto/test_x25519.py pass, so the module is functional, but ping.py can’t resolve it.

Next Steps:

I’m debugging the x25519 module resolution issue. @lla-dane, could you share the exact py-libp2p commit/branch you’re using or confirm how you’re running native_ping.py to avoid this error?
Once the module issue is resolved, I’ll test the updated ping.py with Noise against the Rust listener using the custom ping behavior (32-byte 0x01 payload) to fix the protocol negotiation issue as mentioned.
I’ll also update native_ping.py to include Noise for consistency with our interop tests.

I’ll post another update with logs once I get Noise working. Please let me know if you have any tips on the x25519 import

lla-dane · 2025-05-24T16:59:34Z

I’m debugging the x25519 module resolution issue. @lla-dane, could you share the exact py-libp2p commit/branch you’re using or confirm how you’re running native_ping.py to avoid this error?

@paschal533: This error is coming on this branch: https://github.com/lla-dane/py-libp2p/tree/interop/py-rust. And I am running the py-dialer using the below command in ./interop/exec directory:

transport=tcp ip=127.0.0.1 is_dialer=true redis_addr=6379 port=8001 test_timeout_seconds=180 security=noise  muxer=yamux  python3 native_ping.py

lla-dane · 2025-05-25T12:01:48Z

interop/arch.py

+                        key_pair, noise_privkey=noise_key_pair.private_key
+                    )
+                },
+            )


I’ve confirmed that the current version uses Plaintext as the security protocol since it calls new_host() without a custom sec_opt configuration. This means it’s not yet aligned with rust-libp2p’s default Noise protocol for our interop tests.

@paschal533: As you can see here, in the ./interop/arch.py the new_host function builds the hosts as per the specs specified in the initiation command, and its not running on plaintext as sec-protocol as default.

Nope, I wasn't refering to this PR. I was refering to py-libp2p/examples/ping/ping.py. py-libp2p/examples/ping/ping.py is running on plaintext as sec-protocol.

lla-dane · 2025-05-25T12:19:29Z

These are the logs of a successful handshake between two py-nodes.

Logs

(venv) shelby@soiarch ~/Desktop/libp2p/py-libp2p/interop/exec ❯ transport=tcp ip=127.0.0.1 is_dialer=true redis_addr=6379 port=8001 test_timeout_seconds=180 security=noise  muxer=yamux  python3 native_ping.py 

2025-05-25 17:42:49.665 | INFO     | interop.lib:run_test:69 - Starting run_test
2025-05-25 17:42:50.712 | INFO     | interop.lib:run_test:75 - Running ping test local_peer=QmbzWn9Xp4Xzwa4kpQWghc1SMJfUoYRfc7dB2v79anX8Ta
2025-05-25 17:42:50.725 | INFO     | interop.lib:run_test:126 - GETTING READY FOR CONNECTION
2025-05-25 17:42:50.725 | DEBUG    | libp2p.network.swarm:dial_peer:139 - attempting to dial peer %s
2025-05-25 17:42:50.725 | INFO     | libp2p.network.swarm:dial_peer:155 - HANDSHAKE GOING TO HAPPEN
2025-05-25 17:42:50.726 | DEBUG    | libp2p.network.swarm:dial_addr:191 - dialed peer %s over base transport
2025-05-25 17:42:50.726 | INFO     | libp2p.protocol_muxer.multiselect_client:select_one_of:70 - TRYING TO GET THE HANDSHAKE HAPPENED
2025-05-25 17:42:50.726 | INFO     | libp2p.protocol_muxer.multiselect_client:handshake:46 - WROTE SUC, /multistream/1.0.0
2025-05-25 17:42:50.726 | INFO     | libp2p.protocol_muxer.multiselect_client:handshake:49 - READ SUC, /multistream/1.0.0
2025-05-25 17:42:50.726 | INFO     | libp2p.protocol_muxer.multiselect_client:select_one_of:72 - HANDSHAKE HAPPENED
2025-05-25 17:42:50.726 | INFO     | libp2p.protocol_muxer.multiselect_client:select_one_of:75 - /noise
2025-05-25 17:42:50.726 | INFO     | libp2p.protocol_muxer.multiselect_client:try_select:101 - /noise
2025-05-25 17:42:50.727 | INFO     | libp2p.protocol_muxer.multiselect_client:try_select:107 - Response: 
2025-05-25 17:42:50.771 | DEBUG    | libp2p.network.swarm:dial_addr:204 - upgraded security for peer %s
2025-05-25 17:42:50.771 | INFO     | libp2p.protocol_muxer.multiselect_client:select_one_of:70 - TRYING TO GET THE HANDSHAKE HAPPENED
2025-05-25 17:42:50.771 | INFO     | libp2p.protocol_muxer.multiselect_client:handshake:46 - WROTE SUC, /multistream/1.0.0
2025-05-25 17:42:50.797 | INFO     | libp2p.protocol_muxer.multiselect_client:handshake:49 - READ SUC, /multistream/1.0.0
2025-05-25 17:42:50.797 | INFO     | libp2p.protocol_muxer.multiselect_client:select_one_of:72 - HANDSHAKE HAPPENED
2025-05-25 17:42:50.797 | INFO     | libp2p.protocol_muxer.multiselect_client:select_one_of:75 - /yamux/1.0.0
2025-05-25 17:42:50.798 | INFO     | libp2p.protocol_muxer.multiselect_client:try_select:101 - /yamux/1.0.0
2025-05-25 17:42:50.798 | INFO     | libp2p.protocol_muxer.multiselect_client:try_select:107 - Response: 
2025-05-25 17:42:50.799 | DEBUG    | libp2p.network.swarm:dial_addr:213 - upgraded mux for peer %s
2025-05-25 17:42:50.799 | DEBUG    | libp2p.network.swarm:dial_addr:217 - successfully dialed peer %s
2025-05-25 17:42:50.800 | INFO     | interop.lib:run_test:128 - HOST CONNECTED
2025-05-25 17:42:50.800 | DEBUG    | libp2p.network.swarm:new_stream:227 - attempting to open a stream to peer %s
2025-05-25 17:42:50.800 | INFO     | libp2p.network.swarm:dial_peer:134 - WE ARE RETURNING, PEER ALREADAY EXISTS
2025-05-25 17:42:50.800 | INFO     | libp2p.network.swarm:new_stream:230 - INETCONN CREATED
2025-05-25 17:42:50.800 | INFO     | libp2p.network.swarm:new_stream:233 - INETSTREAM CREATED
2025-05-25 17:42:50.800 | DEBUG    | libp2p.network.swarm:new_stream:235 - successfully opened a stream to peer %s
2025-05-25 17:42:50.800 | INFO     | libp2p.host.basic_host:new_stream:186 - INETSTREAM CHECKING IN
2025-05-25 17:42:50.800 | INFO     | libp2p.host.basic_host:new_stream:187 - ['/ipfs/ping/1.0.0']
2025-05-25 17:42:50.801 | DEBUG    | libp2p.host.basic_host:new_stream:190 - PROTOCOLS TRYING TO GET SENT
2025-05-25 17:42:50.801 | INFO     | libp2p.protocol_muxer.multiselect_client:select_one_of:70 - TRYING TO GET THE HANDSHAKE HAPPENED
2025-05-25 17:42:50.801 | INFO     | libp2p.protocol_muxer.multiselect_client:handshake:46 - WROTE SUC, /multistream/1.0.0
2025-05-25 17:42:50.802 | INFO     | libp2p.protocol_muxer.multiselect_client:handshake:49 - READ SUC, /multistream/1.0.0
2025-05-25 17:42:50.802 | INFO     | libp2p.protocol_muxer.multiselect_client:select_one_of:72 - HANDSHAKE HAPPENED
2025-05-25 17:42:50.802 | INFO     | libp2p.protocol_muxer.multiselect_client:select_one_of:75 - /ipfs/ping/1.0.0
2025-05-25 17:42:50.802 | INFO     | libp2p.protocol_muxer.multiselect_client:try_select:101 - /ipfs/ping/1.0.0
2025-05-25 17:42:50.804 | INFO     | libp2p.protocol_muxer.multiselect_client:try_select:107 - Response: 
2025-05-25 17:42:50.804 | INFO     | libp2p.host.basic_host:new_stream:194 - PROTOCOLS GOT SENT
2025-05-25 17:42:50.804 | INFO     | interop.lib:run_test:133 - CREATED NEW STREAM
2025-05-25 17:42:50.804 | INFO     | interop.lib:run_test:136 - Remote conection established
2025-05-25 17:42:50.804 | INFO     | interop.lib:run_test:142 - handshake time: 79.69ms
sending ping to QmUVzokJA5siraZSfFD8YXHUaR8GjzSitGcT1eP3snkshb
received pong from QmUVzokJA5siraZSfFD8YXHUaR8GjzSitGcT1eP3snkshb

Between rust and py, its failing around this part:

seetadev · 2025-05-26T16:06:46Z

@lla-dane and @paschal533 : Appreciate your contribution. Do we need help from rust-maintainers here (Elena and Joao). We have a community call tomorrow and can discuss on this specific pull request.

Also, touch base with @acul71 on this effort. He is about to start the js-libp2p inteop effort in the coming days.

paschal533 · 2025-05-29T09:40:40Z

These are the logs of a successful handshake between two py-nodes.

Logs
Between rust and py, its failing around this part:

Noted. Thank you.
I'm currently working on this. I will give my update by evening.

paschal533 · 2025-05-29T15:39:25Z

Hi @lla-dane

I've been digging into the py-libp2p and rust-libp2p interoperability issues, and I think I've found the root cause. The problem seems to be with py-libp2p's incomplete Noise implementation. It's preventing successful connections between the two implementations. I discovered that py-libp2p's Noise is currently using X25519 keys, while rust-libp2p expects Ed25519 keys for the identity verification part of the handshake. When I tried to modify py-libp2p to use Ed25519 keys, it gets further in the process but then fails because of the incomplete implementation.

What's happening:

py-libp2p generates the Ed25519 key pair fine: public=95bbc18d2e79774320ae4f996dc3fd1ee9f1be498f6979f6b17b3fc607b8950c
But rust-libp2p can't parse it: InvalidKey(DecodingError { msg: "failed to parse Ed25519 public key" })

This suggests there's a mismatch in how the keys are being encoded/serialized during the Noise handshake.

I want to discuss this with @seetadev and @acul71... thinking of taking on the task of completing the Noise implementation in py-libp2p.

lla-dane · 2025-05-29T15:45:27Z

@paschal533 : Great, this is great. Thanks for finding this out.

paschal533 · 2025-05-29T17:02:54Z

Hi @acul71, After further investigation, I discovered that both implementations should be using X25519 for the Noise Diffie-Hellman key exchange. That part is actually correct. The issue appears to be with key encoding/serialization compatibility during the handshake process.

py-libp2p generates keys that should be compatible, but there's an encoding mismatch
rust-libp2p fails to parse what should be a valid key: InvalidKey(DecodingError { msg: "failed to parse Ed25519 public key" })
The error mentions Ed25519, but this likely refers to libp2p identity keys rather than the Noise DH keys themselves.

The real issue is a mismatch in how the keys (possibly identity keys used alongside the Noise handshake) are being encoded/serialized between the two implementations. The py-libp2p Noise implementation may be incomplete in how it handles key formatting or the integration between Noise protocol keys and libp2p identity verification.
This suggests the fix should focus on key serialization compatibility rather than changing the fundamental cryptographic primitives being used. I will keep you posted with my updates

paschal533 · 2025-05-29T18:16:48Z

Hi @lla-dane, @seetadev, @acul71 So I made some modifications to py-libp2p/examples/ping/ping.py and found out what's actually happening. Good news is we're now closer than we thought

The real issue isn't about X25519 vs Ed25519 keys - both implementations are actually using X25519 correctly for the Noise protocol. The problem is much more specific, py-libp2p's Noise code is trying to call .get_public_key() on the noise private key object, but our current implementation doesn't have that method. It only has .public_key(). So it crashes with: 'NoisePrivateKey' object has no attribute 'get_public_key'

What this means:

The connection setup now works fine (rust-libp2p even confirms the /noise protocol)
Protocol negotiation is successful
It only fails when trying to build the handshake payload because of this missing method

On the rust side:

It just sees the connection die unexpectedly ("eof" error)
Which makes sense since our Python side crashes before completing the handshake

This is actually encouraging because it means py-libp2p's Noise implementation is mostly there. It just needs the proper API methods implemented. It's more of a "finish the implementation" problem rather than a "rewrite everything" problem.

I think this should be pretty straightforward to fix. currently working on fixing it.

acul71 · 2025-05-31T00:38:28Z

This is actually encouraging because it means py-libp2p's Noise implementation is mostly there. It just needs the proper API methods implemented. It's more of a "finish the implementation" problem rather than a "rewrite everything" problem.

I think this should be pretty straightforward to fix. currently working on fixing it.

@paschal533
Great news, You are a good "detective" Paschal. :-)
I hope that when this rust-libp2p and py-libp2p issue will be solved, also py-libp2p and js-libp2p ping will work.
Share your last finding here and ping me if you need something.
Ciao Luca

varun-r-mallya · 2025-06-06T09:51:12Z

I get an error like this on a fresh install of this branch. I'll try get this fixed.

varun-r-mallya · 2025-06-06T10:05:08Z

setup.py

@@ -37,10 +37,14 @@
        "pytest-trio>=0.5.2",
        "factory-boy>=2.12.0,<3.0.0",
    ],
+    "interop": ["redis==6.1.0", "logging==0.4.9.6" "loguru==0.7.3"],


Missed comma here is causing it to fail building

varun-r-mallya · 2025-06-06T10:30:55Z

varun-r-mallya#2
As you can see, the failing tests are due to very simple issues. I'll try getting these fixed

varun-r-mallya · 2025-06-06T13:54:40Z

These are the logs of a successful handshake between two py-nodes.

Logs
Between rust and py, its failing around this part:

why does it fail here when I run the same code ??

lla-dane · 2025-06-06T14:04:38Z

why does it fail here when I run the same code ??

Hey @varun-r-mallya , thanks for taking an interest in this PR. Actually there was a noise encryption incompatibility with the rust-libp2p ping interop example. As you can see from the above conversations, there was a stream rejection issue withthe rust node, so @paschal533 worked on this and created a test plan in #532 for ping example with appropriate adoption of noise and yamux upgrades. He has been working on creating an appropriate test plan for the ping-interop, for new contributors to work on.

varun-r-mallya · 2025-06-06T14:11:14Z

why does it fail here when I run the same code ??

Hey @varun-r-mallya , thanks for taking an interest in this PR. Actually there was a noise encryption incompatibility with the rust-libp2p ping interop example. As you can see from the above conversations, there was a stream rejection issue withthe rust node, so @paschal533 worked on this and created a test plan in #532 for ping example with appropriate adoption of noise and yamux upgrades. He has been working on creating an appropriate test plan for the ping-interop, for new contributors to work on.

Can I please have the test plan and know exactly what to continue work on so I can contribute to this effort ?

lla-dane · 2025-06-06T14:15:21Z

Can I please have the test plan and know exactly what to continue work on so I can contribute to this effort ?

So firstly, we have to test out the ping example in #532 appropriately with rust node locally. It was throwing an error at my end, so @paschal533 said he would be documenting on how he ran the py and rust nodes appropriately, as we have to do some tweaks on the rust side also. So after that's done locally, then we just have to integrate the noise and yamux updates in this PR's arch.py file and run the ping-interop successfully with the rust node.

seetadev · 2025-06-06T15:55:40Z

why does it fail here when I run the same code ??

Hey @varun-r-mallya , thanks for taking an interest in this PR. Actually there was a noise encryption incompatibility with the rust-libp2p ping interop example. As you can see from the above conversations, there was a stream rejection issue withthe rust node, so @paschal533 worked on this and created a test plan in #532 for ping example with appropriate adoption of noise and yamux upgrades. He has been working on creating an appropriate test plan for the ping-interop, for new contributors to work on.

Can I please have the test plan and know exactly what to continue work on so I can contribute to this effort ?

@varun-r-mallya and @lla-dane : Great progress. Please study in details: https://github.com/libp2p/test-plans

Ping is a part of the interop suite. We will follow it up wth interop focused on hole punching, transport interop (webrtc, quic, websockets) followed by gossipsub interop :) @mystical-prog and @paschal533 will help you in this specific project related to interop with rust-libp2p with focus on ping protocol.

seetadev · 2025-06-09T03:57:00Z

@paschal533 : Wish to share that we discussed internally with the rust-libp2p team.

Kindly don't close interop pull requests before the interop scripts land up in the test plans repository.

seetadev · 2025-06-09T03:57:28Z

@lla-dane and @varun-r-mallya : CI/CD tests are failing. Kindly resolve the issues. Please keep in touch with Elena from rust-libp2p team for helping this land up in the test plans repository.

@paschal533 : Please add your notes/feedback here in this pull request. This has been shared with the rust-libp2p team.

lla-dane · 2025-06-09T10:08:08Z

@paschal533 : Ran the ping examples from #664. The py-listener logs look like this:

Is this the farthest that is possible at present ?

lla-dane · 2025-06-09T10:13:18Z

@seetadev : Sir actually @paschal533 mentioned in #664 that the Ping protocol has been blocked by Yamux frame parsing issues, which is under investigation. Till then the ping test in #664 is the farthest that we have arrived, and will do the same thing here in the interop tests.

paschal533 · 2025-06-09T10:18:21Z

@paschal533 : Ran the ping examples from #664. The py-listener logs look like this:

Is this the farthest that is possible at present ?

Yes, this is the farthest that is possible at the present.

lla-dane · 2025-06-09T10:19:20Z

Okay then I will reflect these changes in this PR

varun-r-mallya · 2025-06-09T10:29:47Z

@lla-dane and @varun-r-mallya : CI/CD tests are failing. Kindly resolve the issues. Please keep in touch with Elena from rust-libp2p team for helping this land up in the test plans repository.

@paschal533 : Please add your notes/feedback here in this pull request. This has been shared with the rust-libp2p team.

I did see why the CI CD errors were happening and I have fixed them on my branch. They are very trivial and can be fixed when we have local tests passing. It would not be nice to add an extra logging library to the actual dependencies (loguru is used here I think), so the tests will pass once we remove these unnecessary dependencies. @seetadev

paschal533 · 2025-06-09T10:33:58Z

@lla-dane and @varun-r-mallya : CI/CD tests are failing. Kindly resolve the issues. Please keep in touch with Elena from rust-libp2p team for helping this land up in the test plans repository.

@paschal533 : Please add your notes/feedback here in this pull request. This has been shared with the rust-libp2p team.

Alright manu, I will the notes/feedback here as soon as possible.

lla-dane mentioned this pull request May 20, 2025

WIP: Interop for ping on py-libp2p and rust-libp2p #615

Closed

lla-dane force-pushed the interop/py-rust branch from 91407d6 to 84e5419 Compare May 23, 2025 10:22

lla-dane commented May 25, 2025

View reviewed changes

lla-dane mentioned this pull request May 31, 2025

WIP: Progress on py-libp2p and rust-libp2p interop for Ping #532

Open

varun-r-mallya reviewed Jun 6, 2025

View reviewed changes

seetadev mentioned this pull request Jun 9, 2025

WIP feat: Add py-libp2p to rust-libp2p interoperability tests suit #664

Closed

13 tasks

lla-dane added 2 commits June 10, 2025 14:41

interop utilities for mplex ping

18524b0

added: logs

f2dbd4a

lla-dane force-pushed the interop/py-rust branch from fda82ff to f2dbd4a Compare June 10, 2025 09:12

lla-dane added 3 commits June 10, 2025 15:04

removed loguru

ac1e3c8

removed extar logs

0589317

updated as per libp2p#664

fd82e55

WIP: Ping interop in py-libp2p and rust-libp2p #620

Are you sure you want to change the base?

WIP: Ping interop in py-libp2p and rust-libp2p #620

Uh oh!

Conversation

lla-dane commented May 20, 2025

Description

Changes

Current Status

Logs

Listener

Dialer

Next Steps

Uh oh!

seetadev commented May 22, 2025

Uh oh!

seetadev commented May 23, 2025

Uh oh!

lla-dane commented May 23, 2025

Uh oh!

lla-dane commented May 24, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

py-dialer logs

rust-listener logs

Uh oh!

paschal533 commented May 24, 2025

Uh oh!

paschal533 commented May 24, 2025

Uh oh!

lla-dane commented May 24, 2025

Uh oh!

lla-dane May 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

paschal533 May 29, 2025

Choose a reason for hiding this comment

Uh oh!

lla-dane commented May 25, 2025

Uh oh!

seetadev commented May 26, 2025

Uh oh!

paschal533 commented May 29, 2025

Uh oh!

paschal533 commented May 29, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

lla-dane commented May 29, 2025

Uh oh!

paschal533 commented May 29, 2025

Uh oh!

paschal533 commented May 29, 2025

Uh oh!

acul71 commented May 31, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

varun-r-mallya commented Jun 6, 2025

Uh oh!

varun-r-mallya Jun 6, 2025

Choose a reason for hiding this comment

Uh oh!

varun-r-mallya commented Jun 6, 2025

Uh oh!

varun-r-mallya commented Jun 6, 2025

Uh oh!

lla-dane commented Jun 6, 2025

Uh oh!

varun-r-mallya commented Jun 6, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

lla-dane commented Jun 6, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

seetadev commented Jun 6, 2025

Uh oh!

seetadev commented Jun 9, 2025

Uh oh!

seetadev commented Jun 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

lla-dane commented May 24, 2025 •

edited

Loading

lla-dane May 25, 2025 •

edited

Loading

paschal533 commented May 29, 2025 •

edited

Loading

acul71 commented May 31, 2025 •

edited

Loading

varun-r-mallya commented Jun 6, 2025 •

edited

Loading

lla-dane commented Jun 6, 2025 •

edited

Loading

seetadev commented Jun 9, 2025 •

edited

Loading