Re: [tor-relays] Custom bandwith for different time ranges

[starlight . 2015q3]

>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 to modifying 'torrc' and sending SIGHUP to the daemon, you 
could use a control-channel script similar to:

nc 127.0.0.1 9151 

Re: [tor-relays] Custom bandwith for different time ranges

[Tim Wilson-Brown - teor]

> 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 reloading 
> the config file applies new (Relay)BandwithRate settings, but from the 
> glances I took at the code it does seem like it should do it.
> Please someone verify or falsify this claim.

Reloading the config file changes all the settings.
For the few settings where it doesn't, tor will warn you, or refuse to reload 
the config.

> 
> ajs124
> 
> On Sun, 6 Dec 2015 21:38:05 +0100
> Zalezny Niezalezny  wrote:
> 
>> 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 will share 100% of its resources for
>> tor and when traffic will be limited.
>> 
>> 
>> Is it possible to schedule the time when bandwith will looks as follow:
>> 
>> 8:00 - 18:00 - Tor relay bandwith 250kb/s
>> 
>> 18:00 - 8:00 - Tor relay bandwith 10 000kb/s
>> 
>> 
>> 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 ?
>> 
>> 
>> Thanks in advance for any feedback.
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Tim Wilson-Brown (teor)

teor2345 at gmail dot com
PGP 968F094B

teor at blah dot im
OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] VPS/Tor Almost There

[Tim Wilson-Brown - teor]

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.000
>  [notice] Our IP Address has changed from 142.4.217.95 to
>  167.114.35.28; rebuilding descriptor (source: METHOD=INTERFACE).
>  Dec 05 21:18:42.000 [notice] Your IP address seems to have changed
>  to 142.4.217.95 (METHOD=GETHOSTNAME HOSTNAME=ca3.pulseservers.com 
> ).
>  Updating. Dec 05 21:18:42.000 [notice] Our IP Address has changed
>  from 167.114.35.28 to 142.4.217.95; rebuilding descriptor (source:
>  METHOD=GETHOSTNAME HOSTNAME=ca3.pulseservers.com 
> ). Dec 05
>  21:18:43.000 [notice] Self-testing indicates your ORPort is
>  reachable from the outside. Excellent. Publishing server
>  descriptor. Dec 05 21:38:37.000 [warn] Your server
>  (142.4.217.95:9030) has not managed to confirm that its DirPort is
>  reachable. Please check your firewalls, ports, address, /etc/hosts
>  file, etc. Dec 05 21:58:37.000 [warn] Your server
>  (142.4.217.95:9030) has not managed to confirm that its DirPort is
>  reachable. Please check your firewalls, ports, address, /etc/hosts
>  file, etc.
> I've gotten this far, not being much good at networking I can't tell
> where the problem lies.. do I need to forward something?
> 

Tor is receiving two different IP addresses using two different methods of 
working out your VPS IP address:
* gethostname() on ca3.pulseservers.com  returns 
142.4.217.95
* an OS-specific interface address system call returns 167.114.35.28

Please find out from your admin which IPv4 address you should use, and specify 
it using the "Address" option in your torrc.
(Or, alternately, make a connection to 
http://www.myipaddress.com/show-my-ip-address/ 
 or similar from the VPS, and 
look at the address it returns.)

> On 7 Dec 2015, at 03:15, Kurt Besig  wrote:
> 
> The VPS isn't allowing Ports 9001 and 9030
> Should I investigate further getting my iptables up and running or
> just contact the admin and have them allow the ports?


Once you know the correct IPv4 address, try launching Tor again, and give it 20 
minutes to check reachability.
If it still complains that it can't reach your ORPort or DirPort, then ask your 
admin if they need to open ports to a VPS.
(From your previous posts, it looks like the ports are not being blocked on the 
VPS OS itself.)

Tim

Tim Wilson-Brown (teor)

teor2345 at gmail dot com
PGP 968F094B

teor at blah dot im
OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Custom bandwith for different time ranges

[ajs124]

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 settings, but from the glances 
I took at the code it does seem like it should do it.
Please someone verify or falsify this claim.

ajs124

On Sun, 6 Dec 2015 21:38:05 +0100
Zalezny Niezalezny  wrote:

> 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 will share 100% of its resources for
> tor and when traffic will be limited.
> 
> 
> Is it possible to schedule the time when bandwith will looks as follow:
> 
> 8:00 - 18:00 - Tor relay bandwith 250kb/s
> 
> 18:00 - 8:00 - Tor relay bandwith 10 000kb/s
> 
> 
> 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 ?
> 
> 
> Thanks in advance for any feedback.
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] Custom bandwith for different time ranges

[Zalezny Niezalezny]

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 will share 100% of its resources for
tor and when traffic will be limited.


Is it possible to schedule the time when bandwith will looks as follow:

8:00 - 18:00 - Tor relay bandwith 250kb/s

18:00 - 8:00 - Tor relay bandwith 10 000kb/s


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 ?


Thanks in advance for any feedback.
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] VPS/Tor Almost There

[Damian Busby]

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-save > /etc/iptables/rules.v6

That is the default location for the files that the init.d script will load
at startup.

Hope this helps and let me know if you have any more questions or I got
anything wrong.

Damian (The other one)


On Sun, Dec 6, 2015 at 8:53 AM ZEROF  wrote:

> 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, 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 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
>>> and arm open properly.
>>> The problem now boils down to this:
>>> The VPS isn't allowing Ports 9001 and 9030
>>> Should I investigate further getting my iptables up and running or
>>> just contact the admin and have them allow the ports?
>>> As I mentioned previously even after saving the tables upon reboot
>>> iptables -L shows no rules, the file is empty.
>>>
>>>   :~$ iptables -L
>>> Chain INPUT (policy ACCEPT)
>>> target prot opt source   destination
>>>
>>> Chain FORWARD (policy ACCEPT)
>>> target prot opt source   destination
>>>
>>> Chain OUTPUT (policy ACCEPT)
>>> target prot opt source   destination
>>>   Any further suggestions would be appreciated.
>>>
>>> Thanks
>>> -BEGIN PGP SIGNATURE-
>>> Version: GnuPG v2.0.22 (MingW32)
>>>
>>> iQEcBAEBAgAGBQJWZF8qAAoJEJQqkaGlFNDPO18H/2Axj4EeGf5joYQ3n2SH1cgs
>>> HhDAawaiMaSKMcfC/Oc9TudwKAxkoY+QkhegZr5senNKXrXjNPeLucfejkRBiUoJ
>>> 8KLOZabSGH2Uf89JNa4ZFbf9QVIiU8GdNJ0vSGy55iAuJQl14ZUpDRQeNnGkmwb5
>>> uhADchwTVjK7Pq+ELyG6OI6l0jlQ69TWCpgH4lnMjQ5U+Nr1QKyApxXqr1ap5Heb
>>> KJmlwchTv4zAxX2eBc1DPqAXdc9OsvEsPG/r/zp4Z/wPWxsUTGoZWoXsWv4xyjPQ
>>> xzAzUKD+b+AvqGQ3ehQbdXtg423kO7/amVidAzux8mDmMeZuFoP3tpfqLd8cH+s=
>>> =uoin
>>> -END PGP SIGNATURE-
>>> ___
>>> tor-relays mailing list
>>> tor-relays@lists.torproject.org
>>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>>>
>>
>>
>> ___
>> tor-relays mailing list
>> tor-relays@lists.torproject.org
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>>
>
>
>
> --
> http://www.backbox.org
> http://www.pentester.iz.rs
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] tor-relays Digest, Vol 59, Issue 8

[Manager Bahia del Sol LLC]

  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 address. The ip addresses are IP:    142.4.217.95Decimal:    2382682463Hostname:    ca3.pulseservers.comASN:    16276ISP:    OVH HostingIP:    167.114.35.28Decimal:    2809275164Hostname:    167.114.35.28ASN:    16276ISP:    OVH Hosting  Message: 2Date: Sat, 5 Dec 2015 11:18:18 -0800From: Kurt Besig To: tor-relays@lists.torproject.orgSubject: Re: [tor-relays] UnbelieveableMessage-ID: <5663387a.3010...@socal.rr.com>Content-Type: text/plain; charset=windows-1252 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.000 [notice] Our IP Address has changed from 142.4.217.95 to 167.114.35.28; rebuilding descriptor (source: METHOD=INTERFACE).  Dec 05 21:18:42.000 [notice] Your IP address seems to have changed to 142.4.217.95 (METHOD=GETHOSTNAME HOSTNAME=ca3.pulseservers.com). Updating. Dec 05 21:18:42.000 [notice] Our IP Address has changed from 167.114.35.28 to 142.4.217.95; rebuilding descriptor (source: METHOD=GETHOSTNAME HOSTNAME=ca3.pulseservers.com). Dec 05 21:18:43.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. Dec 05 21:38:37.000 [warn] Your server (142.4.217.95:9030) has not managed to confirm that its DirPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc. Dec 05 21:58:37.000 [warn] Your server (142.4.217.95:9030) has not managed to confirm that its DirPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.I've gotten this far, not being much good at networking I can't tellwhere the problem lies.. do I need to forward something? ___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] VPS/Tor Almost There

