duniter issueshttps://git.duniter.org/nodes/typescript/duniter/-/issues2020-10-04T18:34:41+02:00https://git.duniter.org/nodes/typescript/duniter/-/issues/1329WS2P sync does not work on nodes with a path in their WS2P endpoint2020-10-04T18:34:41+02:00Cédric MoreauWS2P sync does not work on nodes with a path in their WS2P endpointFor example with this endpoint:
WS2P 90e9b12 duniter.g1.1000i100.fr 443 /ws2p
Duniter will try to join `wss://duniter.g1.1000i100.fr /ws2p`. There is an extra space here which make the connection fail.For example with this endpoint:
WS2P 90e9b12 duniter.g1.1000i100.fr 443 /ws2p
Duniter will try to join `wss://duniter.g1.1000i100.fr /ws2p`. There is an extra space here which make the connection fail.1.10Cédric MoreauCédric Moreauhttps://git.duniter.org/nodes/typescript/duniter/-/issues/1306Member nodes stopped2018-07-09T11:20:32+02:00MoulMember nodes stoppedMy two member nodes stopped for the same reason with a two-hour intervals:
```bash
2018-07-08T22:23:29+02:00 - info: WS2P: init: bundle of peers 42/42
2018-07-08T22:23:29+02:00 - error: WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT...My two member nodes stopped for the same reason with a two-hour intervals:
```bash
2018-07-08T22:23:29+02:00 - info: WS2P: init: bundle of peers 42/42
2018-07-08T22:23:29+02:00 - error: WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE
2018-07-08T22:23:29+02:00 - error: WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE
2018-07-08T22:23:29+02:00 - error: WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE
2018-07-08T22:23:29+02:00 - error: Error: read ETIMEDOUT
at _errnoException (util.js:992:11)
at TCP.onread (net.js:618:25)
```
```bash
2018-07-08T19:56:26+02:00 - info: WS2P: Could not connect to peer HCpZPZKN using `WS2P 88.186.240.163 20900: WS2P connection timeout`
2018-07-08T19:56:26+02:00 - info: WS2P: Could not connect to peer CbjLvBvL using `WS2P g1.madeinzion.org 443: WS2P connection timeout`
2018-07-08T19:56:26+02:00 - info: WS2P: init: bundle of peers 41/41
2018-07-08T19:56:37+02:00 - error: Error: read ETIMEDOUT
at _errnoException (util.js:1003:13)
at TCP.onread (net.js:620:25)
```
One is on my local network and the other one in a data-center.
I assume they crashed because of an issue with WS2P implementation.https://git.duniter.org/nodes/typescript/duniter/-/issues/1305During the sync, propagate a new peer document and start listening to the net...2018-06-20T20:18:21+02:00Cédric MoreauDuring the sync, propagate a new peer document and start listening to the networkWe can listen to the network even if we don't have a blockchain: using WS2P private for example.
This way even if the sync takes a lot of time, we can keep up with the network's HEAD by receiving the new incoming blocks. Also, we would ...We can listen to the network even if we don't have a blockchain: using WS2P private for example.
This way even if the sync takes a lot of time, we can keep up with the network's HEAD by receiving the new incoming blocks. Also, we would get notified of each node's HEAD packet and display a view of the network during the synchronization.
This could help the user to understand what is the final state to reach. For example we could say "the node will reach this consensus".https://git.duniter.org/nodes/typescript/duniter/-/issues/1289On a new installation ws2p quota outgoing is 102020-10-04T18:36:17+02:00ÉloïsOn a new installation ws2p quota outgoing is 10On a new installation ws2p quota outgoing is 10 while it should be at 5On a new installation ws2p quota outgoing is 10 while it should be at 52.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1285Sync : check integrity of downloaded chunks2020-10-04T18:38:49+02:00ÉloïsSync : check integrity of downloaded chunkshttps://forum.duniter.org/t/ca-y-est-cest-lance-ou-presque-au-secours/4344/31?u=eloishttps://forum.duniter.org/t/ca-y-est-cest-lance-ou-presque-au-secours/4344/31?u=elois2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1284Node stopped2020-10-04T18:39:11+02:00MoulNode stopped1.6.21 stop:
```bash
2018-03-03T13:39:13+01:00 - warn: ESOCKETTIMEDOUT
2018-03-03T13:39:13+01:00 - info: Peer DJQjWdkUB9YWzGRPTjPCdGgC5pBx6CA24Dghu6NNvpuH unreachable: now considered as DOWN.
2018-03-03T13:39:15+01:00 - info: Pulling bl...1.6.21 stop:
```bash
2018-03-03T13:39:13+01:00 - warn: ESOCKETTIMEDOUT
2018-03-03T13:39:13+01:00 - info: Peer DJQjWdkUB9YWzGRPTjPCdGgC5pBx6CA24Dghu6NNvpuH unreachable: now considered as DOWN.
2018-03-03T13:39:15+01:00 - info: Pulling blocks from the network...
2018-03-03T13:39:16+01:00 - info: Node 5gJYnQ (g1.imirhil.fr:80) is UP!
2018-03-03T13:39:16+01:00 - info: Block resolution: 0 potential blocks after current#99603...
2018-03-03T13:39:16+01:00 - info: Will pull blocks from the network in 3 min 21 sec
2018-03-03T13:39:16+01:00 - info: Node FEkbc4 (me.jytou.fr:9007) is UP!
2018-03-03T13:39:20+01:00 - error: Error: read ETIMEDOUT
at _errnoException (util.js:1022:11)
at TCP.onread (net.js:615:25)
```2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1264Explicit SSL/TLS endpoints2020-10-04T18:40:29+02:00Kévin GuignardExplicit SSL/TLS endpointsPlease add explicit HTTPS endpoint for BMA (i.e. **BMAS**) and explicit WSS endpoint for WS2P (i.e. **WS2PS**).
I am NOT talking about handling SSL/TLS but how the nodes declare themselves on the network. By the way, a reverse-proxy (ngi...Please add explicit HTTPS endpoint for BMA (i.e. **BMAS**) and explicit WSS endpoint for WS2P (i.e. **WS2PS**).
I am NOT talking about handling SSL/TLS but how the nodes declare themselves on the network. By the way, a reverse-proxy (nginx, apache, stunnel, whatever) would still be required.2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1261clean old peer files and old endpoints2020-10-04T18:41:08+02:00Éloïsclean old peer files and old endpointshttps://forum.duniter.org/t/expiration-des-noeuds-connus/4048
* [ ] give up the concept of key peer card to switch to a node peer card.
* [ ] Add status field to node peer card.
* [ ] Delete longstanding continuous DOWN peer cards. ...https://forum.duniter.org/t/expiration-des-noeuds-connus/4048
* [ ] give up the concept of key peer card to switch to a node peer card.
* [ ] Add status field to node peer card.
* [ ] Delete longstanding continuous DOWN peer cards.
link to #12262.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1259WSP2 WebUI configuration make crash when set private2020-05-11T19:31:48+02:00MikeWSP2 WebUI configuration make crash when set privateWhen I try to input private as lo 127.0.0.1 or local ip, Duniter crash.<br />
I solved it with command line configuration. <br />
It appears now blank in WebUI:<br />
![Capture](/uploads/486dd2839aa30c81bec3221fdec7c579/Capture.PNG)
![Ca...When I try to input private as lo 127.0.0.1 or local ip, Duniter crash.<br />
I solved it with command line configuration. <br />
It appears now blank in WebUI:<br />
![Capture](/uploads/486dd2839aa30c81bec3221fdec7c579/Capture.PNG)
![Capture2](/uploads/7e735909184caea5a8dc51937ec70554/Capture2.PNG)1.9https://git.duniter.org/nodes/typescript/duniter/-/issues/1258add WS2P into wizard network command2020-10-04T18:42:39+02:00Éloïsadd WS2P into wizard network command2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1254Initial WS2P connection is too slow2018-01-20T23:53:45+01:00Cédric MoreauInitial WS2P connection is too slowIn the very first phase of WS2P connection when we start the service (`startCrawling()`), we try each peer one by one and most of the time without success. This delays a lot the start of the whole node's lifecycle (pull the network, ask ...In the very first phase of WS2P connection when we start the service (`startCrawling()`), we try each peer one by one and most of the time without success. This delays a lot the start of the whole node's lifecycle (pull the network, ask for missing blocks, getting new peers, etc.). This is quite annoying.
Instead of connecting node by node, I suggest we try a bunch of nodes at once and then repeat the process. For example, we could try 10 peers in a row, then 10 other peers, etc.1.6.0Cédric MoreauCédric Moreauhttps://git.duniter.org/nodes/typescript/duniter/-/issues/1252WS2P HEAD message can be incorrect on UPnP config2018-01-20T19:41:31+01:00Cédric MoreauWS2P HEAD message can be incorrect on UPnP configI'm using this configuration:
```json
"ws2p": {
"uuid": "65f71152",
"privateAccess": true,
"publicAccess": true,
"preferedOnly": false,
"privilegedOnly": false,
"upnp": true,
"maxPublic": 30,
"maxPrivate": 10,
"remotep...I'm using this configuration:
```json
"ws2p": {
"uuid": "65f71152",
"privateAccess": true,
"publicAccess": true,
"preferedOnly": false,
"privilegedOnly": false,
"upnp": true,
"maxPublic": 30,
"maxPrivate": 10,
"remotepath": ""
}
```
Which generates the following messages:
WS2POC:HEAD:1:EGYd1ENzqoqFtBfgPuLfony8Bza9WEVLztDjpHJfCJNZ:87738-0000044E6E81C696B996C7D63E168271687D1D24347C2B8900182711C4B4DA99:65f71152:duniter:1.6.15:1
WS2POC:HEAD:2:2ny7YAdmzReQxAayyJZsyVYwYhVyax2thKcGknmQy5nQ:87738-0000044E6E81C696B996C7D63E168271687D1D24347C2B8900182711C4B4DA99:a0a45ed2:duniter:1.6.15:1:26:21
But this always leads me to this error:
https://git.duniter.org/nodes/typescript/duniter/blob/1.6/app/modules/ws2p/lib/WS2PCluster.ts#L147
In the end, I never see my HEADs accepted by any node.1.6.0ÉloïsÉloïshttps://git.duniter.org/nodes/typescript/duniter/-/issues/1228Document WS2P v1 Protocol2018-06-14T18:12:52+02:00ÉloïsDocument WS2P v1 Protocol1.6.0ÉloïsÉloïshttps://git.duniter.org/nodes/typescript/duniter/-/issues/1226Create an up/down peers report for the ws2p network layer2020-10-04T18:41:01+02:00ÉloïsCreate an up/down peers report for the ws2p network layer2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1220ws2p private : apply the quota to the number of keys rather than the number o...2018-01-10T22:18:38+01:00Éloïsws2p private : apply the quota to the number of keys rather than the number of connectionsFor better network connectivity, ws2p v1.1 allows to connect to multiple nodes of the same key as long as their uuid is different.
However, in order to prevent a member from lying massively to the network by introducing hundreds of nodes...For better network connectivity, ws2p v1.1 allows to connect to multiple nodes of the same key as long as their uuid is different.
However, in order to prevent a member from lying massively to the network by introducing hundreds of nodes with its key that would fill the quotas of the other nodes, the quota must be calculated by key and not by connection.1.6.0ÉloïsÉloïshttps://git.duniter.org/nodes/typescript/duniter/-/issues/1219ws2p network renewal: delete 1 connection from each time to force the network...2018-01-10T22:19:07+01:00Éloïsws2p network renewal: delete 1 connection from each time to force the network to remain dynamicImplementation: If the incoming connection quota is full, delete a low-priority connection every 10 minutes.Implementation: If the incoming connection quota is full, delete a low-priority connection every 10 minutes.1.6.0ÉloïsÉloïshttps://git.duniter.org/nodes/typescript/duniter/-/issues/1214WS2P HEAD : add freeMemberRoom and freeMirorRoom fields2018-01-20T14:58:07+01:00ÉloïsWS2P HEAD : add freeMemberRoom and freeMirorRoom fieldshttps://forum.duniter.org/t/beta-test-duniter-1-6-ws2p/3247/248?u=eloishttps://forum.duniter.org/t/beta-test-duniter-1-6-ws2p/3247/248?u=elois1.6.0ÉloïsÉloïshttps://git.duniter.org/nodes/typescript/duniter/-/issues/1210Décrochage récurrent de nœud2020-10-04T18:45:03+02:00Cédric MoreauDécrochage récurrent de nœud*Created by: LeoBoudet*
Je ne sais pas si cela est lié à la version 1.6.14 mais depuis que je l'ai installée, mon nœud décroche sans arrêt et ne parvient pas à raccrocher les wagons. Régulièrement il perd toutes ses connexions aux autre...*Created by: LeoBoudet*
Je ne sais pas si cela est lié à la version 1.6.14 mais depuis que je l'ai installée, mon nœud décroche sans arrêt et ne parvient pas à raccrocher les wagons. Régulièrement il perd toutes ses connexions aux autres nœuds et ne les récupère pas de lui-même.
Séries de messages type :
**WS2P: Could not connect to peer D3krfq6J using `WS2P 77.152.31.154 20900: WS2P connection timeout`**
_Start/stop server_ n'améliorent pas le problème. Le dernier _reset data_ n'a rien donné non plus...
[duniter.log](https://github.com/duniter/duniter/files/1484498/duniter.log)2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1205add a step field in WS2P Head2018-01-15T15:56:04+01:00Éloïsadd a step field in WS2P HeadThe idea is to estimate the density of the WS2P network by knowing for each head by how many nodes it passed before reaching itself.
The node will initialize its own head with step=0
Each time the node relays headers it increments th...The idea is to estimate the density of the WS2P network by knowing for each head by how many nodes it passed before reaching itself.
The node will initialize its own head with step=0
Each time the node relays headers it increments their step field.
Note that this step field will not be signed. It will provide purely indicative data and will nevertheless be useful for statistical purposes if it is assumed that the majority of the nodes in the network do not lie.1.6.0ÉloïsÉloïshttps://git.duniter.org/nodes/typescript/duniter/-/issues/1203Planning the improvement of WS2P for duniter 2.02018-01-25T00:05:52+01:00ÉloïsPlanning the improvement of WS2P for duniter 2.0_A description in English is available below the description in French_
# 2.0
WS2P V2 : (dev en 2018)
- [ ] ne pas tenter de se connecter à un noeud qui est déjà connecté a soi #1180
- [ ] Envoyer l'uuid et la version de la communicat..._A description in English is available below the description in French_
# 2.0
WS2P V2 : (dev en 2018)
- [ ] ne pas tenter de se connecter à un noeud qui est déjà connecté a soi #1180
- [ ] Envoyer l'uuid et la version de la communication dans le message de connexion
- [ ] Gérer les erreurs de version
- [ ] Lorsqu'on se connecte a la même clé que soit, ajouter le préfixe au message
- [ ] Détecter lorsque la clique est complète et affecter alors automatiquement un nouveau préfix en cas de duplicata
- [ ] Créer et diffuser un endpoint v2 avec le même UUID (en plus de l'endpoint v1 pour la compatibilité)
- [ ] Créer un concept de nœuds up/down pour la couche réseau ws2p #1226
- [ ] Transmettre sa fiche de peer lors du message CONNECT (https://forum.duniter.org/t/4015/15)
- [ ] Créer un système de synchronisation via ws2p #1179
- [ ] Créer un head V3 avec timestamp diffuser en duplicata du head V2
- [ ] Dans le format HEAD v3, créer des champs spécifiques pour les types de couches réseaux
- [ ] filtrer les heads diffusés pour les connexions de version strictement inférieure à 3
(Ce plan n'est pas figé, il vas changer régulièrement en fonction des besoins que je constate et de vos retours)
----
# 2.0
WS2P V2 : (in 2018)
- [ ] not attempt to connect to a node that is already connected to itself #1180
- [ ] Send the uuid and communication version in the connection message
- [ ] Handling version errors
- [ ] When connecting to the same key, add the prefix to the message.
- [ ] Detect when the clique is complete and automatically assign a new prefix in case of duplicate.
- [ ] Create and distribute an endpoint v2 with the same UUID (in addition to endpoint v1 for compatibility)
- [ ] Create an up/down peers report for the ws2p network layer #1226
- [ ] Transmit your peer record during the CONNECT message
- [ ] Create a synchronization mechanism via ws2p #1179
- [ ] Create a V3 head with timestamp broadcast in duplicate V2 head
- [ ] In V3 head, create specific fields for network layer types
- [ ] Filter heads broadcast for connections of version strictly inferior to 3
(This plan is not fixed, it will change regularly according to the needs I see and your feedback.)2.0ÉloïsÉloïs