Public bug reported:
When running in Secure mode a connecting client is not passing the
IDENTIFY state, the client side never receives his CID.
No error indication in debug window just stating IDENTIFY.
[HUB]
DNCQ connected
DNCQ entering IDENTIFY
[CLIENT]
Hub: [Outgoing][10.0.0.1:20443] HSUP ADBAS0 ADBASE ADTIGR
ADUCM0 ADBLO0
Hub: [Incoming][10.0.0.1:20443] ISUP ADBASE ADTIGR ADPING
And there it stops ....
Hub on same pc, with same configs running in Non-Secure mode works ...
OS: WinXP
** Affects: adchpp
Importance: Undecided
Status: New
--
Rev396 (mingw non official) hangs on IDENTIFY state
https://bugs.launchpad.net/bugs/663093
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to ADCH++.
Status in ADCH++: New
Bug description:
When running in Secure mode a connecting client is not passing the IDENTIFY
state, the client side never receives his CID.
No error indication in debug window just stating IDENTIFY.
[HUB]
DNCQ connected
DNCQ entering IDENTIFY
[CLIENT]
Hub: [Outgoing][10.0.0.1:20443] HSUP ADBAS0 ADBASE ADTIGR
ADUCM0 ADBLO0
Hub: [Incoming][10.0.0.1:20443] ISUP ADBASE ADTIGR ADPING
And there it stops ....
Hub on same pc, with same configs running in Non-Secure mode works ...
OS: WinXP
_______________________________________________
Mailing list: https://launchpad.net/~linuxdcpp-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~linuxdcpp-team
More help : https://help.launchpad.net/ListHelp
