Sign in to follow this  
Followers 0
RainyShadow

Better traffic control

28 posts in this topic

Simple example: to open the "New topic" page and write this, it took about 2 minutes instead of the usual few seconds. I currently have PWDC running, taking out all the awailable bandwidth for itself.

I tried the "Transfer Rate limiting" option, and got banned from few hubs for using it.

Also, sometimes the uploading/downloading cause disconnection from hubs because there's no free bandwidth left for simple hub-client communication.

Share this post


Link to post
Share on other sites

Simple example: to open the "New topic" page and write this, it took about 2 minutes instead of the usual few seconds. I currently have PWDC running, taking out all the awailable bandwidth for itself.

I tried the "Transfer Rate limiting" option, and got banned from few hubs for using it.

Also, sometimes the uploading/downloading cause disconnection from hubs because there's no free bandwidth left for simple hub-client communication.

this is my current uptime, [20:23] * Crise uptime: 1 week 23 hours 49 min and during this week i've never expirienced anything similiar to what you described in your post, could you please provide info, such as what kind of setup you have, what ports do you use, how many ul's and dl's you got ongoing when that happened etc...

Share this post


Link to post
Share on other sites

It's not like "when that happened", it's happening all the time when PWDC is running. Having PWDC started means slow browsing, crappy ICQ, etc. It just "sucks" all the available bandwidth.

I tried NetLimiter, but it crashes on startup, probably because of some bad DLLs left over. [EDIT] my mistake, not Netlimiter, but other internet apps crash when have it installed.

My setup is the following:

PC - Duron@950, Via KT133A chipset, 512MB RAM

Software: Win98SE, newest drivers (except for my GF4 MX card), PPPoE connection, no firewall, working but disabled ICS (sometimes used to share net with my laptop), 6 IPs on a single LAN adapter (one for each private range + one public), no funny settings in PWDC, default (random) ports.

Share this post


Link to post
Share on other sites

It just "sucks" all the available bandwidth

shurley thats a good thing :).

Share this post


Link to post
Share on other sites

You need to emulate in your favourite hub so they cannot see you uging the bandwidth limit feature (properties > emulate DC++).

PWDC will not cause you to disconnect if all you bandwidth is being used. It's more than likely your firewall/router is dropping your connection to the hub.

This really belongs in support. Moved.

Share this post


Link to post
Share on other sites

You need to emulate in your favourite hub so they cannot see you uging the bandwidth limit feature (properties > emulate DC++).

Lee, the L:x in tag is always visible, regardless of emulation.

Share this post


Link to post
Share on other sites

Lee, the L:x in tag is always visible, regardless of emulation.

I thought you hid that. Nevermind then, maybe it should he hidden for emulation mode.

Share this post


Link to post
Share on other sites

I thought you hid that. Nevermind then, maybe it should he hidden for emulation mode.

no it shouldn't as if we did that it'd be sure to get us banned :)

Share this post


Link to post
Share on other sites
no it shouldn't as if we did that it'd be sure to get us banned :)
They'll ban it whatever due to segment downloading, limiter, etc.

Share this post


Link to post
Share on other sites

They'll ban it whatever due to segment downloading, limiter, etc.

not everyone will ban because of segmented dl or limiter, but they will if the limiter is not shown in tag :)

Share this post


Link to post
Share on other sites

don't hide it!... it's one of the good points for allowing SDC++ clients in all hubs I'm in.

It would be perfectly good client if there was a way for hub to tell client how many max segments are allowed (yeah - something like secured executor from Zion++).

Share this post


Link to post
Share on other sites

It would be perfectly good client if there was a way for hub to tell client how many max segments are allowed (yeah - something like secured executor from Zion++).

What would this achieve? Basically overriding the max segments they have set in their settings?

Share this post


Link to post
Share on other sites

You need to emulate in your favourite hub so they cannot see you uging the bandwidth limit feature (properties > emulate DC++).

PWDC will not cause you to disconnect if all you bandwidth is being used. It's more than likely your firewall/router is dropping your connection to the hub.

This really belongs in support. Moved.

I don't use a firewall, neither a router. And as Crise said, the emulation won't help.

I'm asking for better connection management in the next client, i.e. give higher priority to control packets and automatic (temporary) lowering of download/upload speeds in order to keep the communication stable.

P.S. "Connection reset by server" - this don't sound like a client-initiated disconnect :)

Share this post


Link to post
Share on other sites

...P.S. "Connection reset by server" - this don't sound like a client-initiated disconnect ;)

It really does not, so why you think think the problem is in the client's traffic management?

You are probably right for the slow browsing, but you said smth about 6 IPs etc...

Can you manage your network in such a way that xKB - 5KB are bound to PWDC (there is such field in Connection settings), and the rest (5KB) remain on another IP for your browser.

I agree it is not the most convenient way, but I see it as a possible solution.

Or we can add smth like "Decrease download speed with x* KB when y*.exe is running" in Settings?

x - user defined KBs

y - browser's *.exe

Multiple fields or "Add..." will allow to define different behavior of Apex DC++ when different network apps are started. But it is probably quite difficult to be done. Can the source of some download manager to be used? F. ex., Download Master has such feature, I suppose that Flashget, Getright, etc. have it too.

P. S. Sorry if talking bullsh*t again. :D This is the green head's duty in a discussion. :P:) :)

