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

New Release: V23 beta 10.07.2005 Bug Reports Here!

Discussion in 'DD-WRT Firmware' started by Cyberian75, Oct 7, 2005.

  1. Cyberian75

    Cyberian75 Network Guru Member

    07.10.2005:
    progressive port forwarding added (gui)
    progressive port triggering added (gui)
    mixed readded for client mode
    some internal kernel changes (will be used in future)
    new pptpd version
    new dropbear version
    [hr:51d352a610]
    "Progressive forwarding/triggering" is an innovative idea/capability! :thumbup:

    V23 Build 07.10.2005
     
  2. zyclone

    zyclone Network Guru Member

    wooo,
    progressive port forwarding & triggering, excellent !

    thanks, great job !

    :D
     
  3. bigjohns

    bigjohns Network Guru Member

    what is progressive forwarding and triggering?
     
  4. Honki

    Honki Network Guru Member

    SCP/SSH is not working on Beta 7.10.2005
     
  5. BrainSlayer

    BrainSlayer Network Guru Member

    progressive means that you dont have a huge port forwarding/triggering list anymore, but a add/remove button where you can add new fields
     
  6. Cyberian75

    Cyberian75 Network Guru Member

    BrainSlayer, could you make DHCP Client List work even when "DNSMasq for DHCP" is enabled before you add anything else???
     
  7. BrainSlayer

    BrainSlayer Network Guru Member

    sure. but this takes a little bit time. its planed
     
  8. Cyberian75

    Cyberian75 Network Guru Member

    :thumbup:
     
  9. jagboy

    jagboy Network Guru Member

    got a link
     
  10. jagboy

    jagboy Network Guru Member

    found it
     
  11. BrainSlayer

    BrainSlayer Network Guru Member

    i'm confused
     
  12. jagboy

    jagboy Network Guru Member

    just needed a link for the newest firmware release. but i got it now.
     
  13. BrainSlayer

    BrainSlayer Network Guru Member

    always on www.dd-wrt.com->downloads
     
  14. jagboy

    jagboy Network Guru Member

    any new feautres going to be added??
     
  15. BrainSlayer

    BrainSlayer Network Guru Member

    the progressive port forwardings and trigger tables from today was only the first change of many in the next days
     
  16. dellsweig

    dellsweig Network Guru Member

    Brainslayer

    Have you made any progress on the config save/restore issues ??
     
  17. BrainSlayer

    BrainSlayer Network Guru Member

    sure. it still works here (with http, with https it crashes too)
     
  18. dellsweig

    dellsweig Network Guru Member

    Might we see a fix for this any time soon?? New features are cool but being able to upgrade in place - and re-loading configs is a nice thing to have working
     
  19. BrainSlayer

    BrainSlayer Network Guru Member

    for https? i need possibly to rework the whole ssl stuff for it. not a good job. i'm afraid
     
  20. dellsweig

    dellsweig Network Guru Member

    Is https what is causing the problem?? I can disable that if you will tell me I can save configs..

    Also, have you been able to re-create the issue with logging stopping after JFF enable (or config save)
     
  21. dellsweig

    dellsweig Network Guru Member

    I just upgraded to the 10/7 build.

    No problems at all - EXCEPT, as in previous releases, logging no longer works.

    I have not done the hard-reset yet - I was hoping I would not have to. Everything else works fine.

    I wish this bug would be found. I use the syslog data and need it to work.
     
  22. BrainSlayer

    BrainSlayer Network Guru Member

    i fixed a logging issue this evening but this time the release was already out
     
  23. dellsweig

    dellsweig Network Guru Member

    You ARE Da'Man

    I know - I am a PIA - but do we have to wait till Monday??
     
  24. 4Access

    4Access Network Guru Member

    Just upgraded to the 10/7 std build on a GSv2 and the ssh bug reported earlier still exists. BrainSlayer, are you able to recreate this? (BTW, I had the option to reset to firmware defaults enabled when I updated.)

    Also, I'm happy to see the progressive port forwarding! Nice! :thumb:

    Update: The problem actually seems to be worse than previously described. I can't get ssh to work AT ALL in the 10/7 build! :? When I log in via telnet and run ps I see the following process:
    dropbearkey -t rsa -f /tmp/root/.ssh/ssh_host_rsa_key
    Even after waiting more than 5 minutes it's still there and ssh can't be connected to. I tried holding the reset button in for 30 sec and then reconfiguring but ran into the same issue... Does anybody have ssh working in the 10/7 build after resetting to defaults?
     
  25. jagboy

    jagboy Network Guru Member

    4Access
    try "nvram:erase;reboot"
     
  26. Cellsplicer

    Cellsplicer Network Guru Member

    V23 beta 10-07-05 and nvram

    Has anyone had issues writing stuff to the nvram? I have tried to change settings directly using 'nvram set', and committing but as I reboot the old setting remains..eg. I've tried to set clkfreq to 300 but it remains at 216 when I reboot.

    Also, is WPA still broken? I cannot seem to get it to work.
     
  27. Toxic

    Toxic Administrator Staff Member

    setting the clk freq to 300 will fry your router.

    I would suggest you first reset the router. do this by pressing the reset button for 30 seconds.
     
  28. 4Access

    4Access Network Guru Member

    When I entered the command "nvram:erase;reboot" (without quotes) the router rebooted but all my configuration settings were still in place (it didn't reset to defaults) and the problem persisted.

    So I decided to try simply entering "nvram:erase" (again without quotes) & got an error... jagboy are you sure that's a valid command? I've noticed in the past you've recommended different variations of the nvram erase command:

    "nvram erase;reboot"
    "nvramerase:reboot "
    Several occurances of "mtd erase nvram"
    And even a "cat /dev/zero >/dev/mtd/3"

    I tried all of the above commands most followed with a "nvram commit" then a reboot, and while most seemed to execute without error, surprisingly none of them reset my router to its default settings, much less had any affect on the problem I described above... (Note that holding the reset button for 30 sec DOES reset my router to default settings...)
    :|

    BTW, thanks for the reply, any other suggestions? (Oh and is ssh working for you after resetting to defaults? Or anyone else for that matter?)

    Update: Based on Cellsplicer's post above (which was originally a differenet thread but got merged in here after I posted this message) I'd say it appears there may be a problem with writing to nvram in the 10/7 build...

    Update 2: Opps, I just noticed this thread where BrainSlayer confirmed ssh isn't working in the 10/7 build. Sorry for posting a bug report for a known issue. I tend to bookmark the threads (like this one) for the latest build and sometimes forget to check for other threads before posing bugs here. I'll try to watch out for that in the future but hopefully that won't be such an issue anymore thanks to the new rules ;)
     
  29. Cellsplicer

    Cellsplicer Network Guru Member

    I have been running on 300MHz for around 3 months now, on prior DD-WRT firmware; no signs of anything dying yet :grin: I have a WRT54G v3.1.

    I did reset my router to default settings after flashing, but I still get this strange issue; nothing is saved when I commit to nvram.
     
  30. et00l

    et00l Guest

    I keep getting a failure when I try to upgrade the firmware. I am using the latest Linksys firmware on a 1.1 model.

    Not sure what I did but I got it to finally flash after about 5 or 6 times.
     
  31. zyclone

    zyclone Network Guru Member

    port forwarding no more works
    in the "Protocol" block , I can't choose tcp, when I hit save , it always switch back to udp,
    I telnet the router and tried :

    ~ # nvram show | grep forward
    forward_entries=1
    forward_port=identd:eek:n:tcp:113:113>192.168.0.100

    It must only be a typo problem on the http admin page, but anyway it don't forward

    I tried to add more rules ; 3 to be exact.
    in the http admin page , if I switch off the 2 first rules , when I hit save , all the switches are showing TCP

    I telnet the router :
    ~ # nvram show | grep forward
    forward_entries=3
    forward_port=identd:eek:ff:udp:113:1132>192.168.0.100
    test1:eek:ff:udp:10000:10000>192.168.0.100
    test2:eek:n:udp:15000:15000>192.168.0.100

    if I reenable the 2 first rules , all the protocol indicators turn back to udp.
    with telnet , I can see the protocol have changed too !!

    ~ # nvram show | grep forward
    forward_entries=3
    forward_port=identd:eek:n:tcp:113:113>192.168.0.100
    test1:eek:n:tcp:10000:10000>192.168.0.100
    test2:eek:n:tcp:15000:15000>192.168.0.100

    .
    strange
     
  32. jagboy

    jagboy Network Guru Member

    4Access, what happens when you try to reset the router from the gui?
     
  33. skipparoo

    skipparoo Network Guru Member

    SSH is definitely broken, but it was updated to the latest version so I'm grateful for that.

    However, https is still being enabled when you enable ssh from the gui and I can't seem to disable it. I tried killing the process and setting the nvram httpsd_enable variable to 0 but this doesn't seem to work, on every reboot https will be running again.
     
  34. kingdaveone

    kingdaveone Network Guru Member

    Hi evereyone,
    i have a problem with the dhcp, after one or two days i have no ip when i try to connect my laptop, i need to unplug the electricity wire.
    After it works again.

    Any solutions ?

    Thank you
     
  35. Hackman

    Hackman Network Guru Member

    i had the same problem.you must enable "Use DNSMasq for DHCP"
     
  36. kingdaveone

    kingdaveone Network Guru Member

    Hi thanks for the answer i ll try it now.
     
  37. il_mostro

    il_mostro Network Guru Member

    I had this problem too with 260905-v23-beta1. After ~1 day none of my computers got any lease from the router. Logging in to the router showed that udhcpd had crashed. After that I switched to using DNS-masq instead and my router worked without DHCP problems for 11 days, when I rebooted due to an upgrade to 061005-v23-beta1.
     

Share This Page