Differences between 9.0.x and 9.1.x, 2 peers as initators ?
See original GitHub issuePlease see the issue we encounter here: https://github.com/mafintosh/webrtc-swarm/issues/37
It fails when we got 2 peers trying to connect to each other as initatiator. However, there were no such issue with simple-peer <= 9.0.x
. Can you help us find what changes between simple-peer v9.0.x
and v9.1.0
could explain that issue ?
Issue Analytics
- State:
- Created 5 years ago
- Comments:7
Top Results From Across the Web
2 peers as initiator ? · Issue #37 · mafintosh/webrtc-swarm
Sometimes, we get 2 peers trying to connect as initiator at same time. ... Differences between 9.0.x and 9.1.x, 2 peers as initators ......
Read more >Peer Zoning Compared to Other Zoning Types - TechDocs
: One-to-many zoning creates a zone with multiple hosts and one target. This approach creates fewer zones as compared to single-initiator zoning ......
Read more >Release Notes for the Cisco ASA Series, 9.1(x)
The effect on each network will be different, but it could range from an issue of limited connectivity to something more extensive like...
Read more >SnapMirror configuration and best practices guide for ONTAP ...
Converting between different data protection modes . ... From ONTAP 9.x onwards, SnapMirror relationships can be encrypted natively end-to-end.
Read more >Changelog - Cypress Documentation
Fixed a 9.x to 10.x migration bug where the migration tool would hang without ... Fixed a regression in 9.2.0 to keep Cypress...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The issue was due to webrtc-swarm allowing two peers to try and connect as initators. I think you can close this issue.
We also had the same issue with the 9.2.0. Is the connection between 2 peers trying to connect as initiators supposed to work ?
I think the error was caused by having two instances of simple-peer on each actual peer. One instance of simple-peer trying to connect as non-initator and at the same time another instance of simple-peer trying to connect as initiator.
We fixed the issue in webrtc-swarm by having only one of the peers try to connect as initiator on this branch of webrtc-swarm.