linuxdcpp-team team mailing list archive

[Pirre <880488@xxxxxxxxxxxxxxxxxx>]

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 :)

-- 
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to ADCH++.
https://bugs.launchpad.net/bugs/880488

Title:
  Rev 543 disconnects PING user

Status in ADCH++:
  In Progress

Bug description:
  It seems that that last access modification lets a user with SUP pass
  2 times the verification status, and disconnects him with reason 1 ,
  think thats CID change :) the momet it verify's the CID second time

To manage notifications about this bug go to:
https://bugs.launchpad.net/adchpp/+bug/880488/+subscriptions