Am Tuesday, 26. August 2014, 17.22:25 schrieb Josh Luthman: > That definitely doesn't look right. Here's mine: > > /ip upnp interfaces > add disabled=no interface=bridge1 type=internal > add disabled=no interface=ether1 type=external
I found the cause... I had a secondary static IP address configured on the external interface. So the destination IP in the dnat rule did not refer to the destination where the packets were sent to internaly, but to the external ip that should be nated. After disabling that secondary ip (which I only use to query snmp values of the cable modem connected to the 'internet' interface, which is only possible of accessed via this private ip) upnp started working as expected. Maybe the logics should be altered to first use a dynamic ip address on an external interface and only if not present a static one. I also found that if I query the upnp xml file on the mikrotik, I get much more information like a comment which gives some information what tool caused the rule to be created (skype on mobile phones as example). I found no way to get that information via webfig or cli. It's not the comment from the dnat rule. Benoit Panizzon -- I m p r o W a r e A G - ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 07 CH-4133 Pratteln Fax +41 61 826 93 02 Schweiz Web http://www.imp.ch ______________________________________________________ _______________________________________________ Mikrotik mailing list [email protected] http://mail.butchevans.com/mailman/listinfo/mikrotik Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
