Hi,
So my bridge at https://metrics.torproject.org/rs.html#details/4D6E3CA2110FC36D3106C86940A1D4C8C91923AB says it has “none “, though the torrc file has it set to be distributed publicly. I’m wondering why the bridge would say that, when it obviously is being used as it’s apparently blocked in Russia? I have not personally given the bridge to anyone. Thanks.
–Keifer
So my bridge at
Relay Search
4C8C91923AB says it has “none “,
Well, then you have configured BridgeDistribution (Default: any) to none.
though the torrc file has it set to be distributed publicly.
PublishServerDescriptor has nothing to do with BridgeDistribution method,
'man torrc' explains the config options.
I have not personally given the bridge to anyone.
Then nobody can use the bridge except you 
You can also see this in the metrics history or in /var/lib/tor/stats/bridge-
stats.
On Donnerstag, 16. Februar 2023 06:15:02 CET Keifer Bly wrote:
--
╰_╯ Ciao Marco!
Debian GNU/Linux
It's free software and it gives you freedom!
Ok. Here is the torrc file:
GNU nano 3.2 /etc/tor/torrc
Nickname gbridge
ORPort 443
SocksPort 0
BridgeRelay 1
PublishServerDescriptor bridge
ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
ServerTransportListenAddr obfs4 0.0.0.0:8080
ExtOrPort auto
Log notice file /var/log/tor/notices.log
ExitPolicy reject :
AccountingMax 5 GB
ContactInfo keiferdodderblyyatgmaildoddercom
Where in this torrc file is that configured? And how would it be blocked in Russia already if it hasn’t even been used? Thanks.
–Keifer
Ok. Here is the torrc file:
GNU nano 3.2 /etc/tor/torrc
Nickname gbridge
ORPort 443
SocksPort 0
BridgeRelay 1
PublishServerDescriptor bridge
ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
ServerTransportListenAddr obfs4 0.0.0.0:8080
ExtOrPort auto
Log notice file /var/log/tor/notices.log
ExitPolicy reject *:*
AccountingMax 5 GB
ContactInfo keiferdodderblyyatgmaildoddercomWhere in this torrc file is that configured?
Then set it to 'any' and wait 24-48 hours to see what happens. Maybe there was
an error in the db.
If your bridge is still not distributed, it could be due to the outdated
obfs4proxy or because of 'AccountingMax 5 GB'.
Sorry but, 5 GB is a 'fart in the wind' the accounting period would only be a
few hours a month. It's not even worth distributing them because it would only
frustrate the users.
And how would it be blocked in
Russia already if it hasn't even been used?
Why should this new feature of the bridgedb, more precisely the rdsys backend,
have anything to do with whether someone uses a bridge? This is a bridgedb
distribution method introduced by meskio.
On Samstag, 18. Februar 2023 18:56:00 CET Keifer Bly wrote:
--
╰_╯ Ciao Marco!
Debian GNU/Linux
It's free software and it gives you freedom!
Where in the torrc file would I set it to any? I am looking for a way to run a bridge without being charged a huge amount of money for it, and I was curious how it would have been detected by Russia if noone had used the bridge there? Thanks.
–Keifer
On Mon, Feb 20, 2023 at 8:45 AM <lists@for-privacy.net> wrote:
On Samstag, 18. Februar 2023 18:56:00 CET Keifer Bly wrote:
Ok. Here is the torrc file:
GNU nano 3.2 /etc/tor/torrc
Nickname gbridge
ORPort 443
SocksPort 0
BridgeRelay 1
PublishServerDescriptor bridge
ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
ServerTransportListenAddr obfs4 0.0.0.0:8080
ExtOrPort auto
Log notice file /var/log/tor/notices.log
ExitPolicy reject :
AccountingMax 5 GB
ContactInfo keiferdodderblyyatgmaildoddercomWhere in this torrc file is that configured?
Then set it to ‘any’ and wait 24-48 hours to see what happens. Maybe there was
an error in the db.If your bridge is still not distributed, it could be due to the outdated
obfs4proxy or because of ‘AccountingMax 5 GB’.
Sorry but, 5 GB is a ‘fart in the wind’ the accounting period would only be a
few hours a month. It’s not even worth distributing them because it would only
frustrate the users.And how would it be blocked in
Russia already if it hasn’t even been used?
Why should this new feature of the bridgedb, more precisely the rdsys backend,
have anything to do with whether someone uses a bridge? This is a bridgedb
distribution method introduced by meskio.–
╰_╯ Ciao Marco!Debian GNU/Linux
It’s free software and it gives you freedom!_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hi,
Your torrc is correct wrt to distribution mechanism (your bridge is
indicating "bridge-distribution-request any" in the descriptor it
sends), but for the record, the line would have been
"BridgeDistribution any".
A bridge uses less bandwidth than a relay, but it's still a proxy. At
5GB per month, you'd be providing a steady 16kbps over the month, or a
single mbps for little over 11 hours. That's very little, if you can't
have more bandwidth (by using a provider with no bandwidth accounting,
or one that gives better pricing per bandwidth), I fear your bridge
won't be very useful at all. Mine consumes between a few hundred GB
and a few TB depending on the distribution mechanism.
Are you sure your bridge is reachable? Bridgestrap reports suggest it isn't.
As the bridge operator, you should know its bridge line. Can you test
it with Tor Browser to make sure?
Given your accounting limits, it could be unreachable because
currently hibernating. Or you could have a firewall issue, or
something else.
I believe not passing bridgestrap can explain not being assigned a
distribution mechanism.
It might also explain why it would be considered blocked in Russia: if
it's not reachable from anywhere, it's not reachable from Russia. An
other possibility, given you use 443 for your ORPort, is that your
bridge was indeed detected by just scanning the whole internet. The
ORPort is very recognizable (enough that some of my former bridges
ended up tagged "tor" on Shodan) so it should be put on a port that's
less likely to be scanned.
Regards,
trinity-1686a
On Mon, 20 Feb 2023 at 21:29, Keifer Bly <keifer.bly@gmail.com> wrote:
Where in the torrc file would I set it to any? I am looking for a way to run a bridge without being charged a huge amount of money for it, and I was curious how it would have been detected by Russia if noone had used the bridge there? Thanks.
--KeiferOn Mon, Feb 20, 2023 at 8:45 AM <lists@for-privacy.net> wrote:
On Samstag, 18. Februar 2023 18:56:00 CET Keifer Bly wrote:
> Ok. Here is the torrc file:
>
> GNU nano 3.2 /etc/tor/torrc
>
>
> Nickname gbridge
> ORPort 443
> SocksPort 0
> BridgeRelay 1
> PublishServerDescriptor bridge
> ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
> ServerTransportListenAddr obfs4 0.0.0.0:8080
> ExtOrPort auto
> Log notice file /var/log/tor/notices.log
> ExitPolicy reject *:*
> AccountingMax 5 GB
> ContactInfo keiferdodderblyyatgmaildoddercom
>
>
> Where in this torrc file is that configured?
Then set it to 'any' and wait 24-48 hours to see what happens. Maybe there was
an error in the db.If your bridge is still not distributed, it could be due to the outdated
obfs4proxy or because of 'AccountingMax 5 GB'.
Sorry but, 5 GB is a 'fart in the wind' the accounting period would only be a
few hours a month. It's not even worth distributing them because it would only
frustrate the users.> And how would it be blocked in
> Russia already if it hasn't even been used?
Why should this new feature of the bridgedb, more precisely the rdsys backend,
have anything to do with whether someone uses a bridge? This is a bridgedb
distribution method introduced by meskio.--
╰_╯ Ciao Marco!Debian GNU/Linux
It's free software and it gives you freedom!_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
tor-relays Info Page_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
tor-relays Info Page
_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Well,
So I just changed my torrc to this:
Nickname gbridge
ORPort 443
SocksPort 0
BridgeRelay 1
PublishServerDescriptor bridge
BridgeDistribution email
ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
ServerTransportListenAddr obfs4 0.0.0.0:8080
ExtOrPort auto
Log notice file /var/log/tor/notices.log
ExitPolicy reject :
AccountingMax 50 GB
ContactInfo keiferdodderblyyatgmaildoddercom
Trying to avoid being charged a huge amount for traffic as these VPS providers can be ridiculous when it comes to that, which is why it was set to so little. Ran killall -HUP tor to reload it and see that happens in the next day or so. And the reason why it’s on port 443 is so as to be on a port that’s not likely blocked by network administrators. Thank you.
–Keifer
And the reason why it's on port 443 is so as to be on a port that's not likely blocked by network administrators.
That might be useful for the ORPort of a relay, and for the obfs4 port
of a bridge, but not for the ORPort of a bridge. Clients are not
supposed to connect to it.
The only reason it's exposed is because the bridge authority still
requires it to verify the bridge is reachable. See
Obfsbridges should be able to "disable" their ORPort (#7349) · Issues · The Tor Project / Core / Tor · GitLab.
You are better of using 443 for the ServerTransportListenAddr, and
some high port for ORPort.
On Tue, 21 Feb 2023 at 03:05, Keifer Bly <keifer.bly@gmail.com> wrote:
Well,
So I just changed my torrc to this:
Nickname gbridge
ORPort 443
SocksPort 0
BridgeRelay 1
PublishServerDescriptor bridge
BridgeDistribution email
ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
ServerTransportListenAddr obfs4 0.0.0.0:8080
ExtOrPort auto
Log notice file /var/log/tor/notices.log
ExitPolicy reject *:*
AccountingMax 50 GB
ContactInfo keiferdodderblyyatgmaildoddercomTrying to avoid being charged a huge amount for traffic as these VPS providers can be ridiculous when it comes to that, which is why it was set to so little. Ran killall -HUP tor to reload it and see that happens in the next day or so. And the reason why it's on port 443 is so as to be on a port that's not likely blocked by network administrators. Thank you.
--KeiferOn Mon, Feb 20, 2023 at 2:23 PM trinity pointard <trinity.pointard@gmail.com> wrote:
Hi,
Your torrc is correct wrt to distribution mechanism (your bridge is
indicating "bridge-distribution-request any" in the descriptor it
sends), but for the record, the line would have been
"BridgeDistribution any".
A bridge uses less bandwidth than a relay, but it's still a proxy. At
5GB per month, you'd be providing a steady 16kbps over the month, or a
single mbps for little over 11 hours. That's very little, if you can't
have more bandwidth (by using a provider with no bandwidth accounting,
or one that gives better pricing per bandwidth), I fear your bridge
won't be very useful at all. Mine consumes between a few hundred GB
and a few TB depending on the distribution mechanism.Are you sure your bridge is reachable? Bridgestrap reports suggest it isn't.
As the bridge operator, you should know its bridge line. Can you test
it with Tor Browser to make sure?
Given your accounting limits, it could be unreachable because
currently hibernating. Or you could have a firewall issue, or
something else.
I believe not passing bridgestrap can explain not being assigned a
distribution mechanism.It might also explain why it would be considered blocked in Russia: if
it's not reachable from anywhere, it's not reachable from Russia. An
other possibility, given you use 443 for your ORPort, is that your
bridge was indeed detected by just scanning the whole internet. The
ORPort is very recognizable (enough that some of my former bridges
ended up tagged "tor" on Shodan) so it should be put on a port that's
less likely to be scanned.Regards,
trinity-1686aOn Mon, 20 Feb 2023 at 21:29, Keifer Bly <keifer.bly@gmail.com> wrote:
>
> Where in the torrc file would I set it to any? I am looking for a way to run a bridge without being charged a huge amount of money for it, and I was curious how it would have been detected by Russia if noone had used the bridge there? Thanks.
> --Keifer
>
>
> On Mon, Feb 20, 2023 at 8:45 AM <lists@for-privacy.net> wrote:
>>
>> On Samstag, 18. Februar 2023 18:56:00 CET Keifer Bly wrote:
>> > Ok. Here is the torrc file:
>> >
>> > GNU nano 3.2 /etc/tor/torrc
>> >
>> >
>> > Nickname gbridge
>> > ORPort 443
>> > SocksPort 0
>> > BridgeRelay 1
>> > PublishServerDescriptor bridge
>> > ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
>> > ServerTransportListenAddr obfs4 0.0.0.0:8080
>> > ExtOrPort auto
>> > Log notice file /var/log/tor/notices.log
>> > ExitPolicy reject *:*
>> > AccountingMax 5 GB
>> > ContactInfo keiferdodderblyyatgmaildoddercom
>> >
>> >
>> > Where in this torrc file is that configured?
>> Then set it to 'any' and wait 24-48 hours to see what happens. Maybe there was
>> an error in the db.
>>
>> If your bridge is still not distributed, it could be due to the outdated
>> obfs4proxy or because of 'AccountingMax 5 GB'.
>> Sorry but, 5 GB is a 'fart in the wind' the accounting period would only be a
>> few hours a month. It's not even worth distributing them because it would only
>> frustrate the users.
>>
>> > And how would it be blocked in
>> > Russia already if it hasn't even been used?
>> Why should this new feature of the bridgedb, more precisely the rdsys backend,
>> have anything to do with whether someone uses a bridge? This is a bridgedb
>> distribution method introduced by meskio.
>>
>>
>> --
>> ╰_╯ Ciao Marco!
>>
>> Debian GNU/Linux
>>
>> It's free software and it gives you freedom!_______________________________________________
>> tor-relays mailing list
>> tor-relays@lists.torproject.org
>> tor-relays Info Page
>
> _______________________________________________
> tor-relays mailing list
> tor-relays@lists.torproject.org
> tor-relays Info Page
_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
tor-relays Info Page_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
tor-relays Info Page
_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Ok, changed to port 8080 and upped my allowed traffic a bit:
GNU nano 3.2 /etc/tor/torrc
Nickname gbridge
ORPort 8080
SocksPort 0
BridgeRelay 1
PublishServerDescriptor bridge
BridgeDistribution email
ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
ServerTransportListenAddr obfs4 0.0.0.0:8080
ExtOrPort auto
Log notice file /var/log/tor/notices.log
ExitPolicy reject :
AccountingMax 50 GB
ContactInfo keiferdodderblyyatgmaildoddercom
Yes, I have limited bandwidth I can give so as to avoid being massively charged for traffic. Perhaps there is a way to set tor to only allow traffic with a small connection? Thanks.
–Keifer
Hi Keifer,
You can't use the same port.
Here is a simple example:
BridgeRelay 1
ORPort 56331
ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
ServerTransportListenAddr obfs4 0.0.0.0:53333
ExtORPort auto
ContactInfo keiferdodderblyyatgmaildoddercom
Log notice file /var/log/tor/notices.log
BridgeDistribution email
Nickname gbridge
AccountingStart day 12:00
AccountingMax 50 GB
Example: Let's say you want to allow 50 GB of traffic every day in each
direction and the accounting should reset at noon each day:
For more details about AccountinMax, see this Support doc:
Did you also install obfs4proxy package? Because on Metrics it says
that your bridge don't have any 'transport protocol'.
cheers,
Gus
On Tue, Feb 21, 2023 at 08:23:44AM -0800, Keifer Bly wrote:
Ok, changed to port 8080 and upped my allowed traffic a bit:
GNU nano 3.2
/etc/tor/torrcNickname gbridge
ORPort 8080
SocksPort 0
BridgeRelay 1
PublishServerDescriptor bridge
BridgeDistribution email
ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
ServerTransportListenAddr obfs4 0.0.0.0:8080
ExtOrPort auto
Log notice file /var/log/tor/notices.log
ExitPolicy reject *:*
AccountingMax 50 GB
ContactInfo keiferdodderblyyatgmaildoddercomYes, I have limited bandwidth I can give so as to avoid being
massively charged for traffic. Perhaps there is a way to set tor to only
allow traffic with a small connection? Thanks.--Keifer
On Tue, Feb 21, 2023 at 1:29 AM trinity pointard <trinity.pointard@gmail.com> > wrote:
> > And the reason why it's on port 443 is so as to be on a port that's not
> likely blocked by network administrators.
>
> That might be useful for the ORPort of a relay, and for the obfs4 port
> of a bridge, but not for the ORPort of a bridge. Clients are not
> supposed to connect to it.
> The only reason it's exposed is because the bridge authority still
> requires it to verify the bridge is reachable. See
> Obfsbridges should be able to "disable" their ORPort (#7349) · Issues · The Tor Project / Core / Tor · GitLab.
> You are better of using 443 for the ServerTransportListenAddr, and
> some high port for ORPort.
>
> On Tue, 21 Feb 2023 at 03:05, Keifer Bly <keifer.bly@gmail.com> wrote:
> >
> > Well,
> >
> > So I just changed my torrc to this:
> >
> > Nickname gbridge
> > ORPort 443
> > SocksPort 0
> > BridgeRelay 1
> > PublishServerDescriptor bridge
> > BridgeDistribution email
> > ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
> > ServerTransportListenAddr obfs4 0.0.0.0:8080
> > ExtOrPort auto
> > Log notice file /var/log/tor/notices.log
> > ExitPolicy reject *:*
> > AccountingMax 50 GB
> > ContactInfo keiferdodderblyyatgmaildoddercom
> >
> > Trying to avoid being charged a huge amount for traffic as these VPS
> providers can be ridiculous when it comes to that, which is why it was set
> to so little. Ran killall -HUP tor to reload it and see that happens in the
> next day or so. And the reason why it's on port 443 is so as to be on a
> port that's not likely blocked by network administrators. Thank you.
> > --Keifer
> >
> >
> > On Mon, Feb 20, 2023 at 2:23 PM trinity pointard < > > trinity.pointard@gmail.com> wrote:
> >>
> >> Hi,
> >>
> >> Your torrc is correct wrt to distribution mechanism (your bridge is
> >> indicating "bridge-distribution-request any" in the descriptor it
> >> sends), but for the record, the line would have been
> >> "BridgeDistribution any".
> >> A bridge uses less bandwidth than a relay, but it's still a proxy. At
> >> 5GB per month, you'd be providing a steady 16kbps over the month, or a
> >> single mbps for little over 11 hours. That's very little, if you can't
> >> have more bandwidth (by using a provider with no bandwidth accounting,
> >> or one that gives better pricing per bandwidth), I fear your bridge
> >> won't be very useful at all. Mine consumes between a few hundred GB
> >> and a few TB depending on the distribution mechanism.
> >>
> >> Are you sure your bridge is reachable? Bridgestrap reports suggest it
> isn't.
> >> As the bridge operator, you should know its bridge line. Can you test
> >> it with Tor Browser to make sure?
> >> Given your accounting limits, it could be unreachable because
> >> currently hibernating. Or you could have a firewall issue, or
> >> something else.
> >> I believe not passing bridgestrap can explain not being assigned a
> >> distribution mechanism.
> >>
> >> It might also explain why it would be considered blocked in Russia: if
> >> it's not reachable from anywhere, it's not reachable from Russia. An
> >> other possibility, given you use 443 for your ORPort, is that your
> >> bridge was indeed detected by just scanning the whole internet. The
> >> ORPort is very recognizable (enough that some of my former bridges
> >> ended up tagged "tor" on Shodan) so it should be put on a port that's
> >> less likely to be scanned.
> >>
> >> Regards,
> >> trinity-1686a
> >>
> >> On Mon, 20 Feb 2023 at 21:29, Keifer Bly <keifer.bly@gmail.com> wrote:
> >> >
> >> > Where in the torrc file would I set it to any? I am looking for a way
> to run a bridge without being charged a huge amount of money for it, and I
> was curious how it would have been detected by Russia if noone had used the
> bridge there? Thanks.
> >> > --Keifer
> >> >
> >> >
> >> > On Mon, Feb 20, 2023 at 8:45 AM <lists@for-privacy.net> wrote:
> >> >>
> >> >> On Samstag, 18. Februar 2023 18:56:00 CET Keifer Bly wrote:
> >> >> > Ok. Here is the torrc file:
> >> >> >
> >> >> > GNU nano 3.2 /etc/tor/torrc
> >> >> >
> >> >> >
> >> >> > Nickname gbridge
> >> >> > ORPort 443
> >> >> > SocksPort 0
> >> >> > BridgeRelay 1
> >> >> > PublishServerDescriptor bridge
> >> >> > ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
> >> >> > ServerTransportListenAddr obfs4 0.0.0.0:8080
> >> >> > ExtOrPort auto
> >> >> > Log notice file /var/log/tor/notices.log
> >> >> > ExitPolicy reject *:*
> >> >> > AccountingMax 5 GB
> >> >> > ContactInfo keiferdodderblyyatgmaildoddercom
> >> >> >
> >> >> >
> >> >> > Where in this torrc file is that configured?
> >> >> Then set it to 'any' and wait 24-48 hours to see what happens. Maybe
> there was
> >> >> an error in the db.
> >> >>
> >> >> If your bridge is still not distributed, it could be due to the
> outdated
> >> >> obfs4proxy or because of 'AccountingMax 5 GB'.
> >> >> Sorry but, 5 GB is a 'fart in the wind' the accounting period would
> only be a
> >> >> few hours a month. It's not even worth distributing them because it
> would only
> >> >> frustrate the users.
> >> >>
> >> >> > And how would it be blocked in
> >> >> > Russia already if it hasn't even been used?
> >> >> Why should this new feature of the bridgedb, more precisely the
> rdsys backend,
> >> >> have anything to do with whether someone uses a bridge? This is a
> bridgedb
> >> >> distribution method introduced by meskio.
> >> >>
> >> >>
> >> >> --
> >> >> ╰_╯ Ciao Marco!
> >> >>
> >> >> Debian GNU/Linux
> >> >>
> >> >> It's free software and it gives you
> freedom!_______________________________________________
> >> >> tor-relays mailing list
> >> >> tor-relays@lists.torproject.org
> >> >> tor-relays Info Page
> >> >
> >> > _______________________________________________
> >> > tor-relays mailing list
> >> > tor-relays@lists.torproject.org
> >> > tor-relays Info Page
> >> _______________________________________________
> >> tor-relays mailing list
> >> tor-relays@lists.torproject.org
> >> tor-relays Info Page
> >
> > _______________________________________________
> > tor-relays mailing list
> > tor-relays@lists.torproject.org
> > tor-relays Info Page
> _______________________________________________
> tor-relays mailing list
> tor-relays@lists.torproject.org
> tor-relays Info Page
>
_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
tor-relays Info Page
--
The Tor Project
Community Team Lead
AccountingStart day 12:00
AccountingMax 50 GBExample: Let's say you want to allow 50 GB of traffic every day in each
direction and the accounting should reset at noon each day:
Hi Gus, I think Keifer meant the 5GB limit or now 50GB per month. 
I would recommend checking here more often:
Server Host: 2048MB RAM, 1000Mbps Unmetered Port
(^^ make sure to use the coupon code!)
There are always offers for Easter, Christmas or Black Friday. (VPS unlimited
for 10-30 dollars/year)
Or:
Yes, Frantech should actually be avoided. But in Miami there are few Tor
relays. A SLICE 512 for $2.00/m or $20.00/y is sufficient for a bridge.
https://buyvm.net/kvm-dedicated-server-slices/
For more details about AccountinMax, see this Support doc:
How can I limit the total amount of bandwidth used by my Tor relay? | Tor Project | Support
Did you also install obfs4proxy package? Because on Metrics it says
that your bridge don't have any 'transport protocol'.
@Keifer read my message how you check that:
https://lists.torproject.org/pipermail/tor-relays/2023-January/020979.html
On Donnerstag, 23. Februar 2023 13:43:29 CET gus wrote:
--
╰_╯ Ciao Marco!
Debian GNU/Linux
It's free software and it gives you freedom!
Hi,
So yes I had obfs4 installed. I accidentally set it to the same port as tor without relazing, silly me. Here is my new torrc:
Nickname gbridge
ORPort 8080
SocksPort 0
BridgeRelay 1
PublishServerDescriptor bridge
BridgeDistribution email
ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
ServerTransportListenAddr obfs4 0.0.0.0:8081
ExtOrPort auto
Log notice file /var/log/tor/notices.log
ExitPolicy reject :
AccountingMax 50 GB
ContactInfo keiferdodderblyyatgmaildoddercom
I am wanting to limit to 50GB per month to avoid being overcharged. Would this do that? Thanks.
–Keifer
Yes, the limit is 50GB per month, but for some reason the distribution mechanism is not updating and the bridge keeps going offline despite the new torrc.
–Keifer
What comes to my mind without logs (& your 'killall -HUP' of a systemd service
is not optimal), your wrong config (2x same Port) has maxed out 'Restart=on-
failure'.
Try:
~# systemctl stop tor
~# systemctl list-units --failed
if not zero than:
~# systemctl reset-failed
~# systemctl start tor
To see if the tor.service has finished successfully:
~# systemctl status tor
if not, read log:
journalctl -xe
On Freitag, 24. Februar 2023 04:11:27 CET Keifer Bly wrote:
Yes, the limit is 50GB per month, but for some reason the distribution
mechanism is not updating and the bridge keeps going offline despite the
new torrc.
--
╰_╯ Ciao Marco!
Debian GNU/Linux
It's free software and it gives you freedom!
Hi,
So I had changed the listener port for obfs4, it’s now 8181.
Upon running your steps, and systemctl status tor, it returns the following:
● tor.service - Anonymizing overlay network for TCP (multi-instance-master)
Loaded: loaded (/lib/systemd/system/tor.service; enabled; vendor preset: enabled)
Active: active (exited) since Tue 2023-02-28 05:42:48 UTC; 18s ago
Process: 15314 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
Main PID: 15314 (code=exited, status=0/SUCCESS)
Feb 28 05:42:48 instance-1 systemd[1]: Starting Anonymizing overlay network for TCP (multi-instance-master)…
Feb 28 05:42:48 instance-1 systemd[1]: Started Anonymizing overlay network for TCP (multi-instance-master).
Will check it in a few hours, but is there a way to limit the bridge to only connections of a certain size? Thanks.
–Keifer
Yep, and after that the same still happens, it is still going offline despite the also different ports and having followed the listed steps.
–Keifer
In the syslog is why tor aborts.
To help you, you should post your logs to a pastbin page. From the start of
the tor daemon until it goes offline.
On Dienstag, 28. Februar 2023 19:02:38 CET Keifer Bly wrote:
Yep, and after that the same still happens, it is still going offline
--
╰_╯ Ciao Marco!
Debian GNU/Linux
It's free software and it gives you freedom!
Wheres the pastebin page? Thanks.
–Keifer
$websearch pastebin
https://pastebin.mozilla.org/
...
On Samstag, 4. März 2023 02:09:19 CET Keifer Bly wrote:
Wheres the pastebin page? Thanks.
--
╰_╯ Ciao Marco!
Debian GNU/Linux
It's free software and it gives you freedom!
Well so here is the current torrc file:
Nickname gbridge
ORPort 8080
SocksPort 0
BridgeRelay 1
PublishServerDescriptor bridge
BridgeDistribution email
ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
ServerTransportListenAddr obfs4 0.0.0.0:8081
ExtOrPort auto
Log notice file /var/log/tor/notices.log
ExitPolicy reject :
AccountingMax 50 GB
ContactInfo keiferdodderblyyatgmaildoddercom
Strangely, nothing whatsoever is being written to the notices.log file, upon checking it it is completely empty, nothing there. I wonder why that would happen and how else to tell what’s going on? Tor is running as root so it’s not a permission issue, and I also set up a port forwarding rule for the obfs4 port. Thanks.
–Keifer