Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WebSocket handler is return invalid messaging immediatly after connection upgrade #14

Open
stv0g opened this issue Apr 9, 2024 · 0 comments

Comments

@stv0g
Copy link
Contributor

stv0g commented Apr 9, 2024

VILLASnode log
21:10:14  dbg webrtc:pc        Signaling connection established
21:10:14  dbg webrtc:pc        Signaling message received: invalid signaling message
21:10:14 warn webrtc:pc        unknown signaling message
21:10:14  dbg webrtc:pc        Signaling message received: type=control, control={"peer_id": 14, "peers": [{"id": 14, "name": "66ba6762-a8a9-0903-f50a-feeaa9783a43", "remote": "[fd67:2f14:1fcd:0:bcea:ab75:4b12:c0b0]:35582"}]}
Packet capture
stv0g@nail:~/ > sudo nix run nixpkgs#tshark -- -Y websocket.payload -E occurrence=l -T fields -e text
Running as user "root" and group "root". This could be dangerous.
Capturing on 'enp2s0'
}
{}\n
 [truncated]{"control":{"peer_id":13,"peers":[{"name":"66ba6762-a8a9-0903-f50a-feeaa9783a43","id":13,"remote":"[fd67:2f14:1fcd:0:bcea:ab75:4b12:c0b0]:36996","created":"2024-04-09T10:14:47.659693694+02:00","connected":"2024-04-09T10:14:47.6^C3 packets captured
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant