[F@H] [LAR_SYSTEMS] Incorrect CPU detection when using SSH tunneling

[KiralyCraft]

Hello, I have this server in a remote location that I do F@H on. Recently I decided to install the LAR_SYSTEMS extension on my local machine, and I forwarded the server's 7396 port to localhost's 7396 via SSH tunneling (so that the extension would pick it up). Unfortunately, it looks like because the FAHClient does not report the CPU model directly on the web, the extension is now picking my localhost's CPU model and essentially wrecking havoc on the CPU database for this model. I've heard here is the best way to reach the devs out, so here goes!

[RollinLower]

@LAR_Systems what say ye?

[cbigfoot]

@KiralyCraft I would probably disable his tool till @LAR_Systemsgets it looked at. but my bet it has a limitation to the fact that it pulls the data from the local computer for that page as that page is meant to be run locally not remotely. i seem to recall that being discussed here: 

at somepoint or another 

[LAR_Systems]

On 11/28/2021 at 8:08 AM, cbigfoot said:

@KiralyCraft I would probably disable his tool till @LAR_Systemsgets it looked at. but my bet it has a limitation to the fact that it pulls the data from the local computer for that page as that page is meant to be run locally not remotely. i seem to recall that being discussed here: 

at somepoint or another 

That is correct, all the CPU detection is on the local browser, no way around that as F@H APIs in the service do not provide the CPU information, only the GPUs.

[rkv_2401]

On 11/21/2021 at 4:48 PM, KiralyCraft said:

Hello, I have this server in a remote location that I do F@H on. Recently I decided to install the LAR_SYSTEMS extension on my local machine, and I forwarded the server's 7396 port to localhost's 7396 via SSH tunneling (so that the extension would pick it up). Unfortunately, it looks like because the FAHClient does not report the CPU model directly on the web, the extension is now picking my localhost's CPU model and essentially wrecking havoc on the CPU database for this model. I've heard here is the best way to reach the devs out, so here goes!

Just out of curiosity, is this the mystical i3-5005U on the database?