+1, thanks for working on IPv6!
Just curious and didn't see an answer on the roadmap -- do bandwidth authority
measurements ever happen over IPv6?
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman
Thanks for all the work you did and keep doing!
IPv6 is really important to me so I'm really pleased to see that you can move
toward its full support in Tor :)
--
Johan Fleury
PGP Key ID : 0x5D404386805E56E6
signature.asc
Description: This is a digitally signed message part
> On 13 Dec 2017, at 15:31, Johan Fleury wrote:
>
> Is there anywhere we could follow the IPv6 support progress?
Here's a quick summary:
We are focused on authorities and relays in 0.3.3.
Later, we will work on clients and onion services.
We chose this order because some client features won't
Is there anywhere we could follow the IPv6 support progress?
--
Johan Fleury
PGP Key ID : 0x5D404386805E56E6
signature.asc
Description: This is a digitally signed message part
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.to
Dear Tor Relay Operators,
Faravahar had some hardware issues last night, while I was on an airplane
without internet access.
It took me a few hours to respond and I apologize for the delay.
Please note that redundancy is built into the network, and I am committed to
operating this system with v
On 13 Dec 2017, at 08:17, tor wrote:
>> this time though I ran Wireshark while started tor, and it appears tor is
>> transmitting encrypted info over port 80.
>
>> Surely tor shouldn't be transmitting unencrypted messages?
>
> I'm not an expert on the protocol but you may just be looking at r
On Tue, Dec 12, 2017 at 1:17 PM, tor wrote:
>>I am getting this too, I saw this the logs a few months ago and didn't think
>>anything of it.
>
>
> I wouldn't worry about it. Faravahar has a long history of misbehavior:
>
> https://lists.torproject.org/pipermail/tor-relays/2015-November/008097.html
>I am getting this too, I saw this the logs a few months ago and didn't think
>anything of it.
I wouldn't worry about it. Faravahar has a long history of misbehavior:
https://lists.torproject.org/pipermail/tor-relays/2015-November/008097.html
https://lists.torproject.org/pipermail/tor-relays/20
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/12/2017 11:54 AM, teor wrote:
> I assume the operator is aware and is working on a fix.
There're since months errors logged here for that machine. I decided to ignore
all errors from that machine.
- --
Toralf
PGP C4EACDDE 0076E94E
-BEGIN
Hello.
I am getting this too, I saw this the logs a few months ago and didn't
think anything of it, this time though I ran Wireshark while started tor,
and it appears tor is transmitting encrypted info over port 80. I have the
.pcap file to prove it.
I started / stopped the relay a few times so I
On Mon, 11 Dec 2017 at 18:07 Felix wrote:
> Hi Alex
>
> Great points.
>
> > conntrack -L -p tcp --dport 9001 | awk '{print $5}' | sort | uniq -c
> | sort -n
>
> On FreeBSD one can do:
>
> In packetfilter:
>
> # play with the numbers but more than 64k per ip if possible
> set limit { frags 700
On Fri, December 8, 2017 7:22 am, x9p wrote:
>
...
>
> Thanks again. Am already on the boat.
>
> cheers.
>
> x9p
The set of "potentially" (no proof!) unwanted relays was updated (looks
automagically via script or sort of), still do not have their HSDir flag
back, only 17h uptime.
Meanwhile, HS u
> On 12 Dec 2017, at 20:36, r1610091651 wrote:
>
> Hi
>
> I'm seeing regular issues with faravahar in logs lately. Is somebody working
> on this?
faravahar is not voting, so it's probably down:
https://consensus-health.torproject.org/
I assume the operator is aware and is working on a fix.
Yup - Me Too...
- Original Message -
From: "Aneesh Dogra"
To: tor-relays@lists.torproject.org
Sent: Tuesday, December 12, 2017 8:47:30 PM
Subject: Re: [tor-relays] Issues with faravahar?
On Tue, Dec 12, 2017 at 3:06 PM, r1610091651 < r1610091...@telenet.be > wrote:
Hi
I'm
On Tue, Dec 12, 2017 at 3:06 PM, r1610091651 wrote:
> Hi
>
> I'm seeing regular issues with faravahar in logs lately. Is somebody
> working on this?
>
> Logs:
> Dec 12 10:32:56.000 [warn] HTTP status 502 ("Bad Gateway") was unexpected
> while uploading descriptor to server '154.35.175.225:80'. Po
Hi
I'm seeing regular issues with faravahar in logs lately. Is somebody
working on this?
Logs:
Dec 12 10:32:56.000 [warn] HTTP status 502 ("Bad Gateway") was unexpected
while uploading descriptor to server '154.35.175.225:80'. Possibly the
server is misconfigured?
Dec 12 10:33:56.000 [warn] Recei
16 matches
Mail list logo
