Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
T
Tor
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,066
    • Issues 1,066
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 17
    • Merge Requests 17
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • The Tor Project
  • Core
  • Tor
  • Issues
  • #24814

Closed
Open
Opened Jan 06, 2018 by Trac@tracbot

Tor relay killing UPC Connect Box

I'm running a Tor relay since some years on my Raspberry 3 (earlier on the raspi 2), but recently my internet connection started to have packet loss. After checking with my ISP, who didn't find anything wrong, I discovered that it's probably because of too many open connections. Running 'arm' on my relay, I see that I have: Connections (2561 inbound, 2115 outbound, 5 circuit) or: netstat -an | wc -l 4897 Besides that my raspi is a tad slow, my internet connection is quite slow because of the 20% packet loss. I've started now to work with the MaxAdvertisedBandwidth option (now set to 550 KB, but would like to offer 10 Mbit/s) and reduced that by nearly 50%, but so far without any positive result (might take a while to propagate?). Anyway, my ISP UPC.ch only allows their own Connect Box (CB) to be connected. I'm running it in modem mode, so my router is actually doing the whole NAT, but that one has enough performance (tested it by directly connecting a client to the CB and still had packet loss. I'm sure this is bad for the whole TOR network :( I assume it might be because of the new blockades in the Arabic areas, as I have the problem since around 3 weeks in varying amounts.

Trac:
Username: pato

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: 0.3.1.x-final
Milestone
Tor: 0.3.1.x-final
Assign milestone
Time tracking
None
Due date
None
Reference: tpo/core/tor#24814