cbnsndwch / badvpn Goto Github PK

Hi I am running windows 7 64bit when I try to initilise tun2socks I get the 
following error

C:\Program Files\OpenVPN\badvpn-1.999.128-win32\bin>badvpn-tun2socks --tundev ta
p0901:TUN:10.0.0.1:10.0.0.0:255.255.255.0 --netif-ipaddr 10.0.0.2 --netif-netmas
k 255.255.255.0 --socks-server-addr 127.0.0.1:1081 --loglevel 5
NOTICE(tun2socks): initializing BadVPN tun2socks 1.999.128
DEBUG(BReactor): Reactor initializing
DEBUG(BSignal): BSignal initializing
INFO(BTap): Looking for TAP-Win32 with component ID tap0901, name TUN
INFO(BTap): Opening device \\.\Global\{63378671-06D6-442B-B98C-766372863399}.tap

ERROR(BTap): DeviceIoControl(TAP_IOCTL_GET_MTU) failed
ERROR(tun2socks): BTap_Init failed
DEBUG(BReactor): Reactor freeing
NOTICE(tun2socks): exiting

Hi I am running windows 7 64bit when I try to initilise tun2socks I get the 
following error

C:\Program Files\OpenVPN\badvpn-1.999.128-win32\bin>badvpn-tun2socks --tundev ta
p0901:TUN:10.0.0.1:10.0.0.0:255.255.255.0 --netif-ipaddr 10.0.0.2 --netif-netmas
k 255.255.255.0 --socks-server-addr 127.0.0.1:1081 --loglevel 5
NOTICE(tun2socks): initializing BadVPN tun2socks 1.999.128
DEBUG(BReactor): Reactor initializing
DEBUG(BSignal): BSignal initializing
INFO(BTap): Looking for TAP-Win32 with component ID tap0901, name TUN
INFO(BTap): Opening device \\.\Global\{63378671-06D6-442B-B98C-766372863399}.tap

ERROR(BTap): DeviceIoControl(TAP_IOCTL_GET_MTU) failed
ERROR(tun2socks): BTap_Init failed
DEBUG(BReactor): Reactor freeing
NOTICE(tun2socks): exiting

What steps will reproduce the problem?
1. Install OpenVPN
2. Default name of device is something like "Local Area Connection 3"
3. Use that name to start tun2socks i.e.

badvpn-tun2socks --tundev tap0901:Local Area Connection 
1:10.0.0.1:10.0.0.0:255.255.255.0 --netif-ipaddr 10.0.0.2 --netif-netmask 
255.255.255.0 --socks-server-addr 127.0.0.1:1080

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

Should find the device and run but returns an error 'Failed to parse arguments'

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

1.999.127rc1


Because we cannot control the name that Windows gives to the device I would 
like to be able to put the default name into the tun2socks program and it work.

Is this  possible to fix?

Thanks

What steps will reproduce the problem?

DNS lookups are not sent through socks server


Is it possible to send DNS lookups through the SOCKS server so that they are 
also forwarded through the tunnel?

Thanks

What steps will reproduce the problem?
1. file_open("testfile","a") file;
2. file->write("abc");

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

Expect code to continue, but I get the following error:

/build/buildd/badvpn-1.999.127/ncd/modules/file_open.c:424 Assertion failed
Aborted (core dumped)

(The data is correctly appended to the file though).

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

badvpn-1.999.127 on ubuntu 12.04

What steps will reproduce the problem?

1. After reboot start tun2socks as normal
2. Start proxy server
3. Add/change routing

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

The traffic should go through the tunnel and then onto the socks proxy but 
instead the connection fails. The tun2socks route is the only route available 
so all connections simply fail until they decide to start working. I cannot see 
any pattern to this, it just appears to start working.

Once it works it will continue to work, even with restarting tun2socks until 
the system is rebooted again. Once it is rebooted the procedure must be started 
again.

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

1.999.127.rc1

Please provide any additional information below.

This problem is only on startup.. if I wait for say 10 mins, sometimes less and 
sometimes longer it eventually starts working.. without restarting tun2socks 
and using the exact same settings.

When it is not working I can successfully ping both the main gateway (10.5.0.1) 
and the second internal IP (10.5.0.2).

