<![CDATA[FedoraForum.org - Servers & Networking]]> https://forums.fedoraforum.org/ Discuss any Fedora server problems and Networking issues such as dhcp, IP numbers, wlan, modems, etc. en-US Thu, 17 Sep 2026 23:00:53 GMT vBulletin 60 https://forums.fedoraforum.org/images/vbmobile/misc/rss.png <![CDATA[FedoraForum.org - Servers & Networking]]> https://forums.fedoraforum.org/ Making it a little easier for guests to connect to your Wifi https://forums.fedoraforum.org/showthread.php?336577-Making-it-a-little-easier-for-guests-to-connect-to-your-Wifi&goto=newpost Fri, 11 Sep 2026 23:43:16 GMT If like me you often have guests at your house who'd like to use the WiFi, and you get tired of pointing them to the fridge for the credentials of the 7 possible networks (I limit guests now to just 5 of them...), today I made a new cheat-sheet to make things easier.

dnf install qrencode

Then create a short bash script with enough lines so there's 1 for every network ID you've got and execute:

qrencode -s 6 -m 1 -o wifi-qrBH52.png 'WIFI:S:BH52;T:WPA;P:Password;H:false;'

Where wifi-qrBH52.png is the output image filename. BH52 is the name of my network and Password is the password of that radio. In my case, all the passwords are the same. Each line will then generate a PGN file of a Wifi QR which when scanned with your device camera, will invoke a dialog asking if you'd like to remember (and connect) to the wifi network defined in the code. And since you can simply remember these (have the device remember) you can scan all 5 in one go and never have to bother with it again.

So in my case, I made a spreadsheet so I could print this out. It has all the credentials both as text and encoded in the QR. It works slick! Import the images and align them with text to identify each. Each command above makes a different filename for a different network.

Also in my case above, security is WPA...

Now I have this printout on the fridge and on the Library door (opposite end of the house) so folks can have wifi at both ends.

Screenshot_20260911_194150.png
Attached Images
]]> Spazzy https://forums.fedoraforum.org/showthread.php?336577-Making-it-a-little-easier-for-guests-to-connect-to-your-Wifi Fedora 44 Sway, Intel Wifi AX200 Wifi Not Working https://forums.fedoraforum.org/showthread.php?336557-Fedora-44-Sway-Intel-Wifi-AX200-Wifi-Not-Working&goto=newpost Fri, 04 Sep 2026 20:40:26 GMT Hello all,

I am trying to enable wifi with network manager but it's not working with the new kernel after updating Fedora.

I've just added secure boot by signing with mokutil (but internet works on the previous kernel)...

nmcli radio wifi returns enabled
nmcli dev wifi list returns nothing
ifconfig doens't show the wifi card (only shows lo)

Finally, lspci shows that the capabilities are marked as accessed denied and it doesn't mention anything regarding drivers/kernel.

I've read through many posts but haven't found a working solution.

Do I need to install drivers (iwlwifi) or something along these lines?

Any advice would be appreciated. ]]> Turbinepilot https://forums.fedoraforum.org/showthread.php?336557-Fedora-44-Sway-Intel-Wifi-AX200-Wifi-Not-Working Preferred method for setting up samba client shares https://forums.fedoraforum.org/showthread.php?336547-Preferred-method-for-setting-up-samba-client-shares&goto=newpost Tue, 01 Sep 2026 13:36:22 GMT For some time I've been looking for where Samba shares are on the filesystem. Only, I'd made one serious wrong assumption and that is that the samba share is connected via samba... Well, in Dolphin it is not unless you explicitly attach to it as such. I really don't recall ever having this problem in the past, but then again I can't say I recall ever having ISO images I wanted to mount remotely, sitting on a linux shared drive.

I had set up several drives on a server system as "Places" in Dolphin. Made the connections by clicking on Network in the left pane, then following the available shares till I got to authentication dialogs, did all that and now the drive is visible in the left pane of Dolphin. Wonderful... But... you can't mount an ISO from there and you can't open an MKV unless you authenticate every single time you access a file. The auth I could live with, not being able to mount an iso not so much. The solution was to copy those files temporarily to the system I wanted to view them on and then they could be viewed locally. Too inconvenient by a long shot.

My web searches for where the samba shares are mounted yielded vastly different paths, all of which led me to nothing. The only system that even remotely replicated those paths was the system that has the drives being shared. Obviously I don't need paths there. Last night I came across info saying to mount these using sudo mount -t cifs bla bla bla, so I gave that a shot. Had to create a /mnt/mountpoint for every drive, and once I had a location to mount on, pow, everything works. Now I can go to Konsole and cd /mnt/mounteddrive and see it in the file system. However, searching more on the topic I found mention that this isn't a recommended way to attach because you can have all sorts of problems if the share becomes unavailable, server goes down, whatever. I'm not sure I should worry about such things, but it also mentioned not to put these mounts in the fstab because that's another can of worms.

Now, as soon as I executed the mount in Konsole, the share appeared in Dolphin as if I'd done an "add to places"). So now I had 2 of each share and so I deleted the ones created by Dolphin. Access in Dolphin appears unchanged but now all the files are accessible.

By what method does Dolphin attach to shares? Why would it not attach to a samba share as smb:// ? Clearly it's not using samba for the connection or I'd have a shared folder under ~/username/1000/samba/.... (I didn't realize that earlier but now that I know it's not using samba, those folders not existing makes sense).

My "server" isn't always on, so these shares are not available unless I turn it on. That never caused Dolphin any headaches unless of course I tried to attach to them and then it just failed as expected, no big deal. I made a script to connect all these shares and at least so far, it appears to work without problems. Since I'm virtually never writing to these drives, I don't believe connections being cut will cause any issues, but I'm open to opinions contrary to that.

Lastly, I'm not in front of the system now, but another question is why would Dolphin specifically take me down the branches of the tree from Network->SMB Shares->SMB Shared System->SMB Shared drive, and then not connect using Samba? After all that did it make an NFS connection or something else? Basically, Dolphin makes a network connecting that only Dolphin can see... To me this skirts the borders of being called a bug... I realize it's just their chosen implementation, but at a minimum it should come with a warning when attaching that "Yo, this ain't the type of conenction/share you think it is..."

Does anyone else do this sort of thing where you require command line access to the shared folders? If so, by what method do you make your client connections? ]]> Spazzy https://forums.fedoraforum.org/showthread.php?336547-Preferred-method-for-setting-up-samba-client-shares