automatic reconnection to hub being delayed

[MiRaGe 0]

So, probably you too meet with hubs where if you get banned hammering keeps reseting the bantime ....

i don't knwo if i could write it down clearly, but i'm thinking of that for example i'm banned for 24 hours and if i reconnect after 20 hours, the hub sends the message hammering makes bantime restart (or sg like that ... i haven't received such messages recently ) ... and the bantime goes up to the original 24 h instead of the remaining 4 hours .....

so, my question: is there a way to do sg against it, because if i don't check the pc severaly ... this could take longer than it should .... instead i correct the cause of the kick+ban and reconnect when the ban is over .....

it's a long long time i've worked with c++, but is it a possible like having a script checker ... like if the line we get from the hub contains [xxh] or [xx:xx] or sg like that then reconnecttime=reconnecttime+xx*24*60*60 .... or some even more simply way?

... just an idea :unsure:

[Aztek 2]

thats the point with the timer reset, so you know you did something wrong and you have to fix it and then reconnect (or wait if ur still banned)

although i think this feature is only for ynhub...

[MiRaGe 0]

thats the point with the timer reset, so you know you did something wrong and you have to fix it and then reconnect (or wait if ur still banned)

although i think this feature is only for ynhub...

i know .... but i was talking about that the client automatically reconnects to the hubs, which consider this as hammering and resets the bantime to the original..... and that is the one i'd like to get solved or sg .... and was thinking of sg like checking the received string for common timestamps as bantime .... and setting the waiting time before reconnection to later date&time so it won't keep reseting the bantime .... sometimes it was a week (when i got banned before) .... and it is annoying when you leave your pc running with dc++ on for some days and when coming back, seeing that you're still banned for a lot of time from some hubs .....

and you're right, i'll just have to correct what i did wrong, but this would only be a small comfortability in the software, what oters don't have

and as i wrote before it's been quite a long time i used c++ for programming, so don't know if it can be solved with a simple 20-25 line part or much harder and longer .... as checking a string and having one more int in the program should not take that much memory and cpu capacity :] .... i remember when i got F- for a program which used about 40 KB more memory than the teacher calculated on a pc with 64 MB ....so when we have computers now with 512 or more MB of

RAM .... it really doesn't matter .... only if it's too complicated.

[ifmn 0]

Why is apex reconnecting so fast ? Have I configured something wrong ?

[11:30:16] <-CORE-> Current user count: 34 after 13:56:25 uptime

[11:30:16] <-CORE-> Current sharesize is: 1.16 TiB

[11:30:17] <god-TANGRA> You're currently connected to too many hubs, you're on 21 hubs and the current limit is: 20

[11:30:17] *** Disconnected

[11:30:17] *** Connecting to black-sea.no-ip.biz...

[11:30:17] *** Connected

[11:30:19] <god-NEPTUN> YnHub version: 1.031 produced by Yoshi and Nev.

[11:30:19] <-CORE-> Current user count: 56 after 1:03:06:12 uptime

[11:30:19] <-CORE-> Current sharesize is: 1.70 TiB

[11:30:21] <god-NEPTUN> You're currently connected to too many hubs, you're on 21 hubs and the current limit is: 20

[11:30:21] *** Disconnected

[11:30:21] *** Connecting to boliarski-stan.no-ip.info...

[11:30:21] *** Connected

[11:30:23] <god-TANGRA> YnHub version: 1.031 produced by Yoshi and Nev.

[11:30:23] <-CORE-> Current user count: 34 after 13:56:32 uptime

[11:30:23] <-CORE-> Current sharesize is: 1.16 TiB

[11:30:24] <god-TANGRA> You're currently connected to too many hubs, you're on 21 hubs and the current limit is: 20

[11:30:24] *** Disconnected

[11:30:24] *** Connecting to black-sea.no-ip.biz...

[11:30:24] *** Connected

[11:30:27] <god-NEPTUN> YnHub version: 1.031 produced by Yoshi and Nev.

[11:30:27] <-CORE-> Current user count: 56 after 1:03:06:19 uptime

[11:30:27] <-CORE-> Current sharesize is: 1.70 TiB

