FlexHub doesn't let ADC hublist pinger connect with ADC

[dchublist.org]

I have noticed that if i set flechub to serve only as adc server after pinger connects it gets wrong protocol used - and converts it to nmdc hub.....

Not sure why! And what causes this .....

[FlipFlop™]

Can you make the pinger store a logfile of the connection? It would be easier to determine the problem then.

Flexhub uses autodetection to see if the client uses adc or nmdc, it does so by waiting for a full second on the first command from the client, HSUP should be sent by client as soon as it's connected to the hub.

If the client (or in this the pinger) waits longer than 1 second, the hub will try NMDC protocol by sending the $Lock. So if your pinger takes too long before sending HSUP, the pinger receives the $Lock and thinks it's an NMDC hub. When a Flexhub is set to be ADC only, the NMDC (partial) login is still used to automatically redirect to the ADC address of the same hub using a $ForceMove.

[dchublist.org]

Hre is regular log of pinger connection on FLEX running in nmdc mode:

Pinging support.flexhub.org:8000

• Socket created
• Connected

 [ 14:11:48 ][ --> ]$Lock EXTENDEDPROTOCOL_FLEXHUB_MULTIPROTOCOL_EDW3 Pk=version0.2
 [ 14:11:48 ][ <-- ]$Supports NoGetINFO NoHello BotINFO|
 [ 14:11:48 ][ <-- ]$Key BÑÀ° A ѱ±ÀÀ01‘ ÑÑqÑ!‘Ñ‘ ѱ±ÀÀ01¡1F|
 [ 14:11:48 ][ <-- ]$ValidateNick HublistPinger|
 [ 14:11:48 ][ --> ]$Supports NoGetINFO NoHello BotINFO
 [ 14:11:48 ][ --> ]$HubName FlexHub Support
 [ 14:11:48 ][ --> ]$Hello HublistPinger
 [ 14:11:48 ][ <-- ]$Version 1,0091|
 [ 14:11:48 ][ <-- ]$GetNickList|
 [ 14:11:48 ][ <-- ]$MyINFO $ALL HublistPinger visit our hublist at dchublist dot org<++ V:0.843,M:A,H:1/0/1,S:5>$ $Cable$admin@unitedhublist.com$2086698705833$|
 [ 14:11:49 ][ --> ]$HubName FlexHub Support - RIP oldindian, you will be missed

And everything looks fine i will have to setup a flexhub myself in adc mode to get that adc log.
Here is what ping does on adc:// address

[ 11:11:09 ][ <-- ]HSUP ADBASE ADTIGR ADPING

 [ 11:11:09 ][ --> ]ISUP ADBAS0 ADBASE ADTIGR ADKEYP ADOSNR ADPING ADUCM0 ADUCMD
 [ 11:11:09 ][ --> ]ISID GY2M
 [ 11:11:09 ][ --> ]IINF NIDCHUBLIST.ORG\sSUPPORT\sHUB\s-\s[ADC] APLUADCH VEv2.16 DEBest\sDirect\sConnect\sHublist! HHdc-united.ddns.net WShttp://dchublist.org NEyour\shubnetwork\sname OWyou UC5 MS0 XS2.199023255552e+014 ML2 XL20 XU20 XR20 XO20 MC2000 UP50390 HU1 HI1 CT32

All looks good yet everytime ping connects to flexhub using adc:// address after 1st ping it converts it to nmdc - will look in code on my end as i know there is protocol verification in php somewhere that could cause this...But for now at dchublist.org its impossible to see any flexhub in adc mode at all :(

[FlipFlop™]

Can't you get the ADC log from the pinger?
You can set it to connect to adc://support.flexhub.org:8000

I've enabled monitoring on the pinger IP in Flex support hub, I can see what happens on this end when you connect now.

[dchublist.org]

Here is how hublist deals with protocol:

//Check if NMDC PROTOCOL
                   if (substr($out, 0 , 5) == '$Lock'){
                      $sql = "UPDATE hubs SET protocol = 'dchub://' , status = 'Wrong protocol, this hubs uses the NMDC protocol. Protocol changed to NMDC' WHERE id = '$id'";
                    $this->setQuery($sql);
                    $this->query();
                    print("<p align=\"center\">Wrong protocol, this hub uses the NMDC protocol. The protocol was changed</p>");
                      fwrite($file , "\r\n\r\n\r\n

• Wrong protocol, this hub uses the NMDC protocol. The protocol was changed\r\n\r\n\r\n");

                    return;
                   }
                   
I did edit address to adc// now will have to wait for ping results up to 2 hours depending where is it i quede..

[FlipFlop™]

I'ts all about the timing.
If your pinger connects to an ADC hub it should immediately send the HSUP, because if the pinger waits for a second before sending HSUP it will receive a $Lock from the hub because the hub will try NMDC login then.

[dchublist.org]

I dont thing that pinger waits at all if the hub is regged as adc:// it will send HSUP immidiately unless there is a network connection issue and connection is slowed down . Maybe setting wait time to 2 seconds will be better. Lets wait for that log...Hard to say whats up withou it...

[dchublist.org]

WOW!
This is all i got:

[ 16:11:20 ][ <-- ]HSUP ADBASE ADTIGR ADPING

 [ 16:11:20 ][ --> ]$Lock EXTENDEDPROTOCOL_FLEXHUB_MULTIPROTOCOL_VJGM Pk=version0.2|

• Wrong protocol, this hub uses the NMDC protocol. The protocol was changed

So still unknown ....looks like flex sends &Lock anyways regardless of HSUP sent
That is the whole log on flexhub support hub connected on adc://

[FlipFlop™]

Thanks, it confirms the log I see in Flexhub.
I think you've found a bug in Flex, the hub doesn't seem to wait at all for HSUP, it immediately sends the $Lock.
Will have a closer look at it soon, and let you know.

[dchublist.org]

Thanks, it confirms the log I see in Flexhub.
I think you've found a bug in Flex, the hub doesn't seem to wait at all for HSUP, it immediately sends the $Lock.
Will have a closer look at it soon, and let you know.

Any chances on gettin this fixed?