wireguard-go/go.mod

module golang.zx2c4.com/wireguard

go 1.16

require (
	golang.org/x/crypto v0.0.0-20201221181555-eec23a3978ad
	golang.org/x/net v0.0.0-20201224014010-6772e930b67b
	golang.org/x/sys v0.0.0-20210105210732-16f7687f5001
	gvisor.dev/gvisor v0.0.0-20210109011639-2fb7a49fea98
)
Change package path 2019-02-18 03:44:41 +00:00			`module golang.zx2c4.com/wireguard`
Switch to go modules 2018-10-09 16:11:36 +00:00
device: receive: do not exit immediately on transient UDP receive errors Some users report seeing lines like: > Routine: receive incoming IPv4 - stopped Popping up unexpectedly. Let's sleep and try again before failing, and also log the error, and perhaps we'll eventually understand this situation better in future versions. Because we have to distinguish between the socket being closed explicitly and whatever error this is, we bump the module to require Go 1.16. Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com> 2021-01-08 13:25:37 +00:00			`go 1.16`
windows: use proper constants from updated x/sys 2019-04-12 23:58:53 +00:00
Switch to go modules 2018-10-09 16:11:36 +00:00			`require (`
device: receive: do not exit immediately on transient UDP receive errors Some users report seeing lines like: > Routine: receive incoming IPv4 - stopped Popping up unexpectedly. Let's sleep and try again before failing, and also log the error, and perhaps we'll eventually understand this situation better in future versions. Because we have to distinguish between the socket being closed explicitly and whatever error this is, we bump the module to require Go 1.16. Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com> 2021-01-08 13:25:37 +00:00			`golang.org/x/crypto v0.0.0-20201221181555-eec23a3978ad`
			`golang.org/x/net v0.0.0-20201224014010-6772e930b67b`
			`golang.org/x/sys v0.0.0-20210105210732-16f7687f5001`
tun: add tcpip stack tunnel abstraction This allows people to initiate connections over WireGuard without any underlying operating system support. I'm not crazy about the trash it adds to go.sum, but the code this actually adds to the binaries seems contained to the gvisor repo. For the TCP/IP implementation, it uses gvisor. And it borrows some internals from the Go standard library's resolver in order to bring Dial and DialContext to tun_net, along with the LookupHost helper function. This allows for things like HTTP2-over-TLS to work quite well: package main import ( "io" "log" "net" "net/http" "golang.zx2c4.com/wireguard/device" "golang.zx2c4.com/wireguard/tun" ) func main() { tun, tnet, err := tun.CreateNetTUN([]net.IP{net.ParseIP("192.168.4.29")}, []net.IP{net.ParseIP("8.8.8.8"), net.ParseIP("8.8.4.4")}, 1420) if err != nil { log.Panic(err) } dev := device.NewDevice(tun, &device.Logger{log.Default(), log.Default(), log.Default()}) dev.IpcSet(`private_key=a8dac1d8a70a751f0f699fb14ba1cff7b79cf4fbd8f09f44c6e6a90d0369604f public_key=25123c5dcd3328ff645e4f2a3fce0d754400d3887a0cb7c56f0267e20fbf3c5b endpoint=163.172.161.0:12912 allowed_ip=0.0.0.0/0 `) dev.Up() client := http.Client{ Transport: &http.Transport{ DialContext: tnet.DialContext, }, } resp, err := client.Get("https://www.zx2c4.com/ip") if err != nil { log.Panic(err) } body, err := io.ReadAll(resp.Body) if err != nil { log.Panic(err) } log.Println(string(body)) } Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com> 2021-01-11 15:28:12 +00:00			`gvisor.dev/gvisor v0.0.0-20210109011639-2fb7a49fea98`
Switch to go modules 2018-10-09 16:11:36 +00:00			`)`