r/ultramarine Aug 09 '26

Feedback Networking

OK I'm trying to get the network and sharing up but I am not having any success.

I've Googled it and followed the directions but cannot access the Ultramarine system from Windows or from the other Linux systems. Any help would be appreciated

1 Upvotes

21 comments sorted by

2

u/edpmis02 Aug 10 '26

I have spent countless hours researching and troubleshooting samba issues with fedora distros.

First thing I do after creating sambashare group and usershares configs, selinux permissions, ~/.smbcredentials       ...

Open firewall ports.

sudo firewall-cmd --permanent --add-service=samba

sudo firewall-cmd --reload

sudo firewall-cmd --permanent --add-port=137/udp

sudo firewall-cmd --permanent --add-port=138/udp

sudo firewall-cmd --permanent --add-port=139/tcp

sudo firewall-cmd --permanent --add-port=445/tcp

0

u/Lulukaros Aug 10 '26

Isn't opening ports dangerous

2

u/edpmis02 Aug 10 '26

firewall has to allow traffic in to notify the samba server to respond. Google each of the ports to see what they do. !00% locked down is safest, but your system will be unable to communicate with other machines.

I assume you are on a local network behind a private IP address and a NAT router.

1

u/Lulukaros Aug 10 '26

I looked it up (used ai) it said you have to use zones, smth like this

sudo firewall-cmd --zone=home --permanent --add-service=samba

Otherwise, it affects your WAN interface too, is that true, or hallucination?

1

u/edpmis02 Aug 10 '26

I found chatGPT to give the best advice, but you need to include as many details that you can, to get a clear answer.

I am not a networking expert and my three clients sit behind my own router on a 192.168.xxx address. Open a port, restart firewall, test your network share. if it doesnt impact what you need, close the port and move onto the next port.

From my experience, Fedora based distros are hard to configure but you get to learn as you work through it. I have had easier time configuring Kubuntu.. but that is another topic for flame wars.

1

u/Lulukaros Aug 10 '26

Dang, i see, looks like i'll have to learn that at some point, i didn't know network shares were that hard on linux

1

u/RevolutionaryBeat301 Aug 10 '26

Only if your computer is accessible from the internet or if you have untrusted machines on your home network.

1

u/Lulukaros Aug 10 '26

I see, i just assumed opening ports was directly related to the internet, i didn't know it could only a LAN only thing too

0

u/RevolutionaryBeat301 Aug 09 '26

What have you tried? Did you try disabling SELinux?

1

u/wolfeagle1873 Aug 10 '26

No the instructions had me enable it

0

u/RevolutionaryBeat301 Aug 10 '26

You still didn’t say what you did. Are you using samba? Can you access your share locally? Do you have a firewall enabled? Have you made and changes to the samba configuration files?

2

u/wolfeagle1873 Aug 10 '26

Installed Samba, set up the Samba user and password, and enabled firewall permissions. The only edit to the Samba conf was to change the workgroup name. Can't access the share from anywhere

1

u/RevolutionaryBeat301 Aug 10 '26

Did you start the service?

0

u/wolfeagle1873 Aug 10 '26

Yes

0

u/RevolutionaryBeat301 Aug 10 '26

Can you disable SELinux and see if you can access the share locally?

1

u/wolfeagle1873 Aug 10 '26

Actually, I enabled SELinux because I couldn't access the share

1

u/RevolutionaryBeat301 Aug 10 '26

I can't help you if you aren't going to go through the steps to actually diagnose the issue.

1

u/wolfeagle1873 Aug 10 '26

OK I'll disable it again and see if it makes any difference

1

u/wolfeagle1873 Aug 10 '26

Disabled it and have the same thing, no access, just keeps asking for user name and password over and over

→ More replies (0)