Re: [Unity-irc3] IPv6 and irc3

[David Westley]

I can add IPv6 to my linux box at home and BitchX has IPv6 support in it so I 
could test it a little. The Undernet coders are adding IPv6 support to ircu and 
hope it'll be in the .12 release whenever that finally gets out the door.

IPv6 support in adns...why don't we follow the development of adns and look at 
what the Hybrid team did and adapt it to suit us... :)

If memory serves I think you can look at one of the TCP flags when a client 
connects and tell then if it's a IPv4 client or an IPv6 client...I'd have to 
check tho.

David

-----Original Message-----
From: Jan Krueger <address@hidden>
To: "irc3 (Unity) public discussion" <address@hidden>
Date: Thu, 13 Mar 2003 11:11:26 +0100
Subject: Re: [Unity-irc3] IPv6 and irc3

> On Thu, 13 Mar 2003 08:20:12 +0100, "C.W.L. Hoogenboezem"
> <address@hidden> wrote this:
> > What will be done with IPv6? Are we going to code that right into the
> > ircd's, or are we going to implement an IPv6 module in a later stage?
> > 
> > This might seem a bit far-away for you guys, but IP is the core of the
> ircd,
> > unless we want to let the people talk over I/SPX. :)
> > 
> > I think we should not hardcode IPv6 into the ircd, we'd rather modularize
> it
> > -- this lessens the size of the ircd, and allows us to focus on more
> > important aspects of the ircd first... ipv4?
> > 
> > Chris
> 
> I agree that we can't just ignore IPv6 like the ircu people do (do they
> really
> ignore it? I haven't seen it anywhere yet...). However, I have no means to
> test IPv6 here, so I can't even see whether what I code would work out for
> IPv6 clients.
> Also, for a start, I have no idea how I can see whether an incoming
> connection
> is IPv4 or IPv6.
> 
> Generally, the only piece of code that has to specifically support IPv6 is
> the
> code that accepts connections and does the DNS stuff and so on. Which is
> where
> we start running into problems: should we decide to use adns, we have to
> follow the ircd-hybrid team and add IPv6 capability to adns (we could as well
> simply rip off the ircd-hybrid version, of course ;)).
> For all the rest of the code we would just have to make sure that we don't
> restrict the code too much, i.e. allow ':' in (unresolved) hostnames.
> 
> Since the IPv6 stuff had to go very deep into the network core of the ircd, I
> don't think there's a really sensible way to modularize it. However, if we
> keep our core code clean (which the current ircd's code is most certainly
> not)
> it should be fairly easy to add "minor" things such as IPv6 support.
> 
> -- 
> regards,
> Jan Krüger
> http://www.jast-dev.net.tc
> 
> 
> 
> _______________________________________________
> irc3 (Unity) public discussion mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/unity-irc3