Re: [tor-relays] Dear OBFS4 bridge operators, please enable timing and packet-size obfuscations to help clients facing timing analysis attacks.

Philipp Winter regarding iat mode: >The feature introduces a substantial performance penalty for a dubious >and poorly understood privacy gain. If I were to write an algorithm to >detect obfs4, I wouldn't bother dealing with its flow properties; there >are easier ways to identify the protocol.

Re: [tor-relays] snowflake prometheus metrics listen address

sideration :blush:). so seems like a won't implement for me atm anyway. On 10/3/23 10:30, Toralf Förster wrote: On 10/3/23 10:24, Fran via tor-relays wrote: Any ideas? yes - DNAT the remote prometheus ip to the local address [1] [1] https://github.com/toralf/tor-relays/blob/main/playbo

[tor-relays] snowflake prometheus metrics listen address

Hey there, snowflake v2.6.1 offers a prometheus metrics endpoint `-metrics`.[1] Unfortunately I am unable to figure out how to let it listen to non-localhost address: tcp LISTEN 04096 127.0.0.1: 0.0.0.0:* users:(("snowflake",pid=402248,f

Re: [tor-relays] [Important] A call for more long running bridges, especially with OBFS IAT-Mode set to 1 or 2.

021-February/019370.html I personally leave my bridges as they are, without iat_mode. Best, Fran On 5/12/23 13:34, George Hartley via tor-relays wrote: Hello dear relay and bridge hosts, recently a paper was published, describing a traffic confirmation attack called DeepCorr, which wo

Re: [tor-relays] We need much more bridges with obfs4 and iat-mode set to 1 or 2..barely can't find any.

Philipp Winter regarding iat mode: >The feature introduces a substantial performance penalty for a dubious >and poorly understood privacy gain. If I were to write an algorithm to >detect obfs4, I wouldn't bother dealing with its flow properties; there >are easier ways to identify the protocol.

Re: [tor-relays] relay memory leak?

il the log messages disappear? What would be best for the network? Thanks a lot! Fran ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Exit Node Questions

/tor/torrc.5.en.html for details. Best fran ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Snowflake vs bridge on home connection on a Raspberry Pi 4

aining new bridges for tor users is a bigger effort than connecting to a snowflake proxy (snowflake was kinda more intended to offer proxy services with changing IP addresses and behind NAT...). Best, fran On 3/19/22 01:02, Cristian Consonni via tor-relays wrote: Hi all, I have a fiber connecti

Re: [tor-relays] Auto-discovered IPv6 address [...] has not been found reachable.

f you configure the IPv6 address by hand in torrc? Can you please send your torrc and the output of ip route show table all ip address show tnx & ciao, fran On 3/11/22 13:33, Onion Operator wrote: Hi Need another couple of eye balls on my relay, RealityLeighWinner. I keep reading &q

Re: [tor-relays] rdsys was ignoring BridgeDistribution

Hey, never mind, with some coffee I find them :blush: Not blocked in Russia (yet) \o/ Thanks anyway and have a great weekend! Fran On 3/4/22 19:08, Fran via tor-relays wrote: Hey, stuff like this happens meskio, thanks for the effort! Slightly off topic: I couldn't find my bridges i

Re: [tor-relays] rdsys was ignoring BridgeDistribution

UTC (1h26m57.41568s ago) Setting is "BridgeDistribution any" Any ideas why this might be? Thanks, fran On 3/4/22 16:56, meskio wrote: As mentioned before[0] BridgeDB now uses rdsys as backend. I just found out that there was a bug in rdsys and the BridgeDistribution configur

Re: [tor-relays] New relay has a problem - Additional info about net config

m the nyx ones. The "Address '::1'" is surprising when not having IPv6 enabled at all (which is also supported by the "ip a" output). Best, fran On 2/12/22 22:03, Olaf Grimm wrote: Here info about netconfig. In the INFO messages is a part of 'Could

Re: [tor-relays] snowflake vs bridges (vs node)

ubbed -verbose increase log verbosity Could be solved with VRFs/namespaces but would involve bridging, veths...too snowflaky for me (same goes for containers). So I guess I'll just keep the bridges and make then relays one day. Thanks for all who helped! best fran On 2/7/22 11:12, me

Re: [tor-relays] snowflake vs bridges (vs node)

nowflake on the same v4 do any "harm"? For example like bridges are easier to be detected and only running snowflake might result in a longer usability of the node. Thanks a lot, have a great weekend! Fran ___ tor-relays mailing list tor-rel

Re: [tor-relays] snowflake vs bridges (vs node)

ges (time to be blocked for a usual bridge would be really interesting to know if/when I should convert the bridges to regular nodes or change IP addressing). Thanks and have a great weekend! Fran [1] https://blog.torproject.org/run-tor-bridges-defend-open-internet/ [2] https://blog.torproject.o

[tor-relays] snowflake vs bridges (vs node)

rally, what's more needed atm: bridge, non-exit, exit or snowflake? Thanks! fran [1] https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/wikis/home ___ tor-relays mailing list tor-relays@lists.torproject

Re: [tor-relays] tor prometheus metrics -> expected label value, got "INVALID"

health metrics for prometheus would be awesome! :) Best, fran [1] https://gitlab.torproject.org/tpo/core/tor/-/issues/40194 ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] tor prometheus metrics -> expected label value, got "INVALID"

replacement: bar now I got not only the labels 'instance=":9035"job="tor_metrics"' but also 'onion="foo" port="bar"' but still the 'expected label value, got "INVALID"' error. Out of ideas for the moment.

[tor-relays] tor prometheus metrics -> expected label value, got "INVALID"

s are running Debian 11, Prometheus 2.32.1 and tor 0.4.6.9-1~d11.bullseye+1 I searched the relays mailinglist and tried to find something in the internet, unfortunately not very successfully. Any ideas? Thanks a lot! fran ___ tor-relays

[tor-relays] prometheus onion service exporter

Hey, I recently stumbled over a prometheus exporter for onion services: https://github.com/systemli/prometheus-onion-service-exporter Maybe this is of interest for some of you... fran ___ tor-relays mailing list tor-relays@lists.torproject.org https

Re: [tor-relays] Dropped off consensus (0.4.4.5) - reason is Libressl 3.2.1

27;ll try again in 2 seconds. > Tor[17665]: fetch_bridge_descriptors(): ask_bridge_directly=1 (1, 1, 0) > Tor[17665]: should_delay_dir_fetches(): Delaying dir fetches (no running > bridges known) > Tor[17665]: should_delay_dir_fetches(): Delaying dir fetches (no running > brid

Re: [tor-relays] Heartbeat: It seems like we are not in the cached consensus.

> Hi there, > >> On 28. Jul 2020, at 22:33, Fran wrote: >> >> thanks @Torix for the IPv6 suggestion, all auth were reachable via v6, but >> for testing I turned of IPv6 in the tor config - no change. > > I can indeed ping both of your IPv4 and IPv6 from gabelmoo

Re: [tor-relays] Heartbeat: It seems like we are not in the cached consensus.

len 514 (0 pending in tls object). Jul 28 22:28:28.000 [debug] connection_or_process_cells_from_inbuf: 12: starting, inbuf_datalen 0 (0 pending in tls object). Jul 28 22:28:29.000 [debug] circuit_remove_handled_ports: Port 443 is already being handled; removing. Jul 28 22:28:29.000 [debug] circuit_remove_handled_po

Re: [tor-relays] Heartbeat: It seems like we are not in the cached consensus.

ne has it's own global unicast ipv4 and ipv6 addresses. best fran > On Sat, Jul 18, 2020 at 9:40 PM Fran <mailto:fa...@mailbox.org>> wrote: > > Hello, > > I'm taking care of a server of a friend who's on holiday. The server is > up and runni

[tor-relays] Heartbeat: It seems like we are not in the cached consensus.

rked addresses. 0 connections closed. 0 single hop clients refused. 0 INTRODUCE2 rejected. Atlas show the server as down: https://metrics.torproject.org/rs.html#details/AC601DBDB7FBD53454045EDC08DAE3C381C8CF88 Accessing the status page on port 80 works. No FW on the machin