Miniupnpd listening to wrong interface



  • Hi,

    I experienced problem getting UPNP and NAT-PNP to work. Log gives following error messages:

    Aug 7 12:17:19 miniupnpd[79815]: ioctl(s, SIOCGIFADDR, …): Can't assign requested address
    Aug 7 12:17:19 miniupnpd[79815]: ioctl(s, SIOCGIFADDR, …): Can't assign requested address
    Aug 7 12:17:19 miniupnpd[79815]: ioctl(s, SIOCGIFADDR, …): Can't assign requested address
    Aug 7 12:17:19 miniupnpd[79815]: ioctl(s, SIOCGIFADDR, …): Can't assign requested address
    Aug 7 12:17:19 miniupnpd[79815]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
    Aug 7 12:17:19 miniupnpd[79815]: Failed to get IP for interface fxp0
    Aug 7 12:17:19 miniupnpd[79815]: ioctl(s, SIOCGIFADDR, …): Can't assign requested address
    Aug 7 12:06:32 miniupnpd[79815]: Listening for NAT-PMP traffic on port 5351
    Aug 7 12:06:32 miniupnpd[79815]: HTTP listening on port 2189

    under closer inspection of /var/etc/miniupnpd.conf I found that ext_ifname=fxp0 which is my WAN interface. I ensured that LAN is selected in Services: UPnP & NAT-PMP, hit CHANGE button. Go back to check file but it still shows ext_ifname=fxp0.

    To work around I manually changed /var/etc/miniupnpd.conf line ext_ifname=bge0 (LAN interface), then restart UPNP service and it seems to work fine. However this is temporary fix and only works until changes are made in "Services: UPnP & NAT-PMP".

    Anyone experienced similar problem?

    2.1-RC1 (i386) built on Thu Aug 1 19:03:40 EDT 2013


  • Rebel Alliance Developer Netgate

    ext == EXTERNAL interface. That should be WAN, that's where it puts the port forwards.

    UPnP isn't compatible with multi-wan, it doesn't have a way in the GUI to select an alternate WAN yet, so it assumes that the interface labeled internally as "wan" is used for the external interface, so fxp0 in your setup.



  • Oh not a bug then, sorry. I now am confused though cause utorrent happily maps ports and I no longer get such errors in pfsense logs. I will try to understand why it looks like it is working fine now.


Log in to reply