UPNP broadcasts on non-LAN interface

[Sv0i]

OPNsense 22.7.4 OPNsense have 2 interfaces - LAN (hn1) and WAN (hn0). WAN interface is of type PPPoE (pppoe0). UPNP plugin is installed. UPNP External Interface is set to WAN. UPNP Interfaces is set to LAN.

tcpdump -i hn0 -n port 1900 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on hn0, link-type EN10MB (Ethernet), capture size 262144 bytes 23:01:44.080662 IP 192.168.1.1.33861 > 239.255.255.250.1900: UDP, length 446 23:01:44.080849 IP 192.168.1.1.33861 > 239.255.255.250.1900: UDP, length 455 23:01:44.081003 IP 192.168.1.1.33861 > 239.255.255.250.1900: UDP, length 518 23:01:44.081514 IP 192.168.1.1.57158 > 239.255.255.250.1900: UDP, length 510 ...

192.168.1.1 is the LAN (hn0) interface IP address. Tried using other LAN addresses and the source of the captured traffic changes accordingly.

hn0 interface is not assigned at all and is not supposed to send anything except PPPoE packets.

UPNP plugin is currently broadcasting your LAN interface address on the WAN interface. It has not been tested if UPNP will act and how if a response is received on hn0 interface.

[OPNsense-bot]

Thank you for creating an issue. Since the ticket doesn't seem to be using one of our templates, we're marking this issue as low priority until further notice.

For more information about the policies for this repository, please read https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md for further details.

The easiest option to gain traction is to close this ticket and open a new one using one of our templates.

[Tawmu]

I can't replicate this on 22.7.4

[OPNsense-bot]

This issue has been automatically timed-out (after 180 days of inactivity).

For more information about the policies for this repository, please read https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md for further details.

If someone wants to step up and work on this issue, just let us know, so we can reopen the issue and assign an owner to it.