ideas

BSOD2600 · Post by **BSOD2600** » 2003-02-09 00:19

So far the hub has been working great except for the high amount of Protocol Violations, 160.88/h my hub seems to get. I worked with Sedulus a bit trying to track it down. Initially it appeared when NMDC users would do a |$RevConnectToMe was the problem. So I kicked all NMDC users and i was still getting violations and it wasnt the |$Revconnecttome. Now I'm stumpted....want the windump log?

Would it be possible to log these errors in a seperate log file?

Would it be possible to log the hub stats on each shutdown so its easier to track the various counters when things are changed?

Sedulus · Post by **Sedulus** » 2003-02-09 04:06

- the protocol violations have been identified as moglo searches. the ones where a $Search is done before the $MyINFO is sent.
- interesting though is that although the $Hello has never been sent to the other clients, only to the connecting client, the $Quit is sent to everyone...
that can't be right, can it?

BSOD2600 · Post by **BSOD2600** » 2003-02-09 16:48

I guess so....take a look at this which occured within a few seconds

$Quit zSearch[MoGLO]|
$Search 24.59.228.231:20665 T?F?5319669?1?08$Nobuo$Uematsu,$Junya$Nakano,$Masashi$Hamauzu$Luca$mp3|
$Quit zSearch[MoGLO]|
$Quit zSearch[MoGLO]|

That damn bot is hammering the hub!

aDe · Post by **aDe** » 2003-02-09 16:55

BSOD2600 wrote:That damn bot is hammering the hub!

Sorry about that. However, it would be strange if GLO/MO made a violation, because they won't search until they get a $Hello, which they won't get, until they send a $MyINFO- which they don't....

Post by **arnetheduck** » 2003-02-10 10:31

Sedulus wrote:- the protocol violations have been identified as moglo searches. the ones where a $Search is done before the $MyINFO is sent.
- interesting though is that although the $Hello has never been sent to the other clients, only to the connecting client, the $Quit is sent to everyone...
that can't be right, can it?

This is very right, because it saves loads of bandwidth and removes the flickering from the userlists...users are not validated until they send a good myinfo, so that they can be share-checked without everyone being bothered by jumping nicks (now you can actually use /showjoins in dc++...)...as to moglo, it's easy to write a bypass plugin / script if a hub owner wants it to work...and yes, they generate protocol violations, but I could separate that one in the statistics ("search before login" or something...sending text before login kicks you as well i think...)...
Anyway, since moglo found you, I take it that the hub registration works? What I'm interested in is what the nm hubpinger looks like, because it's most probably being blocked as well...

Post by **arnetheduck** » 2003-02-10 10:43

aDe wrote:
BSOD2600 wrote:That damn bot is hammering the hub!

Sorry about that. However, it would be strange if GLO/MO made a violation, because they won't search until they get a $Hello, which they won't get, until they send a $MyINFO- which they don't....

Oh, the connecting client get's a hello...nobody else does tho until the client's been validated...

Sedulus · Post by **Sedulus** » 2003-02-10 17:37

Sedulus wrote:- interesting though is that although the $Hello has never been sent to the other clients, only to the connecting client, the $Quit is sent to everyone...

resolved by arne

DC++

ideas

ideas

Who is online