Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • 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.

  • Legacy
  • TracTrac
  • Issues
  • #2964

Closed (moved)
Open
Opened Apr 20, 2011 by cypherpunks@cypherpunks

Tor network scanning?

Running TBB relay, Tor 0.2.1.30 on Windows 7. I have changed my old router to a more modern firewall with NAT, SPI, DoS-prevention, UPnP and QOS. Has automatically configured port forward successfully. I do not mirror relay directory. Tor message log showing “warning eventdns: all nameservers have failed” and “notice eventdns: nameserver …. is backup” during start. Firewall log below. Tor is working, but has Tor gone crazy port scanning (ACK,SYN,FIN,UDP) the network?

Apr 20 19:28:33 DOS [TCP]: Attack Outgoing 192.168.0.100->0.0.0.0 [ACK Scan] Apr 20 19:21:02 DOS [TCP]: Attack Outgoing 192.168.0.100->0.0.0.0 [FIN Scan] Apr 20 19:20:30 DOS [TCP]: Attack Outgoing 192.168.0.100->0.0.0.0 [FIN Scan] Apr 20 19:15:21 DOS [TCP]: Attack Outgoing 192.168.0.100->0.0.0.0 [FIN Scan] Apr 20 19:10:31 DOS [TCP]: Attack Outgoing 192.168.0.100->0.0.0.0 [FIN Scan] Apr 20 19:04:29 DOS [TCP]: Attack Outgoing 192.168.0.100->0.0.0.0 [ACK Scan] Apr 20 19:04:20 DOS [TCP]: Attack Outgoing 192.168.0.100->0.0.0.0 [ACK Scan] Apr 20 19:04:17 DOS [TCP]: Attack Outgoing 192.168.0.100->0.0.0.0 [ACK Scan] Apr 20 18:59:20 DOS [TCP]: Attack Outgoing 192.168.0.100->0.0.0.0 [FIN Scan] Apr 20 18:53:08 DOS [TCP]: Attack Outgoing 192.168.0.100->0.0.0.0 [ACK Scan] ….. Apr 19 19:38:56 DOS [TCP]: Attack Outgoing 192.168.0.100->0.0.0.0 [SYN Scan] Apr 19 19:38:51 DOS [TCP]: Attack Outgoing 192.168.0.100->0.0.0.0 [FIN Scan] Apr 19 19:37:52 DOS [TCP]: Attack Outgoing 192.168.0.100->0.0.0.0 [ACK Scan] Apr 19 19:25:08 DOS [TCP]: Attack Outgoing 192.168.0.100->0.0.0.0 [ACK Scan] Apr 19 19:25:00 DOS [TCP]: Attack Outgoing 192.168.0.100->0.0.0.0 [ACK Scan] Apr 19 19:24:11 DOS [TCP]: Attack Outgoing 192.168.0.100->0.0.0.0 [FIN Scan] Apr 19 19:17:33 DOS [TCP]: Attack Outgoing 192.168.0.100->0.0.0.0 [ACK Scan] Apr 19 19:14:04 DOS [TCP]: Attack Outgoing 192.168.0.100->0.0.0.0 [ACK Scan] Apr 19 19:12:29 DOS [TCP]: Attack Outgoing 192.168.0.100->0.0.0.0 [ACK Scan] Apr 19 19:07:51 DOS [TCP]: Attack Outgoing 192.168.0.100->0.0.0.0 [ACK Scan]

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