Closed GoogleCodeExporter closed 9 years ago
It appears that tun2socks is not receiving any packets from the operating
system. Have you followed tun2socks my guide on the wiki? It explicitly says
that you have to assign the right IP address to the TUN device yourself
(10.0.0.1 netmask 255.255.255.0 for the command line you posted), and it does
not appear you did so. You also set up the routes properly.
Please try the guide first and report problems after you're sure you did
exactly what it says.
Original comment by ambr...@gmail.com
on 21 Mar 2012 at 9:28
[deleted comment]
maskeye, in your case too the OS is not sending any packets into the Local
interface. You have to adjust the routing table properly. Either add the
route(s) you want manually, via the gateway 10.0.0.2, or configure it as a
default gateway in the IP configuration dialog for the Local interface. Anyway,
it would help if you provided your routing table (route print) and IP
configurations of both interfaces (write down or screenshot).
Original comment by ambr...@gmail.com
on 19 May 2012 at 12:11
maskeye, it's likely that your metrics are incorrect and that the OS is still
using the default gateway of "Local Area Connection". There are multiple ways
to achieve the desired routing; one is by forcing the new tun2socks route to
have a lower metric than the existing "Local Area Connection" route.
Original comment by ambr...@gmail.com
on 19 May 2012 at 12:13
Alternatively, you can remove the default gateway from "Local Area Connection"
and only have the tun2socks route. However this is inconvenient when you want
to not use tun2socks.
Original comment by ambr...@gmail.com
on 19 May 2012 at 12:15
It works great on my computer. I can share my ssh internet connection trough
wifi hotspot with this tiny tools. Just a little tricks and we can enjoy shared
ssh internet connection. Haturnuhuun mas bro..o
Original comment by ay1...@gmail.com
on 9 Sep 2013 at 5:13
Original issue reported on code.google.com by
ezio.bo...@gmail.com
on 21 Mar 2012 at 8:59