Hello,

I can't wait anymore to get my DSL-G624T fully working, and I have but only one last try. I need to make a build that will reliably serve me for the next 4 months. Problems with latest SVN ( I didn't try 2.6.24 but it seems even more unstable than recent 2.6.23 revisions ) are the following : router always crash after one day or two of use, QoS isn't working anymore because tc segfaults since the iproute2 update, and shadow passwords don't work ( I can live without them but they are very welcome if working on some revision ). Does anyone has an old revision which has all of the above fixed + working wireless ?

These problems with the current trunk, have you filed any bug reports? If a problem is not known about, then it cannot be solved.

Hi nabcore,

Here they are:
tc -> https://dev.openwrt.org/ticket/3026
AR7 unstability -> https://dev.openwrt.org/ticket/3019
shadow passwords -> https://dev.openwrt.org/ticket/2887

Ok, Thank you. I'm using r10156 at the moment. This is really stable for me: ADSL is fine and so is ethernet. The acx (not acx-mac80211) wireless drivers work(ish). I'm not sure on the status of iproute2/tc or shadow passwords under this snapshot.

As for current trunk, I really don't have a clue anymore. For me, the Ethernet seems to have stopped working with the recent 2.6.24 update: https://dev.openwrt.org/ticket/3124

Mine is r10365, and it is unstable

(Last edited by Cyberlullaby on 16 Feb 2008, 09:36)

Seems on the right track . I reverted back to r9234, the last 2.6.12 revision I had used some time ago and the last revision that was perfectly stable for me if I remember correctly (but no wireless nor shadow passwords).

I'm using r10417, last before changing kernel version to 2.6.24. After this version mac80211 doesn't compile (it's disabled as well).
Stable, but acx-mac80211 in AP mode is still unusable (ssid isn't visible, neither without ap scan wpa_supplicant finds ap)

But how stable is it ?

As far as I remember the first 2.6.23 revisions were very unstable for everyone, crashing every 30mins or so, and then the big issue was fixed but remained less unbeareable but still bad unstability for some devices..