PS2: Some would say “of course”, but you first need to have configured ufw firewall. PS: Think about using prime-run to speed up display … and an easy way to do so is to simply make a shortcut with ctrl alt s to launch Second Life instantly. Have fun ! And if some are more specialized in the voice part of Linux Manjaro … for now it doesn’t worrk with Phoenix Firestorm and i hadn’t time to look at it. If some know a better way to make it work … i am always open to learn, especially about firewalls as it is far from my domain of expertise. To set correctly the hardware of your graphics card (tno need to spend time reloading things that can stay in the VRAM) To set the viewer cache at the maximum size (your SSD is quicker than your optic fiber internet connection) To set your bandwitdh correctly (it will avoid crashes or make it work quicker) To force your screen fps display at the correct speed if it is not so much modern with automatic features (by the way no need to have your graphic card working at 180fps if your screen is just 60Hz) And then Phoenix Firestorm working on the great refined environement Manjaro KDE and you have access to Second Life, at a quicker speed than Windows 11 by the way.Ī few tricks to technically optimize your Second Life experience = use Firestorm preferences Once those files updated just type sudo ufw reload A ufw6-before-input -m conntrack -ctstate INVALID -j DROP A ufw6-before-input -m conntrack -ctstate INVALID -j ufw6-logging-deny A ufw6-before-input -p tcp -dport 443 -j ACCEPT #TJA Stops ufw.log filling with 443 notices despite port 443 being 'allowed' A ufw6-before-input -p icmpv6 -icmpv6-type echo-reply -j ACCEPT # be marked INVALID, so allow here instead. # 4.4.1 and 4.4.2), but don't have an associated connection and are otherwise A ufw-before-input -m conntrack -ctstate INVALID -j DROPĪnd les # multicast ping replies are part of the ok icmp codes for INPUT (rfc4890, A ufw-before-input -m conntrack -ctstate INVALID -j ufw-logging-deny # drop INVALID packets (logs these in loglevel medium and higher) A ufw-before-input -p tcp -dport 443 -j ACCEPT #TJA Stops ufw.log filling with 443 notices despite port 8080 being 'allowed' A ufw-before-forward -m conntrack -ctstate RELATED,ESTABLISHED -j ACCEPT A ufw-before-output -m conntrack -ctstate RELATED,ESTABLISHED -j ACCEPT A ufw-before-input -m conntrack -ctstate RELATED,ESTABLISHED -j ACCEPT Then searching on the web you will maybe find this link about the different ways ports are managed.Īnd at the end, the solution seems to be to define the parameters for port 443 not as mentionned in the firewall parameters but updating filesīles # quickly process packets for which we already have a connection journalctl | grep -i 'ufw block'Īnd i see that my port 443 is planting a problem. So let’s look at the log to see what is not working fine when activating ufw firewall the normal way and leading to a stuck avatar and an inconstant 3D display. moreover nothing is done to make it simple as you need to do it by yourself. … and there are good chances that Second Life doesnt work as the Linux kernel doesn’t work like Windows etc. You follow the explanations from the Second Life firewalls page As it seems that setting up a firewalll brings many questions, especially while using games or on Linus Tricks, let"s look at one of the oldest Metaverse ancestors : Second life and using UFW to setup the firewall.ĪSUS Notebook TUF 15 / 32 GB RAM / NVIDIA 3070 8GB VRAM / NVME 1 TB
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |