mirror of
https://github.com/crosstool-ng/crosstool-ng.git
synced 2024-12-20 05:17:54 +00:00
e6ca02b829
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(-) |
||
|---|---|---|
| .. | ||
| build | ||
| crosstool.sh | ||
| functions | ||
| saveSample.sh | ||
| showSamples.sh | ||
| tarball.sh.broken | ||