Cannot be pinged while minslots 5 set [ SOLVED ]

[Delion]

https://dchublist.org/685-babylon.html

Tried to change pinger INF, but no luck.

[Admin]

By default pinger declares 3 open slots.
Changed to 7 ATM next ping should do fine. Lets see.
...
Doesnt ping. Can we get a log somewhere?
Changed slots to 7 then 10 it errors out with:

Error: expected disconnect, received: &adc.InfoPacket{Msg:(*adc.RawMessage)(0xc000091820)}

Whats the min share and other requirements? Can you try changing slots to 3 and see if this is really the issue?

[Delion]

Whats the min share and other requirements?

Hm. AFAIK uHub reports its minshare and minslots actually...

Anyway: minshare: 1GiB, minslots: 5, min 'user' hubs: 2

The last option was added just recently and minslots caused problems before (I did that test already by reverting restriction to 1 open slot).

try changing slots to 3

Done.

[Admin]

OK. Let me see now. I think it will work now.

[Delion]

Minslots 3 did it.

However what if I raise minslots to 15?..

[Admin]

I think up to 9 slots will be fine now.

[Delion]

Hmmm.

Are custom pinger options functional? Seems to be not.

https://prnt.sc/u92eoj

[Admin]

Only on legacy, old pinger. New one runs preset. I did set slots to 20 seems like no hubs are set to limit number of open upload slots for now,
so it's ok. Since you running uhub in strict tls 1.3 don't use legacy ping it won't ping.

[Delion]

Aha, I see now.

Thanks for help!

[Admin]

No problem.
Thanx for reporting. This could lead to potential issues in the future.