tun2socks just sits there saying entering event loop and waits.. if I keep 
disabling and reenabling the routing eventually it will successfully route. 
Sometimes restarting tun2socks is required, sometimes not.

The prog is being started with the following params:

 --tundev tap0901:ehvpn:10.5.0.1:10.5.0.0:255.255.255.0 --netif-ipaddr 10.5.0.2 --netif-netmask 255.255.255.0 --socks-server-addr 127.0.0.1:4021

Any my socks server is running and working on 127.0.0.1:4021.. the routing 
table is as follows:

----

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0         10.5.0.2    192.168.0.104     31
          8.8.8.8  255.255.255.255      192.168.0.1    192.168.0.104     30
    81.94.201.130  255.255.255.255      192.168.0.1    192.168.0.104     30
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
      192.168.0.0    255.255.255.0         On-link     192.168.0.104    281
    192.168.0.104  255.255.255.255         On-link     192.168.0.104    281
    192.168.0.255  255.255.255.255         On-link     192.168.0.104    281
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link     192.168.0.104    281
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link     192.168.0.104    281
===========================================================================

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!

I realise this is more of a request than a bug but I am not sure where requests 
should be posted?

What I'd really like to be able to do is exclude certain ports from the system. 
So for example a mail client connecting to IMAP or SMTP would bypass tun2socks 
and use the default gateway.

This is fairly easy to do in Linux but Windows does not offer any sort of per 
port routing.

I'm fairly sure it would be easy enough to have tun2socks detect those ports 
and do something different with them in case they are part of the exclusion 
list but where I'm getting stuck is the what..

Say a connection for port 25 comes in and tun2socks decides it should not send 
this connection through the SOCKS as far as I can tell there is no way for it 
to establish the connection as any attempt to make the connection directly will 
end up right back into tun2socks due to the system routing rules?

The only way I can think of is perhaps intercepting the packets with dest port 
25 from within tun2socks and forwarding them to another gateway kind of like an 
ip tables packet filter in linux..

That is where I'm getting stuck as packet processing goes beyond my knowledge 
of badvpn.

Is what I'm suggesting even possible?

I'm happy to look at the code if you could point me in the right direction?

Many thanks

Is it possible  to add SOCKS authentication to tun2socks?

Or is it possible/supposed to be via NCD?

What steps will reproduce the problem?
1. OpenVPN installed & Tun adapter configured to 10.0.0.1 / 255.255.255.0
2. Run badvpn-tun2sock with params below. (tunnel created with putty, and its 
working)
3. route add [single_ip] mask 255.255.255.255 10.0.0.2 metric 1
4. telnet [single_ip] 80

What is the expected output? What do you see instead?
Working connection.
Telnet connects, but after a single keypress it disconnects (no message)

What version of the product are you using? On what operating system?
win32-1.999.127rc1

Please provide any additional information below.

D:\badvpn-win32-1.999.127rc1\bin>badvpn-tun2socks.exe --tundev 
"tap0901:tundev:10.0.0.1:10.0.0.0:255.255.255.0" --netif-ipaddr 10.0.0.2 
--netif-netmask 255.255.255.0 --socks-server-addr 127.0.0.1:8080 --loglevel 4
NOTICE(tun2socks): initializing BadVPN tun2socks 1.999.127rc1
INFO(BTap): Looking for TAP-Win32 with component ID tap0901, name tundev
INFO(BTap): Opening device \\.\Global\{2149300B-D86B-46C0-8F0E-10D3D906BF13}.tap

INFO(BTap): Device opened
NOTICE(tun2socks): entering event loop
ERROR(BConnection): faild to get ConnectEx
ERROR(BSocksClient): BConnector_Init failed
ERROR(tun2socks): listener accept: BSocksClient_Init failed

How can i log the sites visited by badvpn?

This is not a issue!

I used tun2socks + ssh perfactly,  now I want to modify some 

function to fix my requests. Can you tell me how to build just tun2socks without

 any other software on Windows system ? 

