BMA UPnP configuration conflicts with WS2P

It seems that a node having both BMA and public WS2P enabled with UPnP enabled only on WS2P, then UPnP just don't work for any API.

changed milestone to %1.7

Testing Duniter Desktop 1.6.17 tar.gz archive. Nodejs

May be it is related.

But playing with upnp on/off on duniter desktop seems to wreck the upnp responses of my livebox.

2018-02-03T16:50:14+01:00 - error: Error: Request failed: 500
    at /mnt/data/Logiciels/duniter-desktop-v1.6.17-linux-x64/node_modules/nnupnp/lib/nat-upnp/device.js:151:27
    at Parser.<anonymous> (/mnt/data/Logiciels/duniter-desktop-v1.6.17-linux-x64/node_modules/xml2js/lib/xml2js.js:199:18)
    at emitOne (events.js:115:13)
    at Parser.emit (events.js:210:7)
    at SAXParser.saxParser.onclosetag (/mnt/data/Logiciels/duniter-desktop-v1.6.17-linux-x64/node_modules/xml2js/lib/xml2js.js:183:24)
    at emit (/mnt/data/Logiciels/duniter-desktop-v1.6.17-linux-x64/node_modules/sax/lib/sax.js:624:35)
    at emitNode (/mnt/data/Logiciels/duniter-desktop-v1.6.17-linux-x64/node_modules/sax/lib/sax.js:629:5)
    at closeTag (/mnt/data/Logiciels/duniter-desktop-v1.6.17-linux-x64/node_modules/sax/lib/sax.js:889:7)
    at SAXParser.write (/mnt/data/Logiciels/duniter-desktop-v1.6.17-linux-x64/node_modules/sax/lib/sax.js:1436:13)
    at Parser.exports.Parser.Parser.parseString (/mnt/data/Logiciels/duniter-desktop-v1.6.17-linux-x64/node_modules/xml2js/lib/xml2js.js:211:31)
    at Parser.parseString (/mnt/data/Logiciels/duniter-desktop-v1.6.17-linux-x64/node_modules/xml2js/lib/xml2js.js:6:61)
    at Request._callback (/mnt/data/Logiciels/duniter-desktop-v1.6.17-linux-x64/node_modules/nnupnp/lib/nat-upnp/device.js:149:14)
    at Request.self.callback (/mnt/data/Logiciels/duniter-desktop-v1.6.17-linux-x64/node_modules/nnupnp/node_modules/request/main.js:120:22)
    at emitTwo (events.js:125:13)
    at Request.emit (events.js:213:7)
    at Request.<anonymous> (/mnt/data/Logiciels/duniter-desktop-v1.6.17-linux-x64/node_modules/nnupnp/node_modules/request/main.js:633:16)
    at emitOne (events.js:115:13)
    at Request.emit (events.js:210:7)
    at IncomingMessage.<anonymous> (/mnt/data/Logiciels/duniter-desktop-v1.6.17-linux-x64/node_modules/nnupnp/node_modules/request/main.js:595:14)
    at emitNone (events.js:110:20)
    at IncomingMessage.emit (events.js:207:7)
    at endReadableNT (_stream_readable.js:1059:12)

I have deleted .config/duniter, restarted a sync on gtest node, and get this error in the logs again...

assigned to @c-geek

changed milestone to %1.6.0

mentioned in commit e4484ac3

changed milestone to %1.7

@vtexier le but est t'il toujours présent suite aux changements qui avait été fais sur le code de l'UPnP ?

changed milestone to %1.9

Je n'ai plus de livebox... J'ai un router perso.

Personnellement sur Freebox je n'ai pas de conflits :

Par contre je sais que j'observe des erreurs 500 (requête UPnP) quand je dispose à la fois d'une connexion Wifi et d'une connexion Ethernet sur la même machine.

C'est peut-être ça le vrai bug.

changed milestone to %2.0

added time estimate of

unassigned @c-geek