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


Channel log from 23 February 2015   (all times are UTC)

00:08
<Bruckner2_>
Hi?
00:18gbaman has joined IRC (gbaman!~gbaman@host81-148-160-23.in-addr.btopenworld.com)
00:22gbaman has left IRC (gbaman!~gbaman@host81-148-160-23.in-addr.btopenworld.com, Ping timeout: 252 seconds)
01:21gbaman has joined IRC (gbaman!~gbaman@host81-148-160-23.in-addr.btopenworld.com)
01:26gbaman has left IRC (gbaman!~gbaman@host81-148-160-23.in-addr.btopenworld.com, Ping timeout: 256 seconds)
02:45telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
02:46telex has joined IRC (telex!teletype@freeshell.de)
03:24gbaman has joined IRC (gbaman!~gbaman@host81-148-160-23.in-addr.btopenworld.com)
03:29gbaman has left IRC (gbaman!~gbaman@host81-148-160-23.in-addr.btopenworld.com, Ping timeout: 250 seconds)
03:56cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 245 seconds)
03:57cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
04:11
<Bruckner2_>
Hello
05:00Bruckner2_ has left IRC (Bruckner2_!4b451a7c@gateway/web/freenode/ip.75.69.26.124, Ping timeout: 246 seconds)
05:27gbaman has joined IRC (gbaman!~gbaman@host81-148-160-23.in-addr.btopenworld.com)
05:32gbaman has left IRC (gbaman!~gbaman@host81-148-160-23.in-addr.btopenworld.com, Ping timeout: 264 seconds)
06:27Fenuks has joined IRC (Fenuks!~Fenuks@212.164.162.221)
06:28gbaman has joined IRC (gbaman!~gbaman@host81-148-160-23.in-addr.btopenworld.com)
06:32gbaman has left IRC (gbaman!~gbaman@host81-148-160-23.in-addr.btopenworld.com, Ping timeout: 245 seconds)
06:58mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk)
07:26khildin has joined IRC (khildin!~khildin@ip-83-134-135-195.dsl.scarlet.be)
08:17bojan has joined IRC (bojan!75ca5860@gateway/web/freenode/ip.117.202.88.96)
08:17
<bojan>
can i configure NIS on LTSP??
08:27bojan has left IRC (bojan!75ca5860@gateway/web/freenode/ip.117.202.88.96, Quit: Page closed)
08:56khildin has left IRC (khildin!~khildin@ip-83-134-135-195.dsl.scarlet.be, Ping timeout: 245 seconds)
09:05fgth has joined IRC (fgth!~fsoyer@LNantes-156-76-22-111.w82-127.abo.wanadoo.fr)
09:05
<fgth>
Hi all
09:11
Does someone know if there is a solution to have thin clients on a ltsp server with two networks card (one ltsp private LAN and one global LAN with internet access), but the thin clients having only access on the first net (private LAN), just using the server as router for internet access (I mean, no access at all to the global LAN resources, only internet) ? Any tutoriel URL if yes ?
09:44feanorsam has joined IRC (feanorsam!984dcbe2@gateway/web/freenode/ip.152.77.203.226)
10:27Fenuks has left IRC (Fenuks!~Fenuks@212.164.162.221, Read error: Connection reset by peer)
11:01work_alkisg has left IRC (work_alkisg!~alkisg@srv1-dide.ioa.sch.gr, Quit: Leaving.)
11:02ricotz has joined IRC (ricotz!~rico@ubuntu/member/ricotz)
11:23work_alkisg has joined IRC (work_alkisg!~alkisg@clnt-dide.ioa.sch.gr)
11:26work_alkisg is now known as alkisg
11:52alkisg has left IRC (alkisg!~alkisg@clnt-dide.ioa.sch.gr, Quit: Leaving.)
12:20khildin has joined IRC (khildin!~khildin@ip-83-134-135-195.dsl.scarlet.be)
12:20work_alkisg has joined IRC (work_alkisg!~alkisg@clnt-dide.ioa.sch.gr)
12:20
<work_alkisg>
!arcfour
12:20
<ltsp`>
arcfour: http://en.wikipedia.org/wiki/RC4 is an SSH cipher which is more than 2 times faster than the default aes128-ctr. To enable it, set LDM_SSHOPTIONS="-o Ciphers=arcfour128".
12:32work_alkisg has left IRC (work_alkisg!~alkisg@clnt-dide.ioa.sch.gr, Quit: Leaving.)
12:37ricotz has left IRC (ricotz!~rico@ubuntu/member/ricotz, Quit: Ex-Chat)
12:45telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
12:46telex has joined IRC (telex!teletype@freeshell.de)
12:46muppis_ is now known as muppis
13:04shogunx has left IRC (shogunx!~shogunx@rrcs-67-79-182-229.se.biz.rr.com, Ping timeout: 264 seconds)
13:04shogunx has joined IRC (shogunx!~shogunx@rrcs-67-79-182-229.se.biz.rr.com)
13:27cliebow has joined IRC (cliebow!~cliebow@gw-rsu24-co.rsu24.org)
13:28shogunx has left IRC (shogunx!~shogunx@rrcs-67-79-182-229.se.biz.rr.com, Ping timeout: 252 seconds)
13:30Faith has joined IRC (Faith!~paty@unaffiliated/faith)
13:30shogunx has joined IRC (shogunx!~shogunx@rrcs-67-79-182-229.se.biz.rr.com)
13:53shogunx has left IRC (shogunx!~shogunx@rrcs-67-79-182-229.se.biz.rr.com, Ping timeout: 240 seconds)
13:57shogunx has joined IRC (shogunx!~shogunx@rrcs-67-79-182-229.se.biz.rr.com)
14:43shogunx has left IRC (shogunx!~shogunx@rrcs-67-79-182-229.se.biz.rr.com, Ping timeout: 255 seconds)
14:44shogunx has joined IRC (shogunx!~shogunx@rrcs-67-79-182-229.se.biz.rr.com)
15:06mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving)
15:08shogunx has left IRC (shogunx!~shogunx@rrcs-67-79-182-229.se.biz.rr.com, Ping timeout: 255 seconds)
15:08shogunx has joined IRC (shogunx!~shogunx@rrcs-67-79-182-229.se.biz.rr.com)
15:30shogunx has left IRC (shogunx!~shogunx@rrcs-67-79-182-229.se.biz.rr.com, Ping timeout: 246 seconds)
15:43shogunx has joined IRC (shogunx!~shogunx@rrcs-67-79-182-229.se.biz.rr.com)
16:11gbaman has joined IRC (gbaman!~gbaman@dab-crx1-h-1-2.dab.02.net)
16:40gbaman has left IRC (gbaman!~gbaman@dab-crx1-h-1-2.dab.02.net, Ping timeout: 250 seconds)
16:53gbaman has joined IRC (gbaman!~gbaman@dab-hlw1-h-48-10.dab.02.net)
16:58fgth has left IRC (fgth!~fsoyer@LNantes-156-76-22-111.w82-127.abo.wanadoo.fr)
17:17stevecook has joined IRC (stevecook!97e3a8d2@gateway/web/freenode/ip.151.227.168.210)
17:17ricotz_ has joined IRC (ricotz_!~rico@ubuntu/member/ricotz)
17:19gbaman has left IRC (gbaman!~gbaman@dab-hlw1-h-48-10.dab.02.net, Ping timeout: 244 seconds)
17:19
<stevecook>
good afternoon. Steve Cook here. I have set up and have got running an ltsp server and client on ubuntu 14. I have had considerable diofficulty getting it up[ and running. I initially followed this instruictional (https://www.thefanclub.co.za/how-to/how-create-ubuntu-1104-x64-ltsp-server-32bit-thin-clients). It works, but i have had to do some extra stuff:
17:20
Firslty, I had to copy the ltsp dhcp config over to the etc/dhcp config file. Unless it was in there as well, it would not work. Secondly, I have to have a non ltsp client machine physically linked to eth0 in order for my dhcpd and tft servers to start. I start them with a startyup script on the server....continied....
17:22
Obviously, i have to start the client machine first, so the server has got an active connection from bootup, otherwise the dhcpd server will fail to start. Hasving once started the servers in the way described, i then fire up a virtualbox VM ltsp client on the server and it boots successfully. Once it is booted, I can disconnet the bare metal full fat client, I mentuioned earlier. From this point, any ltsp client connected to eth0
17:24
If I tried to start the vm ltsp client before an active connection was established witht he full fat bare metal client, it would fail for the reasons alreasdy given. However once load, and kep open, the ltsp Vm client keeps the dhcpd server connection alive for any ohher eal world ltsp clients. It's a bit messy, but it works.....continued....
17:26
what I am wanting to fix is a way for some kind of fake eth0 connection to be establised at bootup so that I can start th servers and they wont fail because they will "think" that the connection is active and so will start. At whiich point, any other ltsp client should boot. Indeed, it may evebn mean i don;t need the Vm ltsp clinet as a "seed" client to keep the dhcpd connection alive.
17:26
any advice folks?
17:34
i should add, for completeness, when i say, that without the full fat client machine being cionnected at bootup on eth0, the dhcpd server "fails", what i mean is that is does not "appear" to fail.. That is to sday, it gives the "OK" as if it has started. Howeever, the ltsp client will not boot and will not recive an address. Only when i boot the dhcpd server with a normal machine attached to eth0, will the ltsp vm client boot.
18:03
<cliebow>
stevecook:everyone must be busy..I d bet someone will answer..I have the same problemwith deploystudio..
18:11gbaman has joined IRC (gbaman!~gbaman@31.205.104.150)
18:14
<stevecook>
Hi cliebow...i do hope so mate...:)
19:06vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
19:08khildin has left IRC (khildin!~khildin@ip-83-134-135-195.dsl.scarlet.be, Remote host closed the connection)
19:14telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
19:14telex has joined IRC (telex!teletype@freeshell.de)
20:19
<gbti>
stevecook: there is no way to "fake" an eth connection.
20:51stgraber has left IRC (stgraber!~stgraber@ubuntu/member/stgraber, Ping timeout: 250 seconds)
20:58stgraber has joined IRC (stgraber!~stgraber@2001:470:b368:1000:1::1)
20:59stgraber has joined IRC (stgraber!~stgraber@ubuntu/member/stgraber)
21:08
<stevecook>
okay gbti, thanks for that. However, I would question your flat statement. That is to say, a physical connection is a physical connection and, short of making a physical change, you indeed "can't" face that physical connection. However, a dhcp server is not a physical connection. It is a piece of software. And any software can be modified
21:09
But, given what you have said, how then do I get the ltsp dhcp server to start in preparation for an ltsp client booting. I ask this becasue this is precisely what was possible up to Ubuntui 12.04. it was only from Ubuntu 13 that this was no longer possible. Even the latest 12.04 ISO's now have this problem. So, Canonical must have done something both retrospectively to as far back, at least, as 12.04 and certainly up to the presen
21:10
"face" should have read as "force"
21:13gbaman has left IRC (gbaman!~gbaman@31.205.104.150, Remote host closed the connection)
21:14gbaman has joined IRC (gbaman!~gbaman@31.205.104.150)
21:14
<stevecook>
Or, failing being either able to fake a connection, nor being able to fix the issue any other way in terms of configuration settings on thre server, is it possble to fit some kind of small, portable, "always on" device, other than an ectual external PC between the server and the clients. Thus, the clients would then be able to access a live eth0 via this intermediary device.
21:16ricotz_ has left IRC (ricotz_!~rico@ubuntu/member/ricotz, Quit: Ex-Chat)
21:16
<stevecook>
does a network switch act in such a way that it will trigger the eth0 to allow the dhcp server to start properly? If so, then this would be trivially solved by putting that in place. the face is, at ther moment, I am only in testing phase and so have my server and clinet directly wired together. but, eventually, i will have about three clients, in turn requyring a switxch in any event
21:17
"face" should read as "fact"
21:19gbaman has left IRC (gbaman!~gbaman@31.205.104.150, Ping timeout: 272 seconds)
21:24gbaman has joined IRC (gbaman!~gbaman@31.205.104.150)
21:25vmlintu has left IRC (vmlintu!~vmlintu@a91-152-200-70.elisa-laajakaista.fi, Ping timeout: 264 seconds)
21:37andygraybeal has left IRC (andygraybeal!~andy@h192.185.190.173.dynamic.ip.windstream.net, Ping timeout: 264 seconds)
21:52alkisg has joined IRC (alkisg!~Thunderbi@ubuntu/member/alkisg)
21:54
<alkisg>
stevecook: so the problem is that dhcpd doesn't start automatically unless you do a lot of workarounds?
21:55psion13 has left IRC (psion13!~psion13@etamail.etatechservice.com, )
21:58
<stevecook>
precisely so, alkisg. In ubuntu 12.04, as soon as ltsp was installed and all config files were set, I could simply issue the dhcd server restart command, with no clients currently loaded. at which point i vould then boot up a client and get stringt into an ltsp session. now, if I issue the dhcp server restyart command, it "looks" like it is restarting. That is to say, it give the "OK" output. but, it has not restarted thus requirin
21:59
<alkisg>
Your sentence was cut in half, type enter more frequently
21:59
"That is to say, it give the "OK" output. but, it has not restarted thus requirin"
21:59
<stevecook>
thus requiring workarounds
21:59
already mentioned upthread
21:59
<alkisg>
The step 4 in the guide you followed isn't appropriate
22:00
It's better to not define an interface name in dhcpd conf
22:00
<stevecook>
ah..okay, Let me jusrt pull it up.....
22:00
<alkisg>
Also, you can use a network-manager static connection instead of /etc/network/interfaces if you want
22:01
<stevecook>
if you mean the managed "true" statement, i should have mentioned, I've set that to false, othrwise nothing happend at all
22:01
Please xplain the network manager static function
22:02
<alkisg>
There are some issues with the guide you followed... it's hard to correct it step by step though
22:02
It's better to follow one of the guides in the wiki...
22:02
<stevecook>
ah right, you mean the dhcp.conf
22:03
<alkisg>
In 1b, the guide says "use network manager"
22:04
In 1c, it says "use /etc/network/interfaces
22:04
...it's not a good guid
22:04
e
22:04
<stevecook>
The guides int he wiki, though, nearly always have certasin assumptions in them of a certian level of knowlefe on given items. That is to saym,t hey are not explicit enough. The reason i have always used this guide is because it is precisely that. Exoplict,. and has always worked on my previous ubuntu installation. I only jusdt recently migrarted form 12,04 to 14
22:04
it was aperfect guide up till 12.04. I know becasue i impk,enented it flawlessly serveral times
22:05
<alkisg>
Well, I'm pointing that 1b is incompatible with 1c, so no it's not perfect
22:05
It just happened to work for you and the author in certain setups :)
22:06
<stevecook>
It worked for me anthe aithor in a setup invo0,ving an eth0 and wlan0. for me, as well, ion several different machine. that, i would suggest, is the most common cofiguration around, is it not?
22:07
<alkisg>
2 nics is pretty common, sure. Wlan for the second nic isn't very common. Single nic setups are very common too.
22:07
<stevecook>
in any event, i do accept it is not perfect now
22:07
<alkisg>
Suggesting to use both /etc/network/interfaces and network-manager is plain wrong though
22:07
<stevecook>
but that is less to do with setups chaging and more to do with something changing in either ltsp or ubuntu. Ubuntu would be my guess
22:07
Wrong or otherwise, it plainly worked, as i can attest, until ubuntu 12.04
22:08
<alkisg>
Yes, wrong solutions happen to work in some circumstances, and break in others
22:09
It's best not to follow them :)
22:09
So, decide what you want to use, network-manager or interfaces, and use it
22:09
The author says "For some mysterious reason if you enter the IP manually in the interfaces file, Network Manager ignores them"...
22:09
...that's because he didn't understand what he was doing...
22:10
<stevecook>
A single wired and a single wireless conection on a desktop is not common? Netowrk manager, alone does not work. Interfaces alone, does not work. I know this becasue the author mentione dprecisely that and I also know this becasue i tried it sperately on both
22:10
<alkisg>
I do know that network-manager alone works here in 1000 schools
22:11
I've also tried /etc/network/interfaces alone, it works fine too
22:12
<stevecook>
Okay, well i am happy fgor you that you have 100 schools sucessfully running ltsp with your current setup. Meanwhile are you able to offer any contructive advice as tyo how my problem may be addressed
22:12
<alkisg>
Yes, I already adviced this: "So, decide what you want to use, network-manager or interfaces, and use it"
22:12
Which one do you want to use?
22:13
Decide first, then undo the other steps as appropriate
22:13
E.g. if you decide to use nm, undo the changes to interfaces
22:13
and to managed=true etc
22:13
<stevecook>
I have already done prescisely that, as I have already mentioned. I f I do that, then the dhcp server not only loads, incorrectly, It fails
22:13
<alkisg>
OK, so, you've decided to use network-manager?
22:15
What I'm proposing is, select one method, undo all other changes, and then we can start asking you for feedback
22:15
E.g. run that command and tell us the output, or put that file into pastebin...
22:15
Now we can't ask for feedback because you haven't selected which method to use
22:16
<stevecook>
I have already done the combination of interfaces alone, with management to false/true, network manager alone with management fale/true. both of them with management to false/true. the only combination thaty works, has been both of them with management to fales. at least on my current setup. On the previous 12.04 setting it was set to true in order to wrok
22:16
I will do that and get back t you, thanks
22:17
<alkisg>
I understand that you've tried several things, but in order to troubleshoot something, you need to focus on it
22:18
So, to troubleshoot "why dhcpd isn't starting when i use nm", you need to minimize the other changes, to /etc/network/interfaces, to /etc/default/isc-dhcp-server, to NetworkManager.conf etc
22:19
In other words, if I just install dhcpd now and change the internal subnet in dhcpd.conf to 192.168.67.x and try to start it, it will just start, without me having to change other things...
22:20
When you're done with reverting the changes, do put the aforementioned files (and any other related files you think you have changed) to pastebin
22:24* alkisg notes that he'll be leaving soon though... it's kinda late here
22:24
<stevecook>
alkisg, I am going to reboot both the server now as well as the client. so , I going offline for a minute. Befor ei do, thoug, iorrespe4ctive of whetehr this works, i owe you an apology for being rude,I;'ve jst been at this for three days, no excuse though
22:25
<alkisg>
stevecook: no problem, if you want help i'll be online in ~7h
22:27stevecook has left IRC (stevecook!97e3a8d2@gateway/web/freenode/ip.151.227.168.210, Quit: Page closed)
22:28alkisg has left IRC (alkisg!~Thunderbi@ubuntu/member/alkisg, Quit: alkisg)
22:37doctari has joined IRC (doctari!~doctari@2602:30a:2ccf:9f00:bcc4:b053:8578:5a1e)
22:39doctari_ has left IRC (doctari_!~doctari@2602:30a:2ccf:9f00:7537:6bab:2c67:d143, Ping timeout: 250 seconds)
22:56Faith has left IRC (Faith!~paty@unaffiliated/faith, Quit: Saindo)
23:25map7_ has joined IRC (map7_!~map7@ppp118-209-57-52.lns20.mel4.internode.on.net)
23:41gbaman has left IRC (gbaman!~gbaman@31.205.104.150, Remote host closed the connection)
23:52vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)