alexkirsz / dispatch-proxy Goto Github PK

Hi Morhaus,

I am exploring dispatch-proxy. As I am new to coffee(java script), I am feeling bit difficult to understand how load balancing is achieved.

Assume I am uploading a youtube video(10 MB) via dispatch-proxy with wlan0, 3g/4g connections (wlan0@1 pdp0@1) running at equal speeds, how can dispatch proxy divide the upload equally among two interfaces.

Does socks proxy support ftp upload(tcp) balancing/dns(udp) query balancing

It would be nice if we could output the "throughput" of each interface being used 😄

dispatch list:

C:\windows\system32>dispatch list
Wireless connection
    fe80::28b9:89c2:6feb:bc63 (IPv6)
    192.168.0.104 (IPv4)

3G connection
    10.215.12.205 (IPv4)

Loopback Pseudo-Interface 1
    ::1 (IPv6, internal)
    127.0.0.1 (IPv4, internal)

Ethernet 2
    2001:0:9d38:90d7:2837:3cb1:a29b:e90e (IPv6)
    fe80::2837:3cb1:a29b:e90e (IPv6)

3G (10.215.12.205) is primary connection in Windows. I thinks so cause whatismyip.com says that I have ip from 3G when I open it in browser without proxy.
Wi-fi (192.168.0.104) is non-primary connection.

I start proxy on non-primary connection:

C:\windows\system32>dispatch start 192.168.0.104
SOCKS server started on localhost:1080
Dispatching to addresses 192.168.0.104@1

And get errors:

     error [6d525a] serverConnection
           Error: connect ENETUNREACH
               at errnoException (net.js:901:11)
               at Object.afterConnect [as oncomplete] (net.js:892:19)
     error [6d525a] clientConnection
           Error: read ECONNRESET
               at errnoException (net.js:901:11)
               at TCP.onread (net.js:556:19)
     error [7dd649] serverConnection
           Error: connect ENETUNREACH
               at errnoException (net.js:901:11)
               at Object.afterConnect [as oncomplete] (net.js:892:19)
     error [7dd649] clientConnection
           Error: read ECONNRESET
               at errnoException (net.js:901:11)
               at TCP.onread (net.js:556:19)
     error [18590a] serverConnection
           Error: connect ENETUNREACH
               at errnoException (net.js:901:11)
               at Object.afterConnect [as oncomplete] (net.js:892:19)
     error [18590a] clientConnection
           Error: read ECONNRESET
               at errnoException (net.js:901:11)
               at TCP.onread (net.js:556:19)

I see the same errors when I start proxy using both internet connections. There is no errors when I start proxy using primary internet connection.
Log with debug enabled

I already tried on 3 computers (2 Win7 and 1 Linux) - on all of them proxy using non-primary connection is not working.

Am I'm missed some setting or something?

BTW, thanks for your program. I've dreamed of such thing for the whole time.

Is there a way to forward only certain TCP ports via selective paths please?
Here are some scenarios, assuming multiplexed public WiFi & wired 3g (cell phone modem) connections:

• only the WiFi for online games (FPS & MMO) since the 3g has too much latency
• only the 3g for HTTPS (port 80), since WiFi at the cafe is less secure for online banking
• multiplex all when leeching files via FTP, but switch to more secure 3g when uploading files to webserver

Hello,

I noticed that proxy bugs with utorrent,i managed once to receive threaded traffic and got x2 speeds (neighbourgh and i same internet packet). Tho i can't get the threads to work again..

How i managed to have x2 traffic once is that i have set the proxy server type to http and port 8080. then i started socks5 and switched type and port ot 1080,when i changed socks5 to http i forgot to change port 1080 and i managed to get x2 download speeds.. not sure how is that possible if http was listening on port 1080..

P.S I am looking forward to see this project alive and 100% functional :)

I'm still can't run it in my Windows
please make some complete tutorials with screenshot,
what proxy software should use,the settings in the OSes,
or make a screencast

is it possible to combine internet connection speed in VPN environment?

I am nt very familiar with Node.js and i have some issues/queries on connecting my 2 network cards to 2 different ISPs using Node.js.

1. I installed node.js, ran npm install -g dispatch-proxy and got npm installed. I was able to assign priorities for the 2 BB connections and verify it thru speed test and got the BW sharing to work with combined speeds.
2. when i shutdown and restarted the machine,the settings are all gone. BW sharing does not happen. How do i put this in every login.
   My machine runs windows XP sp3 and I use ver node-v0.10.22-x86 (v12 doesnot work for me).
   Any suggestions

