duniter issueshttps://git.duniter.org/nodes/typescript/duniter/-/issues2020-10-04T18:47:45+02:00https://git.duniter.org/nodes/typescript/duniter/-/issues/1180WS2P Optimization: do not attempt to connect to a node whose key has already ...2020-10-04T18:47:45+02:00ÉloïsWS2P Optimization: do not attempt to connect to a node whose key has already connected us.It seems that Private WS2P is trying to connect to keys that are already connected in public mode.
Provide an exception for oneself (for multi-node cases).It seems that Private WS2P is trying to connect to keys that are already connected in public mode.
Provide an exception for oneself (for multi-node cases).2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1176resolv why test ws2p server limitations needs to establish a oneself ws2p con...2020-10-04T18:46:39+02:00Éloïsresolv why test ws2p server limitations needs to establish a oneself ws2p connectionthis test does not pass any more when we warn oneself ws2p connection :
So in the meantime we're applying an exception on the 11111111 uuid : https://github.com/duniter/duniter/commit/9fe597ee15631ff924addcb8a41a40577c211c93this test does not pass any more when we warn oneself ws2p connection :
So in the meantime we're applying an exception on the 11111111 uuid : https://github.com/duniter/duniter/commit/9fe597ee15631ff924addcb8a41a40577c211c932.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1179Create a synchronization mechanism via ws2p2020-10-04T18:45:53+02:00ÉloïsCreate a synchronization mechanism via ws2pThis requires creating a new type of WS2P connection specifically designed for sync, a kind of temporary websocket just the time to download chunk files.This requires creating a new type of WS2P connection specifically designed for sync, a kind of temporary websocket just the time to download chunk files.2.0https://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/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/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/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/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/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/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/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/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/1151ws2p-public doesn't work if ws2p-private is disabled2018-12-08T16:02:08+01:00Éloïsws2p-public doesn't work if ws2p-private is disabledThe ws2p endpoint is not published if ws2p-private is disabledThe ws2p endpoint is not published if ws2p-private is disabledHorizonhttps://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/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ïshttps://git.duniter.org/nodes/typescript/duniter/-/issues/1160Wrong WS2P endpoint generated2017-11-28T16:49:17+01:00insoWrong WS2P endpoint generatedWhile testing Sakia parser of peers present on the network, I encountered the following one :
```
Version: 10
Type: Peer
Currency: g1
PublicKey: 5jfUpXPWAiBXNVG49tjQYA7R3VFX2oG2aPiskR5PE8Mc
Block: 62955-00000464C24BAF5A6BDD56D1A...While testing Sakia parser of peers present on the network, I encountered the following one :
```
Version: 10
Type: Peer
Currency: g1
PublicKey: 5jfUpXPWAiBXNVG49tjQYA7R3VFX2oG2aPiskR5PE8Mc
Block: 62955-00000464C24BAF5A6BDD56D1AB5C73C9A6A1684C577B97A04FAB7D5ADF772C23
Endpoints:
WS2P c0b55f43 90.25.85.172 20901
WS2P c0b55f43 [object Object] 20900
BASIC_MERKLED_API lilel.hopto.org 90.25.209.55 10901
ajpRexbt1qxaWHJYtthZHlzh1L1EYDKpNgaejLoVmNH1vP6cROUiMSu/rdISxL8fHvLGVll/MoHa1qb91BgyDg==
```
The owner of this node is http://g1.duniter.org/cesium/#/app/wot/5jfUpXPWAiBXNVG49tjQYA7R3VFX2oG2aPiskR5PE8Mc/DamageCo.
The WS2P field contains an [object Object] entry.
Maybe DamageCo should be contacted to check his node configuration and see if there is a real bug.
Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/1102WS2P: prevent JSON injection2017-11-28T16:49:16+01:00Cédric MoreauWS2P: prevent JSON injectionWS2P parses received JSON. We need to take a big care on the received JSON because it could carry invalid content.WS2P parses received JSON. We need to take a big care on the received JSON because it could carry invalid content.Horizon