https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162014-09-19T14:49:06ZpfSense bugtrackerpfSense - Todo #3874: Make miniupnpd config syntax compatible with new versionshttps://redmine.pfsense.org/issues/3874?journal_id=148352014-09-19T14:49:06ZRenato Botelhorenato@netgate.com
<ul><li><strong>Target version</strong> set to <i>2.2</i></li></ul> pfSense - Todo #3874: Make miniupnpd config syntax compatible with new versionshttps://redmine.pfsense.org/issues/3874?journal_id=148362014-09-19T15:00:11ZRenato Botelhorenato@netgate.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Applied in changeset <a class="changeset" title="Recent versions of miniupnpd does not accept IPv4 address anymore, use interface name always. It ..." href="https://redmine.pfsense.org/projects/pfsense/repository/2/revisions/8718669cafdb241a7b801489ba0d6dd20f8d1e7e">8718669cafdb241a7b801489ba0d6dd20f8d1e7e</a>.</p> pfSense - Todo #3874: Make miniupnpd config syntax compatible with new versionshttps://redmine.pfsense.org/issues/3874?journal_id=148422014-09-21T19:43:27ZAngel Torresangel@torres.li
<ul></ul><p>UPnP is working again for my gaming consoles with Open NAT thanks to this fix.</p> pfSense - Todo #3874: Make miniupnpd config syntax compatible with new versionshttps://redmine.pfsense.org/issues/3874?journal_id=148452014-09-22T05:05:40ZRenato Botelhorenato@netgate.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul>