SS5 SOCKS Proxy: Difference between revisions

Line 20:

At a certain point one has to give up, but I didn't. Instead I changed strategies. I noticed the ss5 binary had a command line switch (-m) that turned logging off, so I modified the /etc/init.d/ss5 file, adding three -m switches in the "start section" of the file;<blockquote> start)</blockquote><blockquote> # Start daemon.</blockquote><blockquote> echo -n "Starting ss5... "</blockquote><blockquote> if [ $OS = "Linux" ]; then</blockquote><blockquote> daemon /usr/sbin/ss5 -m -t $SS5_OPTS</blockquote><blockquote> touch /var/lock/subsys/ss5</blockquote><blockquote> else</blockquote><blockquote> if [ $OS = "SunOS" ]; then</blockquote><blockquote> /usr/sbin/ss5 -m -t </blockquote><blockquote> touch /var/lock/subsys/ss5</blockquote><blockquote> else</blockquote><blockquote> /usr/local/sbin/ss5 -m -t </blockquote><blockquote> fi</blockquote><blockquote> fi</blockquote><blockquote> echo "done"</blockquote>...and good to go. It still creates the log file, but the size remains zero. Make sure to run systemctl daemon-reload when the /etc/init.d/ss5 file is modified and don't forget to remove any variables from the /etc/opt/ss5/ss5.conf file that don't work as this will prevent the service from starting.

Several additional observations after some usage;

- Using systemctl start ss5 was not always reliable (especially after a crash, see below), so used the service ss5 start command, which seems to only convert to the equivalent systemctl command, but makes ss5 happy.

- My client has a setting related to using proxy for host name lookups which crashes the SS5 service. Nothing in the log file (system or SS5 log), even when set to debug level. So I disabled that setting, all good to go.

<br />

@@ Line 20: / Line 20: @@
 At a certain point one has to give up, but I didn't.  Instead I changed strategies.  I noticed the ss5 binary had a command line switch (-m) that turned logging off, so I modified the /etc/init.d/ss5 file, adding three -m switches in the "start section" of the file;<blockquote>  start)</blockquote><blockquote>       # Start daemon.</blockquote><blockquote>       echo -n "Starting ss5... "</blockquote><blockquote>   if [ $OS = "Linux" ]; then</blockquote><blockquote>           daemon /usr/sbin/ss5 -m -t $SS5_OPTS</blockquote><blockquote>           touch /var/lock/subsys/ss5</blockquote><blockquote>   else</blockquote><blockquote>     if [ $OS = "SunOS" ]; then</blockquote><blockquote>             /usr/sbin/ss5 -m -t </blockquote><blockquote>             touch /var/lock/subsys/ss5</blockquote><blockquote>     else</blockquote><blockquote>             /usr/local/sbin/ss5 -m -t </blockquote><blockquote>     fi</blockquote><blockquote>   fi</blockquote><blockquote>   echo "done"</blockquote>...and good to go.  It still creates the log file, but the size remains zero.  Make sure to run systemctl daemon-reload when the /etc/init.d/ss5 file is modified and don't forget to remove any variables from the /etc/opt/ss5/ss5.conf file that don't work as this will prevent the service from starting.
+Several additional observations after some usage;
+- Using systemctl start ss5 was not always reliable (especially after a crash, see below), so used the service ss5 start command, which seems to only convert to the equivalent systemctl command, but makes ss5 happy.
+- My client has a setting related to using proxy for host name lookups which crashes the SS5 service.  Nothing in the log file (system or SS5 log), even when set to debug level.  So I disabled that setting, all good to go.
 <br />