Server select empty when using wifi (linux)

[Nori]

Originally Posted by Rabcor [You must be logged in to view images. Log in or Register.]

Lastly (and probably most easily) you can just get it precompiled, here's mine, I compiled it on manjaro (the .txt extension was necessary to be able to upload the file, just download it, remove .txt, make it executable (chmod +x) and run it if you want to use it):

I actually was in the correct directory, I was just lazy and copied and pasted this error from someone else who had the same issue as me.

Thank you for posting the precompiled script, I'm going to try that next. I've seen it suggested to install build essential libraries for arch linux, but that also threw back the same error w/ the .h file.

Fingers crossed!

[Nori]

Originally Posted by Naethyn [You must be logged in to view images. Log in or Register.]

Installing base-devel still results in the same error on makefile. I tried using your and my own precompiled file and that throws an error on GLIBC_2.34 not found. For now, tethering to my phone works on steamdeck, but I'd like to get this compiled for arch linux (steam os).

Have you tried any combination of VPNs? Hardware/software?

[mcoy]

I thought I would have to use this, but I just tried p99 anyway and my server select is populating fine on the deck on both my fios and my 4g hotspot. I'm visiting some family this weekend so I'll try from their connection but so far it doesn't seem necessary.

-Mcoy

[8bitbang]

I installed Project 99 in kubuntu 22.10 and used the p99-login-middlemand. The servers now show up and I made sure to use the latest Spell files. But I'm getting the spells file is out of date error. I have no issues on windows but sadly NZXT put a bad update and now my CPU cooler pump doesn't work under windows. So I resorted to using linux, can anyone provide any feedback?

[8bitbang]

Originally Posted by 8bitbang [You must be logged in to view images. Log in or Register.]

I installed Project 99 in kubuntu 22.10 and used the p99-login-middlemand. The servers now show up and I made sure to use the latest Spell files. But I'm getting the spells file is out of date error. I have no issues on windows but sadly NZXT put a bad update and now my CPU cooler pump doesn't work under windows. So I resorted to using linux, can anyone provide any feedback?

Figured it out, delete my post

[nanopino]

Here's a repo with a python script that replicates Zaela's fix. No build tool chain required so it can run on the Steam Deck with minimal effort. Also has some beginner friendly instructions to setup Project 1999 on Steam Deck Gaming mode.

https://github.com/rtrajano/p99_login_helper

[Muchew]

Originally Posted by nanopino [You must be logged in to view images. Log in or Register.]

Here's a repo with a python script that replicates Zaela's fix. No build tool chain required so it can run on the Steam Deck with minimal effort. Also has some beginner friendly instructions to setup Project 1999 on Steam Deck Gaming mode.

https://github.com/rtrajano/p99_login_helper

Thanks for this. Any idea why I cant connect to login server after changing the eqhost? Pretty sure I followed instructions exactly. Prior to eqhost change I was able to login with no servers listed.

Only thing I did differently is install it to an SD card instead of home directly. Not sure why that would matter.

[nanopino]

Originally Posted by Muchew [You must be logged in to view images. Log in or Register.]

Thanks for this. Any idea why I cant connect to login server after changing the eqhost? Pretty sure I followed instructions exactly. Prior to eqhost change I was able to login with no servers listed.

Only thing I did differently is install it to an SD card instead of home directly. Not sure why that would matter.

In desktop mode, try running the script in a separate terminal. Navigate to where the script lives and type ./login_helper.py

Leave it running and start EQ with the eqhost.txt pointed at localhost:5998

The Launch Options might be hiding the error or if you followed the instructions exactly, you will have only 1 minute to login before the script kills itself. Modify the Launch Options to be 5m or more instead of the 1m that was suggested.

[Muchew]

Originally Posted by nanopino [You must be logged in to view images. Log in or Register.]

In desktop mode, try running the script in a separate terminal. Navigate to where the script lives and type ./login_helper.py

Leave it running and start EQ with the eqhost.txt pointed at localhost:5998

The Launch Options might be hiding the error or if you followed the instructions exactly, you will have only 1 minute to login before the script kills itself. Modify the Launch Options to be 5m or more instead of the 1m that was suggested.

Appreciate it. Was able to fix it, but then I accidentally tried to log into a different server. Now I can't connect to the login server for some reason lol. Not clicking the "quick connect" button.

[Joffeyhinton2000]

Originally Posted by Zaela [You must be logged in to view images. Log in or Register.]

I had a thought after my last post. I know that, in my case at least, the server list packets are getting through fine, it's just that the Client chokes on them for whatever reason.

The EQEmu login server does have a lot of servers listed on it, so the server list is somewhat big (~6k), and gets split into several fragments (10 or so) to be sent over the wire. So I thought, why not just filter out all the non-P99 servers before letting the client see them? That way the client only has to deal with a few hundred bytes, in a single packet.

I made a tiny, localhost man-in-the-middle program between the client and the login server to do just that. It is totally working for me, server select is much much more reliable with it running. Some of the code is a bit of a mess right now (lots of last-minute debugging, couldn't test it while I was coding it at work), but you can find it here: https://github.com/Zaela/p99-login-middlemand. Includes a makefile. You can check for yourself, but I can promise that it doesn't try to sniff passwords or anything dumb like that -- all client-to-server packets are simply forwarded and maybe tweaked slightly due to the filtering desychronizing the session somewhat.

Definitely could have some bugs, but I urge you to at least give it a quick try. If it works out well, it shouldn't be too hard to set it up as a daemon and forget about all your server select problems for good.

One thing you will need to do if you want to try it is to update your eqhost.txt to point at the middleman:

[LoginServer]
Host=localhost:5998

It's configured to forward things to the EQEmu login server by default.

How are you supposed to use this, ive been trying to play for days cant get it to work on my pc so i figured ill try my steam deck it will launch but no servers