RouterOS 3.24 release, uPnP is not working. Anyone tested uPnP ?
I’m having the same issue. I couldn’t get 3.23 or 3.24 uPnP to work either. I thought maybe it was just me 
It would be nice if there was a way in winbox to display the nPnP mapings.
Turno on “Show Dummy Rule” from the UPNP settings to see rules in NAT.
Version 3.24 pre-relase uPNP works 
hahaha so strange 
Heeeey what happeend? Anyone has UPnP working?
very strange. Only work’s whith one external interfaz defined , if make two or more, not dst-nat properly.
In public ip (adsl) works well , in other public (same isp) no 
regards
I am talking about v3.24 May 22nd/release. UPnP IS NTO WORKING with one external Public interface and one Internal LAN interface.
we just made several tests and it’s working fine. can anyone else confirm it? we would need access to this router to see
Granted, just wrote to support. I will lower traffic going throu it if you will use sniffer, leaving the UPnP apps on.
When I sniff on the LAN interface of the RB, I see my main test host sending SSDP IPv4 multicast UPD packets to the proper UDP port 1900. No activity on tcp 2828 though.
So RouterOS sees the packets and does nothing? Or UPnP communication is incomplete?
When I click “Follow UDP Stream” in Wireshark, I get this:
M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
ST:upnp:rootdevice
MAN:“ssdp:discover”
MX:3M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
ST:upnp:rootdevice
MAN:“ssdp:discover”
MX:3M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
ST:upnp:rootdevice
MAN:“ssdp:discover”
MX:3M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
ST:upnp:rootdevice
MAN:“ssdp:discover”
MX:3M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
ST:upnp:rootdevice
MAN:“ssdp:discover”
MX:3
I have just tested v3.23 and v3.24. UPnP works ONLY WHEN I DISABLE IT AND THEN ENABLE IT. This disable/enable is done right after the router has booted. This means that UPnP can not start up properly.
Could this be due to, when UPnP starts, the Public interface has not yet been established as a PPPoE connection, so it stops working right there… ?
I can see it working on my devices as well, but theres an ongoing problem that Upnp doesn’t allow us to pick the external address we want it to run on.
Eg: If i have 2 external IP’s on a device and I want to allow 2 groups of users access to UPnP each behind one of those external IP’s I’m unable to do so. It will just pick the lowest IP address and add all mappings to that address.
Which is a problem when I’m using a high end router with more than 10 user groups behind it.
The UPnP rpblem I reported is temporarily fixed when I disable and enable UPnP after the Public interface has been established as a connection after the router has fully initialised. Support said it will be fixed in 3.25.
Multiple Public interfaces/addresses is different story! I have routers where I need to set UPnP like omega-00 explained in his post above!
Multiple public addresses is pretty much useless at the moment unless the users know which address the connections are supposed to be coming into and even then oubound will go via their regular nat rule.
Also, xbox360 upnp still doesn’t work yet.
3.25 is out, initial tests show problem is fixed.
I’m running 3.25. I first enabled upnp and then created two rules internal, external. Didn’t work. Spent a couple of hours wondering why it is not working, checked software firewall etc. then found this thread, disabled and enabled upnp once again and now it works. I don’t see the dummy rule though.
So, when you create it, it doesn’t work if you enable it before you have rules, I guess..
Running 3.25 on my RB450, UPnP we’re working on 3.20 but didn’t on 3.25.
After disabling / enabling UPnP it works! Dummy rules also!
EDIT: Also need to mention that I’m on a pure ethernet connection with DHCP-Client enabled on WAN interface.