[lgkahn]

its not trying to get the client specific options so i can get the iroute located from the correct location.. see attachments.. any ideas.

[eibgrad]

If you have JFFS enabled, the OpenVPN server looks in /jffs/etc/openvpn/ccd for client-specific files, NOT /tmp/openvpn/ccd.

Also, it appears you have other issues. The syslog indicates the server is configured w/ auth=sha256, while the client is using the default (sha1). The client and server will never be able to communicate until they match.

[egc]

Basically it is like @eibgrad said

Without permanent storage DDWRT will by default look into /tmp/openvpn/ccd/

Of course the files will be gone after reboot (but you can create small files at startup)

By default the common name is used so the name of the file has to be the same as the common name of the client (usually the keys/certs files are named with the common name)

You cannot allow duplicates so you have to disable "Allow Duplicate Clients" unless you are using username/passwords then you set "username-as-common-name" and use the username as name of the CCD file.

The OpenVPN server setup guide might shed some light on this, also on the other points which are mentioned by @eibgrad
https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1157343#1157343

[lgkahn]

not true. connection and vpn is working fine.. i can see the entire server network 1o2.168.11.0
from my client..

and i as shown above have put the correct lgk.com (client name) in the /tmp/openvpn/ccd directory as shown in the screen shot..

[lgkahn]

ok thanks.. copied clkient config to jffs/etc/...

but still does not appear to be reading from there?

[lgkahn]

also got rid of the warnings.. but they were only warnings.. the vpn was still working fine.

added
auth SHA256
cipher AES-128-CBC

to my clients

[eibgrad]

Looks to me like it *is* picking up the iroute. You posted a snapshot of the syslog rather than the actual syslog, so it makes it harder to point it out. But there is a line @ 17:22:19 (second to last line at that time) where the server has learned the internal route 192.168.2.0/24 and associated it w/ the client.