Bug 287412 - security/tor Bug: Edge connection not in circuit's list.
Summary: security/tor Bug: Edge connection not in circuit's list.
Status: Closed DUPLICATE of bug 287411
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: Yuri Victorovich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-06-10 03:33 UTC by John Studnicka
Modified: 2025-06-10 03:36 UTC (History)
0 users

See Also:
bugzilla: maintainer-feedback? (yuri)


Attachments
Filtered log output /var/log/messages (8.60 KB, text/plain)
2025-06-10 03:33 UTC, John Studnicka
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description John Studnicka 2025-06-10 03:33:14 UTC
Created attachment 261130 [details]
Filtered log output /var/log/messages

Hello,

I run a Tor client on a FreeBSD 14.2 server with a somewhat unreliable ue0 network interface using if_urndis tethering. It looks like a little while after Android dropped the connection and the ue0 interface was destroyed, this bug was triggered in the Tor node:

Jun  9 19:07:30 HP-DL361 Tor[44453]: circuit_detach_stream: Bug: Edge connection not in circuit's list. (on Tor 0.4.8.16 )
Jun  9 19:07:30 HP-DL361 Tor[44453]: tor_bug_occurred_: Bug: src/core/or/circuituse.c:1439: circuit_detach_stream: This line should not have been reached. (Future instances of this warning will be silenced.) (on Tor 0.4.8.16 )

This is my system configuration:

~ » uname -a && freebsd-version
FreeBSD HP-DL361 14.2-RELEASE-p1 FreeBSD 14.2-RELEASE-p1 GENERIC amd64
14.2-RELEASE-p3

~ » pkg info tor-0.4.8.16
tor-0.4.8.16
Name           : tor
Version        : 0.4.8.16
Installed on   : Sun May  4 04:59:57 2025 MST
Origin         : security/tor
Architecture   : FreeBSD:14:amd64
Prefix         : /usr/local
Categories     : security net
Licenses       : GPLv3
Maintainer     : yuri@FreeBSD.org
WWW            : https://www.torproject.org/
Comment        : Anonymizing overlay network for TCP

I've attached some relevant log output for the node startup config and what was going on with the network interface. Let me know if any more info is needed.

Thanks
Comment 1 John Studnicka 2025-06-10 03:36:23 UTC

*** This bug has been marked as a duplicate of bug 287411 ***