> On 1 Mar 2019, at 10:26, s7r wrote:
>
> teor wrote:
>>
>>
>> Cc'ing Linus, because he is also interested in IPv6.
>>
>> On 28 Feb 2019, at 19:01, s7r mailto:s...@sky-ip.org>>
>> wrote:
>>>
>>> However, shouldn't the line:
>>> ORPort 9050
>>>
>>> bind to all v4 and v6 available interfaces
teor wrote:
> Hi,
>
> Cc'ing Linus, because he is also interested in IPv6.
>
> On 28 Feb 2019, at 19:01, s7r mailto:s...@sky-ip.org>>
> wrote:
>>
>> However, shouldn't the line:
>> ORPort 9050
>>
>> bind to all v4 and v6 available interfaces / IP addresses? If it does
>> not, we should fix it to
Hi,
Cc'ing Linus, because he is also interested in IPv6.
> On 28 Feb 2019, at 19:01, s7r wrote:
>
> However, shouldn't the line:
> ORPort 9050
>
> bind to all v4 and v6 available interfaces / IP addresses? If it does
> not, we should fix it to do so. As in:
>
> ORPort 9050 - bind to all
> >> ORPort []:9050
> >
> > This config line will probably cause a parse error.
> >
> > If this is meant to be an IPv6 ORPort, try:
> >
> > ORPort [::]:9050
> >
> > T
>
> Indeed, ORPort []:9050 is incorrect, even it's not the reason of the
> error described in this message.
Sorry for the
Hello,
teor wrote:
> Hi,
>
>> On 28 Feb 2019, at 09:57, technon...@fea.st wrote:
>>
>> I run one relay and another tor instance for hidden services and socksport.
>> Haven't had a problem until 0.4.0.2_alpha. Ive had it crash twice so far.
>> Maybe my configs aren't sane?
>>
>> [err]
