I admit, I am lazy, as I could learn enough to write the script manually instead of recording it. I use an IPCop Linux router, whose web interface does not run on a standard port, it's https on port 443. How can I record a Reconnect despite that? Or is anyone else here using IPCop and can post the script here?

oops, wrong section, sorry. Mods, please feel free to move. Thanks!

OK, now I have figured it out how to let IPCop do a reconnect:

Copy the following script as /root/reconnect.sh to your IPCop machine:

#!/bin/bash

if [ ! -z "`ps -eaf | grep updatered | grep -v grep`" ]; then
    # IPCop macht gerade einen reconnect
    /usr/bin/logger -t ipcop "reconnect.sh: rc.updatered is running.
Exit."
    exit
fi

/usr/bin/logger -t ipcop "reconnect.sh: Starting reconnect"

/etc/rc.d/rc.red stop

while [ -e "/var/ipcop/red/active" -o -e "/var/run/ppp-ipcop.pid" ]; do
    /bin/sleep 1
done

/etc/rc.d/rc.red start

/usr/bin/logger -t ipcop "reconnect.sh: Reconnect finished."

Make the script executable with:

chmod +x reconnect.sh

Then, if your run Windows, use plink.exe from the PuTTY suite to execute the script on IPCop:

plink.exe -ssh -P 222 -pw $ROOTPASSWORT root@ipcophostname ~/reconnect.sh

If you don't want to have your root password written in clear text somewhere else than your brain, you'll have to configure sshd on the IPCop to RSA authentication. The key gets stored in Pageant, and you'll have to type in it's passphrase once at each startup (you could leave the passphrase empty).

In JD, go to the "Batch" tab under "Reconnection". Put "cmd /C" in the interpreter field, and the above plink command line is the batch script. In the advanced options, set the "first IP check wait time" to 10-15 sec., and reduce the "max. retries" to 2 or 3.

It is not 100% reliable (yet), sometimes the reconnect fails. I will post again if I can find some settings that bring improvement.