Re: [Csync2] ipv6 problems

2016-04-27 Thread Lars Ellenberg
On Wed, Apr 27, 2016 at 06:49:21PM +1000, Aristedes Maniatis wrote: > On 27/04/2016 11:45am, Aristedes Maniatis wrote: > > On 19/04/2016 9:14pm, Lars Ellenberg wrote: > >> I don't think so. > >> It's supposed to bind to something that is suitable for *both* IPv6 and > >> IPv4. > > > > A patch

Re: [Csync2] ipv6 problems

2016-04-27 Thread Aristedes Maniatis
On 27/04/2016 11:45am, Aristedes Maniatis wrote: > On 19/04/2016 9:14pm, Lars Ellenberg wrote: >> I don't think so. >> It's supposed to bind to something that is suitable for *both* IPv6 and IPv4. > > A patch has been submitted that might fix the IPv6 problem: > >

Re: [Csync2] ipv6 problems

2016-04-26 Thread Aristedes Maniatis
On 19/04/2016 9:14pm, Lars Ellenberg wrote: > I don't think so. > It's supposed to bind to something that is suitable for *both* IPv6 and IPv4. A patch has been submitted that might fix the IPv6 problem: https://github.com/ari/csync2/commit/10636a4786485f7a45d1c35a554b9bb57fa52aae I haven't

Re: [Csync2] ipv6 problems

2016-04-20 Thread Lars Ellenberg
On Wed, Apr 20, 2016 at 04:28:26PM +1000, Aristedes Maniatis wrote: > On 19/04/2016 9:14pm, Lars Ellenberg wrote: > > You can tell it to bind to "-N your.node.name". > > If not specified, it will use the "any" address > > (pass a NULL node to getaddrinfo) > > Passing -N on the command line works