I read the recent discussions here on IPv6 and the interest in a presentation.
I've been playing with IPv6 for a few years now, recently participated as both an end user and service provider on IPv6 day (June 8). Have recently been thinking about putting myself on an IPv6 only diet at both work and home to try and break my addiction to news and articles on the web so I can get some real work done. (most of my favourite time killer web sites don't have ipv6 enabled; the AAAA records are not even available in the name server my tunnel broker uses which does successfully query records unavailable to most like google.ca AAAA)
After the Wikipedia binge I went on today I'm thinking I might as well bite the bullet, follow through on this idea, and make a MUUG presentation out of it.
Consider that my formal offer to do it. (subsequent details I'll take off list direct with board folks)
Like all diets, I know I'm going to cheat -- but hopefully only for work purposes and by suffering the inconvenience of tunneling and proxies to reach ipv4 on an as needed basis. (shouldn't be too much, too often.. so I think...).
What I'm implying by IPv6 only is that I'd like to go without a v4 address assigned to my personal machines at all -- it will be my routers at home and work that will be dual stack -- allowing me to be single stack on my actual machines without screwing things up for everyone else that I share those routers with.
Could present in September, but with some fairly busy stuff going on September/October I'd prefer November.
Presentation outline: 1. Basic address, subnet, and routing theory 2. Manual command line configuration in zee penguin land -- address auto discovery and static config 3. Reflections on my IPv6 only diet over the last few months 4. My theory and advocacy on how a transition could come about without putting everyone on dual stack first. 5. The "joy" of writing ipv6 reverse DNS entries and fun with the $ORIGIN keyword in BIND (time permitting) 6. route advertisement daemon (time permitting
Topics I'm not going to cover: * DHCPv6 * setting up any garden variety of tunneling
I am going to bring a wireless access point (disabled as a router), hook it up to my laptop, run a route advertisement daemon and let folks use address auto discovery to pull real ipv6 addresses from me and be able to access the ipv6 internet through me for the evening.
This is the easiest "try it" you could possibly get -- beats manual tunnel set up.
Thinking of giving priority in the presentation to questions asked over a jabber daemon that I'll restrict to ipv6 only as an additional incentive for folks to try it. (also fun for anyone in a merry prankster mood to put things on my screen....)
Mark
A very thorough and helpful project, Mark - when IPv6 starts being seriously used we'll be well prepared. Unfortunately from current trends that'll be in 2027.
-----Original Message----- From: Mark Jenkins mark@parit.ca Sender: roundtable-bounces@muug.mb.ca Date: Sun, 10 Jul 2011 01:10:33 To: roundtable@muug.mb.ca Reply-To: Continuation of Round Table discussion roundtable@muug.mb.ca Subject: [RndTbl] IPv6 only diet followed by presentation?
I read the recent discussions here on IPv6 and the interest in a presentation.
I've been playing with IPv6 for a few years now, recently participated as both an end user and service provider on IPv6 day (June 8). Have recently been thinking about putting myself on an IPv6 only diet at both work and home to try and break my addiction to news and articles on the web so I can get some real work done. (most of my favourite time killer web sites don't have ipv6 enabled; the AAAA records are not even available in the name server my tunnel broker uses which does successfully query records unavailable to most like google.ca AAAA)
After the Wikipedia binge I went on today I'm thinking I might as well bite the bullet, follow through on this idea, and make a MUUG presentation out of it.
Consider that my formal offer to do it. (subsequent details I'll take off list direct with board folks)
Like all diets, I know I'm going to cheat -- but hopefully only for work purposes and by suffering the inconvenience of tunneling and proxies to reach ipv4 on an as needed basis. (shouldn't be too much, too often.. so I think...).
What I'm implying by IPv6 only is that I'd like to go without a v4 address assigned to my personal machines at all -- it will be my routers at home and work that will be dual stack -- allowing me to be single stack on my actual machines without screwing things up for everyone else that I share those routers with.
Could present in September, but with some fairly busy stuff going on September/October I'd prefer November.
Presentation outline: 1. Basic address, subnet, and routing theory 2. Manual command line configuration in zee penguin land -- address auto discovery and static config 3. Reflections on my IPv6 only diet over the last few months 4. My theory and advocacy on how a transition could come about without putting everyone on dual stack first. 5. The "joy" of writing ipv6 reverse DNS entries and fun with the $ORIGIN keyword in BIND (time permitting) 6. route advertisement daemon (time permitting
Topics I'm not going to cover: * DHCPv6 * setting up any garden variety of tunneling
I am going to bring a wireless access point (disabled as a router), hook it up to my laptop, run a route advertisement daemon and let folks use address auto discovery to pull real ipv6 addresses from me and be able to access the ipv6 internet through me for the evening.
This is the easiest "try it" you could possibly get -- beats manual tunnel set up.
Thinking of giving priority in the presentation to questions asked over a jabber daemon that I'll restrict to ipv6 only as an additional incentive for folks to try it. (also fun for anyone in a merry prankster mood to put things on my screen....)
Mark _______________________________________________ Roundtable mailing list Roundtable@muug.mb.ca http://www.muug.mb.ca/mailman/listinfo/roundtable
FYI, one of the FreeBSD developers attempted to go IPv4-less, and did a presentation about it at BSDCan this year.
Short version: the stack is ready, the apps REALLY, BADLY aren't ready.
"Why do apps matter?", you wonder... any code that uses struct inetaddr is automatically IPv4-only. Any code that calls gethostbyname() et al. is IPv4-only (because that uses struct inetaddr). Then there's the truly weird bugs that crop up in otherwise-IPv6-enabled apps when they don't have a valid PF_INET to fall back upon.
There's a link to the audio recording of Bjorn's talk at http://www.bsdcan.org/2011/schedule/events/222.en.html.
Given that most of his problems were app-related, I can't see Linux being any better. Nor, for that matter, Windows or Mac OS X - at least at this point in time.
(FWIW, he wasn't any easier to understand in person...)
-Adam Thompson athompso@athompso.net