Date: Wed, 1 Jul 2015 19:27:43 +0300 From: Peter Pentchev <roam@ringlet.net> To: soc-status@FreeBSD.org Subject: Re: Status report: ng_ayiya - an AYIYA Netgraph node Message-ID: <20150701162743.GA3137@straylight.m.ringlet.net> In-Reply-To: <20150620164531.GB2937@straylight.m.ringlet.net> References: <20150620164531.GB2937@straylight.m.ringlet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--huq684BweRXVnRxX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi all, The goal of this project is to create a Netgraph node that acts as a link between a socket (TCP, UDP, SCTP, ...) connection to an AYIYA server (for a start, the SixXS POPs) and a local network interface (for a start, one that can route IPv6 traffic). Wiki: https://wiki.freebsd.org/SummerOfCode2015/AYIYASixXSNetgraphNode Subversion: https://svnweb.freebsd.org/socsvn/soc2015/roam/ Testing: https://svnweb.freebsd.org/socsvn/soc2015/roam/README.txt?view=3Dco The major change in week 5 was that the Netgraph node now forwards all the "unusual" packets received from the AYIYA server to a userland application, and also signs and forwards any AYIYA packets received from the application to the remote server. This allows userland programs to take care of all the non-IPv6-forwarding aspects of the AYIYA protocol, such as: - sending periodic "heartbeat" packets to the server to let it know that we are still alive even if there has been no forwarded traffic (nobody is really using the IPv6 tunnel) - sending various queries to the server to figure out who we are talking to (operating system, software version, etc) - replying to such queries received from the server - handling a server's "message of the day" packet that, by specification, should be displayed to the operator who brought the tunnel up I also added a sample configuration file describing a tunnel between two IPv4 addresses in the RFC 1918 space, so it would be even easier to test the Netgraph AYIYA node - the testing scaffold may be run on two hosts in the local network to bring up a ng_ayiya node and an IPv6 interface on each host. In the documentation department, a ng_ayiya.4 manual page is also present now and will be installed once the kernel module source is turned into a FreeBSD port. With these changes, and with the assorted minor bugfixes and cleanup that also happened this week, I believe that the ng_ayiya node is functionally complete and ready for testing and optimization. Thus, in the next week I'll try to teach the SixXS AICCU tool to bring up and use the Netgraph node instead of a gif interface as it does now. G'luck, Peter --=20 Peter Pentchev roam@ringlet.net roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 --huq684BweRXVnRxX Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJVlBT6AAoJEGUe77AlJ98TrfgQAIELVwPgc6e6cBnrk1IJYPF/ voBTZydExvDPC+bx+8em3KFjUCJ9KlH0B4ta6lLf9iVdbTmbuL+0/pjIikyD+9bq luSH0GsvV37Eqn2A6WFxCz9Y19zebo+02P7WNpVjeE+1FAEP/1ZqTc0O+m9jqY1M 4/LsMglEuB3xFpHM6cmWuTly0Lo62Rz7HXsf0kbpJufr4FAd73Iyj5tGho0GSfzA CGXM+CGnZp/CiyLThq9NFv8m1dhjFnST4bswLwIQKn0PznKkUc4AAPwMoHzV2pxt 9uKC66jY5T3J+Jv/7DAvjkV4CWvjjwx+BvuxFJILjxFr6YWnp6Nu49uGtTOj0T7+ yqDXZHdKeWeEq+68t7C7EMDqqTAqb1Ln2NQ7gWKIeaLnsaKvgP8fBsT7+7dli7TE fWSVJBfszuhrKDooCZDZo2XD6CWUZU4Zet80s6FYxSFL8La2BhuMewsWVB9ox0Co ErqB4NJIU1disKtWHkOya+8nqDywQ/8pzWjW7oppusdFNj+UFoKhE/mle8r+58kT Ic6i7AZQUxbT+34LDqz0C9iCFlcLk4MCdDh9X+UgMKlbm3+8ZYzw8BKwiEf6iYYF KtwBYstNCuzUUOUuzB7zbbNrHzTS7dPOVFlQfTODdSzDyhwDW321Wh+1FBN/f+Fq sV8l1UVzf+06PnjWAGri =Sx36 -----END PGP SIGNATURE----- --huq684BweRXVnRxX--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150701162743.GA3137>