Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T torflow
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Network Health
  • torflow
  • Issues
  • #2043
Closed
Open
Created Oct 10, 2010 by Roger Dingledine@armaOwner

soat with --target never ends?

I've been running

bwauth     679 10.8  2.6 302752 157672 pts/43  Sl   Sep30 1443:58 /usr/bin/python ./soat.py --http --target http://www.torproject.org/index.html

for the past week and a half.

I just checked its logs, and it's got things like

WARN[Sun Oct 10 04:25:39 2010]:A SOCKS5 error 2 occured for http://www.torproject.org/index.html: (2, 'connection not allowed by ruleset')
INFO[Sun Oct 10 04:25:39 2010]:Completed HTTP Reqest for: http://www.torproject.org/index.html
DEBUG[Sun Oct 10 04:25:39 2010]:Removed 127.0.0.1:36402 from our local port list
DEBUG[Sun Oct 10 04:25:39 2010]:0.000572919845581 STREAM 119366 FAILED 0 38.229.70.16 80 REASON=EXITPOLICY
DEBUG[Sun Oct 10 04:25:39 2010]:No last exit.
NOTICE[Sun Oct 10 04:25:39 2010]:Stream 119366 FAILED with EXITPOLICY
NOTICE[Sun Oct 10 04:25:39 2010]:We had no exit node to test, skipping to the next test.
DEBUG[Sun Oct 10 04:25:39 2010]:0.000684976577759 STREAM 119366 CLOSED 0 38.229.70.16 80 REASON=EXITPOLICY
NOTICE[Sun Oct 10 04:25:39 2010]:Stream 119366 CLOSED with EXITPOLICY

Sure enough, the Tor log agrees:

Oct 10 04:26:29.306 [info] connection_ap_handshake_send_begin(): Sending relay cell 0 to begin stream 48972.
Oct 10 04:26:29.306 [info] connection_ap_handshake_send_begin(): Address/port sent, ap socket 11, n_circ_id 38707
Oct 10 04:26:30.349 [info] connection_ap_process_end_not_open(): Address 'www.torproject.org' refused due to 'exit policy failed'. Considering retrying.
Oct 10 04:26:30.349 [info] addressmap_register(): Addressmap: (re)mapped 'www.torproject.org' to '38.229.70.16'
Oct 10 04:26:30.349 [info] addressmap_rewrite(): Addressmap: rewriting "www.torproject.org" to "38.229.70.16"

Does soat not know to exit when it's done with its scans?

Assignee
Assign to
Time tracking