UPnP not working



  • I'm currently running snap 20080713-2318.  I don't see any UPnP ports open even though BitTorrent and Messenger Live are both running and trying to use UPnP.  The UPnP service is running on pfSense.



  • upnp and Azureus seemed to work ok for me yesterday; if I get a chance I'll try it again and see if I can validate that it is indeed working.



  • I think it's more of a page layout problem. I think UPnP is actually working fine, just the status page isn't "readable". This can be seen in the attached image. You can see from the screenshot of my uTorrent, which uses UPnP, that it is working okay…

    Additionally you can see the rules/NAT have been created by UPnP

    # pfctl -a miniupnpd -sr
    pass in quick on ng0 inet proto tcp from any to any port = 54721 flags any keep state label "utorrent" rtable 0
    pass in quick on ng0 inet proto tcp from any to any port = 1249 flags any keep state label "MsnMsgr (<ip>:9049) 1249 TCP" rtable 0
    pass in quick on ng0 inet proto tcp from any to any port = 62501 flags any keep state label "utorrent" rtable 0
    pass in quick on ng0 inet proto udp from any to any port = 53491 keep state label "MsnMsgr (<ip>:12685) 53491 UDP" rtable 0
    pass in quick on ng0 inet proto tcp from any to any port = 19094 flags any keep state label "utorrent" rtable 0
    # pfctl -a miniupnpd -sn
    rdr pass on ng0 inet proto tcp from any to any port = 54721 label "utorrent" rtable 0 -> <ip> port 54721
    rdr pass on ng0 inet proto tcp from any to any port = 1249 label "MsnMsgr (<ip>:9049) 1249 TCP" rtable 0 -> <ip> port 9049
    rdr pass on ng0 inet proto tcp from any to any port = 62501 label "utorrent" rtable 0 -> <ip> port 62501
    rdr pass on ng0 inet proto udp from any to any port = 53491 label "MsnMsgr (<ip>:12685) 53491 UDP" rtable 0 -> <ip> port 12685
    rdr pass on ng0 inet proto tcp from any to any port = 19094 label "utorrent" rtable 0 -> <ip> port 19094</ip></ip></ip></ip></ip></ip></ip></ip></ip>
    

    Version: 1.2.1-TESTING-SNAPSHOT built on Sun Jul 13 23:18:23 EDT 2008
    (about to be updated…)






  • Confirming problem still exists in version: 1.2.1-TESTING-SNAPSHOT built on Wed Jul 16 02:31:27 EDT 2008



  • Problem also exists in 1.3

    This probably means it is probably a FreeBSD 7 changeover problem.

    We'll look into it.

    Update: Fixed in CVS



  • @databeestje:

    Update: Fixed in CVS

    Yes, appears to be fixed in 1.2.1-TESTING-SNAPSHOT-20080717-0408!! :D Thanks!!


Log in to reply