Google Groups

Re: UDP Support?


Peter Valdemar Mørch Jul 19, 2011 7:00 PM
Posted in group: sshuttle
On Wed, Jul 20, 2011 at 1:55 AM, Brian May <br...@microcomaustralia.com.au> wrote:
Can you please rerun with -vvv and post the results here? Also "sudo
iptables -L -t mangle -n" will show if that table really exists or
not.

Sure:

host:~/sshuttle# ./sshuttle -vvv --method=tproxy -r root@cosmo:22000 172.27.114.0/24
Starting sshuttle proxy.
recvmsg socket_ext support enabled.
tproxy UDP support enabled.
Binding redirector: 12300
TCP redirector listening on ('::1', 12300, 0, 0).
TCP redirector listening on ('127.0.0.1', 12300).
UDP redirector listening on ('::1', 12300, 0, 0).
UDP redirector listening on ('127.0.0.1', 12300).
firewall manager ready method tproxy.
c : connecting to server...
c : executing: ['ssh', '-p', '22000', 'root@cosmo', '--', 'P=python2; $P -V 2>/dev/null || P=python; exec "$P" -c \'import sys; skip_imports=1; verbosity=3; exec compile(sys.stdin.read(764), "assembler.py", "exec")\'']
c :  > channel=0 cmd=PING len=7 (fullness=0)
Debian GNU/Linux lenny/sid

server: assembling 'cmdline_options.py' (45 bytes)
server: assembling 'helpers.py' (791 bytes)
server: assembling 'ssubprocess.py' (13704 bytes)
server: assembling 'ssnet.py' (5582 bytes)
c : connected.
Connected.
c : Waiting: 5 r=[3, 5, 7, 8, 11] w=[11] x=[] (fullness=7/0)
c :   Ready: 5 r=[11] w=[11] x=[]
c : <  channel=0 cmd=PING len=7
c :  > channel=0 cmd=PONG len=7 (fullness=7)
c : <  channel=0 cmd=ROUTES len=36
firewall manager: starting transproxy.
server: assembling 'hostwatch.py' (2242 bytes)
server: assembling 'server.py' (2970 bytes)
 s: latency control setting = True
 s: available routes:
 s:   2/10.143.96.16/28
 s:   2/10.143.96.16/28
 s:  > channel=0 cmd=PING len=7 (fullness=0)
 s:  > channel=0 cmd=ROUTES len=36 (fullness=7)
 s: Waiting: 1 r=[4] w=[5] x=[] (fullness=43/0)
 s:   Ready: 1 r=[] w=[5] x=[]
 s: mux wrote: 15/15
 s: mux wrote: 44/44
 s: Waiting: 1 r=[4] w=[] x=[] (fullness=43/0)
>> iptables -t mangle -N sshuttle-m-12300
>> iptables -t mangle -F sshuttle-m-12300
>> iptables -t mangle -N sshuttle-d-12300
>> iptables -t mangle -F sshuttle-d-12300
>> iptables -t mangle -N sshuttle-t-12300
>> iptables -t mangle -F sshuttle-t-12300
>> iptables -t mangle -I OUTPUT 1 -j sshuttle-m-12300
>> iptables -t mangle -I PREROUTING 1 -j sshuttle-t-12300
>> iptables -t mangle -A sshuttle-d-12300 -j MARK --set-mark 1
>> iptables -t mangle -A sshuttle-d-12300 -j ACCEPT

>> iptables -t mangle -A sshuttle-t-12300 -m socket -j sshuttle-d-12300 -m tcp -p tcp
iptables: No chain/target/match by that name.
firewall manager: undoing changes.
>> iptables -t mangle -D OUTPUT -j sshuttle-m-12300
>> iptables -t mangle -F sshuttle-m-12300
>> iptables -t mangle -X sshuttle-m-12300
>> iptables -t mangle -D PREROUTING -j sshuttle-t-12300
>> iptables -t mangle -F sshuttle-t-12300
>> iptables -t mangle -X sshuttle-t-12300
>> iptables -t mangle -F sshuttle-d-12300
>> iptables -t mangle -X sshuttle-d-12300
fatal: ['iptables', '-t', 'mangle', '-A', 'sshuttle-t-12300', '-m', 'socket', '-j', 'sshuttle-d-12300', '-m', 'tcp', '-p', 'tcp'] returned 1
c : fatal: cleanup: ['python', './main.py', 'python', '-v', '-v', '-v', '--firewall', '12300', '12300', '0', '0', 'tproxy', '1'] returned 99
host:~/sshuttle#  s:   Ready: 1 r=[4] w=[] x=[]

host:~/sshuttle# sudo iptables -L -t mangle -nChain PREROUTING (policy ACCEPT)
target     prot opt source               destination        

Chain INPUT (policy ACCEPT)
target     prot opt source               destination        

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination        

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination        

Chain POSTROUTING (policy ACCEPT)
target     prot opt source               destination        
host:~/sshuttle#