Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #2787

Closed (moved)
(moved)
Open
Created Mar 22, 2011 by Damian Johnson@atagar

DNS Connection for Non-exits

Hi. When the ORPort is set Tor makes connections to the system's resolvers: atagar@fenrir:~$ netstat -np | grep "ESTABLISHED 3776/tor" ... tcp 0 0 10.243.55.20:49947 206.217.215.183:53 ESTABLISHED 3776/tor
udp 0 0 10.243.55.20:60630 10.128.128.128:53 ESTABLISHED 3776/tor

My understanding is that this is to provide dns resolution for exit traffic we're handling. However, these connections are made for both exiting and non-exiting relays alike. Functionally this isn't an issue, but is probably a little confusing for operators.

Am I misunderstanding the purpose for these connections? Do they serve a purpose for non-exits? I thought it was appropriate to label them as belonging to exit traffic in arm but I'll need to rethink this, lest we get some very confused non-exit operators. ;)

Cheers! -Damian

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking