wireguard-go/ip.go

package main

import (
	"net"
)

const (
	IPv4offsetTotalLength = 2
	IPv4offsetSrc         = 12
	IPv4offsetDst         = IPv4offsetSrc + net.IPv4len
)

const (
	IPv6offsetPayloadLength = 4
	IPv6offsetSrc           = 8
	IPv6offsetDst           = IPv6offsetSrc + net.IPv6len
)
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 19:48:15 +00:00			`package main`

			`import (`
			`"net"`
			`)`

			`const (`
Fixed cookie reply processing bug 2017-07-07 11:47:09 +00:00			`IPv4offsetTotalLength = 2`
			`IPv4offsetSrc = 12`
			`IPv4offsetDst = IPv4offsetSrc + net.IPv4len`
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 19:48:15 +00:00			`)`

			`const (`
Fixed cookie reply processing bug 2017-07-07 11:47:09 +00:00			`IPv6offsetPayloadLength = 4`
			`IPv6offsetSrc = 8`
			`IPv6offsetDst = IPv6offsetSrc + net.IPv6len`
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 19:48:15 +00:00			`)`