Re: [tor-relays] Possible to run a tor bridge/relay via tor browser?

2020-03-27 Thread Keifer Bly
Well, I just tried, and no luck, see the attached video. I edited the torrc file included with the torrc file to run the bridge, and after doing this, it causes tor to immediately crash on startup before even making any logs. This is what is entered in the torrc file, the same as what is

Re: [tor-relays] New relay

2020-03-27 Thread William Pate
I'll increase it. I have two running from home, so I don't want to eat up too much bandwidth, but I left the config at the default rate until certain it was working. :) William Pate willp...@pm.me 512-947-3311 inadequate.net ‐‐‐ Original Message ‐‐‐ On Friday, March 27, 2020 5:09 AM,

Re: [tor-relays] BadExit

2020-03-27 Thread niftybunny
This. Port 22 especially is a nightmare. niftybunny > On 27. Mar 2020, at 16:29, Toralf Förster wrote: > > Signed PGP part > On 3/27/20 2:17 PM, ger...@bulger.co.uk wrote: >> I have been free of abuse complaints and copyright claims for two years now. > Well, the main problem here fore me is

Re: [tor-relays] BadExit

2020-03-27 Thread Toralf Förster
On 3/27/20 2:17 PM, ger...@bulger.co.uk wrote: > I have been free of abuse complaints and copyright claims for two years now. Well, the main problem here fore me is to get complaints from my hoster itself b/c any open address range are abused soon for port scans -- Toralf signature.asc

Re: [tor-relays] BadExit

2020-03-27 Thread gerard
Thanks. Funny that my long time restricted IPv4 port 80 exit was noticed just now giving the bad exit tag. I suspect the hour one of my server was quarantined by my ISP may have precipitated the system to look hard. As for my single /8 for port 80, for reason not clear to me, having many

Re: [tor-relays] BadExit

2020-03-27 Thread Georg Koppen
teor: > Hi, > >> On 27 Mar 2020, at 02:00, niftybunny >> wrote: >> >> My bad. Never seen this before. I there a good reason for the accept >> 133.0.0.0/8:80 ? >> >>> On 26. Mar 2020, at 15:06, ger...@bulger.co.uk wrote: >>> >>> "btw, you need to have at least port 80 and 443 … port 80 is

Re: [tor-relays] BadExit

2020-03-27 Thread teor
> On 27 Mar 2020, at 20:42, teor wrote: > >>> On 26. Mar 2020, at 15:06, ger...@bulger.co.uk wrote: >>> >>> "btw, you need to have at least port 80 and 443 … port 80 is missing …" >>> >>> It there. But to a /8 area IPV4, all IPv6 >>> > The Exit flag only request one IPv4 /8 : >

Re: [tor-relays] BadExit

2020-03-27 Thread teor
Hi, > On 27 Mar 2020, at 02:00, niftybunny > wrote: > > My bad. Never seen this before. I there a good reason for the accept > 133.0.0.0/8:80 ? > >> On 26. Mar 2020, at 15:06, ger...@bulger.co.uk wrote: >> >> "btw, you need to have at least port 80 and 443 … port 80 is missing …" >> >> It

Re: [tor-relays] New relay

2020-03-27 Thread teor
Thanks! Looks like a small bandwidth rate, did you really mean 300 kilobytes per second? T -- teor -- > On 26 Mar 2020, at 04:59, William Pate wrote: > >  > Set up another relay (this time on Raspberry Pi 4): >

Re: [tor-relays] Possible to run a tor bridge/relay via tor browser?

2020-03-27 Thread teor
Hi, > On 25 Mar 2020, at 06:35, Keifer Bly wrote: > > So I am currently running an OBFS4 bridge here: > > https://metrics.torproject.org/rs.html#details/386E99371B8CD938248940B754F16AAC54B5712B > > It is being done via the TOR expert bundle on Windows 10. I am wondering, > would it be