Fully supported right now .
Works even without patch.
Fixed VE - versions available for download below - many thanx to eMTee.
Note - debug version is not VE fixed.
Moderator: Admin
by Admin » Sun Apr 30, 2017 8:33 pm
by Derek » Sun Sep 09, 2018 12:26 pm
Have tryed this with 7 different clients , none has a prob with sending that INF after the users verification, seems its only the pinger that not replys on the ISID, have posted a support ticket on dchublist.
Access.lua does seems completely correct now.
IF the protocol not specifies that the IINF must be send first, then the pinger is wrong.
Just a warning using this rev 544 will cause the hub the disappear from the hublist .... , will post answer from hublist here
now the pinger stay's in IDENTIFY state untill the timeout disconnects him