[vtphilk]

Anyone know how/where the route-up.sh gets created and run from?

The stupid thing keeps launching the default /tmp/openvpn/route-up.sh /route-down.sh scripts which has masq nat in them! I tried writting a rc_startup script to change the route-up.sh and down but no luck.


~# nvram get rc_startup
(sleep 10; cp /etc/openvpn/route-down.sh /tmp/openvpn/route-down.sh;
cp /etc/openvpn/route-up.sh /tmp/openvpn/route-up.sh ) &



/etc/openvpn is the route-up.sh i built in using the firmware mod kit.

I want to be able to use the startup methods of the standard openvpn client but just need it to us my route-up/down which is located in /etc/openvpn.

Is there any way to do this or do I have to create my own process startup/monitoring to get the openvpn to start with the --route-up /etc/openvpn/route-up.sh rather --route-up /tmp/openvpn/route-up.sh like it does.

It seems everytime the openvpn service is stop/started it re-writes the /tmp/openvpn/route-up.sh and route-down.sh files from some magical location :)

Thanks

[vtphilk]

bump... anyone have any idea where this is set?

[Brainscanner]

If you still have that problem take a look here: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=6465

[portsup]

You can use the "up" command to load a script to overwrite the files in /tmp/openvpncl.

for example

place this without "" in the additional config of the services/vpn tab

"up /jffs/scriptname.sh"


in the script you have

"
#!/bin/sh
cp -a /jffs/openvpncl/* /tmp/openvpncl/
"

which writes over /tmp/openvpncl/ with anything in /jffs/openvpncl/

From memory you need to use jffs as other mounts don't load early enough.

[Eleanor Richards]