Will it support windows? #2

TongxiJi · 2016-09-01T15:27:03Z

I want to use it to work with shadowsocks.That'll be wanderful.

yinghuocho · 2016-09-02T00:43:47Z

I did't test on Windows. I guess the package itself works, and the command in bin directory lacks a Windows implementation to open a tun device and returns a os.File struct. I will look at this. You can also try to play with it. Thanks.

TongxiJi · 2016-09-02T01:38:06Z

Thanks a lot.
I'm look forward to the windows version!

yinghuocho · 2016-12-02T16:35:19Z

@TongxiJi gotun2socks now partially works on Windows. I tested on Windows XP, the basic function works, but very slow. It seems not working on Windows 10. That said, it is not ready to use before I find time to figure out these issues. But you can take a look and welcome to comment or suggest features.

dogfight360 · 2016-12-02T17:55:55Z

in Windows 10 does not work
Is it possible to increase ICMP transport support in the future?

yinghuocho · 2016-12-02T19:02:24Z

@wu360463231 Yes, I just tried Windows 10, the tun device can be opened, but no packet comes. I need to figure out the problem.

I can think of one way to support ICMP while keeping the tunnel protocol as socks. Let gotun2socks dispatches ICMP messages to a local ICMP-client daemon/module. The ICMP-handle-client daemon/module then encapsulates ICMP messages into a socks session connecting to a remote ICMP-handle-server running on the VPN server. The ICMP-handle-server forwards ICMP messages and relays responses through the socks session. This is similar as how tun2socks supports UDP.

dogfight360 · 2016-12-02T19:38:25Z

@yinghuocho Yes, the firewall does not have any connection information
When the application exits, the firewall will act only when port 2222 is connected

yinghuocho · 2016-12-06T10:29:58Z

@TongxiJi @wu360463231 Now gotun2socks should work on Windows. You can have a try. Please let me know if you have any problem.

dogfight360 · 2016-12-06T13:31:04Z

@yinghuocho
UDP work properly, the game test
TCP seems to have problems with some connection processing, the error log:

panic: runtime error: slice bounds out of range

goroutine 1 [running]:
panic(0x5c0f80, 0xc042004060)
C:/Go/src/runtime/panic.go:500 +0x1af
github.com/yinghuocho/gotun2socks/tun.(*winTapDev).Read(0xc04210a000, 0xc042088c00, 0x5dc, 0x5dc, 0xc042565cd0, 0xc0420a80f0, 0x0)
g:/GOPATH/src/github.com/yinghuocho/gotun2socks/tun/tun_windows.go:308 +0x388
github.com/yinghuocho/gotun2socks.(*Tun2Socks).Run(0xc04207ab00)
g:/GOPATH/src/github.com/yinghuocho/gotun2socks/gotun2socks.go:120 +0x15e
main.main()
g:/GOPATH/src/github.com/yinghuocho/gotun2socks/bin/gotun2socks/main.go:55 +0x964

dogfight360 · 2016-12-06T14:28:19Z

@yinghuocho

I deleted it (tun_windows.go line 307-310)

