-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This time the iptable applied, but I still have the same problem; cannot
verify that 443 is reachable.
- --
People just like you lose untold millions in personal wealth due to
frivolous lawsuits and unfair government seizures.
Are you protected? Read
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I got nothing:
Chain PREROUTING (policy ACCEPT)
target prot opt source destination
Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source
Andrew Del Vecchio wrote:
I got nothing:
Chain PREROUTING (policy ACCEPT)
target prot opt source destination
Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source
Andrew Del Vecchio wrote:
Sudo route and iptables -L don't show the below in the routing table as
being applied. Any debugging suggestions?
iptables -L -t nat
Olaf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sudo route and iptables -L don't show the below in the routing table as
being applied. Any debugging suggestions?
~Andrew
- --
People just like you lose untold millions in personal wealth due to
frivolous lawsuits and unfair government seizures.
Are
On Mon, Dec 24, 2007 at 10:12:48AM +0100, TOR-Admin (gpfTOR1) wrote:
Drake Wilson schrieb:
The obvious way to handle this, if you have iptables available, is
probably to run the Tor server on some other port (say, 1443) and then
use iptables to redirect incoming connections on port 443 to
Trying to run a bridge I get the following error:
Starting tor daemon: tor...
Dec 24 08:13:15.454 [notice] Tor v0.2.0.14-alpha (r12937). This is
experimental software. Do not rely on it for strong anonymity. (Running on
Linux x86_64)
Dec 24 08:13:15.456 [notice] Initialized libevent version 1.1a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian W. Carver wrote:
I sort of understand what the error is saying but I don't know how to fix
it. Suggestions?
http://archives.seul.org/or/talk/Dec-2007/msg00284.html ;-)
- --
Marco Bonetti
Slackintosh Linux Project Developer:
Brian wrote:
I sort of understand what the error is saying but I don't know how to
fix
it. Suggestions?
http://archives.seul.org/or/talk/Dec-2007/msg00284.html ;-)
- --
Marco Bonetti
Ah, thanks. Now tor started without error. But, how can I tell if the
bridge is working? The log file
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ricky Fitz wrote:
(snip)
Bridge relays (or bridges for short) are Tor relays that aren't listed
in the main directory.
If I am running TOR as a server, and I add the option bridge relay,
than my server wouldn't be available in the main
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Drake Wilson wrote:
Quoth Andrew Del Vecchio [EMAIL PROTECTED], on 2007-12-23 13:36:45 -0800:
Roger, I'm good to go except for one thing: The permissions issue with
the port being 443 (less than 1024). Is there an easy way around this
without
2007/12/22, Roger Dingledine [EMAIL PROTECTED]:
- is there a log, so that I see, if someone is entering the url?
Not really. You could run Vidalia's 'bandwidth graph' and see, but Tor
does its own activity too, so it would probably be hard to tell.
What sort of interface did you have in
Hi folks,
I had some problems with my mailserver, so probably the following
questions were already discussed. If so, I am sorry.
Bridge relays (or bridges for short) are Tor relays that aren't listed
in the main directory.
If I am running TOR as a server, and I add the option bridge relay,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Roger, I'm good to go except for one thing: The permissions issue with
the port being 443 (less than 1024). Is there an easy way around this
without having to create a chroot jail, etc? I'm using the latest Ubuntu
7.10. I can change file permissions
Quoth Andrew Del Vecchio [EMAIL PROTECTED], on 2007-12-23 13:36:45 -0800:
Roger, I'm good to go except for one thing: The permissions issue with
the port being 443 (less than 1024). Is there an easy way around this
without having to create a chroot jail, etc? I'm using the latest Ubuntu
7.10.
On Sat, Dec 22, 2007 at 05:00:28AM -0500, Roger Dingledine wrote:
The harder way is to edit your torrc file manually
https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc
and add the following lines:
ORPort 443
BridgeRelay 1
PublishServerDescriptor bridge
ExitPolicy reject
16 matches
Mail list logo
