[Citadel Development] Re: Citadel commit log: revision 8825

2010-08-15 Thread dothebart


 

So Aug 15 2010 16:30:16 EDT von   IGnatius T Foobar @ Uncensored  Betreff: Re: Citadel commit log: revision 8825

Citserver doesn't have IPv6 yet.  


yep, but for some reason webcit isn't able to connect to 127.0.0.1 anymore, aside of resolving 'localhost' to that. (it seems as if resolving localhost already is an issue in 7.8x)




[Citadel Development] Re: Citadel commit log: revision 8825

2010-08-15 Thread IGnatius T Foobar
Citserver doesn't have IPv6 yet. 
 


[Citadel Development] Re: Citadel commit log: revision 8825

2010-08-15 Thread dothebart


webcit 127.0.0.1 504 won't work for me anymore too.
i'm getting:
Can't connect to 127.0.0.1.504: Connection refused




[Citadel Development] Re: Citadel commit log: revision 8825

2010-08-15 Thread IGnatius T Foobar
Ok, there we go. 
  
 The previous IPv6-only implementation required a hybrid stack host such as
Linux or FreeBSD, on which the listening address "in6addr_any" causes it to
accept both IPv6 and IPv4 connections on the same socket.  I was ok with 
dropping
support for OpenBSD, but when I found out that MacOS would also be affected,
it became clear that this needed to be re-thought. 
  
 Linux users will probably still want to listen on "any ipv4 or ipv6" by 
omitting
the listening address completely.  OpenBSD and MacOS users will have to do
that plus run a second copy of webcit listening on "0.0.0.0" to accept IPv4
connections. 
  
 This implementation still *requires* the host to support IPv6, even if only
IPv4 is in use.  I don't think that's a problem -- pretty much all of the
major operating systems have had IPv6 support for nearly a decade now. 
  
 Next up: the Citadel server.  This will
add a bit more complexity because we can't just say "run a second copy on
0.0.0.0" if they want to run both protocols.