{"action":"created","issue":{"url":"https://api.github.com/repos/sshuttle/sshuttle/issues/106","repository_url":"https://api.github.com/repos/sshuttle/sshuttle","labels_url":"https://api.github.com/repos/sshuttle/sshuttle/issues/106/labels{/name}","comments_url":"https://api.github.com/repos/sshuttle/sshuttle/issues/106/comments","events_url":"https://api.github.com/repos/sshuttle/sshuttle/issues/106/events","html_url":"https://github.com/sshuttle/sshuttle/issues/106","id":164703601,"number":106,"title":"Ubuntu 16.04 Gnome - Shuttle Master UDP issues","user":{"login":"DiagonalArg","id":5190243,"avatar_url":"https://avatars.githubusercontent.com/u/5190243?v=3","gravatar_id":"","url":"https://api.github.com/users/DiagonalArg","html_url":"https://github.com/DiagonalArg","followers_url":"https://api.github.com/users/DiagonalArg/followers","following_url":"https://api.github.com/users/DiagonalArg/following{/other_user}","gists_url":"https://api.github.com/users/DiagonalArg/gists{/gist_id}","starred_url":"https://api.github.com/users/DiagonalArg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/DiagonalArg/subscriptions","organizations_url":"https://api.github.com/users/DiagonalArg/orgs","repos_url":"https://api.github.com/users/DiagonalArg/repos","events_url":"https://api.github.com/users/DiagonalArg/events{/privacy}","received_events_url":"https://api.github.com/users/DiagonalArg/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":14,"created_at":"2016-07-10T07:17:20Z","updated_at":"2016-07-30T19:54:24Z","closed_at":null,"body":"sshuttle-master is running fine for TCP.  Output appears to indicate that with --method=tproxy it is accepting/sending UDP, but that doesn't seem to be the case.  I find I am unable to ping anything and already open connections are shut down.\r\n\r\n    sudo SSH_AUTH_SOCK=\"$SSH_AUTH_SOCK\" su                                                                                                                   \r\n    ip route add local default dev lo table 100\r\n    ip rule add fwmark 1 lookup 100\r\n    ./run --method=tproxy --disable-ipv6 -vvv --pidfile=/tmp/sshuttle.pid -r user@server.com 0/0 -x <server.ip>\r\n\r\n[Output](https://github.com/sshuttle/sshuttle/files/355882/sshuttleout.git.txt).  \r\n\r\nI notice this line in the output: `/proc/net/route: No such file or directory`.  It's odd because that file does exist.\r\n\r\n192.168.10.1 is the router, and 192.168.10.10 is my machine.\r\n\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/sshuttle/sshuttle/issues/comments/236386813","html_url":"https://github.com/sshuttle/sshuttle/issues/106#issuecomment-236386813","issue_url":"https://api.github.com/repos/sshuttle/sshuttle/issues/106","id":236386813,"user":{"login":"vieira","id":207460,"avatar_url":"https://avatars.githubusercontent.com/u/207460?v=3","gravatar_id":"","url":"https://api.github.com/users/vieira","html_url":"https://github.com/vieira","followers_url":"https://api.github.com/users/vieira/followers","following_url":"https://api.github.com/users/vieira/following{/other_user}","gists_url":"https://api.github.com/users/vieira/gists{/gist_id}","starred_url":"https://api.github.com/users/vieira/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vieira/subscriptions","organizations_url":"https://api.github.com/users/vieira/orgs","repos_url":"https://api.github.com/users/vieira/repos","events_url":"https://api.github.com/users/vieira/events{/privacy}","received_events_url":"https://api.github.com/users/vieira/received_events","type":"User","site_admin":false},"created_at":"2016-07-30T19:54:24Z","updated_at":"2016-07-30T19:54:24Z","body":"@DiagonalArg Not being an expert in tproxy I have tried a few things today and managed to get it working with 0/0 as long as I use the right combination of excludes `-x <server_ip> -x <client_ip>` where `<client_ip>` is the IP of the client connecting via ssh to the server.\r\n\r\nIn my tests I was connecting over the internet so I set it to the client public IP. If your server is in the same network you should probably use the IP of the client in that same network.\r\n\r\nIf you don't have physical access to the client and are connecting to it via, e.g., ssh, to start sshuttle you also have to exclude the IP of the machine you are connecting from, in my case, the public IP of my laptop, otherwise the ssh connection will be closed as soon as the firewall rules are set (I end up with `-x <server_ip> -x <client_ip> -x <laptop_ip>`).\r\n\r\nLet me know if this also works for you. Tested on Ubuntu 16.04.1."}}
{"actor":{"display_login":"vieira"}}