[tor-relays] tor-relays Digest, Vol 150, Issue 13

Mon Jul 31 22:43:09 UTC 2023

Hi. Everybody. In Turkmenistan these IPs are open:
96.233.128.72
167.62.193.195
108.50.165.220
71.33.251.73
99.232.152.8
108.184.202.115
108.34.184.5
99.230.178.2
108.184.201.30
71.212.129.108
88.22.43.218
67.6.147.5
79.16.171.221
79.113.212.117
88.91.78.20
172.88.64.65
67.251.118.15
41.109.196.229
96.237.186.35
95.31.20.151
71.113.184.94
151.225.43.243
141.255.66.158
88.19.75.220
67.11.187.237
67.6.182.48
95.252.250.216
67.6.161.111
95.236.84.157
143.107.229.252
92.194.57.57
I think for now port 8080 is open too. Can anybody make obfs4 server with
these ips and port 8080?

On Mon, Jul 31, 2023 at 5:01 PM <tor-relays-request at lists.torproject.org>
wrote:

> Send tor-relays mailing list submissions to
>         tor-relays at lists.torproject.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> or, via email, send a message with subject or body 'help' to
>         tor-relays-request at lists.torproject.org
>
> You can reach the person managing the list at
>         tor-relays-owner at lists.torproject.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of tor-relays digest..."
>
>
> Today's Topics:
>
>    1. Re: Help Turkmens to bypass Internet censorship: run an obfs4
>       bridge! (lists at for-privacy.net)
>    2. Re: Help Turkmens to bypass Internet censorship: run an obfs4
>       bridge! (Gary C. New)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 30 Jul 2023 23:30:26 +0200
> From: lists at for-privacy.net
> To: tor-relays at lists.torproject.org
> Subject: Re: [tor-relays] Help Turkmens to bypass Internet censorship:
>         run an obfs4 bridge!
> Message-ID: <2156503.WeTp2EQoyn at t520>
> Content-Type: text/plain; charset="us-ascii"
>
> On Freitag, 21. Juli 2023 18:07:35 CEST gus wrote:
>
> > New update: In the last few weeks, internal political conflicts and
> > other events[1] in Turkmenistan have led to another wave of censorship
> > on Tor and anti-censorship tools. Tor bridges have been one of the few
> > free alternatives for people in Turkmenistan to connect with the world
> > and access the open Internet.
> >
>
> I stopped snowflake and now a bridge is running on my dynIP.
>
> >
> > ## torrc example
> >
> > BridgeRelay 1
> > ORPort 127.0.0.1:auto
> > AssumeReachable 1
> > ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
> > ServerTransportListenAddr obfs4 0.0.0.0:8080
> > ExtORPort auto
> > Nickname helptm
> > ContactInfo <please-add-your-email-here>
> > Log notice file /var/log/tor/notices.log
> > # If you set BridgeDistribution none, please remember to email
> > # your bridge line to us: frontdesk at torproject.org
> > BridgeDistribution none
>
> But I have that in the log :-(
> Jul 30 16:48:29 t520 Tor-01[93466]: The IPv4 ORPort address 127.0.0.1 does
> not match the descriptor address  203.0.113.18. If you have a static public
> IPv4 address, use 'Address <IPv4>' and 'OutboundBindAddress <IPv4>'. If you
> are behind a NAT, use two ORPort lines: 'ORPort <PublicPort> NoListen' and
> 'ORPort <InternalPort> NoAdvertise'.
> Jul 30 16:48:29 t520 Tor-01[93466]: The IPv6 ORPort address ::1 does not
> match the descriptor address 2001:db8:1234:1:bbbb:eeee:eeee:ffff. If you
> have a static public IPv4 address, use 'Address <IPv6>' and
> 'OutboundBindAddress <IPv6>'. If you are behind a NAT, use two ORPort
> lines: 'ORPort <PublicPort> NoListen' and 'ORPort <InternalPort>
> NoAdvertise'.
>
> I don't know if I should ignore that or better configure it that way:
> ORPort 127.0.0.1:8443 NoListen
> ORPort 8443 NoAdvertise
> ORPort [::1]:8443 NoListen
> ORPort 8443 NoAdvertise
>
> I'm aware of
> https://gitlab.torproject.org/tpo/core/tor/-/issues/40208
> I hope to get it done with scipting on my Mikrotik, or switch to ipv4 only.
>
> frontdesk at torproject.org has no PGP key, can I send you or meskio the
> bridgeline?
>
> Bridgeline must be:
> Bridge obfs4 <IP ADDRESS>:<PORT> <FINGERPRINT> cert=abra+kadabra iat-mode=0
> But DynIP changes every few days. Do you also give the bridge users
> myrouter.example.net?
>
> Because of your post in the forum:
> https://forum.torproject.org/t/orport-127-0-0-1-auto/8470
> should we do this with all running bridges, or only the hidden ones?
>
> --
> Ciao Marco!
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 3872 bytes
> Desc: This is a digitally signed message part.
> URL: <
> http://lists.torproject.org/pipermail/tor-relays/attachments/20230730/1bd6e180/attachment-0001.sig
> >
>
> ------------------------------
>
> Message: 2
> Date: Sun, 30 Jul 2023 22:55:15 +0000 (UTC)
> From: "Gary C. New" <garycnew at yahoo.com>
> To: <tor-relays at lists.torproject.org>
> Subject: Re: [tor-relays] Help Turkmens to bypass Internet censorship:
>         run an obfs4 bridge!
> Message-ID: <732690672.7302134.1690757715803 at mail.yahoo.com>
> Content-Type: text/plain; charset="utf-8"
>
> On Sunday, July 30, 2023, 3:30:55 PM MDT, lists at for-privacy.net <
> lists at for-privacy.net> wrote:
>
>
> >?I don't know if I should ignore that or better configure it that >way:
> >?ORPort 127.0.0.1:8443 NoListen
> >?ORPort 8443 NoAdvertise
> >?ORPort [::1]:8443 NoListen
> >?ORPort 8443 NoAdvertise
>
> Other way around:
> ORPort 8443?NoListen
> ORPort 127.0.0.1:8443?NoAdvertise
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.torproject.org/pipermail/tor-relays/attachments/20230730/ca49d9b3/attachment-0001.htm
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> tor-relays mailing list
> tor-relays at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
>
> ------------------------------
>
> End of tor-relays Digest, Vol 150, Issue 13
> *******************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20230801/ac93e452/attachment-0001.htm>