Hi
I have more than one ip address in a server - I want to assign a new ip to a current relay that I am running. The new ip is correctly setup on my ubuntu server so i know thats ok
In order to make the relay use the new ip I added Address <New IP Address> to the torrc file and restarted tor - this did seem to work and tor detectedthe new address and started to use it but then I got a number of warnings like 'Remote server sent bogus reason code'
The relay does seem to be working but with these errors im not sure - is the method above how you should assign a particular IP address to a Tor relay?
Thanks for any advice
Snap
On Mon, Nov 28, 2016 at 08:31:39PM +0000, Sec INT wrote:
- this did seem to work and tor detectedthe new address and started to use it but then I got a number of warnings like
'Remote server sent bogus reason code'
The relay does seem to be working but with these errors im not sure
Those warnings are scary-sounding but not dangerous: https://trac.torproject.org/projects/tor/ticket/20307
- is the method above how you should assign a particular IP address to a Tor relay?
It depends what you're trying to do. If your server has one primary IP address but you want to be running your Tor relay on a different one, then you probably want to set both Address and OutboundBindAddress. You may also wish to specify an IP address in your ORPort line, to bind your listeners to one or some but not all of your IP addresses -- but if you don't care there's no need to do that.
--Roger
Hi Thanks for the reply - exit node is all up and running along with 6 relays so all happy here - I decided just to keep the main IP
One thing I did have was the DirFrontpage parameter in the torrc file was badly formed so I commented it out but was wondering if anyone else had that issue? It looks fine to me from what i can see in the sample file
Cheers
On 28 Nov 2016, at 21:41, Roger Dingledine arma@mit.edu wrote:
On Mon, Nov 28, 2016 at 08:31:39PM +0000, Sec INT wrote:
- this did seem to work and tor detectedthe new address and started to use it but then I got a number of warnings like
'Remote server sent bogus reason code'
The relay does seem to be working but with these errors im not sure
Those warnings are scary-sounding but not dangerous: https://trac.torproject.org/projects/tor/ticket/20307
- is the method above how you should assign a particular IP address to a Tor relay?
It depends what you're trying to do. If your server has one primary IP address but you want to be running your Tor relay on a different one, then you probably want to set both Address and OutboundBindAddress. You may also wish to specify an IP address in your ORPort line, to bind your listeners to one or some but not all of your IP addresses -- but if you don't care there's no need to do that.
--Roger
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On Mon, Nov 28, 2016 at 11:25:29PM +0000, Sec INT wrote:
Hi Thanks for the reply - exit node is all up and running along with 6 relays so all happy here - I decided just to keep the main IP
Thanks for running relays!
One thing I did have was the DirFrontpage parameter in the torrc file was badly formed so I commented it out but was wondering if anyone else had that issue? It looks fine to me from what i can see in the sample file
Can you clarify what you mean by badly formed?
Basically that option takes a file and serves it out of the DirPort when people ask for the root ("/").
So if the file that gets served is badly formed in your browser, then consider fixing the file. Whereas if it can't find the file, then consider pointing it at a file that really exists. :)
Hope that helps, --Roger
Hi
Thanks ;-) As for the 'DirFrontPAge' the error is below
Nov 29 09:52:55.000 [warn] Failed to parse/validate config: Unknown option 'DirFrontPage'. Failing. Nov 29 09:52:55.000 [err] Reading config failed--see warnings above. For usage, try -h. Nov 29 09:52:55.000 [warn] Restart failed (config error?). Exiting.
the setting is
DirPort 80 DirFrontPage /etc/tor/tor-exit-notice.html ExitPolicy accept *:20-21 # FTP - File Transfer Protocol (data / control) etc
the html page is working fine so its not that - it looks like DirFrontPAge is an unknown option?
any thoughts?
cheers
Mark
On Mon, Nov 28, 2016 at 11:43 PM, Roger Dingledine arma@mit.edu wrote:
On Mon, Nov 28, 2016 at 11:25:29PM +0000, Sec INT wrote:
Hi Thanks for the reply - exit node is all up and running along with 6
relays so all happy here - I decided just to keep the main IP
Thanks for running relays!
One thing I did have was the DirFrontpage parameter in the torrc file was badly formed so I commented it out but was wondering if anyone else had that issue? It looks fine to me from what i can see in the sample file
Can you clarify what you mean by badly formed?
Basically that option takes a file and serves it out of the DirPort when people ask for the root ("/").
So if the file that gets served is badly formed in your browser, then consider fixing the file. Whereas if it can't find the file, then consider pointing it at a file that really exists. :)
Hope that helps, --Roger
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On Tue, 29 Nov 2016, Sec INT wrote:
Hi
Thanks ;-) As for the 'DirFrontPAge' the error is below
Nov 29 09:52:55.000 [warn] Failed to parse/validate config: Unknown option 'DirFrontPage'. Failing.
What is DirFrontPage supposed to be? The manpage only mentions a DirPortFrontPage.
Hi
Its on a number of setup guides for an exit relay whereby if someone looks up your ip and port 80 they will see this webpage - its designed to reduce DMCA notices and accusations against someone running an exit - I've attached the actual page
https://blog.torproject.org/running-exit-node https://tor-relay.co/
Perhaps this option no longer exists as I use the most up to date versions of tor (0.2.8.9) at the moment - I run on ports 443 and 80
cheers
Mark
On Tue, Nov 29, 2016 at 10:14 AM, Peter Palfrader weasel@torproject.org wrote:
On Tue, 29 Nov 2016, Sec INT wrote:
Hi
Thanks ;-) As for the 'DirFrontPAge' the error is below
Nov 29 09:52:55.000 [warn] Failed to parse/validate config: Unknown
option
'DirFrontPage'. Failing.
What is DirFrontPage supposed to be? The manpage only mentions a DirPortFrontPage.
-- | .''`. ** Debian ** Peter Palfrader | : :' : The universal https://www.palfrader.org/ | `. `' Operating System | `- https://www.debian.org/ _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On Tue, 29 Nov 2016, Sec INT wrote:
On Tue, Nov 29, 2016 at 10:14 AM, Peter Palfrader weasel@torproject.org wrote:
On Tue, 29 Nov 2016, Sec INT wrote:
Nov 29 09:52:55.000 [warn] Failed to parse/validate config: Unknown option 'DirFrontPage'. Failing.
What is DirFrontPage supposed to be? The manpage only mentions a DirPortFrontPage.
Its on a number of setup guides for an exit relay whereby if someone looks up your ip and port 80 they will see this webpage - its designed to reduce DMCA notices and accusations against someone running an exit - I've attached the actual page
https://blog.torproject.org/running-exit-node https://tor-relay.co/
Perhaps this option no longer exists as I use the most up to date versions of tor (0.2.8.9) at the moment - I run on ports 443 and 80
Please read what I wrote, and read your error message.
Got it - sorry was distracted by Nagios install ;-)
all working - I've added a comment to the site I was using
cheers
Mark
On Tue, Nov 29, 2016 at 10:32 AM, Peter Palfrader weasel@torproject.org wrote:
On Tue, 29 Nov 2016, Sec INT wrote:
On Tue, Nov 29, 2016 at 10:14 AM, Peter Palfrader weasel@torproject.org
wrote:
On Tue, 29 Nov 2016, Sec INT wrote:
Nov 29 09:52:55.000 [warn] Failed to parse/validate config: Unknown
option 'DirFrontPage'. Failing.
What is DirFrontPage supposed to be? The manpage only mentions a DirPortFrontPage.
Its on a number of setup guides for an exit relay whereby if someone
looks
up your ip and port 80 they will see this webpage - its designed to
reduce
DMCA notices and accusations against someone running an exit - I've attached the actual page
https://blog.torproject.org/running-exit-node https://tor-relay.co/
Perhaps this option no longer exists as I use the most up to date
versions
of tor (0.2.8.9) at the moment - I run on ports 443 and 80
Please read what I wrote, and read your error message.
-- | .''`. ** Debian ** Peter Palfrader | : :' : The universal https://www.palfrader.org/ | `. `' Operating System | `- https://www.debian.org/ _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hi
Not sure if my reply worked yesterday so thanks for this - adding 'port' worked and Ive now got two fully working exits ;-) thanks for the help
Cheers Mark
On 29 Nov 2016, at 10:32, Peter Palfrader weasel@torproject.org wrote:
On Tue, 29 Nov 2016, Sec INT wrote:
On Tue, Nov 29, 2016 at 10:14 AM, Peter Palfrader weasel@torproject.org wrote:
On Tue, 29 Nov 2016, Sec INT wrote: Nov 29 09:52:55.000 [warn] Failed to parse/validate config: Unknown option 'DirFrontPage'. Failing.
What is DirFrontPage supposed to be? The manpage only mentions a DirPortFrontPage.
Its on a number of setup guides for an exit relay whereby if someone looks up your ip and port 80 they will see this webpage - its designed to reduce DMCA notices and accusations against someone running an exit - I've attached the actual page
https://blog.torproject.org/running-exit-node https://tor-relay.co/
Perhaps this option no longer exists as I use the most up to date versions of tor (0.2.8.9) at the moment - I run on ports 443 and 80
Please read what I wrote, and read your error message.
-- | .''`. ** Debian ** Peter Palfrader | : :' : The universal https://www.palfrader.org/ | `. `' Operating System | `- https://www.debian.org/ _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays@lists.torproject.org