[DiscordArchive] HI guys.. I see channel 4.3.4 but without support, I assume questions are still possible.
[DiscordArchive] HI guys.. I see channel 4.3.4 but without support, I assume questions are still possible.
Original source
HI guys.. I see channel 4.3.4 but without support, I assume questions are still possible.
I do have some questions, but you may want to hear my back-story first
**Story**
Obtained the 4.3.4 Preservation Projectand compiled it on Win 11 x64 with the following: openssl 1.1.1 (self compiled), boost 1.78
Initially VS 2022 gave me compile errors in the ScriptMgr's CreatureGameObjectScriptRegistrySwapHooks visitor not able to convert all arguments, but I think I fixed that.
Mysql8 running as database.
Bnetserver and worldserver running fine ( maybe not all mmaps correctly loaded yet) Also the libssl_1_1 and crypto.dll are there in the Bin
I have 2 different cata 4.3.4 clients downloaded, one of them has a wow-64.exe)
I ran the connection_patcher and client_loader_64. So many different exe's to choose from.
bnetserver was ran ports 1118 and 1119 by default. I ran server and client on same machine (firewall turned off)
None of the wow exe were able to connect (login server down), I had bnetserver running in VS debugmode, full with breakpoints..Not any triggered.
Wireshark gave me insight that 4.3.4 was also using port 3724 to connect (like 3.3.5). But bnetserver only had 1118 and 1119 configured
I assumed 1118 is for communication between bnetserver and worldserver(s).
So what was 1119 then? I changed that to 3724.
Now void Battlenet::Session::ReadHandler() gets triggered and redirects to void Battlenet::Authentication::LogonRequest::Read()
where I see Garbage being read and msg size dont match 333 bytes expected (got 312).
**Questions**
To keep it short:
1) Is 1119 change to 3724 good?
2) Is OpenSSL 1.1.1 okay?
3) Is the TC 4.3.4 version from the Preservation project okay?
4) are the AUTH files from The-Cataclysm-Preservation-Project/AuthModules ok?
rektbyfaith
09-22-2024, 06:06 PM #1Archived author: martijnh • Posted: 2024-09-22T18:06:46.434000+00:00
Original source
HI guys.. I see channel 4.3.4 but without support, I assume questions are still possible.
I do have some questions, but you may want to hear my back-story first
**Story**
Obtained the 4.3.4 Preservation Projectand compiled it on Win 11 x64 with the following: openssl 1.1.1 (self compiled), boost 1.78
Initially VS 2022 gave me compile errors in the ScriptMgr's CreatureGameObjectScriptRegistrySwapHooks visitor not able to convert all arguments, but I think I fixed that.
Mysql8 running as database.
Bnetserver and worldserver running fine ( maybe not all mmaps correctly loaded yet) Also the libssl_1_1 and crypto.dll are there in the Bin
I have 2 different cata 4.3.4 clients downloaded, one of them has a wow-64.exe)
I ran the connection_patcher and client_loader_64. So many different exe's to choose from.
bnetserver was ran ports 1118 and 1119 by default. I ran server and client on same machine (firewall turned off)
None of the wow exe were able to connect (login server down), I had bnetserver running in VS debugmode, full with breakpoints..Not any triggered.
Wireshark gave me insight that 4.3.4 was also using port 3724 to connect (like 3.3.5). But bnetserver only had 1118 and 1119 configured
I assumed 1118 is for communication between bnetserver and worldserver(s).
So what was 1119 then? I changed that to 3724.
Now void Battlenet::Session::ReadHandler() gets triggered and redirects to void Battlenet::Authentication::LogonRequest::Read()
where I see Garbage being read and msg size dont match 333 bytes expected (got 312).
**Questions**
To keep it short:
1) Is 1119 change to 3724 good?
2) Is OpenSSL 1.1.1 okay?
3) Is the TC 4.3.4 version from the Preservation project okay?
4) are the AUTH files from The-Cataclysm-Preservation-Project/AuthModules ok?
Original source
openssl 1.1.1 is not okay. burn it. delete it. pretend it never existed
rektbyfaith
09-22-2024, 06:25 PM #2Archived author: Northstrider • Posted: 2024-09-22T18:25:08.235000+00:00
Original source
openssl 1.1.1 is not okay. burn it. delete it. pretend it never existed
Original source
use openssl 3.x
rektbyfaith
09-22-2024, 06:25 PM #3Archived author: Northstrider • Posted: 2024-09-22T18:25:13.889000+00:00
Original source
use openssl 3.x
Original source
Thanks for the quick response Ovahlord... I will update to 3.3.2 again.. I thought that the old 4.3.4 client had troubles connecting to the server with newer ssl. But that was before I changed ports from 1119 to 3724.. Do you also believe that this could be the reason for the Garbage data being read?
rektbyfaith
09-22-2024, 06:27 PM #4Archived author: martijnh • Posted: 2024-09-22T18:27:59.399000+00:00
Original source
Thanks for the quick response Ovahlord... I will update to 3.3.2 again.. I thought that the old 4.3.4 client had troubles connecting to the server with newer ssl. But that was before I changed ports from 1119 to 3724.. Do you also believe that this could be the reason for the Garbage data being read?
Original source
No. openssl is not related to any connectivity issues. the 4.3.4 repo has a own wiki on the git page that lists all possible reasons why a connection fails
rektbyfaith
09-22-2024, 06:28 PM #5Archived author: Northstrider • Posted: 2024-09-22T18:28:43.958000+00:00
Original source
No. openssl is not related to any connectivity issues. the 4.3.4 repo has a own wiki on the git page that lists all possible reasons why a connection fails
Original source
Ok good to know.. I did have connectivity issues myself at work, when attempting a ssl 1.0.x client to MicroSoft's App Service, that runs with the latest OpenSSL 3.3.x version. Client basically said incompatible TLS/SSL version.
Any way good to know that this is not the case with 4.3.4 client.. thanks again (Y)
rektbyfaith
09-22-2024, 06:32 PM #6Archived author: martijnh • Posted: 2024-09-22T18:32:14.932000+00:00
Original source
Ok good to know.. I did have connectivity issues myself at work, when attempting a ssl 1.0.x client to MicroSoft's App Service, that runs with the latest OpenSSL 3.3.x version. Client basically said incompatible TLS/SSL version.
Any way good to know that this is not the case with 4.3.4 client.. thanks again (Y)
Original source
you are safe, 4.3.4 doesnt use tls/ssl
rektbyfaith
09-22-2024, 06:42 PM #7Archived author: Tea • Posted: 2024-09-22T18:42:24.158000+00:00
Original source
you are safe, 4.3.4 doesnt use tls/ssl
Original source
I have Openssl 3.3.2 back running again.. Have the same issue still.. But I noticed differences in the ScriptMgr.cpp that was committed on the new Fork.. So I just took the one-liner fix from @Shauren / or <@228947336800370689> .. that <@283302203957968897> added.. So I also tried that complete repo.. I have two different Preservation Projects as it seems.
I will figure that out..
<@283302203957968897> , the one you shared does not build with many errors ( On my system I mean.. I will figure that out too, and let you know what I think may be the reason)
Main question I still have is whether the port change from 1119 to 3724 was a good change? Maybe the client is now able to connect to bnetserver, but is 1119 not intended for the client, I cant distinguish.
rektbyfaith
09-22-2024, 07:12 PM #8Archived author: martijnh • Posted: 2024-09-22T19:12:32.639000+00:00
Original source
I have Openssl 3.3.2 back running again.. Have the same issue still.. But I noticed differences in the ScriptMgr.cpp that was committed on the new Fork.. So I just took the one-liner fix from @Shauren / or <@228947336800370689> .. that <@283302203957968897> added.. So I also tried that complete repo.. I have two different Preservation Projects as it seems.
I will figure that out..
<@283302203957968897> , the one you shared does not build with many errors ( On my system I mean.. I will figure that out too, and let you know what I think may be the reason)
Main question I still have is whether the port change from 1119 to 3724 was a good change? Maybe the client is now able to connect to bnetserver, but is 1119 not intended for the client, I cant distinguish.
Original source
This is a screen shot of the bnetserver.exe right after the client username+pw was entered.. and Client says "Authenticating". The bnetserver will crash.
![[Image: image.png?ex=690c4c6a&is=690afaea&hm=d56...d6902af3e&]](https://cdn.discordapp.com/attachments/376457068506382336/1287493936319037512/image.png?ex=690c4c6a&is=690afaea&hm=d56f8eb759a3c668e956370724f52f1642b9dd6c43b6f7c5041195cd6902af3e&)
rektbyfaith
09-22-2024, 07:21 PM #9Archived author: martijnh • Posted: 2024-09-22T19:21:14.948000+00:00
Original source
This is a screen shot of the bnetserver.exe right after the client username+pw was entered.. and Client says "Authenticating". The bnetserver will crash.
1 Guest(s)
1 Guest(s)