wireguard-openbsd/etc/protocols, branch jd/queueboosts WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/etc/protocols?h=jd%2Fqueueboosts 2014-07-12T14:38:38Z Sync with IANA. 2014-07-12T14:38:38Z ajacoutot ajacoutot@openbsd.org 2014-07-12T14:38:38Z urn:sha1:dbce27bcfd7da62bd66851f99d86c0774305ee08 "fine" claudio@ deraadt@ Sync protocols 43 (ipv6-route) & 44 (ipv6-frag) names with IANA database. 2011-09-08T19:30:29Z matthieu matthieu@openbsd.org 2011-09-08T19:30:29Z urn:sha1:e031e40373bab940000a1f7a499ffc0d94a04970 ok henning@, bluhm@ Add (again) support for divert sockets. They allow you to: 2009-10-04T16:08:37Z michele michele@openbsd.org 2009-10-04T16:08:37Z urn:sha1:d85f7bc16ff4db5aedffd92a6397af819385204f - queue packets from pf(4) to a userspace application - reinject packets from the application into the kernel stack. The divert socket can be bound to a special "divert port" and will receive every packet diverted to that port by pf(4). The pf syntax is pretty simple, e.g.: pass on em0 inet proto tcp from any to any port 80 divert-packet port 1 A lot of discussion have happened since my last commit that resulted in many changes and improvements. I would *really* like to thank everyone who took part in the discussion especially canacar@ who spotted out which are the limitations of this approach. OpenBSD divert(4) is meant to be compatible with software running on top of FreeBSD's divert sockets even though they are pretty different and will become even more with time. discusses with many, but mainly reyk@ canacar@ deraadt@ dlg@ claudio@ beck@ tested by reyk@ and myself ok reyk@ claudio@ beck@ manpage help and ok by jmc@ zap duplicate 2004-05-07T16:27:23Z henning henning@openbsd.org 2004-05-07T16:27:23Z urn:sha1:29e9e94ca1b28522838e7997071611c365409544 From: Myk Taylor <myk@ucla.edu> Change pfsync IP protocol and multicast group numbers. 2003-12-17T21:36:17Z mcbride mcbride@openbsd.org 2003-12-17T21:36:17Z urn:sha1:f580e9d770a530665a841d6c50128e1ea2ec5cba IPPROTO_PFSYNC -> 240 INADDR_PFSYNC_GROUP -> 224.0.0.240 ok deraadt@ Add pfsync. 2003-12-15T07:15:44Z mcbride mcbride@openbsd.org 2003-12-15T07:15:44Z urn:sha1:1f3f02ce8ef04b44f838f4a3f2e0e800d416833d ok deraadt@ Common Address Redundancy Protocol 2003-10-17T21:04:57Z mcbride mcbride@openbsd.org 2003-10-17T21:04:57Z urn:sha1:c05683a61744ff285c243f7a856485b47beaa13f Allows multiple hosts to share an IP address, providing high availability and load balancing. Based on code by mickey@, with additional help from markus@ and Marco_Pfatschbacher@genua.de ok deraadt@ more up to date, some input by todd@ 2003-01-16T19:49:52Z rohee rohee@openbsd.org 2003-01-16T19:49:52Z urn:sha1:2af360a6ed309ab9aae93fbb8add1dca99061cf7 Add icmp6 as an alias for ipv6-icmp. This helps clear up confusion about 2002-12-30T22:17:03Z mcbride mcbride@openbsd.org 2002-12-30T22:17:03Z urn:sha1:5096359ad965c13a66ddcfa1649ce73573ea757f icmp protocol naming particularly with pfctl, since the manpage is icmp6(4) (not ipv6-icmp(4)). suggested by espie@, cleared with deraadt@, ok dhartmei@ update URL and fix a typo; David Krause 2002-12-11T12:35:53Z henning henning@openbsd.org 2002-12-11T12:35:53Z urn:sha1:6970ffaad2f5b21f1cc9d9d235c66bc331ddcfe7