Works fine
exception should occur in this

  if nr > 14 {
  	if isStopMarker(data[14:nr], dev.addrIP, dev.gwIP) {
  		return 0, errors.New("received stop marker")
  	}

dogfight360 · 2016-12-06T16:28:50Z

Delete (tun_windows.go line: 307-310) no exceptions
But can not keeplive long time
The TCP connection will still be disconnected at some point in time

yinghuocho · 2016-12-06T20:31:14Z

@wu360463231 Thanks for the feedback. The bug causing the panic should be fixed now. Can you give some details about the TCP disconnection problem, are you chaining gotun2socks with shadowsocks ? I tested with browser to open some pages and videos, didn't notice unexpected TCP disconnection issues.

dogfight360 · 2016-12-07T06:13:32Z

Yes, I use shadowsocks
shadowsocks and gotun2socks logs do not see any information
today try to test on a more stable network
the TCP connection maybe disconnected because GFW, or China Mobile

yinghuocho · 2016-12-14T09:10:57Z

@wu360463231 how do you config shadowsocks connect with gotun2socks to forward UDP traffic? I tried to use shadowsocks-libev, the UDP relay did't work.

Thanks.

dogfight360 · 2016-12-14T09:16:31Z

@yinghuocho I use the shadowsocksR C # windows client

missdeer · 2017-01-18T03:32:31Z

@yinghuocho AFAIK, shadowsocks-libev's UDP relay feature is not compatible with shadowsocksR server (aka. python version), but C# windows client's implementation does.

yinghuocho · 2017-01-18T16:39:41Z

@missdeer Yes, I also noticed that shadowsocks-libev's UDP relay does not comply with the RFC. It closes UDP Associate's corresponding TCP connection prematurely. After I commented a few lines of code, it worked well.

yiqing95 · 2017-10-22T03:27:05Z

E:\yiqing-go\src\github.com\yinghuocho\gotun2socks\bin\gotun2socks>gotun2socks.exe --local-socks-addr=192.168.0.100:9666 --tun-device=tap0901:SSTAP:10.0.0.1:10.0.0.0:255.255.255.0
2017/10/22 11:20:01 device component id: {4054C3DD-32C4-49B9-A5B2-0103872D5550}
2017/10/22 11:20:01 device name: SSTAP
2017/10/22 11:20:02 set SSTAP with net/mask: 10.0.0.2/255.255.255.0 through DHCP
2017/10/22 11:20:02 set SSTAP with dns: 8.8.8.8,8.8.4.4 through DHCP
2017/10/22 11:20:02 ipv6 packet
2017/10/22 11:20:03 ipv6 packet
2017/10/22 11:20:03 ipv6 packet
2017/10/22 11:20:03 ipv6 packet
2017/10/22 11:20:03 ipv6 packet
2017/10/22 11:20:03 ipv6 packet
2017/10/22 11:20:04 ipv6 packet
2017/10/22 11:20:04 ipv6 packet
2017/10/22 11:20:04 Unsupported packet: protocol 2
2017/10/22 11:20:04 ipv6 packet
2017/10/22 11:20:04 Unsupported packet: protocol 2
2017/10/22 11:20:04 ipv6 packet
2017/10/22 11:20:04 Unsupported packet: protocol 2
2017/10/22 11:20:04 Unsupported packet: protocol 2
2017/10/22 11:20:04 ipv6 packet
2017/10/22 11:20:04 ipv6 packet
2017/10/22 11:20:04 tracking 1 UDP connections
2017/10/22 11:20:05 error to send UDP packet to relay: write udp 192.168.0.100:59392->127.0.0.1:16764: wsasendto: The requested address is not valid in its context.
2017/10/22 11:20:05 tracking 0 UDP connections

...
2017/10/22 11:21:03 Unsupported packet: protocol 2
2017/10/22 11:21:03 ipv6 packet
2017/10/22 11:21:03 Unsupported packet: protocol 2
2017/10/22 11:21:03 ipv6 packet
2017/10/22 11:21:03 tracking 1 UDP connections
2017/10/22 11:21:03 Unsupported packet: protocol 2
2017/10/22 11:21:03 ipv6 packet
2017/10/22 11:21:03 error to send UDP packet to relay: write udp 192.168.0.100:57940->127.0.0.1:13889: wsasendto: The requested address is not valid in its context.
2017/10/22 11:21:03 tracking 0 UDP connections
2017/10/22 11:21:05 ipv6 packet
2017/10/22 11:21:28 tracking 1 UDP connections
2017/10/22 11:21:28 error to send UDP packet to relay: write udp 192.168.0.100:57945->127.0.0.1:62162: wsasendto: The requested address is not valid in its context.
2017/10/22 11:21:28 tracking 0 UDP connections

win10 platform

these errors mean are there something wrong with my socks5-server (not using the shadowsocks )?
or I give the wrong config options ?

plz help and give some advice on windows platform . ✌️ 🐰

txthinking · 2017-10-28T07:02:45Z

@yinghuocho

Yes, I also noticed that shadowsocks-libev's UDP relay does not comply with the RFC. It closes UDP Associate's corresponding TCP connection prematurely. After I commented a few lines of code, it worked well.

A UDP association terminates when the TCP connection that the UDP ASSOCIATE request arrived on terminates.

Client(1) <----socks5 protocol(2)----->Socks5 Server<----> Remote [<----> Remote...]

Tun is also a client.
I think we should strictly abide by the standards here.

yinghuocho mentioned this issue Dec 7, 2016

icmp support #4

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Will it support windows? #2

Will it support windows? #2

TongxiJi commented Sep 1, 2016

yinghuocho commented Sep 2, 2016

TongxiJi commented Sep 2, 2016

yinghuocho commented Dec 2, 2016

dogfight360 commented Dec 2, 2016

yinghuocho commented Dec 2, 2016

dogfight360 commented Dec 2, 2016

yinghuocho commented Dec 6, 2016

dogfight360 commented Dec 6, 2016

dogfight360 commented Dec 6, 2016

dogfight360 commented Dec 6, 2016

yinghuocho commented Dec 6, 2016

dogfight360 commented Dec 7, 2016

yinghuocho commented Dec 14, 2016

dogfight360 commented Dec 14, 2016

missdeer commented Jan 18, 2017

yinghuocho commented Jan 18, 2017

yiqing95 commented Oct 22, 2017

txthinking commented Oct 28, 2017 •

edited

Loading

Will it support windows? #2

Will it support windows? #2

Comments

TongxiJi commented Sep 1, 2016

yinghuocho commented Sep 2, 2016

TongxiJi commented Sep 2, 2016

yinghuocho commented Dec 2, 2016

dogfight360 commented Dec 2, 2016

yinghuocho commented Dec 2, 2016

dogfight360 commented Dec 2, 2016

yinghuocho commented Dec 6, 2016

dogfight360 commented Dec 6, 2016

dogfight360 commented Dec 6, 2016

dogfight360 commented Dec 6, 2016

yinghuocho commented Dec 6, 2016

dogfight360 commented Dec 7, 2016

yinghuocho commented Dec 14, 2016

dogfight360 commented Dec 14, 2016

missdeer commented Jan 18, 2017

yinghuocho commented Jan 18, 2017

yiqing95 commented Oct 22, 2017

txthinking commented Oct 28, 2017 • edited Loading

txthinking commented Oct 28, 2017 •

edited

Loading