Can someone please explain how to properly configure the stunnel service so that it automatically starts after the router is rebooted? I'm running "Tomato Firmware v1.28.0495 MIPSR2-Toastman-RT-N K26 USB Ext" on a Cisco E3000. Here's what I did: Formatted a USB flash drive as ext2. It automounts as "/tmp/mnt/sda1". It must be mounted as "/opt" so I added the following lines (found on a blog) to "USB and NAS > USB Support > Run after mounting": #!/bin/shsleep 5umount -f /tmp/mnt/sda1mount -rw -o noatime,nodev /dev/sda1 /optNOTE: There's probably a cleaner way of doing this and I'm open to suggestions (something to do with fstab?). Installed "ipkg" as per the instructions in Tomato's Optware tutorial Used ipkg to install stunnel Modified "/opt/etc/stunnel/stunnel.conf" to redirect port 5000 to "smtp.gmail.com:465". The purpose is to allow simple email clients, that are incapable of handling Secure SMTP, to work with Gmail. client = yes[ssmtp]accept = 5000connect = smtp.gmail.com:465 I executed the supplied script "/opt/etc/init.d/S68stunnel" that kills existing stunnel processes and restarts stunnel. From the command prompt on a PC, I can "telnet <MyRouterIPaddress> 5000" and receive a response from Gmail's ESMTP server. Using a non-SSMTP-aware email client, configured to use <MyRouterIpAddress> on port 5000, it can send email using Gmail. Success! Here is what I noticed: Stunnel is not automatically started after the router is rebooted. What is the correct way of configuring stunnel so that it automatically runs as a daemon? After running "PS", I notice there are multiple stunnel processes (typically seven). Executing "/opt/etc/init.d/S68stunnel" kills all of them and creates a fresh batch of seven stunnel processes. Is this normal? Initially, stunnel refused to redirect the port (i.e. no response from Gmail on port 5000). Stopping/restarting/rebooting finally cleared the cobwebs. Can someone confirm that stunnel is stable and reliable on Tomato?