Re: [tor-relays] Running A Bridge Alongside My Relay

[Mirimir <mirimir@xxxxxxxxxx>]

On 05/26/2018 03:10 PM, Keifer Bly wrote:
> They do support  port forwarding, I have used it before. I have just only ever used their service before with Windows so may need to get used to it some on Linux.  Is there a guide to setting up an obfuscated bridge on Debian? I am aware this may not work fantastically as virtual machines can be a pain, and also the vpn may not be the best way to run a relay, but will try it to see if it works out ok.

Well, their website isn't very helpful about how to do it :)

This looks like a decent guide:
https://dcamero.azurewebsites.net/tor-obfs4-bridge.html

But maybe you'd be happier using nano as editor, instead of vi ;)

In /etc/tor/torrc you'd want "PublishServerDescriptor 1" instead of
"PublishServerDescriptor 0".

> From: Mirimir
> Sent: Saturday, May 26, 2018 6:56 PM
> To: tor-relays@xxxxxxxxxxxxxxxxxxxx
> Subject: Re: [tor-relays] Running A Bridge Alongside My Relay
> 
> On 05/26/2018 01:30 PM, Keifer Bly wrote:
>> I am subscribed to a vpn service (purevpn) however there service changes
>> their IP address and location every few minutes. Would this be a useable
>> bridge? Thank you.
> 
> It's the custom PureVPN client that's changing servers periodically. If
> you run standard openvpn demon, you can specify particular servers. So
> the IP address won't be changing.
> 
> However, you would need to forward the bridge port (TCP 443) to the VPN
> exit server. And it looks like PureVPN doesn't allow that. So you'd need
> to use a VPN service that does.
> 
> For the one-year plan, PureVPN costs ~$4 per month. Decent VPNs that do
> support port forwarding cost about $5-$9 per month. But for that, you
> can lease a VPS with gigabit uplink. And running a bridge won't likely
> generate abuse complaints.
> 
>> On Sat, May 26, 2018 at 4:40 PM Neel Chauhan <neel@xxxxxxxxx> wrote:
>>
>>> You normally can't run a server through a regular "proxy" as you would
>>> need to be able to advertise an open port for the bridge and regular
>>> proxy servers won't let you do that. You can do it if you use a VPN with
>>> a public IP address for the bridge however, or a second IP address, but
>>> you would need to pay $$$ for this.
>>>
>>> -Neel Chauhan
>>>
>>> ===
>>>
>>> https://www.neelc.org/
>>>
>>> On 2018-05-26 16:19, Keifer Bly wrote:
>>>> Yes but I would run it through the proxy so it would have the proxy IP
>>>> address. I just noticed tor could use more bridges as there are four
>>>> times as many public relays as their are bridges.
>>>>
>>>> Sent from my iPhone
>>>>
>>>> On May 26, 2018, at 12:44 PM, Logforme <m7527@xxxxxx> wrote:
>>>>
>>>>>> So I am considering running a bridge alongside my relay gotland
>>>>> Would the bridge use the same public IP address as the relay?
>>>>> Since you already run a relay, that IP address is public. The point of
>>>>> bridges is that they are not public so they are harder to block.
>>>>> A government that censors the internet would surely block access to
>>>>> all Tor relay IP addresses.
>>>>>
>>>>> _______________________________________________
>>>>> tor-relays mailing list
>>>>> tor-relays@xxxxxxxxxxxxxxxxxxxx
>>>>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>>>> _______________________________________________
>>>> tor-relays mailing list
>>>> tor-relays@xxxxxxxxxxxxxxxxxxxx
>>>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>>> _______________________________________________
>>> tor-relays mailing list
>>> tor-relays@xxxxxxxxxxxxxxxxxxxx
>>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>>>
>>
>>
>>
>> _______________________________________________
>> tor-relays mailing list
>> tor-relays@xxxxxxxxxxxxxxxxxxxx
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>>
> _______________________________________________
> tor-relays mailing list
> tor-relays@xxxxxxxxxxxxxxxxxxxx
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
> 
> 
> 
> _______________________________________________
> tor-relays mailing list
> tor-relays@xxxxxxxxxxxxxxxxxxxx
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays