Bug 40994 (reported at
https://gitlab.torproject.org/tpo/core/tor/-/issues/40994) has become a
fairly serious impediment to running relays. I generally obtain two
ipv4 addresses on my machines and the ports I want to use for tor are
not available on both addresses. So listening on 0.0.0.0 is
All:
Nevermind... After roughly 48 hours, the written/read bytes per second graph,
on the metrics.torproject.org site, began showing normal activity, again.
Please consider this thread resolved.
Respectfully,
Gary
On Monday, August 23, 2021, 2:15:07 AM MDT, Gary C. New
wrote:
All:
All:
It turns out that this issue was related to PortForwarding to the Private
Gateway Address (192.168.0.1:9001).
The solution was to include an iptables ACCEPT Rule in the INPUT Chain to the
PortForward destination (the Private Gateway Address - 192.168.0.1:9001).
# iptables -I INPUT
All:
After reviewing several packet-traces of Tor bound directly to the Public
Address:Port vs Tor bound to the Private Address:Port and Advertising the
Public Address:Port, I believe I may have found the the issue.
It appears that when Tor is bound directly to the Public Address:Port, the
init
Gary C. New wrote:
All:
After reviewing several packet-traces of Tor bound directly to the
Public Address:Port vs Tor bound to the Private Address:Port and
Advertising the Public Address:Port, I believe I may have found the the
issue.
It appears that when Tor is bound directly to the Public
David,
The ISP has port 9001 blocked to the Public Address.
Do the ports have to be the same, when using NoAdvertise & NoListen with the
ORPort directive?
Thanks!
Gary
On Saturday, August 14, 2021, 12:20:36 AM MDT, David Figuera
wrote:
> ORPort 198.91.60.78:443 NoListen
> ORPort 192.
> ORPort 198.91.60.78:443 NoListen
> ORPort 192.168.0.1:9001 NoAdvertise
Why two different ports?
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hi!
I'm having issues when implementing the NoAdvertise & NoListen options of the
ORPort directive and am hoping someone here might be able to point me in the
right direction.
I can get Tor to successfully work as a relay without using the NoAdvertise &
NoListen options of the ORPort directive
I'm not sure how TOR gets its addresses but sometimes you need to
specify it directly, especially for bridges for some reason. Just use
your whole IP
ORPort 123.456.789.123:80
Dont forget if you are mapping Obfs4 you need to add the permissions so
obfs can go to a port that low
/Don't
Thank you for this! I'm back online!
Sent from ProtonMail mobile
Original Message
On Feb 17, 2021, 6:19 PM, wrote:
> On 15.02.2021 21:00, Anonforpeace wr
>
>> Unable to find IPv4 address for ORPort 80. You might want to specify
>> IPv4Only to it or set an explicit address or se
On 15.02.2021 21:00, Anonforpeace wr
Unable to find IPv4 address for ORPort 80. You might want to specify
IPv4Only to it or set an explicit address or set Address.
^^
Have you upgraded to a 0.4.5.n version? (New IPv6 address discovery)
Is explained here:
https://www.mail-archive.com/to
Hello:
Am trying to configure my bridge according to instructions on Tor site. Using
Ubuntu. No matter what port I pick for the ORPort I keep getting this error:
Unable to find IPv4 address for ORPort 80. You might want to specify IPv4Only
to it or set an explicit address or set Address.
Have n
Is your node behind a routee/firewall? You most likely need to forward ports in
your router.
--
Matt Westfall
President & CIO
ECAN Solutions, Inc.
804.592.1672
On September 10, 2019 9:46:50 PM EDT, Anonforpeace
wrote:
>Hello:
>
>Hope someone can help me. I'm trying to configure a bridge a
Thanks so much for your reply!! Will check it out!!
Sent from ProtonMail mobile
Original Message
On Sep 12, 2019, 2:49 AM, Matt Westfall wrote:
> Is your node behind a routee/firewall? You most likely need to forward ports
> in your router.
> --
> Matt Westfall
> President & C
Thanks so much!!
Sent from ProtonMail mobile
Original Message
On Sep 11, 2019, 11:49 PM, Mauricio Genta wrote:
> Hey! How are you?
>
> Are you sure you have configured the port at your firewall to be accessible
> from the outside? You should forward the correct ports from ther
I'll check the firewall, thanks!!
Sent from ProtonMail mobile
Original Message
On Sep 11, 2019, 11:45 PM, niftybunny wrote:
> Firewall is blocking? Port ist above 1024 so you do not need root?
>
>> On 11. Sep 2019, at 03:46, Anonforpeace wrote:
>>
>> Hello:
>>
>> Hope someone
Hey! How are you?
Are you sure you have configured the port at your firewall to be accessible
from the outside? You should forward the correct ports from there. You can
check at the logs (/var/log/syslog) for the tor logs to try to identify
other causes.
---
Mauricio.
El jue., 12 sept. 2019 a la
Firewall is blocking? Port ist above 1024 so you do not need root?
> On 11. Sep 2019, at 03:46, Anonforpeace wrote:
>
> Hello:
>
> Hope someone can help me. I'm trying to configure a bridge and I've followed
> all the instructions and I've chosen several ports and none of them are
> reachabl
Hello:
Hope someone can help me. I'm trying to configure a bridge and I've followed
all the instructions and I've chosen several ports and none of them are
reachable. I've used the test site that Tor lists on its site. "Your server
has not managed to confirm that your its ORPort is reachable
Hi,
You must not forward your control port to the internet.
If you accidentally disable control authentication, then
anyone on the internet can control your relay.
> On 3 Aug 2019, at 21:10, Fabio De Sicot wrote:
>
> Hello everyone
> I have a problem I wasn't able to fix until now. Could you he
Hello everyone
I have a problem I wasn't able to fix until now. Could you help me whit this?
- when I start tor I receive this error:
[...]
Aug 03 09:48:29.000 [notice] Have tried resolving or connecting to address
'[scrubbed]' at 3 different places. Giving up.
> On 17 Oct 2018, at 02:38, Toralf Förster wrote:
>
>> On 10/15/18 11:49 PM, teor wrote:
>> The post contains conflicting advice.
>
> Said that, is the following a good choice for a bridge? :
>
> # torrc
>
> RunAsDaemon 1
>
> SocksPort 0
> ControlPort 9051
> ORPort auto
> BridgeRelay 1
> Exi
On 10/15/18 11:49 PM, teor wrote:
> The post contains conflicting advice.
Said that, is the following a good choice for a bridge? :
# torrc
RunAsDaemon 1
SocksPort 0
ControlPort 9051
ORPort auto
BridgeRelay 1
Exitpolicy reject *:*
ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
--
To
> On 16 Oct 2018, at 03:58, Toralf Förster wrote:
>
> I do wonder if the advice [1] is ok or wrong.
>
> [1] https://tor.stackexchange.com/questions/6370/how-to-run-an-obfs4-bridge
The post contains conflicting advice.
> But diversity of obfs4 ports is actually really important, so I'd argue
I do wonder if the advice [1] is ok or wrong.
[1] https://tor.stackexchange.com/questions/6370/how-to-run-an-obfs4-bridge
--
Toralf
PGP C4EACDDE 0076E94E
signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lis
On Fri, Nov 21, 2014, at 09:18 AM, Julien ROBIN wrote:
> I would like to know how does the test works, in order to check what can
> fail during the test.
> If my server's IP (95.130.9.190) is not reachable by a part of the
> Internet for example, in order to open a support ticket with my ISP (do
>
Hi everybody,
Second time it happen to me so I would like to know if you have ideas about it.
Sometimes after a reboot, I haven't the following message into the log :
"Self-testing indicates your ORPort is reachable from the outside. Excellent.
Publishing server descriptor."
And after a while (
Hello,
This is probably not a full log (it's already been deleted and there is no need
to get back to 0.2.4.21). The problem is not made up: if I roll back to
tor-0.2.3.25_1 port revision 327769, everything works fine without this problem
(earlier and now talking about FreeBSD >=9.0).
25.03.20
Hi,
The self test for the *DirPort* is successful, not the one for the ORPort.
On 03/23/2014 11:58 AM, Tachkov Sergey wrote:
> Hello,
>
> We have previously set up and adjusted a non-exit node with the following key
> parameters:
>
> ORPort 443 NoListen
> ORPort 127.0.0.1:4443 NoAdvertise
>
>
Hello,
We have previously set up and adjusted a non-exit node with the following key
parameters:
ORPort 443 NoListen
ORPort 127.0.0.1:4443 NoAdvertise
After upgrading tor up to the latest version (0.2.4.21) we started receiving in
log the following:
Mar 23 11:53:06.000 [notice] Now checking w
Sorry I didn't get back to you sooner not been at the computer, but yes
you have it right there just use your 192.168.1.12 internal address for
tor to listen on, the other advantage of this way over just giving the
port number is that you will only be accepting traffic arriving at your
router using
The thing is, with this setup arm and also vidalia reported "can not
bind 0.0.0.0:443. Thats why I went back to the old setting.
For the moment I do not really care, because it works, I was just wondering.
My router forwards 443 to 192.168.1.12:9001. So you suggest I put
"192.168.1.12" instead of
Sorry there is an error in my example, forgot the NoAdvertise attribute
didn't notice till the mail came back through the list, should have been
DirPort 80 NoListen
DirPort 127.0.0.1:9030 NoAdvertise
Other than that the rest all should work as I suggested either specify the
actual address your r
There is no need to actually write out the IPv4 unspecified address in
the config file (0.0.0.0), all you need to do is just put:
ORPort 9001 NoAdvertise
Admittedly I have not actually tried it with ORPort personally but I
have had that configuration on one of my relays in the past for DirPort
to
Hi!
I want to have port 443 advertised but listen on port 9001. My router
then forwards 443->9001 to the machine tor is running on.
It works with this:
ORport 433
ORListenAddress 0.0.0.0:9001
However I thought this is deprecated and I rather use:
ORport 443 NoListen
ORPort 0.0.0.0:9001 NoAdver
35 matches
Mail list logo
