Bug #3388
closed
WebSocketTransport: inaccurate LocalUri
0%
Description
Steps to reproduce:
- Connect to NFD over WebSocket.
- Execute
nfd-status -f.
Expected: LocalUri for WebSocket face contains IP address.
Actual: LocalUri for WebSocket face looks like ws://[::]:9696 and does not contain IP address.
Updated by Davide Pesavento almost 9 years ago
Unit testing didn't catch this bug because TestWebSocketTransport/StaticProperties only checks an IPv4 loopback address. Can you confirm that using IPv4 yields the expected result?
As part of this issue, TestWebSocketTransport needs to be extended to test IPv6 endpoints as well.
Updated by Junxiao Shi almost 9 years ago
Can you confirm that using IPv4 yields the expected result?
Either IPv4 and IPv6 connection shows ws://[::]:9696 as LocalUri.
I'm okay with showing ws://[::ffff:192.0.2.128]:9696 for IPv4 connection.
Updated by Davide Pesavento almost 9 years ago
Sorry I wasn't clear. In your test you tried connecting via IPv4, but NFD was still using the IPv6 WebSocketChannel (this is because the v6 channel is really v4+v6, since websocketpp doesn't allow creating v6-only servers). What I meant was: disable the v6 websocket listener in NFD and try again (via IPv4 obviously).
Updated by Junxiao Shi almost 9 years ago
- Status changed from New to Closed
The issue is gone after updating to NFD 0.4.0. Both IPv4 and IPv6 work correctly.
The report was based on NFD 0.4.0-beta2.