When you say "the NAT problem", which of the very many problems one can encounter when using NAT are you referring to?
Do you mean the issue of whether an application sat behind a NAT firewall can listen for incoming connections? That would be one of the more common NAT problems that p2p apps need to deal with, but I'm not sure it's what you mean here since it doesn't really have anything to do with IPv6. Right now I'm sat behind an IPv4 NAT firewall, but my instant messenger client is entirely capable of accepting incoming TCP connections for things like p2p file transfers, audio, and video. This is because my firewall supports a negotiation protocol specifically designed to allow p2p applications to get the firewall to open up ports on demand, and for the application to discover what the outward facing IP address and port number is. (No special configuration is required, beyond the fact that I enabled this feature on the firewall at some point in the past.) So IPv6 isn't technically necessary to solve that particular problem. Nor is it sufficient - whether you can listen for connections like this is not merely a technological issue: it's also one of local security policy. Lots of places have equipment that could allow apps behind the firewall to listen for incoming requests but which are configured not to. So the main thing you require to solve this problem is the support of those who run your network infrastructure - once you have that, it's possible to solve this today with IPv4 and off-the-shelf network equipment. So given all that, I guess we have to presume that this isn't the problem you're talking about. So are you referring to the problems of running IPv6 in a context where you have a NAT firewall that only knows about IPv4? (I gather this is the area Toredo is intended for) I guess not, since you're proposing *introducing* IPv6 as a solution to the problem. But if you just use IPv4 you wouldn't have that particular problem in the first place... Or are you referring to the fact that although solutions exist for allowing apps behind an IPv4 NAT firewall to listen for incoming network requests, these are not universally adopted? (Doesn't IPv6 suffer from exactly the same problem?) Or is it some other problem? If you could be a little more clear about what specific problem you're talking about, and in particular how you think that IPv6 would help you solve it, it would probably be easier for people to help you. -- Ian Griffiths DevelopMentor > -----Original Message----- > From: Mark Anthony Spiteri [mailto:[EMAIL PROTECTED] > > Currently I am planning my final year project which will > basically entail am online framework for group based collaboration > using .NET for Tablet PC's. This will be a Peer-to-Peer project that > will handle such things as instant messaging, shared notice board, > whiteboard, dynamic shared file systems, VoIP and so on. On of the > problems currently at hand is to deal with the NAT problem. One > solution is to program for IPv6 as Microsoft suggests. > > I have found ways of programming with IPv6 in .NET however I am unsure if > it > is possible to integrate with the Teredo infrastructure proposed by > Microsoft in order to deal with the NAT issue. Is this at all possible in > .NET? > > Cheers, > Mark > > =================================== > This list is hosted by DevelopMentor(r) http://www.develop.com > NEW! ASP.NET courses you may be interested in: > > 2 Days of ASP.NET, 29 Sept 2003, in Redmond > http://www.develop.com/courses/2daspdotnet > > Guerrilla ASP.NET, 13 Oct 2003, in Boston > http://www.develop.com/courses/gaspdotnet > > View archives and manage your subscription(s) at > http://discuss.develop.com =================================== This list is hosted by DevelopMentor� http://www.develop.com NEW! ASP.NET courses you may be interested in: 2 Days of ASP.NET, 29 Sept 2003, in Redmond http://www.develop.com/courses/2daspdotnet Guerrilla ASP.NET, 13 Oct 2003, in Boston http://www.develop.com/courses/gaspdotnet View archives and manage your subscription(s) at http://discuss.develop.com
