Error: invalid slots for pinger

[Kcchouette]

Hello

When trying to ping a Verlihub hub, I have this error:

2020/01/04 20:17:44 invalid slots: "6><go-dcpp V:0.20.1"

Here more detailed information I have, is it a pinger problem or a hub software problem?

$ dcping ping --hubs=2 --slots=6 --share=324882100000 --encoding=cp1252  dchub://tortura-abuser.eu:66

{"name":"S€V€R€ †ØR†µR€","addr":["dchub://tortura-abuser.eu:66"],"soft":{"name":"Verlihub","vers":"1.2.0.7","ext":["NoHello","NoGetINFO","TLS","UserIP2","TTHSearch","ZPipe","HubINFO","BotList","MCTo","FailOver","HubTopic","OpPlus","NickRule","SearchRule","UserCommand"]},"users":0,"status":"error"}

Moreover, it's weird because 1.2.0.7 does not exist on your release version: https://github.com/Verlihub/verlihub/releases Or maybe is it the master version?

Thanks anyway

[RoLex]

2020/01/04 20:17:44 invalid slots: "6><go-dcpp V:0.20.1

where you see this message? verlihub dont send this message to user.

yes, 1.2.0.7 is not final, from master branch.

[Kcchouette]

where you see this message?

On error channel of my pinger

[Kcchouette]

Here more debug information:

2020/01/05 18:14:53 <- "$Lock EXTENDEDPROTOCOL_NMDC_1445 Pk=Verlihub 1.2.0.7|"
2020/01/05 18:14:53 -> "$Supports NoHello NoGetINFO TLS UserIP2 UserCommand TTHSearch ZPipe0 ADCGet BotINFO HubINFO BotList MCTo NickChange ClientNick IN FeaturedNetworks GetZBlock ClientID XmlBZList Minislots TTHL TTHF ZLIG ACTM BZList SaltPass FailOver HubTopic OpPlus BanMsg NickRule SearchRule ExtJSON2 Locale|"
2020/01/05 18:14:53 -> "$Key \x14\xd1\xc0\x11\xb0\xa0\x10\x10A ѱ\xb1\xc0\xc001\x110\x90p\xc1\xe6P/%DCN000%/\x10|"
2020/01/05 18:14:53 <- "$Supports NoHello NoGetINFO TLS UserIP2 TTHSearch ZPipe HubINFO BotList MCTo FailOver HubTopic OpPlus NickRule SearchRule UserCommand |"
2020/01/05 18:14:53 -> "$ValidateNick pinger_29152b9e|"
2020/01/05 18:14:54 <- "$NickRule Min 1$$Max 120$$Char 60 62$$|"
2020/01/05 18:14:54 <- "$HubName S\x80V\x80R\x80 \x86\xd8R\x86\xb5R\x80|"
2020/01/05 18:14:54 79.XXX.XX.XX:66 switched to a fallback encoding
2020/01/05 18:14:54 <- "$Hello pinger_29152b9e|"
2020/01/05 18:14:54 -> "$Version 1,0091|"
2020/01/05 18:14:54 -> "$GetNickList|"
2020/01/05 18:14:54 -> "$MyINFO $ALL pinger_29152b9e <go-dcpp V:0.20.1,M:A,H:2/1/0,S:6>$ $100\x04$$324882100000$|"
2020/01/05 18:14:54 -> "$BotINFO pinger_29152b9e|"
2020/01/05 18:14:54 <- "$SearchRule Min 1$$Max 256$$Num 1$$Int -1$$IntPas -1|"
2020/01/05 18:14:54 <- "$HubName S\x80V\x80R\x80 \x86\xd8R\x86\xb5R\x80 -  Nu ti arata dispretul fata de un copil mai slab, pentru ca poate devenii cel mai nemilos tigru|"
2020/01/05 18:14:54 <- "$MyINFO $ALL pinger_29152b9e FR,France,Paris,<go-dcpp V:0.20.1,M:A,H:2/1/0,S:6><go-dcpp V:0.20.1,M:A,H:2/1/0,S:6>$ $\x04$$324882100000$|"
2020/01/05 18:14:54 invalid slots: "6><go-dcpp V:0.20.1"

[RoLex]

i see. admin of this hub has set desc_insert_vars option in verlihub to %[CC],%[CN],%[CITY],%[TAG]. this means that hub inserts another tag right before the real tag in description field (nmdc $myinfo). so hub sends back to pinger his own myinfo with double tag as you can see here:

FR,France,Paris,<go-dcpp V:0.20.1,M:A,H:2/1/0,S:6><go-dcpp V:0.20.1,M:A,H:2/1/0,S:6>

then pinger is unable to parse this new duplicate tag. this is a bug in pinger parser. it reads first < before the $, while it should read the last. you can create an issue in go-dcpp.

this is typical mistake, i have done it myself when i was new at this. :)

[Kcchouette]

thank you, I'm closing the ticket!