Connects/routes perfectly but after 5 minutes connections revert to normal route?

[GoogleCodeExporter]

What steps will reproduce the problem?

1. Connect Putty to server and enable tunnel
2. Start badvpn-tun2socks routing through local proxy
3. Add route tables to direct traffic
4. Connect to various sites to verify the connection
5. Wait a few minutes, close browser then try again

What is the expected output? What do you see instead?

When I first connect as described in the doc 
(https://code.google.com/p/badvpn/wiki/tun2socks) the results are as expected. 
I can for example see that my IP changes using various IP checking websites. 
All works fantasticly!

After about 5 minutes however I notice that my IP has returned back to its real 
IP and it appears that connections are no longer being routed.

I've checked the route table and confirmed that my route is still active and 
that the tun2socks program is running and that the socks tunnel is still there.

I cannot think of why this would happen. It is almost like the route table is 
ignoring its own rules?


What version of the product are you using? On what operating system?

1.999.127rc1

Any idea what could be going on?

Many thanks!

Original issue reported on code.google.com by mi...@wangled.com on 11 Mar 2013 at 4:23

[GoogleCodeExporter]

I've seen this happen on Windows 7 (but not XP). I'm sorry but I have no idea 
about the cause, it seems external to tun2socks, that is, the OS just stops 
routing packets into tun2socks. You can try playing with stuff in Network 
Connection and Windows Firewall, and check the Windows Event Log.

Original comment by ambr...@gmail.com on 11 Mar 2013 at 4:31

• Changed state: Accepted

[GoogleCodeExporter]

Yes, this is on Windows 7.

I'm looking at my routing tables and as you say it seems that Windows is just 
ignoring them.

What about removing the other 0.0.0.0 route, essentially meaning that all other 
traffic must go through 10.0.0.2?

Original comment by mi...@wangled.com on 11 Mar 2013 at 4:33

[GoogleCodeExporter]

Monitoring the virtual network interface with Wireshark may also provide some 
hints. One suspicion I have is that something in Windows is deciding that the 
route doesn't work and disables it silently.

Original comment by ambr...@gmail.com on 11 Mar 2013 at 4:33

[GoogleCodeExporter]

Yes, removing the default route entry does the job. I've now been connected for 
about 10 minutes and connections are still going through as they should.

It looks like it is something MS changed in their implementation from Vista 
onwards:

http://serverfault.com/questions/255799/windows-vista-and-7-dont-honor-routing-t
able-metric

Apart from that tun2socks works great by the way.. very smooth!

Original comment by mi...@wangled.com on 11 Mar 2013 at 4:45

[GoogleCodeExporter]

Ok, I guess there's nothing that can be done from tun2socks about this problem.

Original comment by ambr...@gmail.com on 11 Mar 2013 at 4:48

• Changed state: WontFix

[GoogleCodeExporter]

Issue 9 has been merged into this issue.

Original comment by ambr...@gmail.com on 24 Apr 2013 at 11:10

[GoogleCodeExporter]

Issue 9 has been merged into this issue.

Original comment by ambr...@gmail.com on 24 Apr 2013 at 11:23

[GoogleCodeExporter]

Issue 9 has been merged into this issue.

Original comment by ambr...@gmail.com on 24 Apr 2013 at 11:35

[GoogleCodeExporter]

Issue 9 has been merged into this issue.

Original comment by ambr...@gmail.com on 24 Apr 2013 at 12:04

[GoogleCodeExporter]

Issue 9 has been merged into this issue.

Original comment by ambr...@gmail.com on 24 Apr 2013 at 12:13

[GoogleCodeExporter]

Issue 9 has been merged into this issue.

Original comment by ambr...@gmail.com on 24 Apr 2013 at 12:16

[GoogleCodeExporter]

Issue 9 has been merged into this issue.

Original comment by ambr...@gmail.com on 24 Apr 2013 at 1:19

[GoogleCodeExporter]

Issue 9 has been merged into this issue.

Original comment by ambr...@gmail.com on 24 Apr 2013 at 1:20