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

v23 (9/21) bugs

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

  1. Cyberian75

    Cyberian75 Network Guru Member

    1. "Use DNSMasq for DHCP" checkbox still isn't working
    2. HTTPd crashes occasionally
    3. The headers in FilterSummary.asp are misaligned
    4. Services in QOSServices.asp aren't selectable

    That's all for now.
     
  2. Maugus

    Maugus Network Guru Member

    Rebooting on a V2 !
     
  3. BrainSlayer

    BrainSlayer Network Guru Member

    hold the reset button and plugin power at the same time. then wait 5 minutes. it does normally 1 - 3 reboots from a clean linksys fw update. i tried it today on a brand new router out from store
    i added a serial adapter and flashed the firmware to debug this issue. i found out that it hangs on a reboot procedure. i fixed the problem in the 210905 fw from today (i guess) and checked it again on this router and it worked.
    don't give up so fast. i know its sometimes problematic, but i'm thankfull for every tester. the speed of finding bugs is very high currently and i want to get it stable so fast i can.
     
  4. dellsweig

    dellsweig Network Guru Member

    Brainslayer

    I just flashed the 9/21 onto a WORKING 9/20 load.

    I had logging working on the 9/20 by NOT doing a config backup.

    I loaded the 9/21 and logging NO LONGER WORKS

    I am hesitant to do a hard reset and re-enter everything again

    PLEASE TRY TO FIND THIS BUG
     
  5. BrainSlayer

    BrainSlayer Network Guru Member

    i was talking about a different one (hanging after flashing)
     
  6. Cyberian75

    Cyberian75 Network Guru Member

    I can confirm that UPnP is not functional.
     
  7. dellsweig

    dellsweig Network Guru Member

    I know....

    Just asking please - it looks like nvram is getting clobbered when you either flash or do a config backup

    I would hope to keep logging working between daily releases....
     
  8. BrainSlayer

    BrainSlayer Network Guru Member

    the 2109 version is broken. i deleted it. i found the problem which was caused by a big misstake by me. dont play around with it. it will start a reboot loop if you change some specific settings
     
  9. daenigma

    daenigma Network Guru Member


    Same problems for me although I have reported #4 since the last Alpha...

    Also add the problem with the UPnP I spoke of previously http://www.linksysinfo.org/modules.php?name=Forums&file=viewtopic&t=6659&start=680


    But I do want to say thank you to BrainSlayer! Even though there are problems the firmware is wonderful and I am sure we will get most of the problems worked out before the final release... This is after all a beta!
     
  10. dellsweig

    dellsweig Network Guru Member

    GREAT

    What should I not do?? I am running the 9/21 build
     
  11. Cyberian75

    Cyberian75 Network Guru Member

    I just tried the "top" command to see the running services, and I do see that UPnP is running; however, Azureus and My Network Places fail to "see" it.
     
  12. devil-strike

    devil-strike Network Guru Member

    Here the same Upnp is seeing by windows , but the router accept no changes from windows.
     
  13. dellsweig

    dellsweig Network Guru Member

    Greetings

    I see there is an 9/22 build of V23 out on the server.

    The release notes are basically the same as for the build yanked yesterday.

    Before I DL it, were any of the nvram issues (relating to iptables, logging, backups) addressed in this build??
     
  14. Cyberian75

    Cyberian75 Network Guru Member

    Here's what 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 -/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:
    HTTP/1.1 200 OK
    ST:upnp:rootdevice
    USN:uuid:0013-1036-3a72007a81b4::upnp:rootdevice
    Location: http://192.168.1.1:5431/dyndev/uuid:0013-1036-3a72007a81b4
    Server: Custom/1.0 UPnP/1.0 Proc/Ver
    EXT:
    Cache-Control:max-age=1800
    DATE: Thu, 22 Sep 2005 12:00:15 GMT
    
    
    UPnP: root discovered = http://192.168.1.1:5431/dyndev/uuid:0013-1036-3a72007a81b4, local = /192.168.1.10
      Downloading: http://192.168.1.1:5431/dyndev/uuid:0013-1036-3a72007a81b4
    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-3a72007a81b4/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-3a72017a81b4/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-3a72027a81b4/WANIPConnection:1
          desc=http://192.168.1.1:5431/dynsvc/WANPPPConnection:1.xml, control=http://192.168.1.1:5431/uuid:0013-1036-3a72027a81b4/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
    com.aelitis.net.upnp.UPnPException: Invoke of 'urn:schemas-upnp-org:service:WANIPConnection:1#AddPortMapping' fails: Connection refused: connect
    com.aelitis.net.upnp.UPnPException: Invoke of 'urn:schemas-upnp-org:service:WANIPConnection:1#AddPortMapping' fails: Connection refused: connect
    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
    
     
  15. TheMunch8

    TheMunch8 Network Guru Member

    Im getting the same problem with UPnP. it is on until Azureus turns on, then UPnP disappears, and doesn't seem to be working. any word on this?
     
  16. Cyberian75

    Cyberian75 Network Guru Member

    BrainSlayer is refusing even to look into this issue saying that he didn't touch UPnP part of this firmware and to contact Linksys about it. Oh, well.

    One workaround is to reboot the router via telnet AFTER starting Azureus. I've found this to work at least temporarily. It appears that Azureus crashes the UPnP process for some reason.
     
  17. aaaaaa

    aaaaaa Network Guru Member

    While he didn't touch UPnP, it looks like he did move to a new version of iptables (more specifically, libipt) between v22r2--where UPnP worked--and v23--where it doesn't. I'm pretty sure it is the new version of libipt that is causing problems. If Brainslayer isn't going to look at this, then I'll try to get a build environment up again (used to compile Sveasoft some) and do it myself.
     
  18. Cyberian75

    Cyberian75 Network Guru Member

    Why don't you speak to him on the messenger yourself???
     

Share This Page