What steps will reproduce the problem?
1. ssh -D 1234 user@server
2. openvpn --mktun --dev tun0 --user root
3. /sbin/ip addr add 10.0.0.1/24 dev tun0
4. route add server gw 10.0.5.1 metric 5
5. route add default gw 10.0.0.2 metric 6
6. delete default gw 10.0.5.1
7. ifconfig tun0 up
8. ./badvpn-tun2socks --tundev tun0 --netif-ipaddr 10.0.0.2 --netif-netmask 
255.255.255.0 --socks-server-addr 127.0.0.1:1234
9. Go to http://speedtest.net/ under Firefox 4.0 wait for upload test... then 
tun2socks should assert.


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

/home/thireus/Bureau/badvpn-1.999.105.1/tun2socks# ./badvpn-tun2socks --tundev 
tun0 --netif-ipaddr 10.0.0.2 --netif-netmask 255.255.255.0 --socks-server-addr 
127.0.0.1:1234
NOTICE(tun2socks): initializing BadVPN tun2socks 1.999.105.1
NOTICE(tun2socks): entering event loop
INFO(tun2socks): 00001 (74.209.160.12:80 10.0.0.1:41705): accepted
NOTICE(BSocksClient): connection failed (7)
INFO(tun2socks): 00001 (74.209.160.12:80 10.0.0.1:41705): SOCKS error
INFO(tun2socks): 00001 (74.209.160.12:80 10.0.0.1:41708): accepted
NOTICE(BSocksClient): connection failed (7)
INFO(tun2socks): 00001 (74.209.160.12:80 10.0.0.1:41708): SOCKS error
INFO(tun2socks): 00001 (74.125.230.78:80 10.0.0.1:56774): accepted
NOTICE(BSocksClient): connection failed (7)
INFO(tun2socks): 00001 (74.125.230.78:80 10.0.0.1:56774): SOCKS error
INFO(tun2socks): 00001 (74.209.160.12:80 10.0.0.1:41711): accepted
INFO(tun2socks): 00001 (74.209.160.12:80 10.0.0.1:41711): SOCKS up
INFO(tun2socks): 00002 (93.184.221.133:80 10.0.0.1:49477): accepted
INFO(tun2socks): 00003 (93.184.221.133:80 10.0.0.1:49478): accepted
INFO(tun2socks): 00004 (93.184.221.133:80 10.0.0.1:49479): accepted
INFO(tun2socks): 00005 (93.184.221.133:80 10.0.0.1:49480): accepted
INFO(tun2socks): 00006 (93.184.221.133:80 10.0.0.1:49481): accepted
INFO(tun2socks): 00006 (93.184.221.133:80 10.0.0.1:49477): SOCKS up
INFO(tun2socks): 00006 (93.184.221.133:80 10.0.0.1:49478): SOCKS up
INFO(tun2socks): 00006 (93.184.221.133:80 10.0.0.1:49481): SOCKS up
INFO(tun2socks): 00006 (93.184.221.133:80 10.0.0.1:49480): SOCKS up
INFO(tun2socks): 00006 (93.184.221.133:80 10.0.0.1:49479): SOCKS up
INFO(tun2socks): 00007 (74.125.230.94:443 10.0.0.1:39823): accepted
INFO(tun2socks): 00007 (74.125.230.94:443 10.0.0.1:39823): SOCKS up
INFO(tun2socks): 00007 (74.209.160.12:80 10.0.0.1:41711): client closed
INFO(tun2socks): 00007 (74.209.160.12:80 10.0.0.1:41725): accepted
INFO(tun2socks): 00008 (74.209.160.12:80 10.0.0.1:41727): accepted
INFO(tun2socks): 00008 (74.209.160.12:80 10.0.0.1:41725): SOCKS up
INFO(tun2socks): 00008 (74.209.160.12:80 10.0.0.1:41727): SOCKS up
INFO(tun2socks): 00008 (74.209.160.12:80 10.0.0.1:41725): client closed
NOTICE(StreamSocketSource): Connection closed
INFO(tun2socks): 00007 (93.184.221.133:80 10.0.0.1:49477): SOCKS closed
NOTICE(StreamSocketSource): Connection closed
INFO(tun2socks): 00006 (93.184.221.133:80 10.0.0.1:49478): SOCKS closed
NOTICE(StreamSocketSource): Connection closed
INFO(tun2socks): 00005 (93.184.221.133:80 10.0.0.1:49480): SOCKS closed
NOTICE(StreamSocketSource): Connection closed
INFO(tun2socks): 00004 (93.184.221.133:80 10.0.0.1:49479): SOCKS closed
NOTICE(StreamSocketSource): Connection closed
INFO(tun2socks): 00003 (93.184.221.133:80 10.0.0.1:49481): SOCKS closed
INFO(tun2socks): 00002 (74.209.160.12:80 10.0.0.1:41727): client closed
INFO(tun2socks): 00002 (91.126.137.226:80 10.0.0.1:50982): accepted
INFO(tun2socks): 00002 (91.126.137.226:80 10.0.0.1:50982): SOCKS up
INFO(tun2socks): 00003 (89.82.180.22:80 10.0.0.1:52035): accepted
INFO(tun2socks): 00003 (89.82.180.22:80 10.0.0.1:52035): SOCKS up
INFO(tun2socks): 00004 (83.167.35.96:80 10.0.0.1:43882): accepted
INFO(tun2socks): 00004 (83.167.35.96:80 10.0.0.1:43882): SOCKS up
INFO(tun2socks): 00005 (91.126.224.101:80 10.0.0.1:44513): accepted
INFO(tun2socks): 00005 (91.126.224.101:80 10.0.0.1:44513): SOCKS up
INFO(tun2socks): 00006 (91.126.221.2:80 10.0.0.1:41991): accepted
INFO(tun2socks): 00006 (91.126.221.2:80 10.0.0.1:41991): SOCKS up
INFO(tun2socks): 00006 (91.126.221.2:80 10.0.0.1:41991): client closed
INFO(tun2socks): 00006 (91.126.221.2:80 10.0.0.1:41993): accepted
INFO(tun2socks): 00006 (91.126.221.2:80 10.0.0.1:41993): SOCKS up
INFO(tun2socks): 00006 (91.126.221.2:80 10.0.0.1:41993): client closed
INFO(tun2socks): 00006 (91.126.221.2:80 10.0.0.1:41995): accepted
INFO(tun2socks): 00006 (91.126.221.2:80 10.0.0.1:41995): SOCKS up
NOTICE(StreamSocketSource): Connection closed
INFO(tun2socks): 00006 (91.126.221.2:80 10.0.0.1:41995): SOCKS closed
INFO(tun2socks): 00006 (91.126.221.2:80 10.0.0.1:41995): waiting until buffered 
data is sent to client
INFO(tun2socks): 00006 (91.126.221.2:80 10.0.0.1:41995): removing after SOCKS 
went down
NOTICE(StreamSocketSource): Connection closed
INFO(tun2socks): 00005 (91.126.137.226:80 10.0.0.1:50982): SOCKS closed
INFO(tun2socks): 00005 (89.82.180.22:80 10.0.0.1:52047): accepted
INFO(tun2socks): 00005 (89.82.180.22:80 10.0.0.1:52047): SOCKS up
NOTICE(StreamSocketSource): Connection closed
INFO(tun2socks): 00005 (91.126.224.101:80 10.0.0.1:44513): SOCKS closed
INFO(tun2socks): 00005 (89.82.180.22:80 10.0.0.1:52049): accepted
INFO(tun2socks): 00006 (89.82.180.22:80 10.0.0.1:52051): accepted
INFO(tun2socks): 00006 (89.82.180.22:80 10.0.0.1:52049): SOCKS up
INFO(tun2socks): 00006 (89.82.180.22:80 10.0.0.1:52051): SOCKS up
/home/thireus/Bureau/badvpn-1.999.105.1/tun2socks/tun2socks.c:1160 Assertion 
failed
Abandon


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

