Opened 10 years ago

Last modified 7 years ago

#1043 closed defect (None)

"LongLivesPorts" don't work, bandwitch trafic , eventDNS, overloads

Reported by: stars Owned by:
Priority: High Milestone:
Component: Core Tor/Tor Version: 0.2.1.19
Severity: Keywords:
Cc: stars, Sebastian, nickm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Hello,

I have found a few bugs on Master 2.2 alpha dev with "circvum windows" patch on ubuntu
jaunty x86 64, libevent 1.3e

"LongLivesPorts" don't work, all programs like irc, chat ect... close the connections in a
couple secounds or minutes.

i have added manualy the command in torrc but make no difference.

Tor become many more trafic "recieve" as "send" ex: 200KB in and only 130 KB out . i run with "DirPort" so
it don't seem normal.

many warn "eventDNS" , in 2 days 3 times tor was overloaded and crashed vidalia. ( i run 4 cpus ) and tor
prcocess was only 2 %

With the patch "circvum windows", when i connect me to a site who open some page or connections on same
circuit, the page don't load or are extrem slow.

ex: when will try a speed test or decloak, when are on the last speed test or when decloak will give the
final result, the page don't load and some connections stay connected on the circuit. so need many time
close it manually

about logs, are nothing who can help except the many "eventDnS" error

[Automatically added by flyspray2trac: Operating System: Other Linux]

Child Tickets

Change History (12)

comment:1 Changed 10 years ago by nickm

What is the "circvum windows" patch?

Do other versions of Tor work for you?

comment:2 Changed 10 years ago by Sebastian

the circvum windows patch is branch circwindow in
git://git.torproject.org/~arma/git/tor

0.2.1.19 works for him

comment:3 Changed 10 years ago by stars

hello,

Well actualy only 2.17 rc are done for jaunty 64 and it run well.

All master branch with or without patch , make the problem describe up.

So only the multi-connections problem can be from patch but about eventDNS, overloads, become many more data as send and the connections closing to early are on all master tested on my OS.

comment:4 Changed 10 years ago by stars

hello,

I have build on another pc in a same os and now the "liveslongPort" work. i have uninstall and clean all version and folders of tor in the pc who was the "circvum windows patch" and work too.

So was a trace who have make problem with the master only ..

For the others errors, i will wait the next days and told if the others stay or not.

my best

SwissTorExit / john

comment:5 Changed 10 years ago by stars

well happy to early, with master brach only, the problem come back after a couple hours...

I don't become so much "eventDNS" errors, that's all

comment:6 Changed 10 years ago by stars

i have updated today my build with last "master" a couple hours before and now all the bugs "LiveLongPorts" , "bandwitch", "multiconnections", "eventDNS", are fixed.

I run more 4 hours yet and my irc with 7 servers open have not 1 time close the connection or failed to build it.

I will run to tomorow andif all are fine , i will try again the patch "circvum windows" to see if it bug or not.

my best SwisstorExit / john

comment:7 Changed 10 years ago by stars

after 8 hours, it start again to make the same problems. but yet there are not so much difference between recieve and send data. so there a bit better .

comment:8 Changed 10 years ago by stars

i have try to use the default exit policy in vidalia and tor have not make all this problems.

If i allow all ports , it start to make all this bugs

comment:9 Changed 10 years ago by stars

here is my torrc:

#MyFamily $F377AAB595C2C4C03252E041E44AA1C718082F3A,$C83B64ECA72443ED41AEF8C08D887DA971927779
NumCPUs 4
ExcludeNodes 204.8.156.142
ExcludeExitNodes 204.8.156.142
NumEntryGuards 8
DirReqStatistics 1
EntryStatistics 1
CellStatistics 1
ExitPortStatistics 1
GeoIPFile /home/starslights/tor/src/config/geoip
SocksPort 9050
SocksListenAddress 127.0.0.1
ControlPort 9051
HashedControlPassword 16:
Nickname SwissTorExit
ContactInfo starslights AT breakthru dot com
ORPort 80
ORListenAddress 0.0.0.0:9090
DirPort 443
DirListenAddress 0.0.0.0:9091
ExitPolicy accept *:*
BandwidthRate 200 KB
BandwidthBurst 3000 KB

mater commit : 6423091f071dc7c843d0fd02ac32b880b7754b24

now if i use the next torrc ( with vidalia default exit policy ) it don't make this bugs up

# This file was generated by Tor; if you edit it, comments will not be preserved
# The old torrc file was renamed to torrc.orig.1 or similar, and Tor will ignore it

# Limit the maximum token buffer size (also known as burst) to the given
# number of bytes.
BandwidthBurst 3072000
# A token bucket limits the average incoming bandwidth on this node to the
# specified number of bytes per second.
BandwidthRate 256000
CellStatistics 1
# Administrative contact information to advertise for this server.
ContactInfo starslights AT breakthru dot com
# If set, Tor will accept connections from the same machine (localhost only)
# on this port, and allow those connections to control the Tor process using
# the Tor Control Protocol (described in control-spec.txt).
ControlPort 9051
# Store working data, state, keys, and caches here.
DataDirectory /home/starslights/SwissTorExit
# Bind to this address to listen for connections from clients and servers,
# instead of the default 0.0.0.0:DirPort.
DirListenAddress 0.0.0.0:9091
# Serve directory information from this port, and act as a directory cache.
DirPort 443
DirReqStatistics 1
EntryStatistics 1
# A list of nodes never to use when building a circuit.
ExcludeNodes 204.8.156.142
ExcludeExitNodes 204.8.156.142
ExitPortStatistics 1
GeoIPFile /home/starslights/tor/src/config/geoip
HashedControlPassword 16:
# Where to send logging messages. Format is minSeverity[-maxSeverity]
# (stderr|stdout|syslog|file FILENAME).
Log notice stdout
# Set the server nickname.
Nickname SwissTorExit
# How many processes to use at once for public-key crypto.
NumCpus 4
# How many entry guards should we keep at a time?
NumEntryGuards 8
# Bind to this address to listen for connections from clients and servers,
# instead of the default 0.0.0.0:ORPort.
ORListenAddress 0.0.0.0:9090
# Advertise this port to listen for connections from Tor clients and servers.
ORPort 80
RelayBandwidthBurst 3072000
RelayBandwidthRate 256000
# Bind to this address to listen to connections from SOCKS-speaking
# applications.
SocksListenAddress 127.0.0.1

comment:10 Changed 10 years ago by Sebastian

Closing by request from John

comment:11 Changed 10 years ago by Sebastian

flyspray2trac: bug closed.

comment:12 Changed 7 years ago by nickm

Component: Tor RelayTor
Note: See TracTickets for help on using tickets.