tun2socks - Assertion failed - ASSERT(client->socks_send_prev_buf_used > 0)
GoogleCodeExporter opened this issue · 2 comments
GoogleCodeExporter commented
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
Original issue reported on code.google.com by thir...@gmail.com on 24 Apr 2011 at 1:01
GoogleCodeExporter commented
Thank you for reporting this bug. I'm sorry about that; something strange must
have been going through my head :)
I've fixed it:
http://code.google.com/p/badvpn/source/detail?r=544
A new stable release (1.999.105.2) is available in Downloads with this bug
fixed.
Original comment by ambr...@gmail.com on 24 Apr 2011 at 9:50
- Changed state: Fixed
GoogleCodeExporter commented
Fixed now, I confirm ;)
Original comment by thir...@gmail.com on 24 Apr 2011 at 1:37