You could just setup a separate namepace with IPv6 disabled and move the process into it. I'd be more detailed, but this comment is one eyed and very sleepy, let us know how you go.
this post was submitted on 26 Mar 2024
31 points (89.7% liked)
Linux
48081 readers
780 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
Seconding this. Take a look at the unshare program and user namespaces.
You can install ufw and a frontend for it that lets you block specific processes. https://wiki.archlinux.org/title/Uncomplicated_Firewall#GUI_frontends It seems KDE already comes with a frontend in the system settings, and there's gufw for gnome/gtk.
with iptables you could block the port used by this app, but maybe it would not fix your problem
ip6tables
I feel selinux should be able to do something clever here, like it can manage/block port access.
Off the top of my head, the only way I can think of is to install steam using docker, and install SF6 on dockerized steam.
Then you've converted the problem to either configuring docker to use ipv4 internally or setting up the container to ignore ipv6, both of which are doable.
There's a good chance it'll be perfectly playable but without trying it out or doing more research than I've invested here, it's not a guarantee.
Docker doesn’t use ipv6 by default.
Nobody out there seems to know how to do IPv6 properly. Lots of issues just went away when I disabled it on my “end user” subnets.
Harsh but true.