wireguard-go/src/tun.go

package main

type TUNDevice interface {
	Read([]byte) (int, error)
	Write([]byte) (int, error)
	Name() string
	MTU() int
}
Beginning work on TUN interface And outbound routing I am not entirely convinced the use of net.IP is a good idea, since the internal representation of net.IP is a byte slice and all constructor functions in "net" return 16 byte slices (padded for IPv4), while the use in this project uses 4 byte slices. Which may be confusing. 2017-06-04 21:48:15 +02:00			`package main`

Work on UAPI Cross-platform API (get operation) Handshake initiation creation process Outbound packet flow Fixes from code-review 2017-06-28 23:45:45 +02:00			`type TUNDevice interface {`
Beginning work on TUN interface And outbound routing I am not entirely convinced the use of net.IP is a good idea, since the internal representation of net.IP is a byte slice and all constructor functions in "net" return 16 byte slices (padded for IPv4), while the use in this project uses 4 byte slices. Which may be confusing. 2017-06-04 21:48:15 +02:00			`Read([]byte) (int, error)`
			`Write([]byte) (int, error)`
			`Name() string`
Handshake negotiation functioning 2017-07-01 23:29:22 +02:00			`MTU() int`
Beginning work on TUN interface And outbound routing I am not entirely convinced the use of net.IP is a good idea, since the internal representation of net.IP is a byte slice and all constructor functions in "net" return 16 byte slices (padded for IPv4), while the use in this project uses 4 byte slices. Which may be confusing. 2017-06-04 21:48:15 +02:00			`}`