Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

webRTCStar discovery disabled by default #858

Closed
pgte opened this issue May 20, 2017 · 11 comments · Fixed by #859
Closed

webRTCStar discovery disabled by default #858

pgte opened this issue May 20, 2017 · 11 comments · Fixed by #859
Assignees

Comments

@pgte
Copy link
Contributor

pgte commented May 20, 2017

Against current master, to use webRTCStar discovery I had to set config.Discovery.webRTCStar.Enabled to true, even though I had config.Addresses.Swarm set to ['/libp2p-webrtc-star/dns4/star-signal.cloud.ipfs.team/wss'].

I think this wasn't necessary before.
If not a bug, perhaps it should be added to the instructions.

@daviddias
Copy link
Member

@pgte could you check your repo to see if this flag is correctly set? https://github.com/ipfs/js-ipfs/blob/master/src/init-files/default-config-browser.json#L15

@daviddias
Copy link
Member

I can see there is something, although discovery seems to be working:

image

I don't get to have two nodes in different Chrome windows (or even one using Firefox) to see each other. This could be related with the new SS set up libp2p/js-libp2p-webrtc-star#111. Do you see the same behaviour?

@daviddias
Copy link
Member

Interesting, it might be my current network configuration (in a coffee shop). The ICE is not working between browser to browser but browser to wrtc works flawlessly.

@victorb
Copy link
Member

victorb commented May 21, 2017

@diasdavid

https://github.com/ipfs/js-ipfs/blob/master/src/init-files/default-config-browser.json#L15

Seems like in that file, the property Discovery is overwritten with {}

@daviddias
Copy link
Member

You have to check what is the loaded config. Note, Discovery works, just to show added a console log on peers found:

image

@daviddias
Copy link
Member

Still, no clue why 2 peers in the same machine are not finding each other. If we dial manually using connect, they dial successfully and exchange files.

@daviddias
Copy link
Member

yeah, WebRTCStar Discovery is not being enabled :( hte whole Discovery disappears

@daviddias
Copy link
Member

Ok, so I narrowed down the problem to this:

image

For some reason, the require('location of config') is yielding a config that has no keys on the Discovery property

@daviddias
Copy link
Member

image

@victorb
Copy link
Member

victorb commented May 21, 2017

image

;)

@daviddias
Copy link
Member

When I read "overwritten" I understood that somewhere in the code that was happening. thanks :)

@daviddias daviddias self-assigned this May 21, 2017
@daviddias daviddias removed the status/in-progress In progress label May 21, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants