What's the output of dispatch list? Have you tried using each connection separately with dispatch, to check if they work individually?

from dispatch-proxy.

john@john:~$ dispatch list
lo
127.0.0.1 (IPv4, internal)
::1 (IPv6, internal)

eth0
192.168.10.2 (IPv4)
fe80::fe61:98ff:fe00:23c5 (IPv6)

wlan0
192.168.0.110 (IPv4)
fe80::227c:8fff:fe2e:577d (IPv6)

this is what I get in dispatch list.

from dispatch-proxy.

As morhaus stated, try each interface. Use command :
dispatch start interface-address.

For your eth0:
dispatch start 192.168.10.2

and for wlan0:
dispatch start 192.168.0.110

Command above will start dispatch as socks proxy.
To test the connection, setup your browser to use socks proxy to localhost with port 1080 and see if you can connect to internet with that.

from dispatch-proxy.

Oopsie sorry...

i tried it both, ethernet and wlan. But the wlan connection is not working. Im not sure if this is an issue with my hardware.

When Im using the ethernet it just works flawlessly. But in WLAN i have no luck..

There is also an error. You can check out the log
error [a4979e] serverConnection
Error: connect ETIMEDOUT
at errnoException (net.js:901:11)
at Object.afterConnect as oncomplete
error [ecf513] serverConnection
Error: connect ETIMEDOUT
at errnoException (net.js:901:11)
at Object.afterConnect as oncomplete
error [69ccc0] serverConnection
Error: connect ETIMEDOUT
at errnoException (net.js:901:11)
at Object.afterConnect as oncomplete
error [2108d7] serverConnection
Error: connect ETIMEDOUT
at errnoException (net.js:901:11)
at Object.afterConnect as oncomplete
error [094b64] serverConnection
Error: connect ETIMEDOUT
at errnoException (net.js:901:11)
at Object.afterConnect as oncomplete
error [8c257c] serverConnection
Error: connect ETIMEDOUT
at errnoException (net.js:901:11)
at Object.afterConnect as oncomplete

from dispatch-proxy.

I have the same problem! Did you find any solution?

from dispatch-proxy.

I finally could solve it. For this you need to configure routing table :

sudo echo 101 eth0 >> /etc/iproute2/rt_tables
sudo echo 101 wlan0 >> /etc/iproute2/rt_tables

Inserting routes in the eth0 table

ip route add 192.168.10.0/24 dev eth0 scope link table eth0
ip route add default via 192.168.10.1 dev eth0 table eth0 #(LAN router IP)

Inserting routes in the wlan0 table

ip route add 192.168.0.0/24 dev wlan0 scope link table wlan0
ip route add default via 192.168.0.1 dev wlan0 table wlan0 #(Wifi router IP)

ip rule is the source routing magic. This will redirect

packets coming from source "X" to table "eth0", "wlan0" or "default".

ip rule add from 192.168.1.0/24 table eth0
ip rule add from 192.168.2.0/24 table wlan0

from dispatch-proxy.

Thank you for sharing your solution. But sadly I am now in Arch Linux, but I will try your solution in Arch.

from dispatch-proxy.

I have same problem, but I can't solve it on Ubuntu 16.04.

from dispatch-proxy.