I don’t mean to pick nits, but Raspbian/RaspiOS is not Debian-- just the same that Ubuntu is not Debian. The builds/repos are different and Raspbian has even gotten architecture naming screwed up (see: armhf on Raspbian is not the same thing as armhf on Debian) … this has led to people trying to use Debian packages from Raspbian and finding out they don’t work.
I’m not sure about Raspi’s packaging of tor, but I know that Ubuntu’s repo has not been good about keeping up. In the case of Ubuntu it’s certainly better to use Tor Project’s repo until Ubuntu establishes a better track record of updating tor.
If the only intent for the rpi4 target is to run a bridge, Debian with Tor Project’s repo seems like the best bet. Unless there’s something drastically wrong with Debian on Raspberry Pis that I’m not aware of.
Thank you, but it was much more dumb, I was supposed to replace <DISTRIBUTION> to bullseye, not <bullseye> …
Alright, now I got version 0.4.6.8.
But even before adding the repository manually, I could have installed
tor | 0.4.5.10-1~deb11u1
unlike before when I used the raspios buster armhf release.
Just a little bit nit picky, but I feelz ya!
I didn’t really want to get into the distro thing just trying to help out someone do what I just did, but I was running 10 and not 11 as I already had the unit doing other stuff on my LAN.
Nice one, I’ve been looking around the site and based on some of the posts I’ve seen I think I may consider getting BSD running on another Pi4 and patch that to my 2nd WAN link for another bridge. A project for the Christmas break, possibly.
I there any common thing I need to set in my router when setting up a relay ?
Ipv6 is deactivated by default in my router, but I dont know what else to consider doing that so I wanted to ignore it first. I dont like activating things I dont actually comprehend.
If your relay is running on a internal net, you need to setup port forwarding. Check this https://portforward.com/ for directions on how to port forward with your NAT/router device.
If your relay is running on a internal net, you need to setup port forwarding. Check this https://portforward.com/ for directions on how to port forward with your NAT/router device.
Thanks I found that in my router but wasnt sure If I actually need to do something there.
Doesnt every common home network user have only a dynamic public ip address ?
I checked my isp, its a thing only available for office contracts.
I havent seen it changes for a couple days now, I dont know the lifecycle but its not like every hour.
Why cant tor check if there is a new public ip and if yes restart all steps and re-release the server automatically on the same identity ?
When bridges are blacklisted for whatever reason, dont they need to restart with a new address anyways ?
Tor will do that, but users will need to ‘discover’ your bridge’s IP address again, i.e., go over the process of requesting a new bridge (by email, Moat or https). On the other hand, Snowflake will discover your proxy new IP and automatically share with them.
Yes, but the time frame of rotating static IP addresses would be days/weeks/months and not hours.
Yes pretty much all ISP will provide a dynamic IP unless a static one is requested.
I have 2 domestic connections but requested static IP’s from ISP.
They just charge a few extra $$ for this.
Unfortunately its not simply a little upgrade to buy on top for me. A rented server would be less expensive for me. (If i find something cheap I will do that)
Ill monitor how often my address changes for now.
Cant users refer to a constant identity instead ?
Anyways, Ill gladly run a snowflake then.
What about sparing it as a middle relay ? Is a static ip just as critical here ?
I have a bridge installed on a Raspberry Pi 3B + with the latest version of Raspberry Pi OS Lite (32 bits), based on Debian 11 Bullseye, and it works very well. Tor versión is 0.4.5.10. My IP is dynamic, but it doesn’t change frequently; it can go several days without changing (even up to two weeks).
If you need it, I can show you step by step the procedure that I have used to configure my bridge. It’s simple.
So ive been logging my public ip for several day now and its always the same, the internet provider forces a reconnect every night at the same time, its called a forced disconnect for technical reasons each 24 hours.
Its in their faq stated that you cannot avoid this: statement in german
You can change the time for the reconnect but not that it will happen once a day. From what I learned its a common thing in germany.
And this would always assign a new ip.
Alright this leaves me with the snowflake and the rented server option.
edit: although the docs say: Your IPv4 address should remain unchanged for at least 3 hours, so 24 isnt that bad right
The bridge is reachable and obfs4: functional. Should I schedule a restart task for tor right after the forced ip reset or is it best to just keep it running ?
Is it harmful to run a snowflake additionally on the same device ?
