1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

UPnP Comparison

Discussion in 'DD-WRT Firmware' started by Cyberian75, Sep 24, 2005.

  1. Cyberian75

    Cyberian75 Network Guru Member

    With the UPnPTest, I tested DD-WRT versions 22 prefinal5 and the latest beta.

    With Ver. 23 beta, I got the following:

    Code:
    TEST 1 - Operating System Support - PASSED
    TEST 2 - SSDP Service Running Check - PASSED
    TEST 3 - SSDP Service Automatic Check - PASSED
    TEST 4 - UPnPHost Service Running Check - PASSED
    TEST 5 - UPnPHost Service Automatic Check - PASSED
    TEST 6 - UPnP Framework Firewall Exception Check - FAILED
    TEST 7 - Adapter #0 - 192.168.1.11 - FAILED
    TEST 8 - Get External IP Address - FAILED
    
    ... while Ver. 22 passed all but #6 test mainly because I have disabled Windows Firewall.

    Also, Azureus reports no problem with Ver. 22:
    Code:
    UPnP::SSDP: ignoring loopback address /127.0.0.1
    UPnP::SSDP: ignoring loopback address /0:0:0:0:0:0:0:1
    UPnP::SSDP: ignoring IPv6 address /fe80:0:0:0:0:0:0:1%1
    UPnP::SSDP: group = /239.255.255.250:0/eth0:3Com 3C905TX-based Ethernet Adapter (Generic) #2 - Packet Scheduler Miniport-/192.168.1.100,/fe80:0:0:0:260:8ff:fece:338b%6: started
    UPnP::SSDP: ignoring IPv6 address /fe80:0:0:0:260:8ff:fece:338b%6
    UPnP::SSDP: ignoring IPv6 address /fe80:0:0:0:0:5445:5245:444f%5
    UPnP::SSDP: ignoring IPv6 address /fe80:0:0:0:0:5efe:c0a8:164%2
    Mapping request: UDP tracker client port (UDP/60000), enabled = true
    Mapping request: Incoming Peer Data Port (TCP/60000), enabled = true
    Mapping request: TCP Tracker Port (TCP/60001), enabled = false
    Mapping request: TCP SSL Tracker Port (TCP/0), enabled = false
    Mapping request: UDP Tracker Port (UDP/60001), enabled = true
    Mapping request: Distributed DB (UDP/60000), enabled = true
    UPnP:SSDP: first response:
    HTTP/1.1 200 OK
    ST:upnp:rootdevice
    USN:uuid:0013-1036-3a72001b44b0::upnp:rootdevice
    Location: http://192.168.1.1:5431/dyndev/uuid:0013-1036-3a72001b44b0
    Server: Custom/1.0 UPnP/1.0 Proc/Ver
    EXT:
    Cache-Control:max-age=1800
    DATE: Fri, 23 Sep 2005 16:12:46 GMT
    
    
    UPnP: root discovered = http://192.168.1.1:5431/dyndev/uuid:0013-1036-3a72001b44b0, local = /192.168.1.100
      Downloading: http://192.168.1.1:5431/dyndev/uuid:0013-1036-3a72001b44b0
    Relative URL base is unspecified
    Residential Gateway Device
      desc=http://192.168.1.1:5431/dynsvc/Layer3Forwarding:1.xml, control=http://192.168.1.1:5431/uuid:0013-1036-3a72001b44b0/Layer3Forwarding:1
      urn:schemas-upnp-org:device:WANDevice:1
        desc=http://192.168.1.1:5431/dynsvc/WANCommonInterfaceConfig:1.xml, control=http://192.168.1.1:5431/uuid:0013-1036-3a72011b44b0/WANCommonInterfaceConfig:1
        urn:schemas-upnp-org:device:WANConnectionDevice:1 *
          desc=http://192.168.1.1:5431/dynsvc/WANIPConnection:1.xml, control=http://192.168.1.1:5431/uuid:0013-1036-3a72021b44b0/WANIPConnection:1
          desc=http://192.168.1.1:5431/dynsvc/WANPPPConnection:1.xml, control=http://192.168.1.1:5431/uuid:0013-1036-3a72021b44b0/WANPPPConnection:1
      Downloading: http://192.168.1.1:5431/dynsvc/WANCommonInterfaceConfig:1.xml
    Device speed: down=11.9 MB/s, up=11.9 MB/s
        Found WANIPConnection
      Downloading: http://192.168.1.1:5431/dynsvc/WANIPConnection:1.xml
    UPnP: Mapping 'UDP tracker client port (UDP/60000)' established
    UPnP: Mapping 'Incoming Peer Data Port (TCP/60000)' established
    UPnP: Mapping 'UDP Tracker Port (UDP/60001)' established
    Mapping Distributed DB (UDP/60000) already established
        Found WANPPPConnection
      Downloading: http://192.168.1.1:5431/dynsvc/WANPPPConnection:1.xml
          mapping [0] 60000/UDP [Azureus UPnP 60000 UDP] -> 192.168.1.100
          mapping [1] 60000/TCP [Azureus UPnP 60000 TCP] -> 192.168.1.100
          mapping [2] 60001/UDP [Azureus UPnP 60001 UDP] -> 192.168.1.100
    Mapping UDP tracker client port (UDP/60000) already established
    Mapping Incoming Peer Data Port (TCP/60000) already established
    Mapping Incoming Peer Data Port (TCP/60000) already established
    Mapping UDP Tracker Port (UDP/60001) already established
    Mapping UDP Tracker Port (UDP/60001) already established
    
    However, the latest beta results in:
    Code:
    UPnP::SSDP: ignoring loopback address /127.0.0.1
    UPnP::SSDP: ignoring loopback address /0:0:0:0:0:0:0:1
    UPnP::SSDP: ignoring IPv6 address /fe80:0:0:0:0:0:0:1%1
    UPnP::SSDP: group = /239.255.255.250:0/eth0:3Com 3C905TX-based Ethernet Adapter (Generic) #2 - Packet Scheduler Miniport-/192.168.1.10,/fe80:0:0:0:260:8ff:fece:338b%4: started
    UPnP::SSDP: ignoring IPv6 address /fe80:0:0:0:260:8ff:fece:338b%4
    UPnP::SSDP: ignoring IPv6 address /fe80:0:0:0:0:5445:5245:444f%5
    UPnP::SSDP: ignoring IPv6 address /fe80:0:0:0:0:5efe:c0a8:10a%2
    Mapping request: UDP tracker client port (UDP/60000), enabled = true
    Mapping request: Incoming Peer Data Port (TCP/60000), enabled = true
    Mapping request: TCP Tracker Port (TCP/60001), enabled = false
    Mapping request: TCP SSL Tracker Port (TCP/0), enabled = false
    Mapping request: UDP Tracker Port (UDP/60001), enabled = true
    Mapping request: Distributed DB (UDP/60000), enabled = true
    UPnP:SSDP: first response:
    NOTIFY * HTTP/1.1 
    HOST: 239.255.255.250:1900
    CACHE-CONTROL: max-age=1800
    Location: http://192.168.1.1:5431/dyndev/uuid:0013-1036-3a7200473e84
    NT: uuid:0013-1036-3a7200473e84
    NTS: ssdp:alive
    SERVER:LINUX/2.4 UPnP/1.0 BRCM400/1.0
    USN: uuid:0013-1036-3a7200473e84
    
    
    UPnP: root discovered = http://192.168.1.1:5431/dyndev/uuid:0013-1036-3a7200473e84, local = /192.168.1.10
      Downloading: http://192.168.1.1:5431/dyndev/uuid:0013-1036-3a7200473e84
    Relative URL base is unspecified
    Residential Gateway Device
      desc=http://192.168.1.1:5431/dynsvc/Layer3Forwarding:1.xml, control=http://192.168.1.1:5431/uuid:0013-1036-3a7200473e84/Layer3Forwarding:1
      urn:schemas-upnp-org:device:WANDevice:1
        desc=http://192.168.1.1:5431/dynsvc/WANCommonInterfaceConfig:1.xml, control=http://192.168.1.1:5431/uuid:0013-1036-3a7201473e84/WANCommonInterfaceConfig:1
        urn:schemas-upnp-org:device:WANConnectionDevice:1 *
          desc=http://192.168.1.1:5431/dynsvc/WANIPConnection:1.xml, control=http://192.168.1.1:5431/uuid:0013-1036-3a7202473e84/WANIPConnection:1
          desc=http://192.168.1.1:5431/dynsvc/WANPPPConnection:1.xml, control=http://192.168.1.1:5431/uuid:0013-1036-3a7202473e84/WANPPPConnection:1
      Downloading: http://192.168.1.1:5431/dynsvc/WANCommonInterfaceConfig:1.xml
    Device speed: down=11.9 MB/s, up=11.9 MB/s
        Found WANIPConnection
      Downloading: http://192.168.1.1:5431/dynsvc/WANIPConnection:1.xml
    com.aelitis.net.upnp.UPnPException: Invoke of 'urn:schemas-upnp-org:service:WANIPConnection:1#AddPortMapping' fails: Connection refused: connect
    UPnP: Mapping 'UDP tracker client port (UDP/60000)' failed
    com.aelitis.net.upnp.UPnPException: Invoke of 'urn:schemas-upnp-org:service:WANIPConnection:1#AddPortMapping' fails: Connection refused: connect
    UPnP: Mapping 'Incoming Peer Data Port (TCP/60000)' failed
    com.aelitis.net.upnp.UPnPException: Invoke of 'urn:schemas-upnp-org:service:WANIPConnection:1#AddPortMapping' fails: Connection refused: connect
    UPnP: Mapping 'UDP Tracker Port (UDP/60001)' failed
    Mapping Distributed DB (UDP/60000) already established
        Found WANPPPConnection
      Downloading: http://192.168.1.1:5431/dynsvc/WANPPPConnection:1.xml
      attempt 2 of 3
      Downloading: http://192.168.1.1:5431/dynsvc/WANPPPConnection:1.xml
      attempt 3 of 3
      Downloading: http://192.168.1.1:5431/dynsvc/WANPPPConnection:1.xml
    org.gudy.azureus2.plugins.utils.resourcedownloader.ResourceDownloaderException: I/O Exception while downloading 'http://192.168.1.1:5431/dynsvc/WANPPPConnection:1.xml':java.net.ConnectException: Connection refused: connect
    org.gudy.azureus2.plugins.utils.resourcedownloader.ResourceDownloaderException: I/O Exception while downloading 'http://192.168.1.1:5431/dynsvc/WANPPPConnection:1.xml':java.net.ConnectException: Connection refused: connect
    com.aelitis.net.upnp.UPnPException: Root device location 'http://192.168.1.1:5431/dynsvc/WANPPPConnection:1.xml' - data read failed
    
    So, clearly, it's a problem with the firmware. According to this, it could be due to the lack of broadcasts of its UPnP capability.

    I hope this helps you somewhat to fix the glitch. :)
     
  2. Cyberian75

    Cyberian75 Network Guru Member

    SOMETHING fixed it temporarily.

    Code:
    UPnP: root discovered = http://192.168.1.1:5431/dyndev/uuid:0013-1036-3a7200141b44, local = /192.168.1.10
      Downloading: http://192.168.1.1:5431/dyndev/uuid:0013-1036-3a7200141b44
    Relative URL base is unspecified
    Residential Gateway Device
      desc=http://192.168.1.1:5431/dynsvc/Layer3Forwarding:1.xml, control=http://192.168.1.1:5431/uuid:0013-1036-3a7200141b44/Layer3Forwarding:1
      urn:schemas-upnp-org:device:WANDevice:1
        desc=http://192.168.1.1:5431/dynsvc/WANCommonInterfaceConfig:1.xml, control=http://192.168.1.1:5431/uuid:0013-1036-3a7201141b44/WANCommonInterfaceConfig:1
        urn:schemas-upnp-org:device:WANConnectionDevice:1 *
          desc=http://192.168.1.1:5431/dynsvc/WANIPConnection:1.xml, control=http://192.168.1.1:5431/uuid:0013-1036-3a7202141b44/WANIPConnection:1
          desc=http://192.168.1.1:5431/dynsvc/WANPPPConnection:1.xml, control=http://192.168.1.1:5431/uuid:0013-1036-3a7202141b44/WANPPPConnection:1
      Downloading: http://192.168.1.1:5431/dynsvc/WANCommonInterfaceConfig:1.xml
    Device speed: down=11.9 MB/s, up=11.9 MB/s
        Found WANIPConnection
      Downloading: http://192.168.1.1:5431/dynsvc/WANIPConnection:1.xml
          mapping [0] 60000/UDP [Azureus UPnP 60000 UDP] -> 192.168.1.10
          mapping [1] 60000/TCP [Azureus UPnP 60000 TCP] -> 192.168.1.10
          mapping [2] 60001/UDP [Azureus UPnP 60001 UDP] -> 192.168.1.10
    Mapping UDP tracker client port (UDP/60000) already established
    Mapping Incoming Peer Data Port (TCP/60000) already established
    Mapping UDP Tracker Port (UDP/60001) already established
        Found WANPPPConnection
      Downloading: http://192.168.1.1:5431/dynsvc/WANPPPConnection:1.xml
          mapping [0] 60000/UDP [Azureus UPnP 60000 UDP] -> 192.168.1.10
          mapping [1] 60000/TCP [Azureus UPnP 60000 TCP] -> 192.168.1.10
          mapping [2] 60001/UDP [Azureus UPnP 60001 UDP] -> 192.168.1.10
    Mapping UDP tracker client port (UDP/60000) already established
    Mapping Incoming Peer Data Port (TCP/60000) already established
    Mapping UDP Tracker Port (UDP/60001) already established
    
     
  3. HansGruber

    HansGruber Network Guru Member

    This is what I get when I run that app

    Code:
    TEST 1 - Operating System Support - PASSED
    TEST 2 - SSDP Service Running Check - PASSED
    TEST 3 - SSDP Service Automatic Check - FAILED
    TEST 4 - UPnPHost Service Running Check - FAILED
    TEST 5 - UPnPHost Service Automatic Check - FAILED
    TEST 6 - UPnP Framework Firewall Exception Check - PASSED
    TEST 7 - Adapter #0 - 192.168.1.101 - FAILED
    TEST 8 - Get External IP Address - FAILED
    
     
  4. Cyberian75

    Cyberian75 Network Guru Member

    Is anyone running v22 prefinal 5? If you are, please post the result from that utility.
     
  5. rtau

    rtau Network Guru Member

    I'm running v22 final with the following result:
    Code:
    TEST 1 - Operating System Support - PASSED
    TEST 2 - SSDP Service Running Check - PASSED
    TEST 3 - SSDP Service Automatic Check - PASSED
    TEST 4 - UPnPHost Service Running Check - PASSED
    TEST 5 - UPnPHost Service Automatic Check - PASSED
    TEST 6 - UPnP Framework Firewall Exception Check - FAILED
    TEST 7 - Adapter #0 - 192.168.0.100 - PASSED
    TEST 8 - Get External IP Address (Result: xxx.xxx.xxx.xxx) - PASSED
    
    The IP in the last test was masked with "xxx". The original one shows the correct IP.
     
  6. Cyberian75

    Cyberian75 Network Guru Member

    Thanks, rtau! :) This proves that it's indeed a bug in v23 beta.
     
  7. Janto

    Janto Network Guru Member

    uPnP test

    hi , i am running with ddwrt #22 final i get this:


    TEST 1 - Operating System Support - PASSED
    TEST 2 - SSDP Service Running Check - PASSED
    TEST 3 - SSDP Service Automatic Check - PASSED
    TEST 4 - UPnPHost Service Running Check - PASSED
    TEST 5 - UPnPHost Service Automatic Check - PASSED
    TEST 6 - UPnP Framework Firewall Exception Check - PASSED
    TEST 7 - Adapter #0 - 192.168.1.2 - FAILED
    TEST 8 - Get External IP Address - FAILED

    UPnP Test Program v1.14 Copyright Mark Gillespie 2005
    Bugs/Comments to: mark.gillespie@gmail.com



    uPnP is enabled in router...
     
  8. aaaaaa

    aaaaaa Network Guru Member

    Yeah, it's a bug.
    "~ # m->desc[Azureus UPnP 6881 UDP]
    Not MSN/Xbox message, commit (add)!
    nvram_commit(): start
    nvram_commit(): end
    ERROR: 1 not a valid target)"

    When a program (Azureus here) tries to map a port using UPnP, it causes the above error, and the upnp daemon crashes.

    BTW, I'm pretty sure the "ERROR: 1 not a valid target)" error message is from iptables. Perhaps the upnp daemon is not compatible with the version of iptables used in v23? I suggest adding some debugging code to upnp that will output the command it passes to iptables when it tries to set up a portmap. That should help you figure out what is going on with upnp...
     
  9. Cyberian75

    Cyberian75 Network Guru Member

    Re: uPnP test

    Is UPnP UI Component installed? Seeing that you passed test 6, it's likely that Windows Firewall is blocking your UPnP service.

    To install that component, click on "Show icons for networked UPnP devices" within My Network Places. This will add an exception to the Windows Firewall rule for UPnP services/devices.
     
  10. Cyberian75

    Cyberian75 Network Guru Member

    Try "upnp -W vlan1 -L br0" via telnet. This apparently helps temporarily.
     
  11. Cyberian75

    Cyberian75 Network Guru Member

    I see the main problem is that UPnP service crashes most of the time. I tried the "top" command when Azureus reports a problem, and sure enough, the UPnP service isn't listed as running. So the problem is not with UPnP itself but the "system" it runs on.
     
  12. Janto

    Janto Network Guru Member

    Re: uPnP test

    i checked and the ports are already open..
     
  13. aaaaaa

    aaaaaa Network Guru Member

    All that does is restart the upnp daemon. It does nothing to help the problem. The next time Azureus etc. attempts to map a port, upnp just crashes again.
     
  14. daenigma

    daenigma Network Guru Member

    What we need is a WRT54G & GS with the latest Linksys firmware installed to test if it also has this trouble...

    I am 100% sure that if BrainSlayer thought some of his programming has helped create the bug he would have fixed it. But he did state that the reason v23 seems to have the trouble is due to a problem with the original Linksys codebase he integrated into v23 where v22 did not have this new codebase.
     
  15. Cyberian75

    Cyberian75 Network Guru Member

    I've just tested Linksys stock filmware v4.70.6 on a WRT54GS v1.0 with no UPnP issues.

    UPnPTest reports:
    Code:
    TEST 1 - Operating System Support - PASSED
    TEST 2 - SSDP Service Running Check - PASSED
    TEST 3 - SSDP Service Automatic Check - PASSED
    TEST 4 - UPnPHost Service Running Check - PASSED
    TEST 5 - UPnPHost Service Automatic Check - PASSED
    TEST 6 - UPnP Framework Firewall Exception Check - FAILED
    TEST 7 - Adapter #0 - 192.168.1.100 - PASSED
    TEST 8 - Get External IP Address (Result: IP deleted) - PASSED
    
    Azureus reports:
    Code:
    UPnP::SSDP: ignoring loopback address /127.0.0.1
    UPnP::SSDP: ignoring loopback address /0:0:0:0:0:0:0:1
    UPnP::SSDP: ignoring IPv6 address /fe80:0:0:0:0:0:0:1%1
    UPnP::SSDP: group = /239.255.255.250:0/eth0:3Com 3C905TX-based Ethernet Adapter (Generic) #2 - Packet Scheduler Miniport-/192.168.1.100,/fe80:0:0:0:260:8ff:fece:338b%4: started
    UPnP::SSDP: ignoring IPv6 address /fe80:0:0:0:260:8ff:fece:338b%4
    UPnP::SSDP: ignoring IPv6 address /fe80:0:0:0:0:5445:5245:444f%5
    UPnP::SSDP: ignoring IPv6 address /fe80:0:0:0:0:5efe:c0a8:164%2
    Mapping request: UDP tracker client port (UDP/60000), enabled = true
    Mapping request: Incoming Peer Data Port (TCP/60000), enabled = true
    Mapping request: TCP Tracker Port (TCP/60001), enabled = false
    Mapping request: TCP SSL Tracker Port (TCP/0), enabled = false
    Mapping request: UDP Tracker Port (UDP/60001), enabled = true
    Mapping request: Distributed DB (UDP/60000), enabled = true
    UPnP:SSDP: first response:
    HTTP/1.1 200 OK
    ST:upnp:rootdevice
    USN:uuid:0013-1036-3a72000099dc::upnp:rootdevice
    Location: http://192.168.1.1:5431/dyndev/uuid:0013-1036-3a72000099dc
    Server: Custom/1.0 UPnP/1.0 Proc/Ver
    EXT:
    Cache-Control:max-age=180
    DATE: Sun, 25 Sep 2005 14:54:50 GMT
    
    
    UPnP: root discovered = http://192.168.1.1:5431/dyndev/uuid:0013-1036-3a72000099dc, local = /192.168.1.100
      Downloading: http://192.168.1.1:5431/dyndev/uuid:0013-1036-3a72000099dc
    Relative URL base is unspecified
    Residential Gateway Device
      desc=http://192.168.1.1:5431/dynsvc/Layer3Forwarding:1.xml, control=http://192.168.1.1:5431/uuid:0013-1036-3a72000099dc/Layer3Forwarding:1
      urn:schemas-upnp-org:device:WANDevice:1
        desc=http://192.168.1.1:5431/dynsvc/WANCommonInterfaceConfig:1.xml, control=http://192.168.1.1:5431/uuid:0013-1036-3a72010099dc/WANCommonInterfaceConfig:1
        urn:schemas-upnp-org:device:WANConnectionDevice:1 *
          desc=http://192.168.1.1:5431/dynsvc/WANIPConnection:1.xml, control=http://192.168.1.1:5431/uuid:0013-1036-3a72020099dc/WANIPConnection:1
          desc=http://192.168.1.1:5431/dynsvc/WANPPPConnection:1.xml, control=http://192.168.1.1:5431/uuid:0013-1036-3a72020099dc/WANPPPConnection:1
      Downloading: http://192.168.1.1:5431/dynsvc/WANCommonInterfaceConfig:1.xml
    Device speed: down=11.9 MB/s, up=11.9 MB/s
        Found WANIPConnection
      Downloading: http://192.168.1.1:5431/dynsvc/WANIPConnection:1.xml
    UPnP: Mapping 'UDP tracker client port (UDP/60000)' established
    UPnP: Mapping 'Incoming Peer Data Port (TCP/60000)' established
    UPnP: Mapping 'UDP Tracker Port (UDP/60001)' established
    Mapping Distributed DB (UDP/60000) already established
        Found WANPPPConnection
      Downloading: http://192.168.1.1:5431/dynsvc/WANPPPConnection:1.xml
          mapping [0] 60000/UDP [Azureus UPnP 60000 UDP] -> 192.168.1.100
          mapping [1] 60000/TCP [Azureus UPnP 60000 TCP] -> 192.168.1.100
          mapping [2] 60001/UDP [Azureus UPnP 60001 UDP] -> 192.168.1.100
    
    So, apparetly, it's a bug in DD-WRT v23.
     
  16. aaaaaa

    aaaaaa Network Guru Member

    As best I can tell from looking at the code in v22 versus v23, the bug in the upnp daemon is due to some sort of incompatibility with the newer version of libipt (the iptables API) used in v23. I haven't been able to isolate exactly what causes the problem yet because I don't have a build environment set up for dd-wrt yet.
     
  17. matthiaz

    matthiaz Network Guru Member

    @Cyberian75: STOP FUCKING WHINING!!! IT'S NOT WORKING RIGHT NOW.

    Go ahead and use stock linksys if you fucking need it. It's getting so damn annoying seeing you posting "UPNP is not working" on a hourly base.... I think Brainslayer might finally have seen this damn post...
     
  18. Cyberian75

    Cyberian75 Network Guru Member

    I'm just providing information to disprove what BrainSlayer has said. I'm complaining nor whining.

    Why are you getting so offensive even when BrainSlayer is not???
     
  19. whatsthedeal

    whatsthedeal Network Guru Member

    we all appreciate people reporting bugs or problems to brainslayer - but once is enough. thank you for your extensive test results - i'm sure brainslayer will/has find/found them useful.
     
  20. Cyberian75

    Cyberian75 Network Guru Member

    I just had a chat with him, and he said that it could be due to his build environment that's causing the crashes. And he was using the stock firmware version 4.60, not 4.70, so he will look into it tomorrow.
     
  21. TheMunch8

    TheMunch8 Network Guru Member

    YAY. I continue to use DD-WRT because of the dedication of Brainslayer and letting the community being involved in the development. I may not be able to write code to help, but I sure as hell find bugs. Hell, they seem to find me.

    (BTW, same problem with Azureus. We are all cheering you on Brainslayer!)
     
  22. Cyberian75

    Cyberian75 Network Guru Member

  23. Cyberian75

    Cyberian75 Network Guru Member

  24. TheMunch8

    TheMunch8 Network Guru Member

    well he aint trying to ban people for giving criticism :grin:

    And he is kinda right. It isn't his fault. He is probably just gunna wait till the other people fix their problem. He has other things to work on
     
  25. eenisweenis

    eenisweenis Network Guru Member

    The Sveasoft guys told me that you have to rewrite UPnP if you upgrade busybox and iptables. They said they did it for Talisman and Brainslayer has to do it if he upgraded Busybox or iptabales or something. Until he rewrites it UPnP is broken I guess.
     
  26. BrainSlayer

    BrainSlayer Network Guru Member

    lol. this is the best joke i ever heard
     
  27. eenisweenis

    eenisweenis Network Guru Member

    Does this mean UPnP works now?
     
  28. matthiaz

    matthiaz Network Guru Member

    What kind of fuck of are you, weenis? Having your first posts here and being already on top of every everything...

    Is sveasoft already so worrying about getting the $$$$$ to state stupid lies? Go the fuck away, bitch!
     
  29. BrainSlayer

    BrainSlayer Network Guru Member

    please, stop with flaming
     
  30. daenigma

    daenigma Network Guru Member

    I agree!

    We have some users who are very frustrated due to the UPnP issue and have probably gone about complaining in a rather annoying fashion but it is understandable... Also we need to understand that Brainslayer is probably just as frustrated about the issue and what we need to do is give Brainslayer some time to see if he can fix it...

    I have 100% faith in his skills to fix the problem and if he can not I am 100% sure someone in the community will but it will take time and until then port forwarding will have to do.
     
  31. bytes2000

    bytes2000 Network Guru Member

  32. whatsthedeal

    whatsthedeal Network Guru Member

Share This Page