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 # dmalloc debug facility
12 prompt "dmalloc version"
14 config DMALLOC_V_5_4_3
16 prompt "5.4.3 (OBSOLETE)"
19 config DMALLOC_V_5_5_2
23 # CT_INSERT_VERSION_ABOVE
24 # Don't remove above line!
27 config DMALLOC_VERSION
29 default "5.4.3" if DMALLOC_V_5_4_3
30 default "5.5.2" if DMALLOC_V_5_5_2
31 # CT_INSERT_VERSION_STRING_ABOVE
32 # Don't remove above line!