-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks again for all the support everyone has bee extremely helpful.
So, I reinstalled the OS on the VPS: lsb_release -d
Description: Ubuntu 14.04.3 LTS
uname -r 2.6.32-042stab102.9
Finally solved all the permissions problems, paths are correct, tor
Try other ports or ask the hoster, if he blocks ports?! Or try 80 and
443, if there are free at your server.
---
Mit freundlichen Grüßen / Yours sincerely
David Schulz
Am 06.12.2015 um 17:15 schrieb Kurt Besig:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks again f
David, low ports numbers are not good idea, he can have same issues. For my
firewall i need to use something more then 9000 to make my exit/relay to
work with my ISP.
On 6 December 2015 at 17:46, David Schulz wrote:
> Try other ports or ask the hoster, if he blocks ports?! Or try 80 and 443,
> i
You should not need to port forward anything.You might consider using a simple front end to iptables like UFW, Uncomplicated Firewall. Simple easy and gets the job done. It is odd that tor complained that your IP address changed. It should not do that. I would assume a VPS would have a static ip
The issue with the iptables rules not being loaded has to do with a script
not being installed. On Debian it is iptables-persistent, and seems to be
the same for Ubuntu. Once that is installed, you can save the rules you
want reloaded by running:
iptables-save > /etc/iptables/rules.v4
ip6tables-sa
Hi All,
this is my first post on this list so warm welcome to every one a specialy
to Tor developers.
On my servers I`m running paralllel prod servers with tor relays on the
separate IP.
I`m supporting tor network for free with high speed tor relays but I need
to customize the time when my server
Hey,
the easiest solution that comes to mind is a cronjob/systemd timer/whatever
that modifies the config file and sends a SIGHUP to tor to trigger a config
reload.
I'm not very familiar with the codebase, so I can't guarantee that reloading
the config file applies new (Relay)BandwithRate sett
Hi Kurt,
You need to know the public IPv4 address of your relay.
Until you have the address correct, it's hard to tell whether you need to open
any ports or not.
> Dec 05 21:17:46.000 [notice] Your IP address seems to have changed
> to 167.114.35.28 (METHOD=INTERFACE). Updating. Dec 05 21:17:46
> On 7 Dec 2015, at 09:39, ajs124 wrote:
>
> Hey,
>
> the easiest solution that comes to mind is a cronjob/systemd timer/whatever
> that modifies the config file and sends a SIGHUP to tor to trigger a config
> reload.
>
> I'm not very familiar with the codebase, so I can't guarantee that rel
>Is it possible to schedule the time when bandwith . . .
>How may I schedule this in tor relay?
>Is it possible to limit traffic on
>the client or I need to do it on my firewall ?
As suggested in an earlier reply, configuring 'cron' jobs to adjust the rate
usually makes sense.
As an alternative
10 matches
Mail list logo