Hi,
I tried to use dispatch-proxy with qBittorrent, both configured to use socks4, the error is:

error socks
Unsupported SOCKS version: 71

In other issues I've read that it's the error you get when proxy receives an http request, which should not considering qBittorrent is using socks4 (not http), anyway, if I try to set up a http proxy instead of a socks proxy (dispatch start --http) the error changes to:

Error: read ECONNRESET
at errnoException (net.js:904:11)
at TCP.onread (net.js:558:19)

Any clue? I'm running windows 7 64 bit - dispach version 0.1.2

1st browser: firefox using HTTP proxy
2nd browser TOR firefox browser using SOCKS Host:1270.0.1 with port# 9150
Question: Both running but TOR not using HTTP proxy. How do I setup TOR to also use HTTP proxy and remove SOCKS Host support?

Hi,

Im using ubuntu 12.04, and when i try to use dispatch-proxy it doesnt combine my LAN and WLAN (neighbor wifi). My internet speed is 2Mbps and my neighbors wifi has 1 Mbps..

Really wanted this because connectify dispatch is too heavy for my system.

Thanks.

Hi,

I want to use dispath to provide http / socks5 proxy for connection to the internet, combining 3G and Ethernet connections and then sharing over Wifi hotspot. I've spent quite sometime setting it up and am now at a point where I'm ready to merge the connections.

All is fine (I'll probably need to put dispath in looping script as 3G ip isn't static), but how do then provide proxy to those over internet, i.e. how to I allow remote connection to local host. I've tried setting up Linux Firewall (iptables) to allow connection from wlan0 but to no avail.

Any ideas.

Help much apprecicated. I can provide more details logs etc as required.

Cheers
Mike

Conjectural question: how would you go about running dispatch on a wireless repeater? For low-bandwidth areas that receive reasonable 3G signal, channel bonding multiple connections might be quite appealing.

Just curious how this relates to multipath tcp. Comparison, drawbacks, compatibility, etc…

Working great, other than a small bug I encountered. When starting the proxy and connecting, I would get:

$ dispatch start
SOCKS5 server started on localhost:1080
Dispatching to addresses 192.168.42.226@1, 10.20.0.2@1, 192.168.1.155@1

C:\Users\Administrator\AppData\Roaming\npm\node_modules\dispatch-proxy\lib\utilities.js:18
  return value.join('.');
               ^
TypeError: Object 74 has no method 'join'
    at Object.exports.formatIPv4 (C:\Users\Administrator\AppData\Roaming\npm\node_modules\dispatch-proxy\lib\utilities.js:18:16)

For some reason, data.byte(4) on line 99 of socks.js was only returning the first octect of the destination IP address. I hack-fixed it by replacing commenting out line 99 and replacing it with the following:

//return u.formatIPv4(data.byte(4));
return data.byte(4) + '.' + data.byte(4) + '.' +  data.byte(4) + '.' + data.byte(4)

Thanks again for your contribution and open sourcing it - fast downloads are enjoyable. I was pulling >5MB/s earlier using cable and 4G internet :)

Hello,

dispatch-proxy 0.1.2
Node 0.12.2
Manjaro Linux 0.8.12 Ascella

After starting dispatch and config firefox to conect via localhost:1080 i have no inernet connection and i get these errors :

$ dispatch start
SOCKS server started on localhost:1080
Dispatching to addresses 192.168.1.123@1, 192.168.1.124@1
     error socks
           Unsupported SOCKS version: 71
     error socks
           Unsupported SOCKS version: 80
     error socks
           Unsupported SOCKS version: 71
     error socks
           Unsupported SOCKS version: 67

I missing something?

I made internet sharing service on my Personal computer.
So I decided aggrigating traffic of eth0 and eth1 with 100Mbps ethernet to eth2 (ethernet card for internet sharing).

But, I can guess that is not working by basic settings of Ubuntu Linux 14.04 and dispatch. How it works?

seongho@seongho-P5K:~$ dispatch list
lo
127.0.0.1 (IPv4, internal)
::1 (IPv6, internal)

eth2
10.42.0.1 (IPv4)
fe80::66e5:99ff:fef9:f800 (IPv6)

eth1
180.68.11.110 (IPv4)
fe80::20e:e8ff:fee1:7664 (IPv6)