[11:30:28] <god-NEPTUN> You're currently connected to too many hubs, you're on 21 hubs and the current limit is: 20

[11:30:28] *** Connecting to boliarski-stan.no-ip.info...

[11:30:28] *** Connected

[11:30:31] <god-TANGRA> YnHub version: 1.031 produced by Yoshi and Nev.

[11:30:31] <-CORE-> Current user count: 34 after 13:56:40 uptime

[11:30:31] <-CORE-> Current sharesize is: 1.16 TiB

[11:30:32] <god-TANGRA> You're currently connected to too many hubs, you're on 21 hubs and the current limit is: 20

[11:30:32] *** Disconnected

[11:30:32] *** Connecting to black-sea.no-ip.biz...

[11:30:32] *** Connected

[11:30:35] <god-NEPTUN> YnHub version: 1.031 produced by Yoshi and Nev.

[11:30:35] <-CORE-> Current user count: 56 after 1:03:06:27 uptime

[11:30:35] <-CORE-> Current sharesize is: 1.70 TiB

[11:30:36] <god-NEPTUN> You're currently connected to too many hubs, you're on 21 hubs and the current limit is: 20

[11:30:37] *** Disconnected

...

[11:33:28] *** Disconnected

[11:33:28] *** Connecting to black-sea.no-ip.biz...

[11:33:28] *** Connected

[11:33:32] <god-NEPTUN> YnHub version: 1.031 produced by Yoshi and Nev.

[11:33:32] <-CORE-> Current user count: 55 after 1:03:09:23 uptime

[11:33:32] <-CORE-> Current sharesize is: 1.56 TiB

[11:33:33] <god-NEPTUN> You're currently connected to too many hubs, you're on 21 hubs and the current limit is: 20

[11:33:33] *** Disconnected

[11:33:33] *** Connecting to boliarski-stan.no-ip.info...

[11:33:36] *** Connected

[11:33:44] <god-TANGRA> YnHub version: 1.031 produced by Yoshi and Nev.

[11:33:44] <-CORE-> Current user count: 34 after 13:59:54 uptime

[11:33:44] <-CORE-> Current sharesize is: 1.16 TiB

[11:33:45] <god-TANGRA> You're currently connected to too many hubs, you're on 21 hubs and the current limit is: 20

[11:33:45] *** Disconnected

[11:33:45] *** Connecting to black-sea.no-ip.biz...

[11:33:45] *** Connected

[11:33:50] <god-NEPTUN> YnHub version: 1.031 produced by Yoshi and Nev.

[11:33:50] <-CORE-> Current user count: 55 after 1:03:09:43 uptime

[11:33:50] <-CORE-> Current sharesize is: 1.56 TiB

[11:33:51] <god-NEPTUN> You're currently connected to too many hubs, you're on 21 hubs and the current limit is: 20

[11:33:51] *** Disconnected

[11:33:51] *** Connecting to boliarski-stan.no-ip.info...

[11:33:52] *** Connected

[11:33:54] <god-TANGRA> YnHub version: 1.031 produced by Yoshi and Nev.

[11:33:54] <-CORE-> Current user count: 34 after 14:00:03 uptime

[11:33:54] <-CORE-> Current sharesize is: 1.16 TiB

[11:33:55] <god-TANGRA> You're currently connected to too many hubs, you're on 21 hubs and the current limit is: 20

[11:33:55] *** Disconnected

[11:33:55] *** Connecting to black-sea.no-ip.biz...

[11:33:55] *** Connected

[11:34:00] <god-NEPTUN> YnHub version: 1.031 produced by Yoshi and Nev.

[11:34:00] <-CORE-> Current user count: 56 after 1:03:09:50 uptime

[11:34:00] <-CORE-> Current sharesize is: 1.71 TiB

[11:34:00] <god-NEPTUN> You're currently connected to too many hubs, you're on 21 hubs and the current limit is: 20

[11:34:00] *** Disconnected

Note: This doesn't happen with other drops (f.e redirect to already conn. hub, conn. reset and so on)

[RoLex 1]

I've heared that DC++ stops reconnecting when it finds word "banned" before connection close. It's an alternative, but maybe not that useful in hubs with non-english languages.