badvpn-1.999.105.1.tar.bz2
2.6.35-28-generic Ubuntu x86_64 GNU/Linux

Please provide any additional information below.

Assertion failed happens everytime it tries to make the upload test :/ There's 
something wrong with buffering :s

Is UDP support for tun2socks possible anytime soon?

regards,
Emanuel

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

Please provide any additional information below.

Hello, I use badvpn-tun2socks.exe on windows xp(computer A) and a plink.exe as 
socks client, install openssh and run sshd on centos (computer B), where dose I 
run the badvpn-udpgw at ? I want to all TCP and DNS traffic pass through the 
sshd using tun2socks, how can I have the [remote DNS resolve] function like 
Proxifier program?

This is not a issue!

I used tun2socks + ssh perfactly,  now I want to modify some 

function to fix my requests. Can you tell me how to build just tun2socks without

 any other software on Windows system ? 

Is there a step-by-step tutorial for the Windows version? 

What steps will reproduce the problem?
1. call net.ipv4.dhcp on a tun device created with openvpn

What version of the product are you using? On what operating system?
badvpn-ncd version 1.999.128

Please provide any additional information below.

I want to find the default gateway of a tun device created with openvpn, so 
that I can update routing tables appropriately.
I try using net.ipv4.dhcp("tun0") and I get the following error: 
BDHCPClient_Init failed