[ZEROF]

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,
> 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 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
>> and arm open properly.
>> The problem now boils down to this:
>> The VPS isn't allowing Ports 9001 and 9030
>> Should I investigate further getting my iptables up and running or
>> just contact the admin and have them allow the ports?
>> As I mentioned previously even after saving the tables upon reboot
>> iptables -L shows no rules, the file is empty.
>>
>>   :~$ iptables -L
>> Chain INPUT (policy ACCEPT)
>> target prot opt source   destination
>>
>> Chain FORWARD (policy ACCEPT)
>> target prot opt source   destination
>>
>> Chain OUTPUT (policy ACCEPT)
>> target prot opt source   destination
>>   Any further suggestions would be appreciated.
>>
>> Thanks
>> -BEGIN PGP SIGNATURE-
>> Version: GnuPG v2.0.22 (MingW32)
>>
>> iQEcBAEBAgAGBQJWZF8qAAoJEJQqkaGlFNDPO18H/2Axj4EeGf5joYQ3n2SH1cgs
>> HhDAawaiMaSKMcfC/Oc9TudwKAxkoY+QkhegZr5senNKXrXjNPeLucfejkRBiUoJ
>> 8KLOZabSGH2Uf89JNa4ZFbf9QVIiU8GdNJ0vSGy55iAuJQl14ZUpDRQeNnGkmwb5
>> uhADchwTVjK7Pq+ELyG6OI6l0jlQ69TWCpgH4lnMjQ5U+Nr1QKyApxXqr1ap5Heb
>> KJmlwchTv4zAxX2eBc1DPqAXdc9OsvEsPG/r/zp4Z/wPWxsUTGoZWoXsWv4xyjPQ
>> xzAzUKD+b+AvqGQ3ehQbdXtg423kO7/amVidAzux8mDmMeZuFoP3tpfqLd8cH+s=
>> =uoin
>> -END PGP SIGNATURE-
>> ___
>> tor-relays mailing list
>> tor-relays@lists.torproject.org
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>>
>
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>



-- 
http://www.backbox.org
http://www.pentester.iz.rs
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] VPS/Tor Almost There

[David Schulz]

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 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
and arm open properly.
The problem now boils down to this:
The VPS isn't allowing Ports 9001 and 9030
Should I investigate further getting my iptables up and running or
just contact the admin and have them allow the ports?
As I mentioned previously even after saving the tables upon reboot
iptables -L shows no rules, the file is empty.

  :~$ iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source   destination

Chain FORWARD (policy ACCEPT)
target prot opt source   destination

Chain OUTPUT (policy ACCEPT)
target prot opt source   destination
  Any further suggestions would be appreciated.

Thanks
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJWZF8qAAoJEJQqkaGlFNDPO18H/2Axj4EeGf5joYQ3n2SH1cgs
HhDAawaiMaSKMcfC/Oc9TudwKAxkoY+QkhegZr5senNKXrXjNPeLucfejkRBiUoJ
8KLOZabSGH2Uf89JNa4ZFbf9QVIiU8GdNJ0vSGy55iAuJQl14ZUpDRQeNnGkmwb5
uhADchwTVjK7Pq+ELyG6OI6l0jlQ69TWCpgH4lnMjQ5U+Nr1QKyApxXqr1ap5Heb
KJmlwchTv4zAxX2eBc1DPqAXdc9OsvEsPG/r/zp4Z/wPWxsUTGoZWoXsWv4xyjPQ
xzAzUKD+b+AvqGQ3ehQbdXtg423kO7/amVidAzux8mDmMeZuFoP3tpfqLd8cH+s=
=uoin
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays



___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] VPS/Tor Almost There

[Kurt Besig]

-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
and arm open properly.
The problem now boils down to this:
The VPS isn't allowing Ports 9001 and 9030
Should I investigate further getting my iptables up and running or
just contact the admin and have them allow the ports?
As I mentioned previously even after saving the tables upon reboot
iptables -L shows no rules, the file is empty.

 :~$ iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source   destination

Chain FORWARD (policy ACCEPT)
target prot opt source   destination

Chain OUTPUT (policy ACCEPT)
target prot opt source   destination
 Any further suggestions would be appreciated.

Thanks
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJWZF8qAAoJEJQqkaGlFNDPO18H/2Axj4EeGf5joYQ3n2SH1cgs
HhDAawaiMaSKMcfC/Oc9TudwKAxkoY+QkhegZr5senNKXrXjNPeLucfejkRBiUoJ
8KLOZabSGH2Uf89JNa4ZFbf9QVIiU8GdNJ0vSGy55iAuJQl14ZUpDRQeNnGkmwb5
uhADchwTVjK7Pq+ELyG6OI6l0jlQ69TWCpgH4lnMjQ5U+Nr1QKyApxXqr1ap5Heb
KJmlwchTv4zAxX2eBc1DPqAXdc9OsvEsPG/r/zp4Z/wPWxsUTGoZWoXsWv4xyjPQ
xzAzUKD+b+AvqGQ3ehQbdXtg423kO7/amVidAzux8mDmMeZuFoP3tpfqLd8cH+s=
=uoin
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays