Yes, in_addr is a standard structure containing a 4 byte integer representing an IPv4 IP address.
https://learn.microsoft.com/en-us/windows/win32/api/inaddr/ns-inaddr-in_addr

It can be used to prevent some players connecting to your host. They can only connect using IPv4 anyway so IPv6 is not needed.

I don't think this new packet will be useful for many people. I implemented it when I changed the way IP bans work as part of the recent updates to make hosts more resilient to attacks. You can set IP bans using the hosting pages, and that system now uses this new InSim packet to allow LFS to reject the connection, instead of setting firewall rules on the server.

I suggest that if you do want to use this packet to set IP bans, you should not use the IP ban system on the website. Choose one or the other.

No, I'm not interested in speculating about future versions at this time.

If you want to know about the future version, check out this page: https://www.lfs.net/report-may2021-so

See at the bottom, there are a lot of links. That info should keep you going for a while. If you would like to discuss it, feel free to start a new thread on the forum, but don't talk about in on this thread, because it is off topic.

Yes, important updates for various technical reasons, but not exciting.

Quote from tankslacno :

Thanks! However, it seems like in Host Control Panel, you can't change version of your LFS host to 0.7F.

You can now select host version 0.7F.

Quote from Justas7771 :

no no, LFS is the most important so it always goes straight into C:\

It's quite puzzling. Do you have a data\misc folder in your new install? Is LFS successfully writing any other files, such as cfg.txt (should save a new copy when you exit LFS).

Sometimes, strange behaviour is related to anti virus software.

I tested a fresh install before release and it worked fine.

Maybe it's the location where you tried to install it? For example, I think there were problems when people tried to install into locations like "Program Files" so we recommend a plain folder on the hard drive like C:\LFS or maybe C:\GAMES\LFS_7F (if you want a separate installation).

Something you are fully in control of, not within the Windows directory structure. LFS is kind of old style, and isn't designed to fit in with the Windows way of doing things, with Program files in one place and user data in another (although I can understand there are reasons to do that).

I will update the hosting system later today. For now you can continue to use 0.7E15 hosts.

The editor patch link is on the Mods Downloads (etc) thread: Mods: Downloads / Web Pages / Videos / Documents

Thanks for all your help with the testing.

The official version is now available: https://www.lfs.net/forum/thread/108684

Hello Racers,

Introducing a variety of updates for Live for Speed and the LFS Editor!

Live for Speed 0.7F:

This year there is an increased emphasis on getting mods approved, so we have improved support for this process. On the mods screen, in addition to some new filters, you can spot approved mods more easily and there is a reminder in the garage if you use a mod but have not yet given it a rating.

Controller support now has increased input resolution and a better range adjustment system. There are some graphical optimisations and multiplayer improvements.

Please read the full list of changes: LFS 0.7F changelog page


LFS Editor 0.7F:

In older versions it could be tricky to produce realistic wheel rims. In reality wheel rims must follow standards to allow the use of tyres from different manufacturers. The updated editor helps you produce rims with realistic dimensions. Detailed rim guides are displayed in the rim editor and the spoke editor.

There are also various updates in the modeller, including a 3D line guide, a function to help align points and support for merging a subobject into another subobject.

Please read the full list of changes: LFS Editor 0.7F changelog page



Four ways to get version 0.7F :

1) AUTO UPDATER - If you already have version 0.5V or later :

- Click on "Multiplayer" then "List of Hosts" in LFS and choose a download mirror.

2) MANUAL PATCH 1 (1.8 MB) - If you already have version 0.7E or later :

- Click HERE and save the patch installer.
- You can run the patch installer from its download location or from your LFS folder.

3) MANUAL PATCH 2 (35 MB) - If you already have version 0.6R or later :

- Click HERE and save the patch installer.
- You can run the patch installer from its download location or from your LFS folder.
4) FULL VERSION (522 MB) - If you are new to LFS or making a fresh installation.

- Click HERE to visit the download page and get the full version installer.


- LFS Developers

Quote from the_angry_angel :

Forgive me if I'm teaching you things you already know...

Thank you, any tips might help as my Linux experience is still low.

In this case I did my own implementation which I think was the easiest way forward with all the logs still being produced in the same folder. No code changed at that point. The new code moves them all into one of the 7 new day folders each time a new day comes around. It's naturally limited to one week of logs.

A first version of the generated log links system is available now on the activity page.

Quote from RealistAdam :

This is very nice. But there are many spelling errors in the text file. They...

That is the LFS code page identifiers as seen in the plain text log file.

I've added an option to see an interpreted version of the file in a browser tab.

Add to the end of the line &html=1

E.g. https://www.lfs.net/hosting/admin/12345/activity?log=Sunday&html=1

I hope to add the links to the activity page today.


About the Join link, that change was intentional. Nearly every time I tried to edit one of my hosts, I clicked the name. Instead of editing the host, my browser tried to start LFS to join the host. This became irritating. It seemed to me the interface wasn't intuitive, so I changed it.

I am in the middle of working on it.

It now saves a week of logs, plus the current day, but that has only started yesterday (Saturday 20 July).

I haven't made the interface for it yet but you can already access your host's logs like this:

Visit your host's "activity" page, so you see a URL like this: https://www.lfs.net/hosting/admin/12345/activity

Then you can add ?log=Saturday to the end of that line to see yesterday's log.

Or add ?log=Today to get today's log.

Moved thread to correct forum section.

Escape then Free View (or SHIFT+U)

You may need to press SPACE or SHIFT+F to see the buttons and you may need to click "edit"

All I can say at this point is that the internet is quite strange at times and I do know of other cases where, temporarily, a user in one location has a different experience connecting to different servers of ours despite them being together on a single rack. And at the same time, every other LFS user reports no issues at all.

Sometimes internet connectivity is extremely strange and is not really possible to understand without some in depth knowledge of what happens at every step between one computer and another.

Sometimes issues are resolved in minutes, sometimes days, they may be a one off or they may be recurrent.

Basically there are sometimes unexplained, full or partial, blockages between one point on the internet and another, and we are unlikely to ever understand why that is the case.

I restarted the Turkish server this morning as our provider made some changes recently to improve the connection again and I wanted the server to have a fresh start.

Just reporting this in case you wondered why it was offline for a few minutes.

I don't imagine that I can help with this but usually such issues are on the internet, somewhere between your computer and our servers.

You could try a traceroute for more information than ping.

What type of internet connection do you have? I believe that these days most problems related to UDP packets are something to do with the use of a mobile phone as a wifi hotspot.

Hello,
Is this reproducible? I mean, can you make another replay and the same thing happens?
Otherwise, it could possibly be related to something done before or after you originally created the replay.
In any case, it would be good to know. Usually if we know how to reproduce it, we can work out if it's a bug or not.
Different LFS versions are not usually supposed to cause an OOS. Different versions of a mod are not expected to cause an OOS, unless you manually renamed them at some point between recording and playback.
So... basically we are short of information at this point.

One possible explanation is if https is allowed but http is blocked.

But why that would be, I don't know. Router? Firewall? Antivirus? ISP?

Maybe you could try accessing some site that you can visit directly by http - to see if the same issue can be reproduced in a browser, unrelated to LFS in any way.

EDIT:
Can you connect to these http-only sites in your browser?
http://httpforever.com/
http://example.com/

Last edited by Scawen, Wed 3 Jul 2024, 13:59.

Yes, it's safe to use and protects websites against DDoS attacks.

If you are interested in the 100 second timeout issue, feel free to read.
https://stackoverflow.com/questions/38536167/is-it-possible-to-increase-cloudflare-time-out

Well, we are a bit stuck at the moment as it's no longer possible to switch off Cloudflare. Constant attacks that bring down the website entirely must be avoided. This is the modern world, some people love to break things and we have to be protected.

Victor doesn't want to work much on LFS at the moment and I really have not a clue how to convert to a new upload system that can avoid the Cloudflare upload time limit. I've spent the first half of this year mostly working on the website, learning how to maintain a large system created by someone else. Development on LFS.exe itself ground to a halt due to the current situation.

Luckily Victor is still there to deal with urgent things I can't deal with. But sorry to say he didn't seem interested when I asked him about ways to get around the Cloudflare upload timeout issue.

I guess I could try to press him on it. But quite honestly I try to avoid bugging him if possible. I'm just starting to have a bit of time to develop LFS. When I looked into it, the special upload thing was way beyond my website capabilities.

There is an issue with long uploads through Cloudflare that is not simple to fix. A possible solution is to reduce the size of the upload and there is an editor option for that.

You can read about here: https://www.lfs.net/forum/post/2090164#post2090164

Hello Hosters,

As some of you may know, I've been looking around in the hosting system a lot recently and have done some fixes and updates that were necessary as some things were going wrong. It's a big system that Victor created but as he has a separate full time job, he prefers to be less involved with Live for Speed these days. He's still there to help but a lot of the website and hosting maintenance must now be done by me.

One thing I noticed is that the host log files just keep on growing endlessly but I don't think this is a good idea. For example, the biggest one is 15 GB in size which I think is just too big for a file that no-one ever looks at. Six other hosts also have a log file over 1 GB.

This is not an urgent problem but I think it should be fixed before too long. I'm wondering how it should really be done.

A few questions I am wondering about.

Do you even have access to these log files? I know you can see a few pages in the 'Virtual console' window - is that it?
What should you really be able to see, or what would you like to see?
I'm wondering if there could be some practical way of preventing the endless growth but provide what is needed. For example, maybe you only really need a few days' worth of log to be visible?

Just brainstorming now, but how about if each day a new log would be started, and only keep the logs from a few days? Maybe there's a normal way to do this kind of thing, I don't know so that's why I'm asking. Just try to keep it simple and practical please.

No, there is no maintenance work today.

Yesterday there were DDoS attacks. I can't see evidence of that at the time you restarted your host today.

But "servers are down" is not a good description. I do not know what symptoms you experienced.

I think I may know the reason and I have made a change. Please let us know if you can connect now.