IRC chat logs for #ltsp on irc.libera.chat (webchat)

Request log from specific day:

Channel log from 27 February 2018 (all times are UTC)

00:04	lucascastro has joined IRC (lucascastro!~lucas@201.182.221.14)
03:48	lucascastro has left IRC (lucascastro!~lucas@201.182.221.14, Remote host closed the connection)
03:48	lucascastro has joined IRC (lucascastro!~lucas@201.182.221.14)
05:50	nehemiah has left IRC (nehemiah!~nehemiah@saphar.net, Quit: Leaving.)
06:33	ricotz has joined IRC (ricotz!~ricotz@p5B2A98EE.dip0.t-ipconnect.de)
06:33	ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
06:50	Statler\|Home has joined IRC (Statler\|Home!~Georg@p5B30E83C.dip0.t-ipconnect.de)
06:56	kjackal has left IRC (kjackal!~quassel@2a02:587:3108:6c00:6de4:d3c5:9783:e1e3, Ping timeout: 256 seconds)
06:57	kjackal has joined IRC (kjackal!~quassel@2a02:587:3108:6c00:6de4:d3c5:9783:e1e3)
07:09	al-geo has left IRC (al-geo!5be2b379@gateway/web/freenode/ip.91.226.179.121, Ping timeout: 260 seconds)
08:06	kjackal has left IRC (kjackal!~quassel@2a02:587:3108:6c00:6de4:d3c5:9783:e1e3, Ping timeout: 256 seconds)
08:37	kjackal has joined IRC (kjackal!~quassel@88.197.38.168)
09:12	<alkisg> !nbd-clients
09:12	<ltsp> I do not know about 'nbd-clients', but I do know about these similar topics: 'nbd-client'
09:12	<alkisg> !client-list
09:12	<ltsp> client-list: to get a list of all nbd-clients (which sometimes is the same as ltsp clients), run: ss -n \| sed -n 's/.:10809 $[0-9.]$:./\1/p' \| sort -Vu
09:15	alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
09:17	alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
09:47	Statler\|Home has left IRC (Statler\|Home!~Georg@p5B30E83C.dip0.t-ipconnect.de, Remote host closed the connection)
09:53	tek__ has left IRC (tek__!tek@kapsi.fi, Ping timeout: 260 seconds)
09:54	tek__ has joined IRC (tek__!tek@kapsi.fi)
10:17	SmashK has joined IRC (SmashK!5b40100b@gateway/web/freenode/ip.91.64.16.11)
10:17	<SmashK> hi
10:26	<alkisg> Hello
10:31	Statler_Office has joined IRC (Statler_Office!~Georg@gwrz3.lohn24.de)
10:35	GodFather has left IRC (GodFather!~rcc@wsip-24-249-172-218.ph.ph.cox.net, Read error: Connection reset by peer)
10:36	GodFather has joined IRC (GodFather!~rcc@wsip-24-249-172-218.ph.ph.cox.net)
11:03	<alkisg> !nbd-client
11:03	<ltsp> nbd-client: To try mounting the NBD image from the client initramfs: nbd-client 192.168.67.1 -N /opt/ltsp/i386 /dev/nbd0
11:06	kjackal has left IRC (kjackal!~quassel@88.197.38.168, Ping timeout: 252 seconds)
11:15	<SmashK> !ltsp that maybe will not work, it didn't work for me yesterday
11:15	<ltsp> Error: "ltsp" is not a valid command.
11:15	<alkisg> SmashK: ltsp is a bot that we use to take and show notes
11:15	It's not a person
11:16	<SmashK> ok
11:17	it seems to be a world of LINUX-magicians here
11:52	Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)
11:57	kjackal has joined IRC (kjackal!~quassel@2a02:587:3108:6c00:6de4:d3c5:9783:e1e3)
12:08	<SmashK> tried yesterday to see the shares of my LTSP-Server (inside vbox) from Windows' Explorer by using \\192.168.67.1 but he showed me the windows-own shares of the host
12:09	why is it mirroring the host shares to the LTSP-IP?
13:52	real PC dont want to boot with PXE from LTSP-Server
13:52	it gets no IP from DHCP
13:53	while thin-Client in other vbox-machine works
13:54	can see DHCP-pings from hardware-PC in Etherape on LTSP-Server, going from routers-IP 192.168.178.1 via 255.255.255.255 to 0.0.0.0
14:37	<\|\|cw> SmashK: what networking mode are you using for VMs in vbox? there's at least one that prevents that a lot of host to guest things from working
14:38	it's really more of a vbox issue than anything else tho
14:46	ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu)
14:55	<SmashK> what kinda working mode you mean?
14:55	lucascastro has left IRC (lucascastro!~lucas@201.182.221.14, Remote host closed the connection)
15:02	<SmashK> bridge from real-hardware-NIC to emulated INTEL Pro 1000, thats you mean?
15:03	<alkisg> SmashK: ltsp and ubuntu don't enable samba shares by default, so it's possible that you're seeing the virtalbox shared folders, if you enabled that
15:04	In general, ltsp is not related at all to samba, it doesn't use it etc
15:06	<SmashK> maybe samaba is enabled by default in the latest Debian 9.3 release
15:06	<alkisg> Are you seeing the ltsp server shares?
15:06	Or the host shares?
15:06	<SmashK> which way when not by \\ip in Windows explorer?
15:07	<alkisg> You can just run systemctl and see if samba is running or not
15:07	<SmashK> I saw host shares by \\192.168.67.1
15:08	<alkisg> !vnc-edide
15:08	<ltsp> vnc-edide: To share your screen with me, open Epoptes → Help menu → Remote support → Host: srv1-dide.ioa.sch.gr, and click the Connect button
15:09	<alkisg> I think it'll be quicker if I see directly... than trying to describe it...
15:09	<SmashK> can't see samba in this wall of text
15:13	<alkisg> 192.168.67.1 is not an ltsp ip
15:13	Your ltsp server ip is 192.168.178.20
15:14	The ltsp server can't even ping 192.168.67.1
15:14	<SmashK> let me see in Windows
15:14	<alkisg> And it doesn't have samba installed at all
15:14	samba => Installiert: (keine)
15:14	<SmashK> cant connect via \\192.168.178.20
15:14	quit confused
15:15	<alkisg> Yes, they're not in the same network
15:15	<SmashK> *quite
15:15	<alkisg> Your router is 192.168.178.1?
15:15	<SmashK> ping from windows-host to .20 is ok
15:16	<alkisg> What is the ip of the windows host?
15:16	<SmashK> .206
15:18	<alkisg> You do have shared folders there in windows
15:18	<SmashK> alot
15:18	<alkisg> I don't see anything having this ip though: 192.168.67.1
15:18	Why do you think that some pc has that ip?
15:19	<SmashK> am sure that IP was shown yesterday
15:19	I did \\.... and it showed me the host shares
15:19	<alkisg> And if you do it now, does it show them?
15:20	<SmashK> do I have any shares on that Server right now?
15:20	<alkisg> In the ltsp server? No
15:20	You don't even have samba installed. Not even the client.
15:20	<SmashK> yes, \\192.168.67.1 gives me the windows-shares o.O
15:20	<alkisg> From the windows server, can you ping 192.168.67.1?
15:21	<SmashK> TTL=128
15:22	<alkisg> I cannot ping that from the ltsp server
15:22	Even when I add an IP inside that subnet
15:22	<SmashK> host name of .67.1 is my hosts name, huh?
15:22	<alkisg> It's not related to ltsp at all
15:22	I don't know what you did in virtualbox
15:22	Maybe you configured a tap interface in windows
15:23	I cannot see that from inside the VM
15:23	But in any case it's not related to ltsp at all
15:23	And it's not something that windows or virtualbox does; you manually added that IP somewhere
15:24	<SmashK> .67.x isnt in my routers settings
15:24	<alkisg> I don't know where you added that. Check in windows, check from other PCs...
15:25	What I do know is that it's not related at all to your ltsp setup
15:25	<SmashK> rgr, thanx alot
15:25	<alkisg> np
15:25	<SmashK> still on the server?
15:25	<alkisg> Yes, click on disconnect to disconnect me
15:28	<SmashK> .67.1 is the virtualBox Host-Only Network
15:29	which is not activated as NIC for the LTSP
15:30	<alkisg> It's activated for your windows though
15:30	So it's like 127.0.0.1
15:30	Btw, this isn't the default ip for the virtualbox host network
15:30	You manually put that...
15:32	<SmashK> yes, thats possible
15:45	adrianorg has left IRC (adrianorg!~adrianorg@189.58.227.228.dynamic.adsl.gvt.net.br, Ping timeout: 265 seconds)
15:45	adrianorg has joined IRC (adrianorg!~adrianorg@189.58.227.228.dynamic.adsl.gvt.net.br)
16:06	Arai has joined IRC (Arai!8048431b@gateway/web/freenode/ip.128.72.67.27)
16:06	<Arai> Greetings!
16:09	Is there an command from server to send broadcast "reboot" message for thick clients?
16:13	<quinox1> thick ? thin / fat :)
16:13	<Arai> fat ones
16:29	<SmashK> think u can do this with Epoptes
16:37	<Arai> Hmm, maybe is exists any easier way? Like "echo -en "0\0\0\0reboot\0" \| nc 192.168.1.255 514" for wtware clients.
16:42	<SmashK> http://ltsp-discuss.narkive.com/Guirg2K5/i-need-to-remote-reboot-a-ltsp-5-client
16:42	maybe this way?
17:01	<Arai> thanks, i'll try
17:13	<alkisg> !epoptes
17:13	<ltsp> epoptes: Epoptes is a computer lab administration and monitoring tool. It works on Ubuntu and Debian based labs with LTSP or non-LTSP servers, thin and fat clients, standalone workstations, NX clients etc. More info: http://www.epoptes.org
17:14	<alkisg> It's very light and much more flexible than just a remote reboot command
17:14	People usually don't want to have an open port than can reboot clients... :)
17:16	But if you do want to have a reboot port, that's just an RCFILE_01="nc -l ..." command away
17:16	adrianor1 has joined IRC (adrianor1!~adrianorg@177.156.62.14)
17:19	adrianorg has left IRC (adrianorg!~adrianorg@189.58.227.228.dynamic.adsl.gvt.net.br, Ping timeout: 248 seconds)
17:42	<quinox1> heh
17:55	<SmashK> ho
17:55	lucascastro has joined IRC (lucascastro!~lucas@200.141.207.18)
18:14	lucascastro has left IRC (lucascastro!~lucas@200.141.207.18, Remote host closed the connection)
18:56	adrianor1 is now known as adrianorg
19:10	vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
19:36	Statler_Office has left IRC (Statler_Office!~Georg@gwrz3.lohn24.de, Remote host closed the connection)
19:44	lucascastro has joined IRC (lucascastro!~lucas@201.182.221.14)
20:08	<lucascastro> alkisg: I brought the !cheap-client.
20:08	!cheap-client
20:08	<ltsp> cheap-client: https://www.gearbest.com/tv-box-c_11262/nt1_windows~10/
20:08	kjackal has left IRC (kjackal!~quassel@2a02:587:3108:6c00:6de4:d3c5:9783:e1e3, Ping timeout: 256 seconds)
20:09	kjackal has joined IRC (kjackal!~quassel@athedsl-174053.home.otenet.gr)
20:09	<lucascastro> brought at aliexpress. the arrive estimate in 14-30 days.
20:13	<alkisg> lucascastro: cool
20:13	bennabiy had reported that he was unable to netboot it
20:13	I think because of uefi
20:14	If you fail too, you can easily netboot it with a local grub or kernel
20:14	lucascastro: which one did you buy?
20:15	<vagrantc> i recently have gotten a bit more experience with network booting EFI systems
20:18	<alkisg> It'd be nice to add uefi support upstream in ltsp...
20:18	vagrantc: did you manage to boot with proxydhcp mode? That was the show-stopper for me...
20:19	But I heard that later on, dnsmasq did support it
20:19	<vagrantc> alkisg: yes, using proxydhcp ... though it was an arm64 (u?)efi implementation ...
20:19	<lucascastro> oops.
20:19	<vagrantc> i get the impression each EFI implementation will have it's own idiosyncracies
20:20	<lucascastro> https://www.aliexpress.com/snapshot/0.html?orderId=90150237732239&productId=32838616866
20:21	I brought this one.
20:26	what client are you using? vagrantc, alkisg ?
20:28	* vagrantc hasn't had real-world clients for year
20:28	<vagrantc> s
20:29	which is why i haven't been as active in ltsp development lately
20:31	<lucascastro> I see
20:31	<alkisg> lucascastro: i'm using regular i3's normallyh
20:34	<lucascastro> I live in Brazil. The ideia of thin client and ltsp is reduce some costs in electricity and computer acquisition. So regular computer is too expensive.
20:36	<alkisg> We don't recommend thin clients anymore
20:36	Only fat clients
20:37	There are i3's or celerons etc in small forms too, e.g. intel nuc
20:37	and atoms are a bit ok, sure
20:40	<lucascastro> intel nuc over here is a little expensive.
20:41	2k+ BRL
20:42	<alkisg> We're getting desktop but diskless i3's for just a bit above 200 euros here
20:42	They score 6000+ in cpubenchmark, while atoms score 2000-
20:42	So that double price will get us 3 more life time for each pc
20:43	Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving)
20:43	<alkisg> The electricity is usually analogous to the performance...
20:43	And if you try to save in client cpu power, you'll spend it on the server AND the network, which isn't better
20:44	If your users can work with atoms, those cheap-clients should be fine then
20:45	Atoms feel slow to me though, I don't recommend them to those that can afford normal CPUs
20:46	<lucascastro> fine. Where I'm planning to implement doesn't demand too much resource, I brought just one for testing.
20:46	I'm guessing will be ok.
20:48	<vagrantc> people frequently underestimate what "just browsing the web" means these days
20:48	<lucascastro> But if I implement a client that will not use 50% of cpu capacity, isn't good too.
20:49	vagrantc: I understand that.
20:49	web browsing but processed at the client.
20:49	<alkisg> Atoms are usually good for browsing the web with a couple of tabs open. If you open a few more programs or tabs, you feel the lack of performance...
20:50	So don't worry about not using all the client cpu :)
20:50	<lucascastro> :D
20:51	<alkisg> lucascastro: how much is a normal salary in brazil?
20:51	E.g. a teacher...
20:51	<\|\|cw> modern PCs that aren't using CPU also aren't use as much power, so that's a good thing.
20:51	<lucascastro> 954,00
20:52	<alkisg> Eh, so an intel nuc is two salaries? Yeah that's lame...
20:53	<\|\|cw> there's a wide range of nuc prices, and power
20:54	<vagrantc> yeah, the power consumption on modern CPUs tends to be lower than older generation stuff
20:54	<alkisg> Google says 2000 Brazil reais =503 euros... so.... yeah that's close to a good nuc here
20:55	<lucascastro> I understand the problem in using older generation.
20:56	<vagrantc> /7/7
20:56	oops
20:56	<\|\|cw> you can get late core2 for around $50, and early i3/5/7 for under $100, with 4GB ram, on ebay.
20:57	<lucascastro> what's means /7/7 ?
20:57	<vagrantc> lucascastro: it was a typo
20:58	<lucascastro> ok
21:02	vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 256 seconds)
21:08	vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
21:17	kjackal has left IRC (kjackal!~quassel@athedsl-174053.home.otenet.gr, Ping timeout: 248 seconds)
21:41	vsuojanen has joined IRC (vsuojanen!~valtteri@83-136-248-31.uk-lon1.host.upcloud.com)
22:20	ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)