I appreciate that this is not an issue as such and more of a request but I am 
not sure how to submit requests to the system.

I am running tun2socks on a server and routing all VPN traffic through. This 
works great and I am very happy.

Each user that connects to my VPN is allocated a unique internal IP, for 
example 192.168.1.100, the next user getting 192.168.1.101. 

For logging purposes I need to have that IP address passed onto my SOCKS 
server. I was hoping that tun2socks would use that same address to connect to 
the SOCKS so I could just log the source IP but it always comes through as 
127.0.0.1 which is to be expected I suppose.

My question is, is there any way to send over that IP with the connection? 
Either by 1) using the source IP as the IP to connect to the SOCKS or 2) 
sending the source IP as part of the user/pass info?

Thanks

[deleted issue]

Hi, I'm Ezio, and I've a problem with tun2socks. I've tryed different 
configurations and the tun2socks always stuck with this debug message:

-----
C:\Utils\badvpn-win32\bin>badvpn-tun2socks.exe --tundev 
"tap0901:tap:10.0.0.1:10.0.0.0:255.255.255.0" --netif-ipaddr 10.0.0.2 
--netif-netmask 255.255.255.0 --socks-server-addr 192.168.33.252:1080 
--loglevel 5
NOTICE(tun2socks): initializing BadVPN tun2socks 1.999.111
DEBUG(BReactor): Reactor initializing
DEBUG(BSignal): BSignal initializing
INFO(BTap): Looking for TAP-Win32 with component ID tap0901, name tap
INFO(BTap): Opening device \\.\Global\{BCDB3D4A-FF30-4C40-B02D-9149E9A68B5D}.tap

INFO(BTap): Device opened
NOTICE(tun2socks): entering event loop
DEBUG(BReactor): Entering event loop
DEBUG(tun2socks): lwip init
DEBUG(tun2socks): netif func init
DEBUG(BReactor): GetQueuedCompletionStatus timed out
DEBUG(BReactor): Dispatching timer
DEBUG(tun2socks): TCP timer
DEBUG(BReactor): GetQueuedCompletionStatus timed out
DEBUG(BReactor): Dispatching timer
DEBUG(tun2socks): TCP timer
DEBUG(BReactor): GetQueuedCompletionStatus timed out
DEBUG(BReactor): Dispatching timer
DEBUG(tun2socks): TCP timer
... and so on
-----

The Os that I've used is a Windows 7 Professional 64bit SP0 with UAC enabled. 
I've tryed to change this variables when I've tryed to get tun2socks work, on 
every combination:
- I've launched the tun2socks from administrative shell and from the user's one.
- I've used the OpenVPN tap device (that on my system is called "OpenVPN") and 
a new tap device created from "OpenVPN/Utility/Add a new TAP virtual ethernet 
adapter", called "tap"
- I've used the suggested network for tap device (10.0.0.0) and another private 
network (the one that I want to use: 192.168.254.0)
- I've used a "lan" socks5 proxy (192.168.33.252:1080) and a local ssh socks5 
proxy (127.0.0.1:1080)

tun2socks stucks with the message reported before, and the tap device specified 
is shown in connection manager as connected, but without ip address, mask and 
gw. The packets count is also 0 for in and 0 for out.

bye,
Ezio