My journey to successfully game under Linux (and overcome Microsoft's Stranglehold)

[Indus]

can you connect to the shares from a different linux system?

I had a thought.. you can normally access your own windows computer on network through the network.. so I thought I'd try it in linux with smb protocal.

Yep just like windows I managed to see the folder there but can't access it.

It did ask me for username and pw and then just says loading cancelled



I'm beginning to lean towards.. firewall is not the problem since I can ping and see the folder. Somehow I have a problem with access.. so permissions somewhere are the hiccup most likely.

 

[Indus]

There's obviously a lot of moving parts here. It's easy to get lost in the weeds of unfamiliarity.

As a random starter question, what does chmod 775 do?

At this point, the first troubleshooting step I would do is to use smbclient to check that the file share is actually "working," over the loopback interface.

Linux smbclient Command Tutorial – LinuxTect

linuxtect.com

Once that is successful, I would continue to troubleshooting over the network. As suggested, I would start by stopping the Fedora firewall service.



Can you explain to us why you would use the -R option?

Did you say that this is an exFAT filesystem? FAT doesn't support Linux permissions on a per-file basis if I recall correctly. That's why the operation is not permitted.
In other words, it's the initial mount options (from fstab) that are meaningful.

Good find on the SELinux context issue; that might be the issue. At a glance, this is a good write-up:

Setting Up Samba and Configure FirewallD and SELinux to Allow File Sharing on Linux/Windows Clients - Part 6

In this article, we will go through the setting up Samba server and configure Firewalld and SELinux to allow file sharing on Linux/Windows clients, respectively.

www.tecmint.com

That's just the "homes" share, probably best to disable it if it's not needed. (Although it could be helpful to get this share working first.)

Yes my Ultramarine drive is btfrs. The rest are all exfat.

And I'm trying to share a folder located on my exfat drive.

I can see it but not access it.

I had trouble with permissions but I managed to fix it by correctly mounting the drive and setting them all to chmod 777 by default in fstab file..

 

[igor_kavinski]

I can see it but not access it.

https://viterbiit.usc.edu/wp-content/uploads/2020/04/How-to-Use-Net-Use-Command.pdf

Try using that command.

Generally on Windows, I've seen actual administrators fixing the permissions issue by fooling Windows.

Here's how:

Remote machine has user ABC with password 123 and shared folder is DEF.

Windows machine unable to access shared folder DEF even though it is visible.

Administrator creates new user on Windows machine with name ABC AND password 123.

Suddenly, like magic, the folder is accessible.

 

[WelshBloke]

Yes but the first time you install it or reinstall it after deleting the pfx folders.. don't you get the install for the EA stuff?

What do you do with it?

I just installed it. Didnt delete any folders (I've not done that for any games!). The EA thing did install itself but I've not had to have any interaction with it.

 

[Indus]

I just installed it. Didnt delete any folders (I've not done that for any games!). The EA thing did install itself but I've not had to have any interaction with it.

Not so in my case.. it comes up and stays put and specifically asks you to log into EA.

 

[Indus]

Major major problems after an nvidia driver update which came automatically since we were given a new kerneup date.. did that and all of my steam games crash upon opening.

Like nothing opens.. not even the oldest games and everything seems super choppy. Don't understand this.

Edit: seems I fixed it.. for some reason the update reverted the system to built in integrated graphics on the 12600k but not only that.. the LOWEST possible setting..

I don't even know how I'm using integrated graphics while being connected on monitor through the GTX 1080.

Also I don't understand how it's at 16MB VRAM, like you have to go out of your way to do that manually.. it generally defaults to 128 MB of memory but I was at 16 and everything was choppy.. even loading a browser.

Seems like a good idea to put a pause on automatic updates with rolling distros and just install what you need rather than blindingly trusting everything they roll out.

 

[Indus]

https://viterbiit.usc.edu/wp-content/uploads/2020/04/How-to-Use-Net-Use-Command.pdf

Try using that command.

Generally on Windows, I've seen actual administrators fixing the permissions issue by fooling Windows.

Here's how:

Remote machine has user ABC with password 123 and shared folder is DEF.

Windows machine unable to access shared folder DEF even though it is visible.

Administrator creates new user on Windows machine with name ABC AND password 123.

Suddenly, like magic, the folder is accessible.

Tried this.. still no go.

I even thought it was SMB2 not opened in windows.. and added it via regedit, but no go on that either.

 

[igor_kavinski]

Tried this.. still no go.

Access the shared folder in Windows. When you get the access denied message, immediately open Event Viewer and see if it says anything interesting about why the access was denied. There may be a clue there.

 

[Indus]

That's interesting.. a bunch of code that I don't understand but it lists my username as @live.com

Maybe that user is not authorized in samba? or I need to make a user called user@live.com??

 

[WelshBloke]

Are you signing into Windows with a Microsoft account?

 

[Indus]

Are you signing into Windows with a Microsoft account?

No.. local I think.. but I don't remember..

Either way just made a new local user

 

[igor_kavinski]

Either way just made a new local user

How many accounts do you recognize when you use the CMD command "net user" ?

Then type whoami in CMD and see if it matches the account you think you are logged in with.

 

[Indus]

Have 2 users on windows.. current one is adminstrator..

And I have a new default user

 

[Indus]

Ok stupid question..

I was going over some other things to troubleshoot this:

Google Search

Google Search

I came across this line:

• Confirm that both the Linux and Windows machines are on the same network and that IPv4 is supported.
  

Well.. what do you think? is it working?? Because even though I see my ip add.. 192.168.1.235 I don't see a IPv4

 

[igor_kavinski]

If ping to the IP is working then IPv4 is also enabled (inet refers to that while inet6 is IPv6).

 

[Indus]

If ping to the IP is working then IPv4 is also enabled (inet refers to that while inet6 is IPv6).

Gosh this is stumping all of us badly.

Not Microsoft.. check
Stability.. check
Gaming.. check except for 1
Software.. check
Everything neat and tidy.. check
Localsend.. check
Filesharing via network to windows computers.. Not yet!

Close to perfection when that's solved.

Infact getting tempted to video card upgrade and I'm very disciplined usually but this has that feel of a new computer for me.

 

[igor_kavinski]

Filesharing via network to windows computers.. Not yet!

Try: https://www.socallinuxexpo.org/scale12x-supporting/default/files/presentations/Samba for Dummies.pdf

Maybe there's some critical step or conf file entry missing.

In fact, I think first you should try to access a Windows share in Linux, if you haven't already done so.

 

[manly]

And I'm trying to share a folder located on my exfat drive.

I can see it but not access it.

I had trouble with permissions but I managed to fix it by correctly mounting the drive and setting them all to chmod 777 by default in fstab file..

Right, my point is that you cannot apply Linux permissions to *FAT filesystems, which is why you saw the "Operation not permitted" errors. (But that isn't the current problem at hand.)

Generally speaking, chmod 777 is a no-no and I'm not sure that you fixed something.

Unless you're just using Steam Deck, using Linux means you'll need to "learn how to fish." Oftentimes, the answers are somewhere on the web, and DuckDuckGo can help point you in the right direction.

For example, I think there's actually a good chance that the SELinux context issue you discovered a couple days ago is the reason you can see the share, but not the underlying files. SELinux is like a more detailed form of "permissions" layered on top of traditional Unix permissions. Now here's the thing, a lot of old timers like myself haven't really learned SELinux. Part of the reason is that Debian-based distros don't use it.* You don't have to become an expert at SELinux, but it's supposed to enhance the security model (mainly on servers). Go back and review the chcon command, and think about how it can apply to this situation. Yesterday I linked to a Samba guide from a decade ago, that also touches upon FirewallD and SELinux.** It's quite possible that the wrong context prevents Samba from serving up files.

Finally, don't forget to have some system of note-taking where you document useful solutions and lessons learned, for future reference.

* In the beginning, SELinux only made it harder to run popular servers. It was common practice just to disable it on RHEL 6 so that things would work as they always had. Debian uses AppArmor, which didn't seem to have these kinds of issues. IIRC modern Android uses SELinux, but users will never see it.

** If you're not setting up any other network services, this might be the only thing you need to know about SELinux.

 

[Indus]

Right, my point is that you cannot apply Linux permissions to *FAT filesystems, which is why you saw the "Operation not permitted" errors. (But that isn't the current problem at hand.)

Generally speaking, chmod 777 is a no-no and I'm not sure that you fixed something.

Unless you're just using Steam Deck, using Linux means you'll need to "learn how to fish." Oftentimes, the answers are somewhere on the web, and DuckDuckGo can help point you in the right direction.

For example, I think there's actually a good chance that the SELinux context issue you discovered a couple days ago is the reason you can see the share, but not the underlying files. SELinux is like a more detailed form of "permissions" layered on top of traditional Unix permissions. Now here's the thing, a lot of old timers like myself haven't really learned SELinux. Part of the reason is that Debian-based distros don't use it.* You don't have to become an expert at SELinux, but it's supposed to enhance the security model (mainly on servers). Go back and review the chcon command, and think about how it can apply to this situation. Yesterday I linked to a Samba guide from a decade ago, that also touches upon FirewallD and SELinux.** It's quite possible that the wrong context prevents Samba from serving up files.

Finally, don't forget to have some system of note-taking where you document useful solutions and lessons learned, for future reference.

* In the beginning, SELinux only made it harder to run popular servers. It was common practice just to disable it on RHEL 6 so that things would work as they always had. Debian uses AppArmor, which didn't seem to have these kinds of issues. IIRC modern Android uses SELinux, but users will never see it.

** If you're not setting up any other network services, this might be the only thing you need to know about SELinux.

I'm gonna investigate that and see if it's the settings in there.

 

[Indus]

I fount out something the scary way and it should scare you..

If you like using a VPN.. do not trust the linux version of the app.. it's not good enough. It leaks DNS and gives away your IP.. and you can be tracked..

ipleak.net is your friend to make sure.. especially if you use p2p share services.

At least on that front Windows version of the app is rock solid.. so good job dual booting whoever chooses to do it.

 

[Indus]

I fount out something the scary way and it should scare you..

If you like using a VPN.. do not trust the linux version of the app.. it's not good enough. It leaks DNS and gives away your IP.. and you can be tracked..

ipleak.net is your friend to make sure.. especially if you use p2p share services.

At least on that front Windows version of the app is rock solid.. so good job dual booting whoever chooses to do it.

Okay I haven't fixed the server thing yet since the IP leak thing took priority.. and I talked with surfshark's customer support. Instead of yelling at them and wanting a refund.. I wanted to ask for a fix first.

They suggested disabling ipv6. And gave me this writeup:



To solve your issue, let's try disabling the IPv6 on your Linux device. All you have to do is follow these steps.

First, please type this to the Terminal:
sudo nano /etc/default/grub

A text editor should open in the Terminal, find this line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

Add "ipv6.disable=1" in the middle, so it would look like this:
GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1 quiet splash"

Press Ctrl + X to save. Then Y. (don't change the file name, press Enter).

Once the Terminal opens again, update the grub with this command:
sudo update-grub

Restart the device and IPv6 should be disabled.




So I wanted to ask you all.. does this make sense or it creates a whole lot of other problems down the line??

What do you guys think?

 

[manly]

Okay I haven't fixed the server thing yet since the IP leak thing took priority.. and I talked with surfshark's customer support. Instead of yelling at them and wanting a refund.. I wanted to ask for a fix first.

They suggested disabling ipv6. And gave me this writeup:



To solve your issue, let's try disabling the IPv6 on your Linux device. All you have to do is follow these steps.

First, please type this to the Terminal:
sudo nano /etc/default/grub

A text editor should open in the Terminal, find this line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

Add "ipv6.disable=1" in the middle, so it would look like this:
GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1 quiet splash"

Press Ctrl + X to save. Then Y. (don't change the file name, press Enter).

Once the Terminal opens again, update the grub with this command:
sudo update-grub

Restart the device and IPv6 should be disabled.




So I wanted to ask you all.. does this make sense or it creates a whole lot of other problems down the line??

What do you guys think?

Honestly, I think it neither "makes sense" or will cause other problems. IPv6 was supposed to save the world, but you're probably not using it.

Although I believe update-grub is a script on Debian and its derivatives. I thought that Red Hat uses grub2-mkconfig ...

It's unclear why fixing their VPN requires disabling IPv6. 🤷‍♂️

 

[igor_kavinski]

It's unclear why fixing their VPN requires disabling IPv6. 🤷‍♂️

Yup. Seems like a moronic techsupport reply.

 

[Indus]

I may not be the smartest person on the planet but thankfully I'm not naively stupid.

Glad I thought their suggestion sounded pretty crazy and I'm glad I consulted you guys here. Thank you for saving me from a ton of issues.

I still think it's the software.. if they can write a software for windows that doesn't leak and has a kill switch.. they can do the same for linux but nope.. no kill switch, no bypass.. just an on/ off and location!

 

[igor_kavinski]

I still think it's the software.. if they can write a software for windows that doesn't leak and has a kill switch.. they can do the same for linux but nope.. no kill switch, no bypass.. just an on/ off and location!

Probably outsourced it to someone on the cheap.

I've done a fair bit of development (mostly for my own needs and my company's needs) and transitioning from Windows GUI development to Linux GUI development isn't straightforward unless you use a cross platform GUI library. And then there's the low level system code that will be wildly different between Windows and Linux. No wonder they don't want to bother.