Bug #16757
open
UPnP IGD & PCP fills the logs with interface matching errors.
0%
Description
After enabling UPNP I noticed that my logs were filled with "miniupnpd 25998 interface index not matching". After applying this post on the forum the errors went away
https://forum.netgate.com/topic/157961/miniupnpd-errors/2?_=1774377196585.
Is it possible to fix the config generator for UPNP?
Updated by
Updated by Emre K 23 days ago
Marcos M wrote in #note-1:
I do not see these errors when testing. Please provide detailed and reproducible steps.
It seems to be result of UPNP clash while PIMD is active. (Possible SSDP issue, devices using SSDP might be needed to be present on these vlans to observe the issue)
1- Multiple VLANs present. VLAN10 (192.168.40.0/24) and VLAN20 (192.168.45.0/24)
2- Enable UPNP with all the options. Select VLAN10 and VLAN20 as interfaces
3- Allow ACL for these networks
allow 1024-65535 192.168.40.0/24 1024-65535 >> for VLAN10
allow 1024-65535 192.168.45.0/24 1024-65535 >> for VLAN20
4- Enable PIMD on these interfaces
5- Wait a while and check the pfsense Routing logs
Updated by Kris Phillips 18 days ago
I'm still not able to recreate this.
This redmine is missing an affected version. What version of pfSense was this tested on so that I can verify I'm testing 1 for 1?
Updated by Emre K 17 days ago
it was present in Plus 25.11.
Since then I have updated to 26.03 and stopped using PIMD since it was not launching properly due to an upstream issue and you had to make a fix to make it work. More details here: https://forum.netgate.com/topic/199686/unable-to-automatically-start-pimd
Updated by Kris Phillips 4 days ago
Emre K wrote in #note-5:
it was present in Plus 25.11.
Since then I have updated to 26.03 and stopped using PIMD since it was not launching properly due to an upstream issue and you had to make a fix to make it work. More details here: https://forum.netgate.com/topic/199686/unable-to-automatically-start-pimd
Hello Emre,
So, to confirm, you're not able to reproduce this issue on 26.03?