IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 17 April 2020 (all times are UTC)
| 00:16 | map7 has left IRC (map7!~user@103.232.216.31, Read error: Connection reset by peer) | |
| 03:47 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
| 04:54 | statler has joined IRC (statler!~Georg@p5B30E178.dip0.t-ipconnect.de) | |
| 05:04 | statler has left IRC (statler!~Georg@p5B30E178.dip0.t-ipconnect.de, Quit: cu) | |
| 05:54 | woernie has joined IRC (woernie!~werner@p5DDEC5BE.dip0.t-ipconnect.de) | |
| 06:01 | statler has joined IRC (statler!~Georg@p5B30E178.dip0.t-ipconnect.de) | |
| 06:18 | RaphGro has joined IRC (RaphGro!~raphgro@fedora/raphgro) | |
| 07:47 | woernie has left IRC (woernie!~werner@p5DDEC5BE.dip0.t-ipconnect.de, Ping timeout: 265 seconds) | |
| 07:48 | woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de) | |
| 08:34 | uumas_ has joined IRC (uumas_!uumas@kapsi.fi) | |
| 08:34 | uumas_ has left IRC (uumas_!uumas@kapsi.fi) | |
| 09:08 | woernie has left IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Ping timeout: 265 seconds) | |
| 09:09 | woernie has joined IRC (woernie!~werner@p5DDEC5BE.dip0.t-ipconnect.de) | |
| 11:08 | Teridon has left IRC (Teridon!~Teridon@dragon.teridon.com, Ping timeout: 256 seconds) | |
| 11:10 | adrianor1 has joined IRC (adrianor1!~adrianorg@179.177.210.212.dynamic.adsl.gvt.net.br) | |
| 11:10 | Teridon has joined IRC (Teridon!~Teridon@dragon.teridon.com) | |
| 11:13 | adrianorg has left IRC (adrianorg!~adrianorg@187.113.218.87, Ping timeout: 265 seconds) | |
| 12:15 | woernie has left IRC (woernie!~werner@p5DDEC5BE.dip0.t-ipconnect.de, Ping timeout: 258 seconds) | |
| 12:16 | woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de) | |
| 12:24 | mgariepy has joined IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy) | |
| 13:18 | danboid has joined IRC (danboid!~ISDADS\sg@cpc126962-macc4-2-0-cust227.1-3.cable.virginm.net) | |
| 13:18 | <danboid> No alkisg?
| |
| 13:19 | It's not possible to use LTSP fat clients over the internet is it? I know you could still kinda use the server via x2go or VNC etc but that's no longer LTSP
| |
| 13:20 | I remember alkisg had some kind of solution in place for these situations but I don't remember what
| |
| 13:21 | highvoltage, ^^
| |
| 13:30 | <alkisg> Hey danboid
| |
| 13:30 | You want to netboot over the internet?
| |
| 13:30 | How fast is your internet?
| |
| 13:32 | Are you sure you don't want to cache the ltsp image locally in the target lan?
| |
| 13:32 | <danboid> I think its 100 Mb/s up at the DC where our LTSP server lives
| |
| 13:33 | <alkisg> Anyway, there's no "LAN" restriction in any phase of an ltsp client boot, except for dhcp
| |
| 13:33 | <danboid> The LAN is gigabit
| |
| 13:33 | <alkisg> You can overcome the dhcp part if you use ipxe
| |
| 13:33 | If you have the ability to use even a raspberry pi there as a dhcp/image server, it would make things a lot faster
| |
| 13:34 | Even if login + /home are over the internet
| |
| 13:35 | If you want better advice, describe the use case in more detail
| |
| 13:35 | <danboid> Yes, I asking about internet netboot. It can be done with ipxe you say?
| |
| 13:35 | <alkisg> Sure, there's no restriction for tftp, nfs, sshfs, ssh etc that says you need to use lan
| |
| 13:35 | Only dhcp uses ethernet packets instead of ip packets, so you need ipxe to overcome that part
| |
| 13:35 | <danboid> Obviously it will be a lot slower than using it on the lan
| |
| 13:36 | <alkisg> Is it about coronavirus teleworking?
| |
| 13:36 | <danboid> How did you guess? :)
| |
| 13:36 | <alkisg> :)
| |
| 13:36 | How many clients, and do you have SSDs in them?
| |
| 13:37 | <danboid> Why do you ask about SSDs?
| |
| 13:37 | <alkisg> Because it would allow you to cache the image there, and make things a lot faster, and put ipxe as well
| |
| 13:38 | (actually, grub in that case, not ipxe)
| |
| 13:41 | <danboid> I think the envisioned scenario is that we'd like students to be able to stick a bootable ipxe USB drive into their laptops/desktops and boot into a fat client. Most will not have a Rpi available and I don;t want to presume they have any kind of disk or OS installed
| |
| 13:42 | Obvs they will but it could be a Mac, Linux or Windows machine with any kind of disk
| |
| 13:42 | <alkisg> OK, see, you gave more info :)
| |
| 13:42 | Instead of putting ipxe in the usb stick, you could put the ltsp image, and make things a lot faster
| |
| 13:43 | But if you want to avoid that, sure; experience teaches better than irc advice :)
| |
| 13:44 | It's also possible to cache the image in any disk that already has an OS, but if you don't want to go there, understandable
| |
| 13:44 | <danboid> I never considered putting the image on a USB. That's a good idea but then again we do update it frequently
| |
| 13:45 | <alkisg> Depending on some things, updating the image over the internet automatically could again be faster than netbooting
| |
| 13:45 | <danboid> So with the caching, it would be able to check if the LTSP server has a newer image and if it does, it downloads that?
| |
| 13:46 | <alkisg> Yeah; and it's possible to either "wait until it's done", or "use the available image, and prompt for reboot when the new has finished downloading"
| |
| 13:46 | A bit of scripting would be needed in either case, it's not automated
| |
| 13:50 | Additionally, wireguard could be used to implement a low-level VPN and make things safer for everyone
| |
| 13:51 | Finally, it's also possible to instruct users to use virtualbox and netboot an LTSP fat client inside their OS. But this requires that they have hardware virtualization and enough RAM.
| |
| 13:52 | <danboid> OK great. There are more options than I thought then
| |
| 14:35 | Teridon1 has joined IRC (Teridon1!~Teridon@dragon.teridon.com) | |
| 14:36 | Teridon has left IRC (Teridon!~Teridon@dragon.teridon.com, Ping timeout: 256 seconds) | |
| 14:44 | Talikka has joined IRC (Talikka!uid18862@gateway/web/irccloud.com/x-ykevneiysowctfry) | |
| 14:53 | woernie has left IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Ping timeout: 258 seconds) | |
| 14:53 | woernie has joined IRC (woernie!~werner@p5DDEC5BE.dip0.t-ipconnect.de) | |
| 15:35 | eu^172-12-54-168 has joined IRC (eu^172-12-54-168!ac0c36a8@172-12-54-168.lightspeed.bcvloh.sbcglobal.net) | |
| 15:50 | danboid has left IRC (danboid!~ISDADS\sg@cpc126962-macc4-2-0-cust227.1-3.cable.virginm.net, Quit: Leaving) | |
| 15:57 | eu^172-12-54-168 has left IRC (eu^172-12-54-168!ac0c36a8@172-12-54-168.lightspeed.bcvloh.sbcglobal.net, Remote host closed the connection) | |
| 16:26 | shored has left IRC (shored!~shored@87-92-92-55.bb.dnainternet.fi, Read error: Connection reset by peer) | |
| 16:30 | shored has joined IRC (shored!~shored@87-92-92-55.bb.dnainternet.fi) | |
| 18:30 | statler has left IRC (statler!~Georg@p5B30E178.dip0.t-ipconnect.de, Quit: cu) | |
| 18:33 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
| 19:11 | woernie has left IRC (woernie!~werner@p5DDEC5BE.dip0.t-ipconnect.de, Ping timeout: 240 seconds) | |
| 19:12 | woernie has joined IRC (woernie!~werner@p5DDEC5BE.dip0.t-ipconnect.de) | |
| 19:27 | RaphGro has left IRC (RaphGro!~raphgro@fedora/raphgro, Quit: Please remember your own message. It'll be read as soon as possible.) | |
| 22:06 | mgariepy has left IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy, Ping timeout: 265 seconds) | |
| 23:35 | vagrantc_ has joined IRC (vagrantc_!~vagrant@unaffiliated/vagrantc) | |
| 23:35 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
| 23:35 | vagrantc_ is now known as vagrantc | |