eth0
112.155.219.131 (IPv4)
fe80::21d:60ff:fea2:26cf (IPv6)

seongho@seongho-P5K:~$

seongho@seongho-P5K:~$ ifconfig
eth0 Link encap:Ethernet
inet addr:112.155.219.131 Bcast:112.155.219.255 Mask:255.255.255.0
inet6 addr: fe80::21d:60ff:fea2:26cf/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:163769909 errors:0 dropped:0 overruns:0 frame:0
TX packets:98470971 errors:0 dropped:0 overruns:0 carrier:2
collisions:0 txqueuelen:1000
RX bytes:167345124322 (167.3 GB) TX bytes:40633658538 (40.6 GB)

eth1 Link encap:Ethernet
inet addr:180.68.11.110 Bcast:180.68.11.255 Mask:255.255.255.0
inet6 addr: fe80::20e:e8ff:fee1:7664/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:29809256 errors:0 dropped:0 overruns:0 frame:0
TX packets:31001 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1796537948 (1.7 GB) TX bytes:7091949 (7.0 MB)

eth2 Link encap:Ethernet
inet addr:10.42.0.1 Bcast:10.42.0.255 Mask:255.255.255.0
inet6 addr: fe80::66e5:99ff:fef9:f800/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:102179262 errors:0 dropped:3 overruns:0 frame:0
TX packets:180414573 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:34422983636 (34.4 GB) TX bytes:213643975647 (213.6 GB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:3304669 errors:0 dropped:0 overruns:0 frame:0
TX packets:3304669 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:34492051456 (34.4 GB) TX bytes:34492051456 (34.4 GB)

seongho@seongho-P5K:~$

Hi, I just started playing with Dispatch and wanted to verify before/after speeds, and the balancing. I think a great enhancement would be to include a command-line argument for creating an output log, that I could in-return graph.

Cheers,
TC

Hello,

dispatch-proxy is not working on Mac OS X 10.7.5.
It just does nothing.
Here the commands I'm using:

$ dispatch start &
SOCKS5 server started on localhost:1080
Dispatching to addresses 192.168.0.10@1
$ export http_proxy=localhost:1080
$ curl http://www.google.com --trace -
== Info: About to connect() to proxy localhost port 1080 (#0)
== Info:   Trying ::1... == Info: Connection refused
== Info:   Trying 127.0.0.1... == Info: connected
== Info: Connected to localhost (127.0.0.1) port 1080 (#0)
=> Send header, 198 bytes (0xc6)
0000: 47 45 54 20 68 74 74 70 3a 2f 2f 77 77 77 2e 67 GET http://www.g
0010: 6f 6f 67 6c 65 2e 63 6f 6d 20 48 54 54 50 2f 31 oogle.com HTTP/1
0020: 2e 31 0d 0a 55 73 65 72 2d 41 67 65 6e 74 3a 20 .1..User-Agent: 
0030: 63 75 72 6c 2f 37 2e 32 31 2e 34 20 28 75 6e 69 curl/7.21.4 (uni
0040: 76 65 72 73 61 6c 2d 61 70 70 6c 65 2d 64 61 72 versal-apple-dar
0050: 77 69 6e 31 31 2e 30 29 20 6c 69 62 63 75 72 6c win11.0) libcurl
0060: 2f 37 2e 32 31 2e 34 20 4f 70 65 6e 53 53 4c 2f /7.21.4 OpenSSL/
0070: 30 2e 39 2e 38 79 20 7a 6c 69 62 2f 31 2e 32 2e 0.9.8y zlib/1.2.
0080: 35 0d 0a 48 6f 73 74 3a 20 77 77 77 2e 67 6f 6f 5..Host: www.goo
0090: 67 6c 65 2e 63 6f 6d 0d 0a 41 63 63 65 70 74 3a gle.com..Accept:
00a0: 20 2a 2f 2a 0d 0a 50 72 6f 78 79 2d 43 6f 6e 6e  */*..Proxy-Conn
00b0: 65 63 74 69 6f 6e 3a 20 4b 65 65 70 2d 41 6c 69 ection: Keep-Ali
00c0: 76 65 0d 0a 0d 0a                               ve....

Curl just hangs out forever. I have also tried with Firefox, it does the same thing.

Can you add some debug information to see where the problem is?

Cheers

command use to update "npm update -g dispatch-proxy". dispatch -V shows 0.1.2 only

I got an error when i try to start dispatch.

dispatch start

module.js:340
    throw err;
          ^
Error: Cannot find module '/usr/local/lib/node_modules/dispatch-proxy/bin/../lib'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/usr/local/lib/node_modules/dispatch-proxy/bin/dispatch.js:2:1)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Function.Module.runMain (module.js:497:10)

I installed dispatch-proxy with commands:

git clone https://github.com/Morhaus/dispatch-proxy.git
cd dispatch-proxy
sudo npm install -g dispatch-proxy

node --version
v0.10.15

 uname -a
Linux sancho 3.11.0-14-generic #21-Ubuntu SMP Tue Nov 12 17:04:55 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Hi! i have two connections and when i try to use jdownloader or any torrent client throws me this errors:
(note: using socks or http option, both of them doesnt work, any ideas?)

C:\Windows\system32>dispatch start
SOCKS server started on localhost:1080
Dispatching to addresses 10.0.0.99@1, 10.0.0.6@1
events.js:85
throw er; // Unhandled 'error' event
^
Error: read ECONNRESET
at exports._errnoException (util.js:746:11)
at TCP.onread (net.js:559:26)

C:\Windows\system32>dispatch start --http
HTTP server started on localhost:8080
Dispatching to addresses 10.0.0.99@1, 10.0.0.6@1
^C¿Desea terminar el trabajo por lotes (S/N)? s

C:\Windows\system32>dispatch start
SOCKS server started on localhost:1080
Dispatching to addresses 10.0.0.99@1, 10.0.0.6@1
events.js:85
throw er; // Unhandled 'error' event
^
Error: read ECONNRESET
at exports._errnoException (util.js:746:11)
at TCP.onread (net.js:559:26)

C:\Windows\system32>dispatch start --http
HTTP server started on localhost:8080
Dispatching to addresses 10.0.0.99@1, 10.0.0.6@1
^C¿Desea terminar el trabajo por lotes (S/N)? s

C:\Windows\system32>dispatch start
SOCKS server started on localhost:1080
Dispatching to addresses 10.0.0.99@1, 10.0.0.6@1
C:\Users\Server\AppData\Roaming\npm\node_modules\dispatch-proxy\node_modules\soc
ks-handler\lib\socks4\index.js:23
return request.call(this, chunk);
^
TypeError: undefined is not a function
at Stream. (C:\Users\Server\AppData\Roaming\npm\node_modules\disp
atch-proxy\node_modules\socks-handler\lib\socks4\index.js:23:24)
at Stream.stream.write (C:\Users\Server\AppData\Roaming\npm\node_modules\dis
patch-proxy\node_modules\socks-handler\node_modules\through\index.js:26:11)
at Socket.ondata (_stream_readable.js:540:20)
at Socket.emit (events.js:129:20)
at readableAddChunk (_stream_readable.js:163:16)
at Socket.Readable.push (_stream_readable.js:126:10)
at TCP.onread (net.js:538:20)

Ty for your time!

Trying to get this running on Windows 7, started as a SOCKS proxy only, as soon as I enable the system proxy settings & try to access anything (i.e. web browsing, ftp, etc) the console starts spitting out "Error Client - Invalid Client Version (4) messages (and no data gets through).

Screenshot: http://screencast.com/t/IMSJZkQFF

You seem to be using port tcp/55667. This is inside the IANA ephemeral range, you really shouldn't be using this port if you can help it.

There's a (non-privileged) port reserved for SOCKS proxies -- tcp/1080. Any chance you could change to use that instead?

does it support of partial download (etc: streaming video) ?

partial download will always return http status code to 206

img http: https://www.dropbox.com/s/jwldi9kfa2d0o2y/dispatch%20error%201st%20attempt.PNG?dl=0
firefox proxy setup: https://www.dropbox.com/s/4yjyys201v7hv61/dispatch%20firefox%20proxy%20setup.PNG?dl=0
firefox version: 42.0a1 (2015-07-02)
Using 1 internet connection for testing, wifi. Please see image and hint me my error in setup. Tnx

any idea what cause following issue?

dispatch start --http -p 7000
HTTP server started on localhost:7000
Dispatching to addresses 10.3.150.3@1, 192.168.1.3@1
error [068db1] clientRequest
Error: connect EADDRNOTAVAIL
at exports._errnoException (util.js:746:11)
at TCPConnectWrap.afterConnect as oncomplete
error [90108d] clientRequest
Error: connect EADDRNOTAVAIL
at exports._errnoException (util.js:746:11)
at TCPConnectWrap.afterConnect as oncomplete

gdm sir, i get those erros all the time when i use the program it did work one time but since then nothing
HTTP server started on localhost:8080
Dispatching to addresses 192.168.1.1@1, 192.168.1.3@1
error [1f5ba2] clientRequest
Error: connect ETIMEDOUT
at errnoException (net.js:905:11)
at Object.afterConnect [as oncomplete] (net.js:896:19
error [ed617b] clientRequest
Error: connect ETIMEDOUT
at errnoException (net.js:905:11)
at Object.afterConnect [as oncomplete] (net.js:896:19
error [4772b7] clientRequest
Error: connect ETIMEDOUT
at errnoException (net.js:905:11)
at Object.afterConnect [as oncomplete] (net.js:896:19
error [ba9caf] clientRequest
Error: connect ETIMEDOUT
at errnoException (net.js:905:11)
at Object.afterConnect [as oncomplete] (net.js:896:19
error [d880a8] clientRequest
Error: connect ETIMEDOUT
at errnoException (net.js:905:11)
at Object.afterConnect [as oncomplete] (net.js:896:19
error [c683fa] clientRequest
Error: connect ETIMEDOUT
at errnoException (net.js:905:11)
at Object.afterConnect [as oncomplete] (net.js:896:19
error [a3b9aa] clientRequest
Error: connect ETIMEDOUT
at errnoException (net.js:905:11)
at Object.afterConnect [as oncomplete] (net.js:896:19
error [613d9c] clientRequest
Error: connect ETIMEDOUT
at errnoException (net.js:905:11)
at Object.afterConnect [as oncomplete] (net.js:896:19
error [44d972] clientRequest
Error: connect ETIMEDOUT
at errnoException (net.js:905:11)
at Object.afterConnect [as oncomplete] (net.js:896:19
error [cc6b42] clientRequest
Error: connect ETIMEDOUT
at errnoException (net.js:905:11)
at Object.afterConnect [as oncomplete] (net.js:896:19
error [088fc0] clientRequest
Error: connect ETIMEDOUT
at errnoException (net.js:905:11)
at Object.afterConnect [as oncomplete] (net.js:896:19
error [653985] clientRequest
Error: connect ETIMEDOUT
at errnoException (net.js:905:11)
at Object.afterConnect [as oncomplete] (net.js:896:19
error [de52ef] clientRequest
Error: connect ETIMEDOUT
at errnoException (net.js:905:11)
at Object.afterConnect [as oncomplete] (net.js:896:19
error [fb422b] clientRequest
Error: connect ETIMEDOUT
at errnoException (net.js:905:11)
at Object.afterConnect [as oncomplete] (net.js:896:19
error [5b277a] clientRequest
Error: connect ETIMEDOUT
at errnoException (net.js:905:11)
at Object.afterConnect [as oncomplete] (net.js:896:19
error [13755a] clientRequest
Error: connect ETIMEDOUT
at errnoException (net.js:905:11)
at Object.afterConnect [as oncomplete] (net.js:896:19
error [16683e] clientRequest
Error: connect ETIMEDOUT
at errnoException (net.js:905:11)
at Object.afterConnect [as oncomplete] (net.js:896:19
error [e66146] clientRequest
Error: connect ETIMEDOUT
at errnoException (net.js:905:11)
at Object.afterConnect [as oncomplete] (net.js:896:19
error [55de0b] clientRequest
Error: connect ETIMEDOUT
at errnoException (net.js:905:11)
at Object.afterConnect [as oncomplete] (net.js:896:19
error [7a2f7c] clientRequest
Error: connect ETIMEDOUT
at errnoException (net.js:905:11)
at Object.afterConnect [as oncomplete] (net.js:896:19
error [460539] clientRequest
Error: connect ETIMEDOUT
at errnoException (net.js:905:11)
at Object.afterConnect [as oncomplete] (net.js:896:19
error [289439] clientRequest
Error: connect ETIMEDOUT
at errnoException (net.js:905:11)
at Object.afterConnect [as oncomplete] (net.js:896:19
error [15e1b0] clientRequest
Error: connect ETIMEDOUT
at errnoException (net.js:905:11)
at Object.afterConnect [as oncomplete] (net.js:896:19
error [515503] clientRequest
Error: connect ETIMEDOUT
at errnoException (net.js:905:11)
at Object.afterConnect [as oncomplete] (net.js:896:19
error [db5253] clientRequest
Error: connect ETIMEDOUT
at errnoException (net.js:905:11)
at Object.afterConnect [as oncomplete] (net.js:896:19
error [6b99ae] clientRequest
Error: connect ETIMEDOUT
at errnoException (net.js:905:11)
at Object.afterConnect [as oncomplete] (net.js:896:19
error [b81146] clientRequest
Error: connect ETIMEDOUT
at errnoException (net.js:905:11)
at Object.afterConnect [as oncomplete] (net.js:896:19

Installed node.js and everything. kept on getting the same error when I type dispatch

root@Potato:/home/potato# dispatch -v
/usr/bin/env: node: No such file or directory

I can't start it on http.

dispatch start --http 192.168.2.15
HTTP server started on localhost:8080
Dispatching to addresses 192.168.2.15@1
events.js:72
throw er; // Unhandled 'error' event
^
Error: listen EACCES
at errnoException (net.js:901:11)
at Server._listen2 (net.js:1020:19)
at listen (net.js:1061:10)
at net.js:1135:9
at dns.js:72:18
at process._tickCallback (node.js:415:13)
at Function.Module.runMain (module.js:499:11)
at startup (node.js:119:16)
at node.js:902:3

Hello,
I'm getting the following error when setting up proxy and trying to connect to any website:

HTTP server started on localhost:8080
Dispatching to addresses 192.168.1.100@1
error [7607a0] clientRequest
Error: getaddrinfo ENOTFOUND
at errnoException (dns.js:37:11)
at Object.onanswer as oncomplete
error [70cb71] clientRequest
Error: getaddrinfo ENOTFOUND
at errnoException (dns.js:37:11)
at Object.onanswer as oncomplete
error [2fd617] clientRequest
Error: getaddrinfo ENOTFOUND
at errnoException (dns.js:37:11)
at Object.onanswer as oncomplete

It doesn't matter what iterfaces I select, I always get this error.
Thanks for any help.

This project is very interesting and seems very promising.
However I don't see any mention of the license under which this code is released.

A LICENSE.txt file would be greatly appreciated.

If you need to, I can provide help for you to choose one.

catalyst-proxy had a option -P to use proxy to fake IP or even make it work on HTTPS site with ProxHTTPSProxy, hope you can add that feature to displatch-proxy because I really want to chain dispatch-proxy with Privoxy or ProxHTTPSProxy to make it works on HTTPS site.
Thank!

Hi,

Conf:

• dispatch-proxy 0.1.2
• Node 0.10.23
• Windows 7 64bits

While playing DotA 2 I got lots of errors:

error socks
      Unsupported SOCKS version: 71
error socks
      Unsupported SOCKS version: 80

Easily reproducible by going into the shop or opening the "Learn how" page on the Workshop tab.

Hi,
I have followed every step carefully and started the dispatch, but to my surprise the speed seems to be same. I tried downloading multiple videos and upload files simultaneously but the bandwidth remains the same of my lan which is 25mbps. Even did a speed test and shows a less speed when dispatch starts.

I have connected with the following in my lap

1. LAN - 25mbps (Sharing Galaxy Broadband)
2. Wifi - 15mbps (Airtel Broadband)

Now it should have the combine speed of 40mbps, I tested using speedtest and downloded+uploaded files but the banwidth seems to reduce rather than increase

Any solution for my problem.
Thanks in advance

Screenshot of my speedtest:

I love to use this. But how i can stop this service. I try "dispatch stop" and not work? Pls help me how to stop this god damm thing.

Here's a screenshot:

Has it got something to do with the DNS?

dispatch-proxy works with firefox but not with curl.

Further examination revealed that when newly connected client sends 3 bytes {0x05, 0x01, 0x00} (as in case of firefox) the proxy sends back {0x05, 0x00} and works properly. But when client sends 4 bytes {0x05, 0x02, 0x00, 0x01} (in case of curl) the server hangs.

I'm getting some exception as I'm trying to run the proxy service. Here is what I did:

$ sudo apt-get install npm
(success)

$ sudo npm install -g dispatch-proxy
(success)

$ dispatch start --debug
node.js:201
    throw e; // process.nextTick error, or 'error' event on first tick
              ^
TypeError: Cannot call method 'bind' of undefined
at new Server (/usr/local/lib/node_modules/dispatch-proxy/lib/socks/server.js:42:42)
at Object.createServer (/usr/local/lib/node_modules/dispatch-proxy/lib/socks/index.js:8:14)
at new SocksProxy (/usr/local/lib/node_modules/dispatch-proxy/lib/proxy/socks.js:19:25)
at Command.<anonymous> (/usr/local/lib/node_modules/dispatch-proxy/lib/index.js:114:13)
at Command.<anonymous> (/usr/local/lib/node_modules/dispatch-proxy/node_modules/commander/index.js:249:8)
at Command.emit (events.js:88:20)
at Command.parseArgs (/usr/local/lib/node_modules/dispatch-proxy/node_modules/commander/index.js:472:12)
at Command.parse (/usr/local/lib/node_modules/dispatch-proxy/node_modules/commander/index.js:370:21)
at Object.<anonymous> (/usr/local/lib/node_modules/dispatch-proxy/lib/index.js:154:9)
at Module._compile (module.js:441:26)

It seems to me I'm missing some dependency, but I don't know. The nodejs package is installed.

$ node --version
v0.6.12

$ npm --version
1.1.4

According to the help, it should start listening on port 1080 and possibly 8080. These are not in use:

$ nc -l 1080 & nc -l 8080 & sudo nc -l 80 # to check, 80 should error
[1] 32276
[2] 32277
nc: Address already in use

Hello!
So I started up the dispatch service to two ips, and I'm getting a bunch of errors.
I ran it with the --debug option and this is what I got.

SOCKS server started on localhost:1080
Dispatching to addresses 192.168.116.228@1, 192.168.1.134@1
   request [efa0a9] 127.0.0.1:54000
  dispatch [efa0a9] 192.168.116.228
     error [efa0a9] serverConnection
           Error: connect ECONNREFUSED
               at errnoException (net.js:904:11)
               at Object.afterConnect [as oncomplete] (net.js:895:19)
       end [efa0a9] clientConnection
   request [acac53] 127.0.0.1:54000
  dispatch [acac53] 192.168.1.134
     error [acac53] serverConnection
           Error: connect ECONNREFUSED
               at errnoException (net.js:904:11)
               at Object.afterConnect [as oncomplete] (net.js:895:19)
       end [acac53] clientConnection

It would repeat this every few seconds for the length of time that i had the service running. As you can see, it's the same error happening on both IPs that I'm bridging. I can still connect to the network and websites while the service is running, so I'm not sure if it's a dire issue, but it's just alarming to get quite so many errors.

I'm running OSX 10.10.1 (Yosemite)
NPM version 1.4.28

Thanks in advance!

My most important usecase for a software like this is unstable mobile connections:

imagine I am on the train, I have the following 3 connections available:

• train wifi
• mobile 3g that I share via wifi
• 3g stick on my notebook

now, as I am on the train, and constantly moving, crossing forests, tunnels, ...
all the connections become unstable.
however, in a tunnel, the train wifi might be still working because they have a source in the tunnel.
or far out the city, one mobile carrier might have a node, but the other carrier has not.

so, I need a software that does load balancing, but more importantly, makes the connection as stable as possible.

is this usecase covered already? if so, can you add it to the readme?
if not, is it a planed feature?

Using black text isn't readable on a black terminal background.

[email protected]
0.1.2
Yosemite

I'm getting a lot of

error [] clientRequest
      Error: connect EHOSTUNREACH

while using dispatch as an http proxy. I mostly encounter them with YouTube and StackOverflow.
YouTube has an exception though, the site load when you access a video page directly.

The command I run:

dispatch start --http  0.0.0.0@8 0.0.0.0@2 -p 1025

Is it safe to assume that the port have something to do with the error?

Publish the SOCKS module as a separate entity on npm.

Hi,

Dispatch crashes everytime I try to visit a website :

/usr/local/lib/node_modules/dispatch-proxy/node_modules/tmpl-log/lib/logger.js:139
          throw new Error("Non-existent style " + tag + " at index " + index);
                ^
Error: Non-existent style magenta-b at index 9
    at Logger.module.exports.Logger.parse (/usr/local/lib/node_modules/dispatch-proxy/node_modules/tmpl-log/lib/logger.js:139:17)
    at Logger.module.exports.Logger.format (/usr/local/lib/node_modules/dispatch-proxy/node_modules/tmpl-log/lib/logger.js:103:18)
    at Logger.format (/usr/local/lib/node_modules/dispatch-proxy/node_modules/tmpl-log/lib/logger.js:2:59)
    at Logger.module.exports.Logger.emit (/usr/local/lib/node_modules/dispatch-proxy/node_modules/tmpl-log/lib/logger.js:70:17)
    at Logger.emit (/usr/local/lib/node_modules/dispatch-proxy/node_modules/tmpl-log/lib/logger.js:2:59)
    at ClientRequest.<anonymous> (/usr/local/lib/node_modules/dispatch-proxy/lib/index.js:93:23)
    at ClientRequest.EventEmitter.emit (events.js:117:20)
    at HTTPParser.parserOnIncomingClient [as onIncoming] (http.js:1688:21)
    at HTTPParser.parserOnHeadersComplete [as onHeadersComplete] (http.js:121:23)
    at Socket.socketOnData [as ondata] (http.js:1583:20)

I started dispatch with the following command :

dispatch start -p 8081 --http --debug

connectify has the exact same name for their application

The internet is not being distributed to other networks. I've set my wifi as the priority network, running a 1mbps 3G. At the same time I had a second priority ethernet cable connected with a 30mbps internet.

Without dispatch, the internet is 1mbps.
With dispatch start, the internet is 1mpbs
With dispatch targeted only to the 30mbps network, the internet is 1mpbs.

I've hit "apply" when setting the socks connection.
I've already tried http only.
I've installed npm with sudo.
I've tried running dispatch command with and without sudo

When running the --debug flag, it will seem to be dispatching accordingly to what I've set, but it does actually not.

On Mac OS 10.9, the dispatch list command crashes. It seems to die during or after listing lo0. dispatch start seems to work fine. Installed via npm.

$ node -v
v0.10.22
$ dispatch -V
0.0.1

dispatch list output:

$ dispatch list
lo0
    ::1 (IPv6, internal)
    127.0.0.1 (IPv4, internal)
    fe80::1 (IPv6, internal)
    127.0.0.2 (IPv4, internal)

/usr/local/lib/node_modules/dispatch-proxy/lib/logger.js:329
    return output.join('');
                  ^
TypeError: Cannot call method 'join' of undefined
    at Logger.module.exports.Logger._style (/usr/local/lib/node_modules/dispatch-proxy/lib/logger.js:329:19)
    at Logger.module.exports.Logger.format (/usr/local/lib/node_modules/dispatch-proxy/lib/logger.js:185:17)
    at Logger.module.exports.Logger.log (/usr/local/lib/node_modules/dispatch-proxy/lib/logger.js:91:24)
    at /usr/local/lib/node_modules/dispatch-proxy/lib/logger.js:2:59
    at Command.program.command.usage.description.option.option.option.option.action.arguments.length.__slice.call._i (/usr/local/lib/node_modules/dispatch-proxy/lib/index.js:44:19)
    at Command.<anonymous> (/usr/local/lib/node_modules/dispatch-proxy/node_modules/commander/index.js:249:8)
    at Command.EventEmitter.emit (events.js:98:17)
    at Command.parseArgs (/usr/local/lib/node_modules/dispatch-proxy/node_modules/commander/index.js:472:12)
    at Command.parse (/usr/local/lib/node_modules/dispatch-proxy/node_modules/commander/index.js:370:21)
    at Object.<anonymous> (/usr/local/lib/node_modules/dispatch-proxy/lib/index.js:154:9)

ifconfig output if it helps:

$ ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
    options=3<RXCSUM,TXCSUM>
    inet6 ::1 prefixlen 128 
    inet 127.0.0.1 netmask 0xff000000 
    inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 
    inet 127.0.0.2 netmask 0xff000000 
    nd6 options=1<PERFORMNUD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
    options=27<RXCSUM,TXCSUM,VLAN_MTU,TSO4>
    ether [REDACTED] 
    inet6 fe80::225:4bff:fec4:5d2c%en0 prefixlen 64 scopeid 0x4 
    inet 192.168.2.28 netmask 0xffffff00 broadcast 192.168.2.255
    nd6 options=1<PERFORMNUD>
    media: autoselect (1000baseT <full-duplex,flow-control>)
    status: active
en1: flags=8823<UP,BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
    ether [REDACTED] 
    nd6 options=1<PERFORMNUD>
    media: autoselect (<unknown type>)
    status: inactive
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
    lladdr [REDACTED] 
    nd6 options=1<PERFORMNUD>
    media: autoselect <full-duplex>
    status: inactive
p2p0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 2304
    ether [REDACTED] 
    media: autoselect
    status: inactive

Publish the Logger module as a separate entity on npm.