If you want to have an identd that can talk IPv6, you can choose oidentd.
If you are running it from inetd, you should configure your inetd to respond to IPv6 as well. I’m using openbsd-inetd, and the lines in /etc/inetd.conf to make it listen on both IPv4 and IPv6 for the auth service are:
auth stream tcp4 nowait root /usr/sbin/tcpd /usr/sbin/oidentd -I auth stream tcp6 nowait root /usr/sbin/tcpd /usr/sbin/oidentd -I
Note the protocol, which specifies IPv4 or IPv6. Also note the -I option to oidentd, to make it read from stdin and write to stdout and to exit after answering one request (needed for inetd operation).
I briefly considered nullidentd, but the description made it sound like it would only ever return one static string. Not quite what I was looking for, and I didn’t investigate further.
I'm doing some IPv6 codig for a client and needed to setup a bunch of 6in4 tunnels.
The procedure can be summarized in these steps:
create a tunnel
mytun between local
18.104.22.168 and remote
ip tunnel add mytun mode sit local 22.214.171.124 \ remote 126.96.36.199 ttl 64 dev eth0
give the local end an address
ip addr add dev mytun f8c0::188.8.131.52/64
bring up the tunnel
ip link set dev mytun up
I'm late with this update (busy catching up on other work that I neglected last month) but I must report that the Ottawa IPv6 Summit went far better than I had hoped: Great turn-out, great venue, great talks and great food.
Pictures are now available from Richard Guy Briggs and we're working on putting the talk videos online with the help of ISI Global Webcasting.
The space at Telfer School of Management was ideal, and the Telfer volunteers got everyone registered helped everything run really smoothly all day.
It was tons of work, but I look forward to doing it again. Maybe I'll even catch more than a couple talks in person next time.
What a busy week!
As the dust of the (extremely) well attended Ottawa IPv6 Summit settles, we are working through some post conference tasks.
I've just updated the presentation page on the site to include the slide decks of most of the presentations. I am still waiting for files from few speakers. You view the ones which are available on the presentation page.
As you may have noticed -- if you were lucky to get in before we sold out -- the talks were recorded. The results of the recordings will go up on our website within a few weeks.
In the summer of 2010 a half dozen OCLUG members decided it would be a good idea to put on an IPv6 conference for Ottawa. I was one of those people!
At the time IANA still had lots of IPv4 addresses, but it was projected to run out in May of 2011. It seemed that no one in Canada was doing anything about it, and people needed to be educated.
And so, the IPv6summit.ca was born.
[ NOTE: this article began as the front page of the IPv6 Summit.ca website ]
Whenever you use the Internet, you are using an Internet Protocol (IP) - a set of rules for communication between computers. Internet Protocol Version 6 (or IPv6 for short) is an upgrade to the most widely available Internet Protocol (version 4, or IPv4). These Internet Protocols are used to assign each computer with an address (called an IP address) that uniquely identifies it on the Web and allows other computers to communicate with it.
Anyway... I've also been learning a lot more about IPv6. Which reminded me that I never finished my IPv6 Certification from Hurricane Electric. I stopped at the Guri level because getting Sage (the top level) meant that I would have had to have a sane domain name registrar.
# whois ipv6summit.ca Domain name: ipv6summit.ca ... Name servers: ns.ipv6summit.ca 184.108.40.206 2001:470:1c:1cb::6:0
Anyway, long story short... I am now a Sage!
Registration for the Ottawa IPv6 Summit has just opened. Also if you want to present a talk (in particular something suitable for the business/management stream) there is still some time to submit a proposal.
The summit will be held Friday April 29 in downtown Ottawa at the new Desmarais building in the University of Ottawa campus. There will be some great talks, a good lunch, fast wireless, power at every seat and plenty of interesting people. I'll post again when the schedule is available.
The conference is being organized by a small group of volunteers, including myself. If your company is willing to sponsor the event please contact the Ottawa IPv6 Summit. The money will go directly into making the conference better for everyone attending.
I want to get an IPv6 address from SixXS.net. The first step is to apply for an account. They gave me one. I tried to use the username/password credentials to log in, and was not able to read the page. I guess it must be xhtml, and it had some kind of error right after the head element. So all I got was a message in the browser saying that there was an error on line 14 character 8.
I tried logging in again today, and was able to see a page full of info.
I don’t know what the problem was. Could have been a problem on the remote end, or maybe I didn’t have cookies enabled. It works now, and I was able to apply for a tunnel. We’ll see what happens next!
Some people have been telling me that they "have no time" or "are too lazy" to setup IPv6 on their desktop, but would like to.
Below are 2 easy steps to get IPv6 running on your Debian Linux sytem (shoudl be identical on Ubuntu, and similar distros).
If you have an IPv6 Linux network at home, you probably have a Linux host on the perimeter that's running radvd -- this is the server that responds to IPv6 neighbour discovery (ND) requests, distributes the default route to all your hosts, and tells your hosts how to auto configure themselves.
All these tasks were handled by the DHCP server, albeit a lot differently, in
the good old days. The one other thing that
dhcpd did for us was to tell
all the hosts where the DNS servers were.
So, do I need to run the IPv6 version of
Apparently there is a huge shortage of Canadian registrars that can provide full ipv6 support. The only one I was able to find is BareMeta.com, which despite it's TLD operates out of Victoria, BC. I haven't switched yet, because while they support ipv6 glue records for .ca, they don't for .net yet.
Here is the discussion on dslreports.com where it was mentioned.