A remote control config change in BearShare ?

ursula · #1 (**permalink**) April 16th, 2008

v5.2.5.3 Pro

Connection to ISP being disconnected... 3 minutes... 5 mins... 2 mins... whatever...
I haven't noted any specific pattern yet but it is only when BS is running.
I know, I know... Been waiting for something, but, is this IT ?

I only noticed it this past Monday as I haven't used it for about 6 weeks or more.

What you think, AW and gang ?

AaronWalkhouse · #2 (**permalink**) April 16th, 2008

No sign of that here. What's the timing on that? A few minutes
offline once in awhile or disconnects every few minutes?
You didn't say which.

If it's a few minutes offline once every few hours it could be your
system running out of RAM and timing out on connections. I do see
that once in awhile after running constantly for a few weeks.

Some routers also choke up because they run out of buffer space.
That can cause failures very quickly on a busy day, such as a short
disconnection every few minutes followed by a router crash and
reset. If you have one that can be flashed with a replacement OS
you can then fiddle with timeouts to prevent that.

ursula · #3 (**permalink**) April 16th, 2008

Disconnects every few minutes. Happens on 6 different systems.
(The 'specs' I give are at least the minimum for the 6 comps.)
And, forgot to mention this before, on 4 of the machines all using an ISP bundled bandwidth monitor the monitor pops up at random but with different intervals.

Re: the RAM comment... Don't think so... 1GB RAM and 2GB 'Virtual'.
Plus, this occurs with no real action with BS... i.e. not D/Ling, not U/Ling, not an Ultrapeer... Average Hosts bandwidth normal low (Ah, good old BearShare !)... Not searching. No other stuff happening with the exception of anti-virus/security running - and being active here in GF.
Task manager with a nice LOW almost level graph.

Know what you mean about the extended run time and RAM, but that's not applicable here as none of the comps are 24/7 and the disconnects start within minutes of launching BS.

4 of the comps are running straight ADSL modems... 2 with routers but both of them are single comps per router.

Last for now, the 6 machines are all connected through fairly widely spaced (geographically) exchanges. And the ISP is NOT a heavy cop type... No caps, no port locks - wide open.

AaronWalkhouse · #4 (**permalink**) April 16th, 2008

Maybe some anti P2P company is bombing the network. Right now I
am seeing a lot of UDP traffic coming out of the 69.85.242.x range
today, so you might find some relief by blocking that /24. I'll give
you a list of ranges to block in your firewall tonight when I get back
home. That'll take some of the load off of BearShare. ;]

There have been no configuration changes in BearShare for a while
but I think you were offline at the time so you wouldn't have noticed
until now. The last change restricted pongs to reporting only the
nodes using the ports 6346 and 6348. Not much of a change but
you might find it worth trying either those ports or something else,
depending on which port you are on right now.