Configure tsocks with a simple heuristic.
Consider the proxy has to be in a 'local' network. It means it is directly
reachable by the local machine, even if the local machine has to hop through
one or more gates to reach the proxy (often the case in enterprise networks
where class A 10.0.0.0/8 is in fact sub-divided into smaller networks, each
one of them in a different location, eg. 10.1.0.0/16 in a place, while
10.2.0.0/16 would be on the other side of the world). Not being in the same
subnet does not mean the proxy is not available.
So we will build a mask with at most high bits set, which defines a network
that has both the local machine and the proxy. Because a machine may have
more than one interface, build a mask for each of them, removing 127.0.0.1
which is added automagically by tsocks, and removing duplicate masks.
If all of this does not work, then it means the local machine can NOT in fact
reach the proxy, which in turn means the user mis-configured something (most
probably a typo...).
/trunk/scripts/crosstool.sh | 61 52 9 0 +++++++++++++++++++++++++++++++++++++++++++--------
1 file changed, 52 insertions(+), 9 deletions(-)
1 # Configuration file for sstrip tool facility
8 The sstrip utility, to maximise the striping of ELF binaries
9 (executables and libraries).
15 prompt "Use sstrip from:"
17 config SSTRIP_ELFKICKERS
21 Use the original, ageing version of sstrip from ELFkickers.
22 It seems to be fully functional, but not maintained.
24 config SSTRIP_BUILDROOT
28 Use the version from buildroot. It comes from the original
29 ELFkickers, but is somewhat maintained by the buildroot guys.
35 default "ELFkickers" if SSTRIP_ELFKICKERS
36 default "buildroot" if SSTRIP_BUILDROOT
40 config SSTRIP_ELFKICKERS_VERSION