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 NoAdvertise
The latter however does not seem to work. Arm for example still errors
"binding failed" and I see no incoming connections.
Is this a bug?
Thanks.
SE
So, some hours ago I noticed a circuit on the network map consisting of
a relay in my own country, another one 11,000 km away, and - surprise -
my own bridge relay. Can this be so? I thought that bridges, though
published, are anonymous.
My TBB configuration seems fine, it's what I've used in previous
implementations. The only difference I've written into torrc for this
run is SocksPort auto. The bandwidth rates seeming way higher than
should be allotted to my bridge (10485760 & 5242880, …
[View More]rather than the
196608 & 98304 of previous runs), I checked my bandwidth-limit setting
and found that I had inadvertently chosen > 1.5 Mpbs instead of 1.5 Mpbs
(but as I'd noted to myself previously, the higher setting doesn't seem
to matter, except maybe to improve performance a bit).
The relays_ published output is as usual (not that I'd be likely to
recognize anything amiss in that report).
One other thing that may be pertinent and which I've wanted to ask about
for a long time is this: I occasionally for convenience run my open
browser from the same vista machine on which I'm running the TBB at the
same time. Is this bad practice, and could it have been the reason that
the bridge nickname showed in the network map?
- eli gpg: 0xE498E90D
[View Less]
Hi,
I have a bridge running and since my ISP is changing my IP at least
daily, I thought it might be a good idea to set my DynDNS in the torrc file.
Is it a good idea? How do I set that?
Thank you.
Sina
I am wondering if anyone with experience in this area could advise me
some on recommended specifications for a 1Gbps exit I think my latest
once needs a package upgrade to handle it, currently seems stuck at
around 100Mbps worth of traffic. Currently it has access to 3 v cores
@1.33Ghz and 1GB of RAM and I think the latter might be becoming the
limit instead now I had thought it was the CPU when it had just the one
core but that alone hasn't helped.
I am not entirely sure if tor is infact …
[View More]using the other cores though
watching with top it is sitting at 100 or a fraction over like 104% or
so. MaxCPU's is set in torrc to 4 as the OS sees 4 virtual cores but is
capped to 300% by the hypervisor perhaps it should be set to 3 not sure
if there is any benefit in setting to 4 I have limited experience with
virtual servers but unfortunately a fully dedicated server for tor is
financially out of my budget at the moment.
Also, just to confirm while I'm aware it's very possible that the
limitation could be bandwidth given it shares with the other VPS'es on
the host I don't believe that was the case, I pulled a backup from there
to another server of mine on a different AS and continent and it
transferred at 250Mbps while tor was running at 100Mbps the entire time,
so unless the contention is over the download which seems less likely
for a server I think we should be able to get a good 300Mbps of exit
capacity out of this possibly more.
So can anyone can advise on recommended CPU, RAM have to consider budget
but will try and meet them, also if there are any settings I should
check in torrc?
[View Less]