|01:35||vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e)|
padikiller: do your printers need a driver? If yes, install it inside the image. If not, they should be directly usable after the clients boot...
|02:43||vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e, Quit: leaving)|
|06:54||jgee has left IRC (firstname.lastname@example.org, Quit: Ping timeout (120 seconds))|
|06:55||jgee has joined IRC (email@example.com)|
|08:02||woernie has joined IRC (firstname.lastname@example.org)|
|08:24||ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)|
|11:04||lucascastro has joined IRC (email@example.com)|
|14:56||eu^i5E866DEEvers has joined IRC (eu^i5E866DEEvers!~eu^i5E866@2001:9e8:631b:eb00:fa1d:a61:4343:35ec)|
<alkisg> "padikiller: do your printers..." <- alkisg - When I netboot the client to Mint 20.2, the printers connected to the LTSP server network are visible and usable, but not the USB printer plugged into the client. When I open "Printers" from the Control Center, the settings are locked. When I click the "Unlock" button, I am prompted to enter the password for the LTSP server administrator. Once I enter the password, I am able to
click "Add New Printer":. After clicking "Add New Printer" the Brother printer is visible. Wnen I click to add it, a window pops up that says "Searching for Drivers". I have to enter the LTSP admin name and password again and the Brother Printer is installed.
Here are the settings in the ltsp.conf HOSTNAME="test"
I'm wondering if it might be because the user is not an admin?
Thanks for you time and attention BTW
i just read through your installation manual - and am not quite sure what is the best image type for me. I want to use an ltsp-server via qnap virtualization station - which is a vm-image run on a qnap-nas. I want the clients to boot kubuntu from that virtual ltsp-server. The client-users should authenticate via ldap - which also is a feature
already available on the qnap-nas (i think they use open-ldap) - so the ldap-server is not on the ltsp-server. Also i want the client-users to have access to the storage of the nas via webdav or similar (e.g. via the file explorer of kubuntu named dolphin). All used clients are quite new lenovo laptops or desktop pcs. Could anyone give me a hint
what to use best?
if it shows the printer from the LTSP server then I suspect the CUPS server setting isn't taking properly
I was thinking the same thing.. but then again the client sees the same network the server does, do maybe it is (for some reason) loading the the network printers but not the local printer?
padikiller: see https://ltsp.org/man/ltsp.conf/ - CUPS_SERVER=localhost will make the clients see their own printers, instead of the server printers
could be - I always get confused when what printer is what when network printer get involved, I think I see the same printer 3 times through different connections in my CUPS interface
quinox: you need to go to the printer properties dialog, right click on the printer, and uncheck "share this printer" from where you don't want it to be shared
E.g. if I install a network printer on my box, and have it shared from my box too, then it appears twice on the network for others
good to know
eu^i5E866DEEvers: from what I understood, you'll want to install kubuntu in a vm on qnap, an configure ldap and webdav and whatever else you want, and then you'd run `ltsp image /` from there and you'd have your "ltsp image" ready,
but additionally, if your /srv/ltsp inside that image is a qnap network mount, and if you configure dnsmasq on qnap itself, then you'll also be able to power off that ltsp-server-vm and use qnap itself as the ltsp server
https://github.com/ltsp/ltsp/commit/184687e8807b41c5916bf265bd516ae4f85c19a2 you can check /etc/cups/client.conf on a freshly booted client, it should say "ServerName localhost"
quinox: quinox - It does say "localhost"
I have the client autologin set to a normal user. I wonder if that is the problem?
padikiller: you need to connect a brother printer to the server, install the drivers there, then run ltsp image /
So that the drivers are inside the image, which will make the printer autodetected at boot
(the you can move it back to the clients)
alkisg: Will do. Thanks!
alkisg thx for your input. As im not that familiar with all the terminology+packages i have to look how dnsmasq is used.But aren't the ltsp packages needed for the clients to boot? I don't think i get the point. If i use a ltsp-server - and save the images on a external storage and shutdown the vm with the ltsp-server - wouldn't that mean only the
files/images in /srv/ltsp are needed to make a network boot of a client possible? Maybe i described it badly - so another try. I got a qnap-nas which runs an ldap-server and whose storage can be accessed via webdav or similar. Now i want some clients to be able to do a network boot on a kubuntu system. dhcp is done by a router. The users who can
access that system should authenticate via the existing ldap-server and after doing so have access to the qnap Storage.
"only the files/images in /srv/ltsp are needed to make a network boot of a client possible?" ==> provided you run dnsmasq elsewhere, and ldap/home is elsewhere (on qnap), then this statement is indeed true
So, if you run dhcp on router, proxydhcp and tftp on qnap (=dnsmasq), authentication on qnap (=ldap), and /home on qnap (=nfs /home), then you don't need a running ltsp server to boot a kubuntu ltsp client image
If you want to do this on two steps, you can also do it; to run a kubuntu ltsp server, and to authenticate via ldap, and mount /home from qnap. Then when you understand what's going on, you can fill in the missing bits and power off the ltsp server
So, the easiest way would be to install kubuntu in a bridged VM, then follow https://ltsp.org/docs/installation/ for "chrootless mode", and then start adding the authentication/home etc bits
thanks a lot - i will give it a try and see if i get that working. have a nice holiday
|15:52||eu^i5E866DEEvers has left IRC (eu^i5E866DEEvers!~eu^i5E866@2001:9e8:631b:eb00:fa1d:a61:4343:35ec, Quit: Client closed)|
|16:17||lucascastro has left IRC (firstname.lastname@example.org, Ping timeout: 240 seconds)|
I still have to manually add the printer on every netboot of the client. I changed ltsp to AUTOLOGIN the administrator and I installed the USB printer on the LTSP server and ran ltsp image / and ltsp initrd and netbooted the client. I don't have to enter credentials anymore, but I still have to manually add the USB printer.
I wonder if should the let the server run CUPS?
Letting the server run cups and forwarding the client printer using jetpipe is possible,
a nd it's also possible to copy the /etc/cups/printers.conf from the booted ltsp client, to the server's /etc/ltsp/printers-$MAC.conf, and run ltsp initrd, and put this in ltsp.conf: POST_INIT_CP_PRINTERS="cp /etc/ltsp/printers-$MAC_ADDRESS.conf /etc/cups/printers.conf"
|16:47||lucascastro has joined IRC (email@example.com)|
<alkisg> "Letting the server run cups..." <- Copying printers.conf as you instructed WORKED LIKE A CHARM! Thanks so much!
Thanks to alkisg and quinox, I now have got LTSP booting RPI 4 clients and I have printers configured!..
One thing that should be added to the Raspberry Pi page on the LTSP website is to tell readers to change the IP addresses in the commands that update command.txt. I (like many dumb users) just cut-and-pasted the commands without reading them. Took me a while to figure out that I needed to edit the IP address,
|22:43||ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)|