[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #33491 [Core Tor/Tor]: tor_bug_occurred_: Bug: src/core/or/dos.c:697: dos_new_client_conn: Non-fatal assertion !(entry == NULL) failed. (Future instances of this warning will be silenced.) (on Tor 0.4.2.6 )

#33491: tor_bug_occurred_: Bug: src/core/or/dos.c:697: dos_new_client_conn: Non-
fatal assertion !(entry == NULL) failed. (Future instances of this warning
will be silenced.) (on Tor 0.4.2.6 )
-----------------------------------------------+---------------------------
 Reporter:  sjcjonker                          |          Owner:  dgoulet
     Type:  defect                             |         Status:
                                               |  needs_information
 Priority:  Medium                             |      Milestone:  Tor:
                                               |  0.4.4.x-final
Component:  Core Tor/Tor                       |        Version:  0.4.2.6
 Severity:  Normal                             |     Resolution:
 Keywords:  FreeBSD 043-backport 042-backport  |  Actual Points:
Parent ID:                                     |         Points:
 Reviewer:                                     |        Sponsor:
-----------------------------------------------+---------------------------

Comment (by sjcjonker):

 Here are the versions:

 {{{
 [root@torrie ~]# uname -a
 FreeBSD torrie.dev.sjc.nl 12.1-RELEASE-p2 FreeBSD 12.1-RELEASE-p2 GENERIC
 amd64
 [root@torrie ~]# tor --version
 Tor version 0.4.2.6.
 [root@torrie ~]# obfs4proxy --version
 obfs4proxy-0.0.11
 }}}

 tor and obfs4proxy are from the packages, as indicated here:
 https://community.torproject.org/relay/setup/guard/freebsd/
 https://community.torproject.org/relay/setup/bridge/freebsd/

 Could it be because the obfs4 is listening on IPv6, besides my normal
 bridge which has both IPv4 and IPv6 connectivity as per here:
 https://metrics.torproject.org/rs.html#search/C51818DB4F3C03EFCA00C127EAA2780DFAFC8862

 I have an complete other IPv6 prefix at my disposal so I added a IPv6
 obfsproxy the whole config is:
 {{{
 SOCKSPort 127.0.0.1:9050
 SOCKSPolicy accept 127.0.0.1/32
 SOCKSPolicy reject *
 Log notice syslog
 RunAsDaemon 1
 DataDirectory /var/db/tor
 ControlPort 9051
 CookieAuthentication 1
 CookieAuthFileGroupReadable 0
 DataDirectoryGroupReadable 0
 DisableDebuggerAttachment 0
 BandwidthRate 50 MBits
 BandwidthBurst 60 MBits
 ORPort 80.127.139.6:443 NoListen
 ORPort 192.168.<<xxx.yyy>>:443 NoAdvertise
 ORPort [2001:985:e77:5::9]:443
 Nickname SJC01
 RelayBandwidthRate 50 MBits
 RelayBandwidthBurst 60 MBits
 ContactInfo SJC Tor Admin <tor AT sjc dot nl>
 DirPort 80
 DirPortFrontPage /usr/local/etc/tor/tor-info-notice.html
 ExitRelay 0
 ClientUseIPv6 1
 ClientPreferIPv6ORPort 1
 IPv6Exit 1
 ExitPolicy reject6 *:*
 ExitPolicy reject *:*
 ServerTransportPlugin obfs4 exec /usr/local/bin/obfs4proxy --enableLogging
 --logLevel=INFO
 ServerTransportListenAddr obfs4 [2001<<REMOVED>>]:<<REMOVED>>
 ExtORPort auto
 }}}

 When I manually set this obfs4proxy as my only proxy in torbrowser it
 works despite the error.

 Please let me know if more info is required.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33491#comment:8>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs