[tedm]

I have a 3 node SSH VPN with a single "server" and 2 "clients" setup per the instructions here:

http://www.dd-wrt.com/wiki/index.php/VPN_%28the_easy_way%29_v24%2B

This works fine on builds up through 15508

Upgrading to a newer build on the client and I get a bunch of error complaints on the server about the client connection failing.

Upgrading to a newer build on the server and openvpn won't even start on boot. I get this error in syslog:

May 25 01:06:33 DD-WRT daemon.notice openvpn[652]: OpenVPN 2.2.0 mipsel-linux [SSL] [LZO2] [EPOLL] built on May 17 2011
May 25 01:06:33 DD-WRT daemon.notice openvpn[652]: MANAGEMENT: TCP Socket listening on 127.0.0.1:5001
May 25 01:06:33 DD-WRT daemon.warn openvpn[652]: IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA. OpenVPN 2.0-beta16 and earlier used 5000 as the default port.
May 25 01:06:33 DD-WRT daemon.warn openvpn[652]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
May 25 01:06:33 DD-WRT daemon.notice openvpn[652]: Diffie-Hellman initialized with 1024 bit key
May 25 01:06:33 DD-WRT daemon.warn openvpn[652]: WARNING: file '/tmp/openvpn/key.pem' is group or others accessible
May 25 01:06:33 DD-WRT daemon.notice openvpn[652]: TLS-Auth MTU parms [ L:1541 D:138 EF:38 EB:0 ET:0 EL:0 ]
May 25 01:06:33 DD-WRT daemon.notice openvpn[652]: Socket Buffers: R=[32767->65534] S=[32767->65534]
May 25 01:06:33 DD-WRT daemon.notice openvpn[652]: TUN/TAP device tun0 opened
May 25 01:06:33 DD-WRT daemon.notice openvpn[652]: TUN/TAP TX queue length set to 100
May 25 01:06:33 DD-WRT daemon.notice openvpn[652]: /sbin/ifconfig tun0 10.0.20.1 pointopoint 10.0.20.2 mtu 1500
May 25 01:06:33 DD-WRT daemon.notice openvpn[652]: /tmp/openvpn/route-up.sh tun0 1500 1541 10.0.20.1 10.0.20.2 init
May 25 01:06:33 DD-WRT daemon.warn openvpn[652]: WARNING: External program may not be called unless '--script-security 2' or higher is enabled. Use '--script-security 3 system' for backward compatibility with 2.1_rc8 and earlier. See --help text or man page for detail
May 25 01:06:33 DD-WRT daemon.err openvpn[652]: WARNING: Failed running command (--up/--down): external program fork failed
May 25 01:06:33 DD-WRT daemon.notice openvpn[652]: Exiting

[mrg666]

I have tested 17084 build on WNR3500L (my gateway router). Wireless was erratic but I did not test long-term stability. As others also said, DDNS is not working. Other than these, firewall port forward and access restrictions worked fine. I don't use wireless on the gateway but DDNS is a must for me. So I went back to Kong mod 16830.

[somms]

[greedj]

[jpl327]

Tested on a WNDR 3300 v1. Wireless speeds were poor. Also experienced the same issue as FarmerBob with the wired port only lighting up amber, this led is always green with other builds. I have reverted back to DD-WRT v24-sp2 (03/10/11) std-nokaid-nohot-nostore - build 16403M. I'll stick with that build until these problems are resolved.

[Vaako]

Wireless is horrible and DDNS is not working.
When can we expect a new build with this all fixed?

[somms]

[mrg666]

[eline]

True,
Wireless speed is very bad & unstable.
Wireless signal sweeps from 20 to 55%;
speed goes down to a very poor 26mbps.
Went back to stock firmware.
I know, not that good but better than 17084.
I leave the extra's for whar they are for the moment.
Stock firmware gives now better connection at lower power.
My device: e3000; wireless router.
('wireless' is a very important thing for a 'wireless' router... )

[somms]

[quote="mrg666"][quote="somms"][quote="greedj"]

[latinpapie]

[oxygenx]

I'm using NEWD_std-nokaid_nohotspot_nostor.bin on my WNDR3300's since yesterday and everything is fine so far.

no problems with wireless speed nor did i notice a change to the displayed SNR.

dyndns.org update is also working flawless.

[brackb01]

upgrade to 17084 big on a wrt610n v2 - couldn't see USB HDD on Samba, just on ftp. so reverted to 16773.

also noted on 16773 that the commands i was using on a previous version of eko arent working from the gui, but do through telnet:

/sbin/insmod /lib/modules/2.6.24.111/kernel/fs/fuse.ko
/usr/sbin/ntfs-3g /dev/discs/disc0/part2 /mnt/NTFS

didn't get to test on 17084

[can't flash]

Upon upgrading to EKO 17084, I noticed that the wireless LED on my E3000 will remain on at boot despite the fact that I have wireless set to off during boot. Status page confirms that radio is off; however, light remains on. This did not occur with build SVN: 16403.

[Comment about profile update removed by user]

[ragit]

no wireless on wrt350n.