Slow bandwidth, bridge + obfsproxy project (+Socks for LAN?)
Hey all, 1. Coming here to learn some quick lessons about bridges+obfsproxy. I'm thinking about that when I see some slow upload bandwidth speed like at home for example. Running a relay will be a bottleneck... so a bridge will be more useful... (less than 1Mbits/s upload :s ) 2. If computers running bridges are not 24/24 powered, will it be useful for people ? When I see the "lifecycle of a relay" article, I can understand a relay will be useful if it's always available, but what about a bridge ? (office hours for example) 3. Will this bridge+obfsproxy can be useful for the LAN computers, with Socks for example for LAN connections, to redirect traffic to Tor ? Those services can run together on the same instance ? ex on the doc: SocksPort 4000 #example for the LAN connection (default = 0) ORPort auto BridgeRelay 1 Exitpolicy reject *:* 4. I'm confused, the "bridge" is acting like a relay ? (like a router on a network, 50% upload / 50% download...?). Or like a hidden door to contact the Tor network, and the client will only use relays after without the bridge ? (I don't want this server to be a bottleneck...!) Many thx for your help and your thoughts about this little contribution! -- Petrusko PubKey EBE23AE5 C0BF 2184 4A77 4A18 90E9 F72C B3CA E665 EBE2 3AE5
On 25.04.2016 11:45, Petrusko wrote:
4. I'm confused, the "bridge" is acting like a relay ? (like a router on a network, 50% upload / 50% download...?). Or like a hidden door to contact the Tor network, and the client will only use relays after without the bridge ? (I don't want this server to be a bottleneck...!)
A bridge is the first hop of a bridge-using client, followed by the other regular hops for a Tor circuit. The bridge's upload and download will directly correspond to the upload/download of the specific user(s) of your bridge. (Plus some overhead for directory requests etc) So if your bridge's internet connection can handle another user next to you, it can handle the bridge.
Ok thx for this explanation! So if this server will be the n°1 on the onion network for the client, it will be a the first bottleneck because of the slow upload bandwidth... (~1Mbits/s). I was thinking the bridge was used as a temporary door to communicate with the Tor network, then the client will use fast relays... But If I've understood, the bridge will be always used by the client as a 1st relay... So finally : + obfsproxy will help people to connect to Tor if censor is too hard ? So it can be helpful ? 1Mbits/s is not very high when I see some big numbers on others servers! + can help the LAN computers to connect to Tor easily (why not with Privoxy...) Is there a tool to show the bridge's usage stats ? (because Atlas and Globe will not show the server stats if I'm not wrong...) Thx! Le 30/04/2016 16:36, Random Tor Node Operator a écrit :
On 25.04.2016 11:45, Petrusko wrote:
4. I'm confused, the "bridge" is acting like a relay ? (like a router on a network, 50% upload / 50% download...?). Or like a hidden door to contact the Tor network, and the client will only use relays after without the bridge ? (I don't want this server to be a bottleneck...!) A bridge is the first hop of a bridge-using client, followed by the other regular hops for a Tor circuit. The bridge's upload and download will directly correspond to the upload/download of the specific user(s) of your bridge. (Plus some overhead for directory requests etc)
So if your bridge's internet connection can handle another user next to you, it can handle the bridge.
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-- Petrusko PubKey EBE23AE5 C0BF 2184 4A77 4A18 90E9 F72C B3CA E665 EBE2 3AE5
participants (2)
-
Petrusko -
Random Tor Node Operator