wireguard-openbsd - WireGuard implementation for the OpenBSD kernel

	Commit message (Collapse)	Author	Age	Files	Lines
*	Switch to scapy with python 3.	bluhm	2020-12-25	1	-8/+8
\|
*	Use consistent address schema with local and remote machine. Fill	bluhm	2017-03-01	1	-5/+5
\| \| \| \|	variables with example IPs from my daily test run.
*	IPv6 packets with routing header 0 are dropped by pf, but answered	bluhm	2017-02-28	1	-0/+2
\| \| \| \| \|	with ICMP6 parameter problem by the network stack. This test expects the ICMP6 packets, so disable pf on the remote machine temporarily.
*	Do not use privileged or NFS source ports for UDP packets as inetd	bluhm	2017-01-18	1	-2/+2
\| \| \| \| \|	ignores such packets. This should avoid some sporadic failures. While there, use variable names consistently in all tests.
*	Fix tests: Restrict getpid() to lower 16 bit so that it can still	bluhm	2016-05-22	1	-1/+1
\| \| \| \| \|	be used as packet id. Now scapy calls nexthopmtu with this name explicitly in icmp structure.
*	Use a simpler expression to check the ether type in scapy. This	bluhm	2014-12-19	1	-1/+1
\| \| \| \|	makes the fragment tests work on FreeBSD. From Ilya Bakulin.
*	Adapt the IPv6 routing header type 0 tests to the current behaviour.	bluhm	2013-11-17	1	-12/+12
\| \| \| \| \| \| \| \|	As header scanning is back, there is always a icmp6 parameter problem response. Add tests that hide the routing header behind an atomic fragment header to get the RFC 5095 behaviour. One test puts the routing header into the second fragment so that it cannot be detected without reassembly.
*	Use scapy to test IPv6 packets with routing header type 0.	bluhm	2013-10-20	1	-0/+41