Solved upnp throwing ConflictInMappingEntry even though port is free, target is local host

[sfx2000]

Probably I should open an issue in github for miniupnpd. If it had failed to start with this f'ed up config it would have saved some time.

miniupnpd threw the correct error...

 

[mvadu]

well, the error didn't say anything about wrong IP segment, it did not complain about incomplete config. Look at samba or nginx, which expects a solid config before starting, and it makes troubleshooting much easier. I did open the issue not sure if maintainer will accept it or not.

 

[RMerlin]

Secure mode can be disabled through the webui BTW. However I advise against it, as it is an important security feature of miniupnpd. One of the reasons why it never got affected by most of these UPnP security issues that appeared these past few months/years.

 

[ColinTaylor]

well, the error didn't say anything about wrong IP segment, it did not complain about incomplete config. Look at samba or nginx, which expects a solid config before starting, and it makes troubleshooting much easier. I did open the issue not sure if maintainer will accept it or not.

My comment: https://github.com/miniupnp/miniupnp/issues/551#issuecomment-860746489

 

[mvadu]

Secure mode can be disabled through the webui BTW. However I advise against it, as it is an important security feature of miniupnpd. One of the reasons why it never got affected by most of these UPnP security issues that appeared these past few months/years.

I am not disabling secure mode, but restricting allowed client to only one. I have two corporate issued laptops in household which have few software which tends to open way too many ports if allowed is list is default all local lan ( 192.168.23.1/255.255.255.0 in my case), my post conf updates that allowed list to raspberry pi's IP with 255.255.255.255 mask, thus restricting it to only one client.

PS> I finally got a reply from Merlin himself.. what a great day

 

[mvadu]

quick update, Mr. Thomas Bernard did consider this bug and has fixed it. The fix is scheduled for miniupnpd_2.3 milestone.

 

[Gewan]

Sigh! When will v2.3 be released? :|

 

[L&LD]

When it's ready.