LTSP 5 is in minimal maintenance mode
The new LTSP is hosted at https://ltsp.github.io

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


Channel log from 25 January 2019   (all times are UTC)

01:07mwalters has left IRC (mwalters!~ubox@c-73-152-61-86.hsd1.va.comcast.net, Ping timeout: 244 seconds)
01:10mwalters has joined IRC (mwalters!~ubox@c-73-152-61-86.hsd1.va.comcast.net)
06:24kjackal has joined IRC (kjackal!~quassel@2a02:587:3101:f300:11c8:94ba:36fa:6264)
06:55
<alkisg>
mwalters: from what I can see, the problem with the uefi clients not requesting any files, was because I was offering both pxe-service and dhcp-boot. Those need to be separated; real dhcp gets dhcp-boot and proxydhcp gets pxe-service.
06:55
I think that's actually a bug in dnsmasq, but anyway that ^ workaround solves it
07:58ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
08:44alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
08:51alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
08:59alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
09:39GodFather has left IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net, Read error: Connection reset by peer)
09:40GodFather has joined IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net)
10:56Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)
11:44uumas has joined IRC (uumas!~uumas@2a00:1d50:3:0:1d39:db65:e957:4264)
11:59
<uumas>
Is there a way to prevent people from connecting to the ltsp server through ssh, but still let them sign in to the clients?
12:00
<alkisg>
Do you mean fat clients?
12:00
<uumas>
Yes
12:00
<alkisg>
You can allow ssh logins only from local subnet and only for specific users
12:00
If that's not enough, set LDM_SERVER elsewhere, e.g. in a vm,
12:01
and, it's also possible to use chroots in ssh, although more difficult to setup
12:01
The LDM login manager doesn't support anything other than ssh
12:02
<uumas>
Okay, would it be possible to use another login manager and login "locally"
12:02
We have authentication through LDAP
12:02
<alkisg>
No, ltsp doesn't support other display managers
12:02
Well...
12:02
you could, if you rewrote that part of lstp
12:02
if you know programming, you should be able to do it within a couple of days
12:03
<uumas>
Okay, well, that sounds like quite a bit too much trouble then.
12:04
What harm could a normal user cause on the server. One thing that comes to my mind is fork bombs, but is there anything else?
12:10kjackal has left IRC (kjackal!~quassel@2a02:587:3101:f300:11c8:94ba:36fa:6264, Ping timeout: 240 seconds)
12:33uumas has left IRC (uumas!~uumas@2a00:1d50:3:0:1d39:db65:e957:4264, Ping timeout: 268 seconds)
12:35kjackal has joined IRC (kjackal!~quassel@2a02:587:3101:f300:11c8:94ba:36fa:6264)
13:02kjackal has left IRC (kjackal!~quassel@2a02:587:3101:f300:11c8:94ba:36fa:6264, Ping timeout: 240 seconds)
13:18josefig has left IRC (josefig!~jose@unaffiliated/josefig, Ping timeout: 240 seconds)
13:35
<mwalters>
they'll be confined to their own userspace... they could fill up /home, I guess? They could do that from their own client regardless, though
13:35
alkisg: I'll take a look at that, thanks
13:40
oh, so you're saying that bios clients don't need the pxe-service line?
13:40
(for X86PC)?
13:41
I think I'm more confused now, sorry. :D
15:10spaced0ut has joined IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut)
15:36
<alkisg>
mwalters: are you using proxydhcp or real dhcp?
15:36
<mwalters>
real dhcp
15:36
<alkisg>
Then don't put any pxe-service lines at all
15:36
<mwalters>
(e.g., my ltsp servers are the dhcp servers, proper)
15:36
<alkisg>
For any client (except raspberries, if you have)
15:36
<mwalters>
thanks, I'll try that
15:36
<alkisg>
np
15:48
<mwalters>
that worked, thanks!
15:48
I lost so much hair over that one
15:50
<alkisg>
Me too :)
15:50
Hours and hours, until the bulb was lighted over my head
15:51
<mwalters>
hah! The one day I had made waaaay too many changes in the conf and it worked... so I knew it was at least a config issue... but I never could narrow it back down, lol
16:23kjackal has joined IRC (kjackal!~quassel@ppp-94-66-220-141.home.otenet.gr)
16:52bcg has left IRC (bcg!~b@dsl-tkubng11-54f942-246.dhcp.inet.fi, Ping timeout: 268 seconds)
16:54kjackal has left IRC (kjackal!~quassel@ppp-94-66-220-141.home.otenet.gr, Ping timeout: 272 seconds)
16:59kjackal has joined IRC (kjackal!~quassel@ppp-94-66-220-141.home.otenet.gr)
17:20kjackal has left IRC (kjackal!~quassel@ppp-94-66-220-141.home.otenet.gr, Ping timeout: 240 seconds)
17:23kjackal has joined IRC (kjackal!~quassel@ppp-94-66-220-141.home.otenet.gr)
19:17JuJUBee has joined IRC (JuJUBee!~knichel@24.105.212.11)
19:18
<JuJUBee>
so I originally setup ltsp as dual nic, but I have not been able to finish everything else and need it to be single nic. How do I switch?
19:20
DO I just re-run ltsp-config dnsmasq ? what about iptables?
19:25JuJUBee has left IRC (JuJUBee!~knichel@24.105.212.11, Ping timeout: 245 seconds)
19:37JuJUBee has joined IRC (JuJUBee!~knichel@24.105.212.11)
19:37
<JuJUBee>
so I originally setup ltsp as dual nic, but I have not been able to finish everything else and need it to be single nic. How do I switch?
19:43mgariepy has joined IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy)
19:48Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving)
19:59
<JuJUBee>
My clients are able to boot and connect to internet now, but my ltsp server has not internet access. I set the default gw in network-manager for the interface connected to the lan.
20:00
<Hyperbyte>
JuJUBee, your problem is not ltsp related.
20:01
Just debug your internet connection on the server. Check your network configuration, ping the next gateway, traceroute, etc.
20:01
Use any guide online to troubleshoot internet connection on Linux.
20:01
<JuJUBee>
There is no default gw for some reason when I "ip route" or route -n
20:02
When I configured ltsp originally I used dual nic config, but now I am only using a single nic until I can finish setting everything else up (web server etc....)
20:09
<mwalters>
https://linuxconfig.org/how-to-configure-static-ip-address-on-ubuntu-18-04-bionic-beaver-linux
20:09
this should help, like Hyperbyte said, this isn't specific to LTSP
20:10
(assuming you're using 18.04/ubuntu
20:10
)
20:25mgariepy has left IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy, Quit: Leaving)
20:38JuJUBee has left IRC (JuJUBee!~knichel@24.105.212.11, Quit: Leaving)
23:29spaced0ut has left IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut, Quit: Leaving)
23:41adrianor1 has left IRC (adrianor1!~adrianorg@187.115.105.202, Ping timeout: 250 seconds)
23:42adrianorg has joined IRC (adrianorg!~adrianorg@187.115.105.202)
23:46ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Remote host closed the connection)
23:56||cw has left IRC (||cw!~chrisw@unaffiliated/cw/x-1182934, Quit: Do not follow the null pointer, for therein lies ma&^%#___)