Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, toxicity and dog-whistling are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either !asklemmyafterdark@lemmy.world or !asklemmynsfw@lemmynsfw.com.
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email info@lemmy.world. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try !politicaldiscussion@lemmy.world or !uspolitics@lemmy.world
7) No Hit-and-Run questions.
Please don't delete your post for no apparent reason. If you plan on deleting a question later, say so in the post, or if you feel that you have a good reason to remove it, message a mod beforehand. It's not fair to the ones who took their time to answer, and it's not in the spirit of the community.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
lots of factors but it could be on your system and not an ISP, if changing the port is the fix it seems like it could be a bunch of things that could be local problems. What OS are you running it on. Did you do any system changes or OS updates? Sometimes a port errors out for some reason and changing it and then changing it back solves the issue. Just because its Tor, is why it might be a bigger concern to you, but it might just be more nuanced and not specificly because of Tor.
I had no idea port configuration is prone to such... Software hiccups? ๐คฃ I am running the bridge on a Raspberry Pi 5 with DietPie and my router is a Raspberry Pi 4B running Openwrt. When the bridge speeds and number of connected users dropped, I did do a full system upgrade, which included some packages, the kernel and an EEPROM update. Since the upgrade didn't improve the stats of the Tor bridge for some days, I assumed that my ISP was choking my connection - which, now that I think of it, shouldn't have had to do with it being a Tor connection, because the whole point of a Tor bridge is that it's obfuscated in order to allow people to use the Tor network in restrictive jurisdictions... ๐ค Anyhow, having assumed that my ISP had pinpointed my Tor ports, I changed them, and now I can see, at least on a hardware level, judging from the LEDs on the switch port that carries the Tor connection, that the speeds/usage are picking up again. Another thing that makes me think that it had to do with the port, regardless of whether it was my ISP doing something or one of those port errors you mentioned, is that meanwhile, my other router, which is sharing the same upstream bandwidth, was still operating at several hundreds of Mbps, while the Tor bridge was "coughing up" a few bytes here and there.