Edited by Zlobomir

Share this post


Link to post
Share on other sites

You need to emulate in your favourite hub so they cannot see you uging the bandwidth limit feature (properties > emulate DC++).

Sorry, where is the "properties" window? Have been looking for that option and I know I have seen it, but I cant find it.

Share this post


Link to post
Share on other sites

Sorry, where is the "properties" window? Have been looking for that option and I know I have seen it, but I cant find it.

Favourite hubs > right click your hub.

It doesn't matter though, as Crise said your limit is always visable.

Connection reset by server (usually) means your port/connection to the hub has closed. When I'm on Bittorrent, it uses far too many ports and usually conflicts with PWDC, therefore hubs get closed.

Try a program called NetLimiter, limit your upload speed and see whether it allows you to browse the internet and also keep the hub open.

Share this post


Link to post
Share on other sites

I tried NetLimiter, but it crashes on startup, probably because of some bad DLLs left over. [EDIT] my mistake, not Netlimiter, but other internet apps crash when have it installed.

try a program called NetLimiter

:)<_< and we have gone full circle.

RainyShadow. perhaps you should post the exception you get when your DC crashes. Mayby some on else will have better luck then me with it :lol:

Edited by balder

Share this post


Link to post
Share on other sites

RainyShadow: What are the other crashing applications?

Share this post


Link to post
Share on other sites

Try NetLimiter 1.3, not 2.0.

I've already tried Netlimiter versions 1.30, 1.29 and 1.25. Neither of these work, they all cause my internet applications to crash while trying to open a port.

RainyShadow: What are the other crashing applications?

Opera, PWDC, DC++, and any other program which tries to open TCP/IP connection.

This is the last exceptioninfo.txt i got from DC++ (didn't found such for PWDC++) :

Code: c0000005

Version: 0.68

Major: 4

Minor: 10

Build: 67766446

SP: 0

Type: 0

Time: 2006-06-05 22:26:09

TTH: K7TTU6MNVUWI77CUWXSFQ33VMBDSCZUTF6HUX2Y


NL_LSP!0x10000003: ?

0x00936E00: ?
This is from faultlog.txt:
Date 06/05/2006 Time 22:22

DUC20 caused an invalid page fault in

module <unknown> at 00de:504d4554.

Registers:

EAX=504d4554 CS=01a7 EIP=504d4554 EFLGS=00010202

EBX=00002778 SS=01af ESP=014bfa20 EBP=014bfa6c

ECX=014bfa2c DS=01af ESI=00d90f90 FS=43bf

EDX=00000000 ES=01af EDI=014bfa5c GS=0000

Bytes at CS:EIP:


Stack dump:

76003481 014bfa2c 00d90f90 00d90f90 76002881 00000000 00c80528 00c807c0 760029ff 00c8041c 014bfa5c 00d906f0 014bfbf4 ffffffff 00d906fc 00000000 

**********************************************************************

Date 06/05/2006 Time 22:25

OPERA caused an invalid page fault in

module <unknown> at 00de:00750072.

Registers:

EAX=00750072 CS=01a7 EIP=00750072 EFLGS=00010206

EBX=00002778 SS=01af ESP=02b1fa18 EBP=02b1fa64

ECX=02b1fa24 DS=01af ESI=007852b0 FS=717f

EDX=00000000 ES=01af EDI=02b1fa54 GS=0000

Bytes at CS:EIP:


Stack dump:

76003481 02b1fa24 007852b0 007852b0 76002881 00000000 0078016c 00781c60 760029ff 00780060 02b1fa54 007807a0 02b1fbec ffffffff 007807ac 00000000 

**********************************************************************

Date 06/05/2006 Time 23:47

NETLIMITER caused an invalid page fault in

module NETLIMITER.EXE at 01a7:00454905.

Registers:

EAX=bff7278d CS=01a7 EIP=00454905 EFLGS=00010286

EBX=000000c8 SS=01af ESP=006fed10 EBP=006fed40

ECX=00000000 DS=01af ESI=00000000 FS=3487

EDX=81d474ac ES=01af EDI=00000000 GS=0000

Bytes at CS:EIP:

8b 41 4c 85 c0 75 0c 6a ec ff 71 1c ff 15 e0 46 

Stack dump:

00460eee 00000000 015d1060 00000000 015d1420 006fed14 006feef0 0047328d bff726c5 bfc02d0b bff7278d bfc02d0b 006fedc8 0046126c 006fed70 00000000

The only working solution is to use the limiting capabilities of PortExplorer and manually regulate the speed of each socket, but this program causes very high CPU usage on high traffic. <_<

Share this post


Link to post
Share on other sites

I dare to suppose this has smth to do with Win 98, as in NT-based versions network management is quite different. F. ex., the new Skype also requires Win 2000/XP or later (at least they say so on the d-d page). If you have time and a chance, please recreate the setup on a 2000/XP machine and let us know if this solves the trouble.

I know that you have some reason(s) to use Win 98, but nobody can fight the time...

Edited by Zlobomir

Share this post


Link to post
Share on other sites

Just got this : Reason: _ban_1w BAD CLIENT: --> [bandwidth limited client]

LOL

btw. on XP browsing seems to get more bandwidth, but the DC speed is terrible ;) and hubs still disconnect.

Share this post


Link to post
Share on other sites
Sign in to follow this  
Followers 0