-
Search Results
-
PPC
Recently I began using network shares, and I learned how hard it is to create one… I searched for GUI’s to do that, and the first one I found was actually more complex than sucefully following LearnLinuxTV (youtube channel) tutorial on the subject…
And then I discovered system-config-samba – it’s a simple and useful GUI, perfecly localized to boot.Mini How to create a shared samba folder:
1- install (samba and it’s dependencies and then) system-config-samba
2- antiX Menu > Preferences > Samba
3- Select the folder you want to share; choose a name for the shared folder (optional, if you don’t choose a name, by default it’s the same as the real folder); choose write and visibility permissions (with a simple tick); in second tab select who can access the share (just check the allow access to everyone, if you don’t want to use a password, for example) and it’s done! Yeah… it’s that simple- no need to edit config files…My antiX 21 laptop is on vacation :-), but my antiX 19 computers run just fine the mx package I got here:
Is it possible to add it to the antiX repo (it’s not on antiX’s 19, and I could not test in antiX’s 21)
P.
olsztyn
@olsztyn – thanks for the “field test”… The thread I pointed to explains how to allow smb v.1, but it points to the fact that that version is no longer supported? I don’t really understand much about samba shares, but… If using v.1 is really discouraged, maybe I should not try to implement it in the script… since you do use it, what are your thoughts on the subject?
Just to clarify:
SMB 1.0 is an older version and by nowadays standards it has a security issue on SMB server. But it is still widely used as many users have SMB 1.0 NAS servers. Most of my SMB servers are SMB 2.0, which are most common, but I also have two SMB 1.0 NAS servers. But it is not about me, as many other users, particular individual home networks are likely to have SMB 1.0 NAS, such as one drive network drives, such as Seagate, Netgear, WesternDigital… Many of these are SMB 1.0, particularly older ones. However warranty usually expired, so manufacturers do not care to provide updated firmware…Every system, even Windows 10 allows connecting SMB 1.0, just has to be enabled explicitly. As much as I know, on Linux it requires SMB 1.0 version to be specified in configuration, such as in Connectshares. SamK had very detailed explanation that such parameter needs to be specified.
For me it does not matter too much if your utility supports SMB 1.0, but for completeness it would be good to have this option in such function.
If SamK, the creator of Connectshares is still in this forum (I have not seen his posts recently) perhaps he would have some additional suggestions…
Thanks again…- This reply was modified 1 year, 2 months ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersI took a look a cursory look at the smb1 problem at lunch time… According to this: https://askubuntu.com/questions/1265923/configuring-20-04-samba-for-smbv1 , “since Samba 4.11 it no longer allows support for NT1 (SMB1)”. The samba version I have installed is “4.9.5+dfsg-5+deb10u3″…
This web page: https://www.cyberciti.biz/faq/how-to-configure-samba-to-use-smbv2-and-disable-smbv1-on-linux-or-unix/ seems to point out that using smb v.1 is insecure…@olsztyn – thanks for the “field test”… The thread I pointed to explains how to allow smb v.1, but it points to the fact that that version is no longer supported? I don’t really understand much about samba shares, but… If using v.1 is really discouraged, maybe I should not try to implement it in the script… since you do use it, what are your thoughts on the subject?
About the “default” user name – I took the care to make the “user” field, by default, be the same as the OS user name, just well… because that’s my particular case, and it also shows, clearly what’s supposed to be on that field. When you begin typing, you instantly overwrite that field’s content, there’s even no need to click that field… But you can adapt the script, if you intend to use it (and not just test it)- Open the script and, in the line that starts with “entry=”, probably is around line 86, delete this variable “$USER”, and save the script. From now on, by default, the user field will show up empty by default…P.
- This reply was modified 1 year, 2 months ago by PPC.
OK, last night I polished the script. It’s available, under a new name, here: https://gitlab.com/antix-contribs/ft10-transformation/-/raw/main/my_network_neighborwood_0.9beta.sh
Changes:
-The script now requires this packages to be installed: smbclient, nmap
– new GUI window to enter credentials (if the shared folder does not require a password, just close the window asking for credentials and the share will be instantly mounted)To do:
-Add check for dependencies and offer to install them, if needed
-Add support for Smb v1 (eventually)The script now does exactly what I though every OS needs: it checks, in a fast way, the network for any existing (samba) shared folders and offers to mount them, all in GUI format (but, if you launch the script in the terminal, you’ll get lots of info about what the script is doing).
There is almost no need for localization- the only text is in the error message windows, if no network or no network shares are detected… I can even replace that text with some nice icons if I find any…Edit:
I forgot to say this – I think connectshares, despite being a great automatization tool lacks something my script has- a way to find out existing (even not mounted) shared folders. You can run my script via the terminal and get the correct ip and share name to add to the connectshares config file – this way activating connectshares does automatically mount the shares… My script does not aim to automate the mounting process of shared folder, only to be an easy GUI way to discover and mount them- it can be tedious to keep entering the user name (the script assumes it’s the same as your session’s user, but you can edit that field), and password… Future versions can have a config file, that store your credentials for each share and automatically insert them on the corresponding user/password fields, so you only need to click “ok” or press enter on the log in window…- but I dislike that option because it would store your password on a plaint text file (just like connectshares, I guess), and if you have a password to access your network shares, it probably is because you don’t want anyone snooping around… right? So, I stand by my initial decision: open shared folder (without password) for stuff I don’t mind sharing, and password protected folders for sensitive stuff (and I have to always enter my password to access them)P.
- This reply was modified 1 year, 2 months ago by PPC.
The current beta version of the script is here: https://gitlab.com/antix-contribs/ft10-transformation/-/raw/main/connect_to_existing_network_shares56.sh
Changes:
-Now the script only external dependency (not included by default in antiX full) is smbclient
-The network shares detection is slower (it ranges from 5 – 50 seconds on my tests), but, as far as I can tell, it’s now flawless, my initial attempt failed to detect shares sometimes…
-because the process now may take more time, I added a pulsating window, showing that the script is working…
-The script looks a bit more polished- with better looking windows, and it even checks if the computer is connected to a network, before starting.@olsztyn -Thanks for the input: the script now has much less dependencies (it no longer requires arp-scan), but I found no way, that works on antiX, to detect a samba shared folder other than using SMBClient…
It’s been only a couple of days since I began experimenting with shared folders (boy, having a shared folder is a time saver, when testing scripts on 2 computers, I wish I got into that before), so I have, at the moment, no idea why the script does not work with SMB 1.0- if it was an arp-scan problem, it’s now solved, since I don’t use it anymore… if it’s a smbclient problem, I have no way to address that…
-About the user/password- hum… since I only recently started using network folders, I though this way: for simple stuff, no password is the way to go, to share documents or scripts between my computers. For more sensitive stuff, I though it made sense using my antiX password- one less password to have on my memory… But it’s not a big deal- the difficult part of the process is finding out the available complete addresses of the shared folders ( ip+folder_name ). Once we have that (and we do), we can modify the script to show a log in window, so the user can enter the user,workgroup and password, and then the script can mount the shared folder and show it in zzzfm…@madibi – since I haven’t used other file managers in years, I can’t help you with any other fm other than zzzfm/rox, but I think there are file system dependencies that you do have to install to have certain features in thunar… probably this includes network shares related stuff…
Edit: on the script’s use of system resources – don’t worry- it’s not only tiny, but once you connect to the network share, the script exits, and you are only using zzzfm (all the script tries to do is to automate the process of entering the share’s address in zzzfm, nothing more).
What frustrated me was that most tutorials about shared folders in Linux take for granted that you always now the ip address of the computer that hosts the shared folder, and the name of the share folder – they always say “just enter the ip”- and I kept thinking- “ok, but most people have no idea what their computer’s ip is- most people don’t even know what that really is, and that the “host” pc has a different ip from the pc that is connecting to it’s shared folder- on Windows, and other Linux’s, it’s easy- you have a list of available network shares and only have to click the one you want- no need to read ip’s etc!”… That is the functionality I want to make available in antiX- even if it’s faster just typing your ip and shared folder name in the address bar, if you know that by heart, on the long run it’s faster to use a script like this, and once you connect to your shared folder, just bookmark it. If it’s ip changes, just delete the bookmark and run the script again… 🙂P.
- This reply was modified 1 year, 2 months ago by PPC.
- This reply was modified 1 year, 2 months ago by PPC.
For those that have been keeping up with my posts here in the forum, my main antiX project right now is FT10 – that aims to both give antiX a more modern look and feel, and still use as little resources as possible and provide some extra amenities- the current FT10 beta provides some extra scripts, including one to configure zzzfm to look more streamlined, and have some extra features, like a trash can and recent files. Thanks to madibi’s request, last night I tried to figure out how to set up a network share, and how to easily mount it in zzzfm. I’m aware that antix includes “connectshares”, but I wanted something that did not require any configuration- I wanted to have a list of all networked shared folders, that I could mount with a single click- some Linux file managers do provide that, but implementing this from the ground up (in the form of a script that could be summoned from zzzfm) was harder than I though.
-the script is available here: https://gitlab.com/antix-contribs/ft10-transformation/-/raw/main/connect_to_existing_network_shares.sh
-Dependencies: arp-scan, smbclient (on my computer this dependencies take about 15mb of disk space, or so…)How to use the script:
1- Configuration:
1.1- open an empty text file
1.2- copy the text in https://gitlab.com/antix-contribs/ft10-transformation/-/raw/main/connect_to_existing_network_shares.sh and paste it to the text file
1.3- save it with a name, something like “connect_to_existing_network_shares.sh” (without the quotation marks), in your user’s home folder
1.4- using zzzfm navigate to your home folder, right click the script you just created >Propreties > Permitions > and check, at least the first “Execute” field > click “ok”
1.5- Don’t forget to make sure all the required dependencies are installed. You can do that doing this in the terminal:
sudo apt install -y arp-scan smbclient
and enter your password, if asked to…2- Running the script:
right click the script, choose to execute it.
If all goes well, the script will present you with the IP’s of all devices connected to your network. click the IP of the device that hosts your network shared folder. If only one shared folder is detected, the script will try to mount it. If more than one shared folder is detected, a new window will allow you to select which one you want to mount. If a password is required to access that folder, enter it, when prompted to in a terminal window that asks for it.
Once again, if all goes well, you’ll see your shared folder displayed in zzzfm…How useful do you folks think this will be? My aim, if it works well, is to include a new Bookmark in FT10’s zzzfm- something like “Shared folders”, that launches this script…
It’s only the first beta, without any checks, etc… As always, all feedback is welcome.P.
Edit: if you want to run the script withou having to enter your sudo password (BE CAREFULL DOING THIS, DO IT AT YOUR OWN RISK):
Menu > Terminal:sudo geany /etc/sudoersand add, in the end of the file:
user host = (root) NOPASSWD: /usr/share/arp-scan user host = (root) NOPASSWD: /usr/sbin/arp-scansave the file, and restart your session. Now you don’t have to enter the password to use the script
- This topic was modified 1 year, 2 months ago by PPC.
anticapitalista
Fresh 19.5 iso files available.
antiX-19.5 is a point release update of our 19 series based on Debian buster.
As usual we offer the following completely systemd-free (and for this particular upgrade – elogind-free) flavours for both 32 and 64 bit architecture. Available iso files for sysVinit or runit.
This is predominantly an update of our last release (19.4).
NOTE: elogind, libpam-elogind and libelogind0 have also been removed.
Instead we use seatd and consolekit.
Many upstream core Debian packages have been rebuilt to remove a hard dependency on libsystemd0/libelogind0
These include apt, cups, dbus, gvfs, openssh, policykit-1, procps, pulseaudio, rpcbind, rsyslog, samba, sane-backends, udisks2, util-linux, webkit2gtk and xorg-serverThose using previous versions of antiX-19 do not need to download this new version. Simply upgrade via apt or synaptic.
Full announcement here: antiX-19.5 point release update
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
In reply to: jwm center all windows
Anonymous
Is the centered placement issue now SOLVED?
post #75731 onward should have merited a separate topic, bearing a topic title mentioning samba, eh
as a further, separate topic, discussion:
“Copy and pasting doesn’t work in antix specially using fsearch as an example.”
Yes, it does (or, said differently, it can)
The linux primary clipboard (aka primary selection) is available for use in antiX. Its usage and configuration are identical to nearly every other linux distro. For extra functionality within a desktop/gui context, same as any other distro… if you are not running a desktop environment which provides a clipboard manager component, you can install a clipboard manager utility program (e.g. debian packages: parcellite // clipit // copyQ). Specific to ROX-filer ~~ in fossapup, investigate how they achieve the custom copy command (an AppDir script?) and you can identically setup same in the ROX-filer of your antiX install. Natively, in antiX’s ROX-filer (same as when installed in other distros)… the expectation is that copy//move operations within ROX will be accomplished via drag-n-drop between multiple ROX-filer windows.rox.sourceforge.net/desktop/book/export/html/6.html
The primary selectionIf you’ve used X for a while, you’ll have discovered the middle-button-paste feature. This pastes the currently-selected text (not the clipboard!) to wherever you click. In particular, if you select some files in ROX-Filer then middle clicking into any application will paste the filenames. That includes:
Paste into Firefox’s address bar (or even just into the main window) to view that file.
Paste into an xterm to add a filename to a command.
Paste into a file Open dialog box for applications that don’t support drag-and-drop.If you select something else in another window, ROX-Filer loses the primary selection (it shows the selection greyed out). To get it back, just click on any item in the greyed-out selection.
Tip: to select files quickly by glob, use . (period). For example, typing .png will instantly select all files ending in .png. With a bit of editing of the pattern with the cursor keys, you can select on other parts of the name (e.g., all files starting with test-).
^—> see also:
antiX 16.2 “Copy” a file, but NO “Destination”
antixlinux.com/forum-archive/solved-rox-filer-can-not-copy-multiple-items-t6776.htmlIn reply to: jwm center all windows
madibi
I like to have my private lan as once I was used in the win lan: every pc is both server and lan.
1. For that reason I set the samba server in the “traditional” debian way.
That means that I compile the smb.conf file according to the usual debian guidelines that you can find in every tutorial.
2. second point from the client I search in the lan with zzzfm: in the navigation bar you need to write the exact address of the share smb:/192.168.xxx.yyy/yourshare/
3. you write name and pw,et voilà, everything worksIn reply to: jwm center all windows
rmcellig
I have tried antix so many times and always had issues. I just installed it today and I think FINALLY I am starting to gain respect for this distro! I always had issues with the samba tool. Is there another way to search for shares on my LAN? I am now using fstab to mount the shares I know about. This works great so do far things are looking up.
I’m a heavy user of fossapup and hopefully I will be able to get antix as close as possible to fossapup or whatever pup I am using.Thank God rox and jwm are part of antix as well as icewm. All of my computers are mini computers. I just recently replaced all six of my computers on my LAN. No laptops.
ensabahnur
Pin Linux OS (MX Linux 21 Spin). A light version of MX Linux LXDE. This is not a new Distro it’s just an MX Linux 21 spin using LXDE. This system is based on antiX-core using MX Linux repository, come with minimal installed, so you can add any app from Debian and MX repositories.
The base version its only the base, only essential to boot up the system with graphic interface. Kernel 5.14
The base for old machines its the same base but with more old drivers and kernel 4.9
The full version its like a ready to go system already customised.
Support only 64 bits (x86_64, amd64).
No support for Printer, Samba, or Bluetooth. But you can install them if you need them easily.For printers:
sudo apt install cupsFor Bluetooth:
sudo apt install bluemanFor Samba sharing:
sudo apt install sambaRecommended for old machines, either laptops or desktops. Nevertheless, if you have a modern machine the system will fly blazing fast, good for games, for example.
Still in the testing stage, so feel free to report any problem, I’ll be happy to help and sort out any case when is possible.
https://sourceforge.net/projects/pin-linux-os/
Attachments:
In reply to: WARNING!
oops
Hello,
My feedback:
Tryed antix21_amd64_runit (with lightdm too) into a VirtualBox VM, and I have an issue at the startup of the VM, after this (apt dist-upgrade).The start process stop at: “bound to 192.168.1.12 — renewal in 16735 seconds.”
But I can after logging to root start lightdm or slim by hand (with a dbus-daemon issue too).Here the OCR screen capture, if it can help:
Welcome to antixX. Powered by Debian. Anacron 2.3 started on 2821-12-23 Normal exit (@ jobs run) invoke-run: WARNING for rsunc: disabled by local settings Skip stopping firewall: ufw (not enabled) invoke-run: WARNING for ufw: disabled by local settings Internet Systems Consortium DHCP Client 4.4.1 Copyright 2464-2818 Internet Systems Consortium. All rights reserved. For info, please visit https: //www.isc.org/software/dhcp/ Listening on LPF/eth@/88: 64: 27: e6:24:c4 bl] Te Pe LPF /ethé/@8: 48:27: e6:24:c4 hl] Te Pe) Socket? fallback DHCPREQUEST for 192.168.1.12 on eth@ to 255.255.255.255 port 6? DHCPACK of 192.168.1.12 from 192.168.1.254 Reloading /etc/samba/smb.conf: smbd. bound to 192.168.1.12 -- renewal in 16735 seconds. Hint: Num Lock on antix-21-64R login: root Password: dbus-daemon[1673]: [system] Activating service name='org.freedesktop.logini’ requested by ':1.8' Cuid=@ pid=1616 comm="/bin/login -- dbus-daemon[1673]: [system] Failed to activate service ‘org. freedesktop.logini': timed out (service_start_timeout=2540Gms) root@antix-21-64R:~#Robin
You are simply riding the wrong horse: You want DNS, not NetBIOS or WINS
Nothing at all about any Netbios names anywhere
This is expectable, since only Windows uses this windows specific protocol. NetBIOS is something you won’t want to set up as your default name resolution method in mixed style networking (MacOS, Linux and Windows machines present in the same network). NetBIOS is something you can use in “windows-only” networking, as long as no other client shows up. From the moment you deal with different OS in a network, use simply DNS instead. The windows machines can handle this properly.
Probably your Ms. Linksys is a lady of doubtful reputation (as you yourself denoted: she is a MS, standing here not for Miss, but for Microsoft obviously). She can possibly only handle “windows-only” networking. Some of the linksys are known to suffer from that strategic business decision of the router manufacturer, to design it windows-exclusively. Neither a WINS server nor a NetBIOS master browser are suitable in mixed networking.
So you possibly won’t get happy with this device. If this turns out to be true for your device you’ll have to run an additional true DNS 24/7 somewhere in your network. For a first reading: Why some routers dont include dns.There is nothing antiX (or any other linux) could change on this situation. If there is actually no local DNS server present in your LAN, antiX can’t guess the networking host names of your devices and the local domain name, since there are none. There are only NetBIOS names for windows-exclusively networking. Seems you are locked in within windows world by your router.
Do I need to do anything else to make the Linksys the DNS server?
Use a device not designed “Windows-exclusively”, or replace its firmware by a version capable of handling universal local DNS, if the manufacturer provides this for your device. Then all your problems caused by missing name resolution in your network will vanish as if by magic.
As a workaround you could edit the hosts files on all your devices (yes, also windows knows about this file), so they contain all the (then mandatory static) IPs correlated to the device names present in your network. Try “man hosts” in a console window for further reading.
You’ll find the hosts file in Windows at:
c:\windows\system32\drivers\etc\hosts
And on antiX and any Linux as well as on any MacOS at:
/etc/hosts
You can edit these hosts files using a simple text editor. But be aware, this is a dirty old-school workaround only for a non functional default networking setup in your LAN. On a correct router/server side setup you won’t even need to use static IP, since your router should know about a feature assigning the same IP always to a specific networking device when using DHCP.
Further reading: wikipedia entry on hosts fileTo put it in a nutshell: You need host names and a local domain name, not Windows NetBIOS names and a Windows WORKGROUP, and also you need to have a true DNS running. Only after these basics are met in your LAN you may start to set up SAMBA for emulating the Windows specific protocols on Linux (or MacOS) machines in a second step.
Windows is like a submarine. Open a window and serious problems will start.
ahoppin
Robin:
> Ms.Linksys has to be the DNS provider for your local network, set up to forward all
> queries she can’t answer herself to Mr.Mofi.That makes sense.
I’ve configured Antix to use static IP address and DNS, with DNS at 192.168.1.1 – that’s the Linksys. Confirmed it with the contents of /etc/resolv.conf.
The other machines currently on the net are also set to static DNS at the Linksys.
Do I need to do anything else to make the Linksys the DNS server?
—–
If I run arp -a on freshly booted live Antix – static DNS on the Linksys – it returns only
_gateway (192.168.1.1) at xx:xx … [ether] on eth0
Nothing at all about any Netbios names anywhere.
If I then run findshares, it locates the Netbios machine names and shares, just as it did before.
After I’ve run findshares the first time, arp -a says something different:
_gateway (192.168.1.1) at xx.xx … [ether] on eth0
? (192.168.1.117) at xx:xx … [ether] on Eth0
? (192.168.1.155) at xx:xx … [ether] on Eth0
? (192.168.1.111) at xx:xx … [ether] on Eth0So running findshares is changing something.
BUT – still no Netbios names, according to arp. And no pings by netbios names.
I read up a little on Netbios. If I understand it right, there are 4 levels of Netbios name resolution:
1. The client’s cache
2. The client’s LMHosts file (that’s on Win; no idea what Samba’s equivalent might be)
3. A WINS server (no such thing exists on my net, as far as I know)
4. Broadcast message to all machines on the netMaybe #4 is what findshares is doing. Just a wild-donkey guess.
ALSO: Apparently some routers can implement either a Netbios master browser, or, less often, a WINS server.
I see nothing about either one of these in the Linksys config menus, so I don’t think it has either capability.
However, if Netbios name resolution can be done by broadcast message, I don’t see why the router would have to provide either WINS or master browser service. Unless Antix just isn’t able to do that.
This is all quite puzzling.
> included my router as a DNS server.
Aha! I’d expect DHCP to tell the OS to use the router as its DNS, but something different happens here, and it’s my fault.
Long story, but I have the Linksys main router’s WAN port connected to a mobile (cellular) router – a Mofi 4500. The Linksys is set for DHCP to the WAN, so it’s handing out the Mofi’s IP address when a client asks “what DNS?”.
This setup has worked fine for me since June of this year.
But since the upstream Mr Mofi has no truck with anyone but Ms Linksys, it knows naught of Ms Linksys’s downstream LAN progeny.
So the idea of introducing Mr Antix to Ms Linksys as DNS provider seemed mighty promising.
I used Connman as you suggested (many thanks!), configuring a static IP address, and also asked it to set the Linksys as DNS.
After a couple of false starts, the process went smoothly. DNS resolution worked and ping found various URLs on the internet. However, dang it, ping still can’t find the local Samba shares!
arp -a finds them exactly as before, with only the IP addresses, and ? where the name would otherwise be.
So, connectshares still won’t work with share names, only IP addresses.
Maybe it’s something different about the Linksys.
On the other forepaw, I now have a working static IP, so that’s progress, for which I thank you heartily! Your screenshots REALLY helped.
I hate to sound defeated, but I think it’s time to write off connectshares. There’s always a Plan B, and here it’s to write up my own shell script to list the shares and get their IP addresses with findshares and/or smbclient, then mount them with mount.cifs.
Thanks again for all the help! Y’all are fantastic.
Forum for users of antiX Linux. Mean and Lean and Proudly anti-fascist.
