Brainslayer's checkin comment for changeset 19277 was "usually solves sha1 problem". Unfortunately, it didn't solve the problem this time.
It did change the symptoms, though. With 19215, I got this error:
Authenticate/Decrypt packet error: packet HMAC authentication failed
TLS Error: incoming packet authentication failed from x.x.x.x:44715
With 19277, I get this:
TLS_ERROR: BIO read tls_read_plaintext error:error:1408F119:lib(20):func(143):reason(281)
TLS Error: TLS object -> incoming plaintext read error
TLS Error: TLS handshake failed
my workaround for openssl by using "auth sha256" is not working anymore.
removing the auth statements from both server and client config files so the orginal config is restored, makes openvpn working again.
Well, a recent unmodified build apparently works for Sash (with some unknown configuration on a Nanostation M2), so he's closed the bug on the DD-WRT tracker again. I don't think he'll work on it any more unless he sees the bug himself, or at least hears from someone who's experiencing the bug with an unmodified (non-Kong) build.
I'd be happy to try an unmodified build, but I can't find one for the E4200 that's recent enough; the latest I can find is Brainslayer's build 18777 from mid-March:
ftp://dd-wrt.com/others/eko/BrainSlayer-V24-preSP2/2012/03-19-12-r18777/broadcom_K26/
Can anyone point me to an unmodified 19277-or-later build with VPN for the E4200?
I'm using an E3000, and the most resent version I've been able to get working is 18946.
Can anyone share there general experience with this new build (disregarding the OpenVPN issues).
I didn't play with it for long, but all the features I use (except VPN) worked fine. Samba performance seemed faster, but that might just have been wishful thinking on my part.
Again, though, I didn't play with it for long; I need the VPN functionality, so I only used build 19277 for an hour or so before going back to build 18730.
Hi running 19277m on a wrt610n v4. noticed that on rebot I lose WL1 (eth1) completely, doesn't even show up as a configuration item in the console. I had to restore from a backup configuration to get it back, tried telnet and various wl commands in the hope I could inject something into the startup script but that didn't work either. is it just me?
debiansid said: when the new version will be released?thanks
A new build was just released

RSS
