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


Channel log from 8 April 2011   (all times are UTC)

00:29Da-Geek (~Da-Geek@nat/redhat/x-mjyhuqvoknrsqszg) joined #ltsp.
00:47dobber (~dobber@89.190.197.77) joined #ltsp.
00:48Lns (~Lns@pdpc/supporter/professional/lns) left irc: Quit: Leaving
00:51bobby_C (~bobby@85-124-22-227.teleworker.xdsl-line.inode.at) joined #ltsp.
01:23viks (ca8a720f@gateway/web/freenode/ip.202.138.114.15) joined #ltsp.
01:23
<viks>
#ulteo
01:30ogra_ (~ogra@p5098ed03.dip0.t-ipconnect.de) left irc: Excess Flood
01:30Trixboxer (~Trixboxer@office.supportdepartment.net) joined #ltsp.
01:31ogra_ (~ogra@p5098ed03.dip0.t-ipconnect.de) joined #ltsp.
01:45toscalix (~toscalix@47.Red-95-126-186.staticIP.rima-tde.net) joined #ltsp.
02:15komunista (~slavko@adsl-195-098-013-196.dynamic.nextra.sk) joined #ltsp.
03:09cyberorg (~cyberorg@opensuse/member/Cyberorg) left irc: Read error: Connection reset by peer
03:13cyberorg (~cyberorg@opensuse/member/Cyberorg) joined #ltsp.
03:14toscalix (~toscalix@47.Red-95-126-186.staticIP.rima-tde.net) left irc: Ping timeout: 246 seconds
03:30mum (ca8a7259@gateway/web/freenode/ip.202.138.114.89) left irc: Quit: Page closed
03:56
<Hyperbyte>
Hrm... I have a USB DVD-drive, I was hoping LTSP would mount it as local media, just like it does with USB sticks
03:56
Doesn't seem to do it though. Any tips on how I can get it to treat it as local media?
03:59
It works on the terminal, I can mount /dev/scd0 correctly. I just need it to appear inside the UI.
05:01viks (ca8a720f@gateway/web/freenode/ip.202.138.114.15) left irc: Ping timeout: 252 seconds
05:17Nick change: zz_evil_root -> evil_root
05:19FrozenZia (~paulvbrow@GYGMMLXII.gprs.sl-laajakaista.fi) joined #ltsp.
05:20
<FrozenZia>
hola - networking question - trying to setup my ltsp server at home following some directions which call for a router/switch, but I'm trying to use an ADSL modem / router in it's place, and I'm wondering if it's even possible...
05:21
It's a bit convoluted, 'cuz my internet connection is via my laptop (wireless broadband), then I
05:22
've got Firestarter fired up, with internet connection sharing on.
05:25
<muppis>
If you can disable DHCP from modem, then it should be fine use it as router.
05:26
<FrozenZia>
Yeah, that's no problem.
05:26
But for instance just now i tried to ping from the modem to my laptop = OK,
05:27
ping from the modem to "the world" (8.8.8.8) = NOK
05:27
that'd seem (to me) to indicate something wrong with my connection sharing set up?
05:27
<muppis>
Enable NAT / Connection sharing from laptop.
05:28
<FrozenZia>
seems to be on (according to firestarter settings)
05:28
But then, I've mostly used it with having dhcp server *also* on in firestarter, and currently I've got that turned off.
05:30
(b/c wouldn't it then effectively "bleed" thru the router and affect anything that got plugged into it?
05:30
)
05:31
<muppis>
What cat /proc/sys/net/ipv4/ip_forward gives ?
05:33
<FrozenZia>
1
05:33
<muppis>
That's good.
05:33FrozenZia1 (~paulvbrow@GYGMMLXII.gprs.sl-laajakaista.fi) joined #ltsp.
05:33
<FrozenZia>
that wasn't too short of an answer?
05:34
<muppis>
Nope, it's just right.
05:34FrozenZia (~paulvbrow@GYGMMLXII.gprs.sl-laajakaista.fi) left irc: Quit: leaving
05:35
<FrozenZia1>
still here...
05:35Nick change: FrozenZia1 -> FrozenZia
05:36
<muppis>
It means IPv4 forwarding is enabled, so it's only from frewall rules.
05:41
<FrozenZia>
hmmm... wonder if this matters - I have a broswer window open in the laptop,
05:41
and am looking at the router uter from there.
05:42
then sending a "ping" thru the web-admin interface of the router to my laptop
05:42
That goes thru fine.
05:42
The ping 1 machine further up the chain, however, doesn
05:42
't
05:43
And firestarter doesn't alert of any incoming hits.
05:45
<muppis>
So you can't ping your client?
05:46
<FrozenZia>
Oh, i don't even have a client here yet - I'm just trying to see if I can even get the server set up with internet access and proper ip addresses and such to start with.
05:47brunolambert (~brunolamb@gw-sherb.rlnx.com) joined #ltsp.
05:49
<FrozenZia>
muppis: if I change the question a bit, maybe it's more of a direct question and easier to answer:
05:49tastle73 (~tom@sarge.pcc.com) joined #ltsp.
05:50
<FrozenZia>
If I do a fresh install of e.g. 10.04 (alternate CD), installing the ltsp-server,
05:50
and tell it that eth0 is my connection to the internet,
05:51
does eth0 get automagically set up with a fixed address or DHCP?
05:52
The instructions i
05:52
<muppis>
During installation it tries DHCP, but it fails it will ask what to do, so you can leave it unconfigured if you want.
05:53
<FrozenZia>
Ok, the instructions I'm trying to follow (http://wiki.ubuntu-fi.org/LTSP5_Perusasennus)
05:53
<muppis>
Or define fixed address also.
05:53
<FrozenZia>
have an ADSL modem with DHCP on, then a router/switch with DHCP OFF, then the LTSP server.
05:54brunolambert (~brunolamb@gw-sherb.rlnx.com) left irc: Quit: brunolambert
05:54
<FrozenZia>
I presome that for the LTSP server (internet connection side), I need to define: ip address, subnet mask, broadcast, and a couple of dns's?
05:55
<muppis>
If you use your 3G (like you do now) for connection, you don't need to.
05:56
<FrozenZia>
And according to what I've understood, if I handle this all correctly during the initial setup, I should be good to go, with no extra configurating worries.
05:56brunolambert (~brunolamb@2001:470:8829:1000:221:6aff:fe94:21d8) joined #ltsp.
05:56
<FrozenZia>
hmmm...
05:57
<muppis>
But I need to go now. Hope someone else here can help you out.
05:57
<FrozenZia>
right now my laptop is using my 3G, connected by wire to a ZyXEL adsl-modem, and then the server would be connected to the modem.
05:57
muppis: thanks for this much1
05:58
!
05:58
<Hyperbyte>
FrozenZia: what exactly is the function of the ADSL router in your network?
05:59
I've been reading along since ^^ way up there, but never quite got the logic between your network infrastructure.
06:05garymc (~chatzilla@host81-139-133-67.in-addr.btopenworld.com) joined #ltsp.
06:06
<FrozenZia>
Hyperbyte: good question.
06:07
The function of *my* ADSL router is that I found one at a flea market for 4 euros, and I'm trying to use it as the missing piece of hardware in my set up.
06:13
I'm trying to configure this server so I can take it to a school pre-configured, but until we have permission to plug it in to the school network, I think we'll have to "pretend" we have internet access by using my laptop and my 3G connection, so I'm just trying to mimic that configuration.
06:13
well, not even mimic, this *IS* the setup we would have.
06:15
I want to have the 64-bit server version anyway, so once I've got it downloaded I'm gonna try the install again with that...
06:29Da-Geek (~Da-Geek@nat/redhat/x-mjyhuqvoknrsqszg) left irc: Quit: Leaving
06:31drdata (~drdata@tw2.udallas.edu) joined #ltsp.
06:32
<Hyperbyte>
So the LTSP server would have two NIC's, one with internet and one with clients?
06:32
And it would act as DHCP server and router?
06:32
Right?
06:34
<FrozenZia>
Hyperbyte: exactly
06:37rad4Christ (~rad4Chris@165.166.57.122) joined #ltsp.
06:39
<Hyperbyte>
Well that's easy enough... where exactly are you at now?
06:40
(with the installation that is)
06:50
<FrozenZia>
Right now I
06:51
m (bloody '-key is just too damn close to the enter key on this laptop)
06:52
still waiting for a few minutes for the 64-bit version to download, then it'll take me a few minutes to burn the CD, and then I'll be off and running...
06:52chupacabra (~chupacabr@cpe-70-112-10-45.austin.res.rr.com) left irc: Quit: WeeChat 0.3.3
06:54
<Hyperbyte>
:)
06:59cyberorg (~cyberorg@opensuse/member/Cyberorg) left irc: Ping timeout: 246 seconds
06:59bobby_C (~bobby@85-124-22-227.teleworker.xdsl-line.inode.at) left irc: Quit: Goin' down hard
07:00FrozenZia (~paulvbrow@GYGMMLXII.gprs.sl-laajakaista.fi) left irc: Ping timeout: 248 seconds
07:02FrozenZia (~paulvbrow@GYGCMXC.gprs.sl-laajakaista.fi) joined #ltsp.
07:06tastle73 (tom@sarge.pcc.com) left #ltsp.
07:12ogra_ (~ogra@p5098ed03.dip0.t-ipconnect.de) left irc: Excess Flood
07:12ogra_ (~ogra@p5098ed03.dip0.t-ipconnect.de) joined #ltsp.
07:19
<FrozenZia>
ok, installation in progress, dhcp didn't work, so it's asking me to give the settings by hand -- for the gateway address I should give the router's address that the server is directly plugged into, right?
07:22garymc (~chatzilla@host81-139-133-67.in-addr.btopenworld.com) left irc: Ping timeout: 246 seconds
07:26patrickmw (~pwright@ip68-231-4-153.ph.ph.cox.net) joined #ltsp.
07:32
<Hyperbyte>
FrozenZia: yes
07:34
<FrozenZia>
07:34
sorry.
07:34
I meant to say - good, that's what I did.
07:35cyberorg (~cyberorg@opensuse/member/Cyberorg) joined #ltsp.
07:38
<Hyperbyte>
Heheh
07:38mistik1 (mistik1@unaffiliated/mistik1) left irc: Ping timeout: 276 seconds
07:45mistik1 (mistik1@unaffiliated/mistik1) joined #ltsp.
07:50dobber (~dobber@89.190.197.77) left irc: Remote host closed the connection
07:55
<FrozenZia>
I can't claim to have read all the guides available, so the answer to this may be rtfm, but: AFTER successfully installing an LTSP-server, is there a "guide" for "Now what??!" I s'pose it mostly goes without saying that you need to create some users, then try and hook up a client to your new network and see what happens, try and log on as a "normal" user. Just wondering if there's anything special that should be taken into account when
07:56
<Hyperbyte>
You need to build the client chroot as well and set up your tftpboot directory with lts.conf (maybe that's already done by default)
07:56
See docs. :)
08:03
<FrozenZia>
tx
08:04
not there yet - plenty of installing still to go...
08:13staffencasa (~staffenca@128-193-148-149.oregonstate.edu) joined #ltsp.
08:13gnunux (~emmanuel@194.167.18.244) left irc: Quit: Ex-Chat
08:26patrickmw (~pwright@ip68-231-4-153.ph.ph.cox.net) left irc: Quit: Ex-Chat
08:41
<FrozenZia>
err... Ok, server is now installed and booted, but no internet. Can't even ping my router. Oddly (?), NetworkManager didn't seem to start up by default, and if I look at the NetworkConnections, there are't any listed. ifconfig looks mostly right, though.
08:59rad4Christ (~rad4Chris@165.166.57.122) left irc: Quit: rad4Christ
09:41ry (~ry@static-71-183-64-28.nycmny.fios.verizon.net) left irc: Remote host closed the connection
09:47
<FrozenZia>
Veeeeeery interesting. To be sure I didn't get confused with eth0 and eth1 during setup, I started with a liveCD of Mepis, made note of which NIC was eth0, and labeled it. Seems that what the liveCD considered to be eth0 was not what Ubuntu10.04 considered to be eth0, so my configuration was backwards.
09:54alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
09:54ry (~ry@static-71-183-64-28.nycmny.fios.verizon.net) joined #ltsp.
09:55toscalix (~toscalix@136.Red-95-127-74.staticIP.rima-tde.net) joined #ltsp.
10:01toscalix (~toscalix@136.Red-95-127-74.staticIP.rima-tde.net) left irc: Read error: Connection reset by peer
10:05drdata (~drdata@tw2.udallas.edu) left irc: Ping timeout: 260 seconds
10:31vagrantc (~vagrant@c-24-21-191-93.hsd1.or.comcast.net) joined #ltsp.
10:40alkisg (~alkisg@ubuntu/member/alkisg) left irc: Ping timeout: 246 seconds
10:40FrozenZia (~paulvbrow@GYGCMXC.gprs.sl-laajakaista.fi) left irc: Ping timeout: 264 seconds
10:41FrozenZia (~paulvbrow@YZKMDCCCIV.gprs.sl-laajakaista.fi) joined #ltsp.
10:41
<FrozenZia>
firestarter is on and "internet connection sharing" is checked.
10:42
I'm using a Zyxel adsl-modem as my "router" between "the internet" and my server.
10:43
So my laptop is supposed to be providing the internet.
10:43
I believe my problem at this point is in the laptop w/firestarter.
10:44
LTSP-server can ping the Zyxel, and eth0 of my laptop (connected to the Zyxel)
10:45
Zyxel can also (obviously) ping eth0 of the laptop
10:45
But they can't seem to get past that.
10:47
1 question - should the server be configured to have the ROUTER's IP as gateway, or the router side of the laptop?
10:50
I'm also wondering about the router. All I can seem to configure there is an IP address and a subnet mask. No gateway.
10:50alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
10:50
<FrozenZia>
I figure that's 'cuz normally the router'd be connected via the modem portion to the internet...
10:50
<vagrantc>
FrozenZia: this isn't really an LTSP question, is it?
10:51
FrozenZia: what are you trying to accomplish?
10:52
<FrozenZia>
vagrantc: yeah, I guess you're right - it's a networking question
10:52
Trying to provide my ltsp-server with internet access.
10:54
Just thought maybe some ltsp folks would have experience with crazy network configurations and might be able to shed some light.
10:56
<vagrantc>
stgraber: any idea what to do about this: http://bugs.debian.org/621544
10:57
stgraber: the .la files were introduced in ldm 2.2.x ... i'm not sure what they're for and all that
10:57
alkisg: ^^ ?
10:57
<alkisg>
Hello, looking..
10:57
<vagrantc>
something to do with how the ssh/rdesktop backends were implemented, it hink
10:59* alkisg passes on that one, no clue about what .la files are, and haven't even seen the new ldm backends, will do so in 12.04
11:00
<alkisg>
I can't even find the .la files in the source tree
11:00
<vagrantc>
heh
11:00
they're generated at build time
11:00
<alkisg>
Ah
11:00
<vagrantc>
i guess i could strip them out during the build and see if it still works
11:03chupacabra (~chupacabr@cpe-70-112-10-45.austin.res.rr.com) joined #ltsp.
11:09shogunx (~shogunx@2001:4978:106:1:21e:33ff:fe47:32f5) left irc: Read error: Operation timed out
11:11
<alkisg>
FrozenZia: from what I understand you have a classic 2-nic setup?
11:13
And the only weird part is that you want to put your laptop between the adsl modem and your ltsp server?
11:19shogunx (~shogunx@2001:4978:106:1:21e:33ff:fe47:32f5) joined #ltsp.
11:20Trixboxer (~Trixboxer@office.supportdepartment.net) left irc: Quit: "Achievement is not the end, its the beginning of new journey !!!"
11:20
<FrozenZia>
alkisg: yes, basically
11:20
or wait, no.
11:21
my adsl modem is not actually being used as a modem in this case, just as a router.
11:21
My laptop is "the modem", and the router sits between the laptop and the server.
11:22
then the server has a 2nd nic connected to a switch, to a client...
11:24drdata (~drdata@tw2.udallas.edu) joined #ltsp.
11:25
<alkisg>
FrozenZia: ermmm I don't think I got your setup. So it goes internet => laptop (wired) => laptop (wireless) => adsl modem (wireless) => adsl modem (wired) => ltsp server?
11:26
If so, ...WHY?! :)
11:26
<FrozenZia>
not quite...
11:26
hold on
11:27
internet => laptop (wireless) => laptop (wired) => adsl modem (wired) => ltsp server
11:27
<alkisg>
The adsl modem has a 4-port switch embedded?
11:27
<FrozenZia>
yes.
11:27
<alkisg>
Does it have its dhcp server enabled?
11:28
<FrozenZia>
no.
11:28
<alkisg>
So you're not using it as a router
11:28
You're using it as a switch?
11:28
<FrozenZia>
aha.
11:29
<alkisg>
So, your only problem is how to do internet connection sharing with your laptop?
11:33
FrozenZia: it might be better to describe your school setup that you're trying to duplicate
11:33
There might be a much easier way to do it
11:35
<FrozenZia>
alkisg: sorry - lost the internet connection...
11:36
hold on, brb...
11:41FrozenZia (~paulvbrow@YZKMDCCCIV.gprs.sl-laajakaista.fi) left irc: Ping timeout: 264 seconds
11:42FrozenZia_ (~paulvbrow@GZYKMDXCI.gprs.sl-laajakaista.fi) joined #ltsp.
11:42
<FrozenZia_>
Ok, so yes, basically I
11:42
ve been using internet connection sharing with my laptop in a similar way before, and thought I had a handle on it.
11:43
using Firestarter it's pretty easy and painless.
11:43
Unfortunately that sorta also means I haven't actually had to UNDERSTAND what's going on in the background.
11:43
But yeah, the school setting:
11:44
It's "computer club" once a week, we're trying to make something out of nothing, recycling old pc's and try to make them worth something.
11:45
We will, at a future time, be putting a router/switch in between the school's network and the ltsp-server
11:45
then have a switch/hub that we build the client network on.
11:46
For the time being, I'm wanting to simulate the "school network" with my laptop.
11:46
<alkisg>
And how is your school network currently?
11:51FrozenZia_ (~paulvbrow@GZYKMDXCI.gprs.sl-laajakaista.fi) left irc: Ping timeout: 260 seconds
11:53FrozenZia_ (~paulvbrow@GMMMCCCIII.gprs.sl-laajakaista.fi) joined #ltsp.
11:55
<alkisg>
FrozenZia_: (09:46:56 PM) alkisg: And how is your school network currently?
11:56
<FrozenZia_>
Sorry - did you not see my reply?
11:56
I don't know. Haven
11:56
t had a chance to talk to the admins about that at all.
11:56
<alkisg>
I read your reply about how your school network will be in the future
11:57
Is that what you're trying to duplicate? Or the current school network?
11:58
<FrozenZia_>
Currently I'm just trying to provide "an internet access" to this router/modem so that I can try to configure it (and the server) and prove to myself that I can get it to work once I
11:58
m "on-site"
11:59
<alkisg>
But you're using it only as a switch
11:59
<FrozenZia_>
and I *should* be using it as a router?
12:00
<alkisg>
No. I mean that there's nothing to configure in this router, if you're only using it as a switch
12:00
<FrozenZia_>
Obviously i
12:00
<alkisg>
*if* I understood your setup correctly, you're only trying to make a difficult setup with no reason :)
12:00
The internet-facing NIC of the ltsp server doesn't need any special configuration
12:01
<FrozenZia_>
Awww, c'mon, what better way to spend a Friday nite?
12:01
<alkisg>
When you go to the school, it'll just get an IP from the dhcp server and it'll be ready
12:01
And now you're putting a laptop with internet connection sharing, a router that works as a switch, and trying to make it hard for no apparent reason :)
12:01
(Again, *if* I understood you correctly)
12:01
<FrozenZia_>
alkisg: I'm pretty sure you did.
12:03komunista (~slavko@adsl-195-098-013-196.dynamic.nextra.sk) left irc: Ping timeout: 246 seconds
12:03
<FrozenZia_>
It's just that I've just come back from a workshop where we placed a router between the school network and the ltsp-server to make absolutely sure that we didn't cause any problems, so I've been trying to duplicate that -- apparently with the wrong parts.
12:04* FrozenZia_ sees a glimmer of an "ahaa" light bulb starting to glow...
12:04muppis (muppis@viuhka.fi) left irc: Ping timeout: 260 seconds
12:04
<FrozenZia_>
I think I've just realized what you've been trying to say about the router used as a switch.
12:04muppis (muppis@viuhka.fi) joined #ltsp.
12:05
<alkisg>
A router connects 2 different networks
12:05
A switch connects computers on the same network
12:05komunista (~slavko@adsl-195-168-242-161.dynamic.nextra.sk) joined #ltsp.
12:06
<FrozenZia_>
Yes, and in the case of this modem, the "other" network would be the one at the other end of the MODEM line, not one of the ethernet jacks in the back
12:06
<alkisg>
Right
12:06
And also I don't see a point in putting a router in front of the ltsp server
12:06
<FrozenZia_>
I may still remember that tomorrow.
12:06
<alkisg>
Why did they do that in the workshop?
12:07
<FrozenZia_>
well, having personally caused some problems earlier while experimenting when I put the wrong NIC onto the network, (leading to 2 DHCP servers on the same network)
12:07
I could see the point.
12:08
In fact, as I was doing my setup today, I had the same problem -- what during setup was eth0 seemed to change to eth1 once the machine rebooted.
12:08
<alkisg>
And it's easier to configure a router than to see which nic is eth0 and which one is eth1?
12:08
<FrozenZia_>
No, certainly not.
12:09
<alkisg>
During setup it's a different "installation" than the installed one
12:09
<abeehc>
it's pretty easy to switch the nic back i run into that with vmwaretools often
12:09
<alkisg>
To rename eth0 to eth1 and vice-versa, you edit the names in /etc/udev/rules.d/70-persistent-net.rules
12:09
But usually you won't need to.
12:10
<FrozenZia_>
OK
12:10
<elias_a>
Hey - dudes!
12:10
<FrozenZia_>
alkisg: thanks hugely for your patience and help.
12:10
<alkisg>
You're welcome
12:10
<FrozenZia_>
elias_a: perhaps you'd like to explain why the router during workshops?
12:10
<elias_a>
Greetings from ITK2011 conference, the leading elearning conference in Finland...
12:11
http://www.dailymotion.com/video/xi166e_tux-raid_fun
12:11
FrozenZia_: The router does what?
12:12
<alkisg>
Hahaha nice tux :)
12:12
<FrozenZia_>
On another topic altogether, I've run into the "invalid release file" error while trying to build an i386 image, but it looks like I can find an answer to that elsewhere - lest someone here wants to tell me the easy answer.
12:12
elias_a: never mind - let's not talk about it...
12:13
<elias_a>
FrozenZia_: Are you talking about the workshop @ Raahe?
12:15
<FrozenZia_>
yeah but really - we can talk about it another time. i
12:15
I'm completely "typed-out" on the subject at this point.
12:15
<elias_a>
Ok.
12:20
<FrozenZia_>
Argh. Okay, maybe this isn't so easy this "invalid release file" problem.
12:21
Tried to do sudo ltsp-build-client --arch i386 on a fresh install of Ubuntu 10.04 LTSP-Server install.
12:23
I get I: Retrieving Release, then E: Invalid Release file, no valid components
12:59Nick change: evil_root -> zz_evil_root
13:03brunolambert (~brunolamb@2001:470:8829:1000:221:6aff:fe94:21d8) left irc: Ping timeout: 264 seconds
13:14
<FrozenZia_>
Ok, "invalid release file" error seems to be resolved by simply running updates.
13:21KBme (~KBme@2001:470:1f13:94::3) left irc: Excess Flood
13:21KBme (~KBme@2001:470:1f13:94::3) joined #ltsp.
13:25alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
13:34mgariepy (~mgariepy@ubuntu/member/mgariepy) left irc: Ping timeout: 260 seconds
14:10komunista (~slavko@adsl-195-168-242-161.dynamic.nextra.sk) left irc: Ping timeout: 260 seconds
14:12FrozenZia_ (~paulvbrow@GMMMCCCIII.gprs.sl-laajakaista.fi) left irc: Ping timeout: 276 seconds
14:43ogra_ (~ogra@p5098ed03.dip0.t-ipconnect.de) left irc: Read error: Operation timed out
14:44bobby_C (~bobby@85.124.22.227) joined #ltsp.
14:45ogra_ (~ogra@p5098ed03.dip0.t-ipconnect.de) joined #ltsp.
14:46bobby_C (~bobby@85.124.22.227) left irc: Client Quit
15:13drdata (~drdata@tw2.udallas.edu) left irc: Ping timeout: 260 seconds
15:28Roasted_ (~jason@206.82.22.190) joined #ltsp.
15:28
<Roasted_>
Hate to bring up the time thing again, but what's up with the time of the user logged in and the time at the login screen being way off?
15:28
I have ntp installed and TIMESERVER=blah blah blah. I just don't see why it's different from login screen vs logged in
15:29
<vagrantc>
different timezone?
15:29
<Roasted_>
no
15:32
<vagrantc>
Roasted_: how did you configure the timezone on the server and for the thin client?
15:33
<Roasted_>
on the server I went in the GUI to time and date in sys-admin. then I added our server IP there and checked synchronize. In lts.conf I have the same IP there as well.
15:33
<vagrantc>
Roasted_: you can set SCREEN_07=shell in lts.conf, reboot, and see what the output of "date" does
15:33
<Roasted_>
one of my clients just got the correct time.
15:33
out of curiosity what is that?
15:33
ha
15:33
my time is wacked out
15:33
18, 18, 22, 21, 17
15:34
<vagrantc>
Roasted_: i'll say this one last time, install ntp on your LTSP server, and configure TIMESERVER=server in lts.conf
15:35
<Roasted_>
vagrantc, I did.
15:35
<vagrantc>
< Roasted_> on the server I went in the GUI to time and date in sys-admin. then I added our server IP there and checked synchronize. In lts.conf I have the same IP there as well.
15:35
<Roasted_>
exactly
15:35
<abeehc>
that's borderline gibberish
15:36
<Roasted_>
TIMESERVER=10.52.1.8
15:36
under default in lts.conf
15:36
<vagrantc>
Roasted_: try TIMESERVER=server
15:36
<Roasted_>
NTP is installed on server
15:36
i
15:36
did
15:36
<vagrantc>
not and ip address.
15:36
<Roasted_>
by hostname?
15:36
<vagrantc>
TIMESERVER=server
15:36
<abeehc>
server is a secret hostname
15:36
<Roasted_>
...you mean actually just have "server" there
15:36
?
15:36
<abeehc>
listed in client /etc/hosts
15:36
<vagrantc>
exactly "TIMESERVER=server"
15:36
<Roasted_>
oh
15:37
k
15:37
done
15:37
<vagrantc>
Roasted_: make sure ntpdate is installed on your thin clients
15:37
then reboot your thin clients
15:37
and maybe it'll work.
15:39
<Roasted_>
already installed. ill reboot them quick.
15:39
once I log in they seem to be relatively fine
15:39
but at the login screen they're all out of sync
15:40
<vagrantc>
sometimes it also takes an NTP server a while to trust itself, and it will refuse to sync times until then...
15:41
<Roasted_>
do the clients have to be on during the trust period? Or is this done entirely on the server alone?
15:42
<vagrantc>
the server's
15:42
<Roasted_>
k
15:42
<vagrantc>
the NTP server's peers need to be connected, but the thin clients just use ntpdate
15:42
<Roasted_>
peers? (clients?)
15:43
<vagrantc>
an NTP server will typically talk to several other NTP servers to corroborate on the time
15:43
<Roasted_>
externally from the network?
15:43
<vagrantc>
they're all effectively servers to each other, or peers
15:43
whatever you configure to be
15:43
<Roasted_>
ah
15:44
<vagrantc>
Roasted_: what we've failed to ever establish, is weather the timeserver you're syncing with is actually an NTP server, or some other time syncronization protocol
15:44
<Roasted_>
Hm, does Windows 03 use NTP by default?
15:44
or another protocol?
15:44
<vagrantc>
no idea
15:45
<Roasted_>
For testing purposes maybe I can just set the time server ot be something external.
15:45
Just to see if the thin clients all mesh up without an issue.
15:45
If that's the case I'll talk to the net admin about our time server here and whether it's NTP or not.
15:45
<vagrantc>
Roasted_: by default, simply installing ntp will configure some external time servers to sync with
15:46
<Roasted_>
well I meant the lts.conf entry.
15:46
<vagrantc>
don't mess with the lts.conf entry...
15:46
<Roasted_>
Removing the entry to our internal time server I set it to and adding an external one there.
15:46
<vagrantc>
TIMESERVER=server
15:46
<Roasted_>
let it as is?
15:46
k
15:46
<vagrantc>
that's what you should have in lts.conf
15:46
<Roasted_>
that's the first time I ever heard that.
15:46
<vagrantc>
then you can just use the defaults for ntp on your LTSP server.
15:46
<Roasted_>
I've always heard IP of server
15:46
even read that on the man page. :P
15:47* vagrantc resists being snarky
15:47
<Roasted_>
just being honest
15:47
I just never heard of using server as the actual input
15:47
<vagrantc>
i definitely told you that the last time we dicussed the issue
15:47
<Roasted_>
if you did, I had mistaken it
15:47
thinking "server" meant OUR server
15:47
so my apologies if I did
15:48
<vagrantc>
sometimes i just have to be more explicit, i suppose
15:48
<Roasted_>
"server" just didn't strike me as an actual entry. I found it vague and just assumed (I know, I know) you meant IP of our server.
15:48
I apologize for that headache.
15:48
With TIMESERVER defaulting to unset if it's not in lts.conf, what happens then? Do clients just read BIOS time?
15:49
<vagrantc>
Roasted_: the other thing, i'm wondering if your GUI time syncing tool configures NTP or does something else ... then you might have two things fighting with each other over setting the time...
15:49
Roasted_: yup.
15:49
<Roasted_>
I removed the GUI thing.
15:49
I had seen it when I was googling around and never noticed it so I wanted to check it out.
15:49
It had an entry to add your own server so I added our's just to see what happened.
15:50
so anyway, the optimal setting is TIMESERVER=server in lts.conf and install NTP on the actual LTSP server. Besides that, it's done. eh?
15:50
<vagrantc>
one can hope.
15:51
<Roasted_>
I hear ya
15:51
<vagrantc>
unless your network's firewall is blocking the standard NTP port or some such
15:51
<Roasted_>
pretty sure time is working properly in the other LTSP lab.
15:51
I just have TIMEZONE set in lts.conf, no timeserver setting.
15:51
I think they're out of whack upon bootup though, but after a few minutes they sync.
15:53
<vagrantc>
that's unusual
15:53
<Roasted_>
this whole time thing has been unusual....
15:53
<vagrantc>
there was a race condition that might have caused problems with the time syncing on fast thin clients...
15:54
<Roasted_>
by using TIMEZONE it essentially uses NTP but with external servers, I would assume...
15:55
<vagrantc>
oh, even better, set TIMESERVER=auto ... although that may be fairly recently introduced
15:55
<Roasted_>
how's auto work?
15:55
<vagrantc>
it sets TIMESERVER to whatever IP address you're booted from
15:56
TIMEZONE won't trigger any time sync
15:56
though ntpdate itself may attempt to sync with a default list of servers
15:56
<Roasted_>
so auto would tie it right back to the ltsp server then?
15:56
<vagrantc>
Roasted_: yes. but maybe a little less confusing than TIMESERVER=server
15:57
<Roasted_>
you say auto is new?
15:57* vagrantc checks
15:57
<vagrantc>
Roasted_: what version of ltsp you running?
15:57
<Roasted_>
whichever is in 10.10
15:58
<vagrantc>
TIMESERVER=auto should definitely be supported
15:58
apparently i introduced it upstream in early 2009
15:58
"fairly new" :)
15:58
<Roasted_>
so if auto points to the server... I just have to make sure the server has the right time as a result
15:59
would auto be any different than TIMESERVER=ip.of.ltsp.server ??
15:59
<vagrantc>
Roasted_: easier to document :)
15:59
<Roasted_>
so same thing in theory, but easier in application
15:59
<vagrantc>
yes
16:00
and it doesn't vary depending on where you are, or if your server changes ip address, etc.
16:00
<Roasted_>
good eal
16:00
deal
16:00
rebooting these clients now to see what else happens
16:01* vagrantc hopes it works
16:01
<Roasted_>
does it take time ?
16:02
or should it work immediately
16:02
<vagrantc>
fairly immediately
16:02
<Roasted_>
well, I'll be patient then...
16:03
<vagrantc>
Roasted_: check to make sure that ntp is running and not complaining ...
16:03
Roasted_: grep ntpd /var/log/syslog
16:04
on the LTSP server
16:04
<Roasted_>
I'm just going to pastebin this...
16:04
<vagrantc>
sure
16:05
<Roasted_>
I'm not noticing any errors but, what I see vs what you see may be different
16:05
http://tinypaste.com/5bc33a
16:06
<vagrantc>
i should document TIMESERVER=auto in the lts.conf manpage...
16:06
<Roasted_>
it'd be nice :)
16:07
anything jump out at you with the paste?
16:07
<vagrantc>
looks fairly ok to me
16:07
<Roasted_>
I'm here with 7 clients.
16:08
19:08, 18:14, 19:07, 19:07, 19:05, 23:07, 19:17
16:08
19:08 = correct
16:08
the 19:07's could be correct too since it just turned over to 08
16:08
<vagrantc>
it seems like you've got both ntpdate and ntp installed on the server ... shouldn't need ntpdate
16:09
<Roasted_>
hm, think they'd conflict?
16:09
wait isn't ntpdate on there by default?
16:09
<vagrantc>
if they ran in the right order, it should be fine.
16:09
but if ntpdate runs after ntp, you could get problems
16:09
<Roasted_>
pretty sure ntpdate is installed by default
16:10
its on my laptop, and I dont recall installing it
16:10
<vagrantc>
they should play nice... it's probably not an issue
16:11
<Roasted_>
any cons to not having ntpdate?
16:11
yeah... that did nothing
16:11
still got the messed up times
16:15
<vagrantc>
Roasted_: ntpq -p
16:15Roasted_ (jason@206.82.22.190) left #ltsp ("Leaving").
16:15
<vagrantc>
should tell you which ntp peers your server is connected to ...
16:15
gah.
16:15Roasted_ (~jason@206.82.22.190) joined #ltsp.
16:15
<Roasted_>
oops
16:16
CTRL W'd the wrong thing
16:16
<vagrantc>
Roasted_: ntpq -p
16:16
should tell you which ntp peers your server is connected to ...
16:16
<Roasted_>
otc2.psu.edu
16:16
penn state university
16:16
<vagrantc>
just one?
16:16
<Roasted_>
college about an hour away
16:16
yes
16:16
under remote
16:16* vagrantc would've expected at least 2 or 3
16:17
<Roasted_>
I can do the same thing on the other ltsp server, and see what it says
16:18
other server only has 1 entry, but its a different location
16:19
<vagrantc>
probably gets one from a pool of ntp servers at boot
16:19
<Roasted_>
it's possible. that ltsp server has been running for a month, whereas this one I booted up an hour ago
16:20
maybe I'll just have to accept mismatched time on every box
16:20
<vagrantc>
that seems ridiculous
16:20
<Roasted_>
I agree, but I just have no idea what else to do.
16:21
<vagrantc>
Roasted_: try setting SCREEN_07=shell and then logging into the thin client and running ntpdate manually
16:21
er, reboot thin thin client ...
16:21
i.e. ntpdate server (and i DO mean "server") :)
16:22
<Roasted_>
ntpdate server = can't find host server
16:22
na,me or service not known
16:23
<vagrantc>
cat /etc/hosts ?
16:23
echo $SERVER
16:23
try: ntpdate $SERVER
16:23
<Roasted_>
no servers can be used, exiting
16:24
<vagrantc>
that's your problem
16:24
for some reason, NTP isn't responding
16:24
<Roasted_>
think it's firewalled?
16:24
<vagrantc>
could be
16:24
<Roasted_>
do you know what port NTP uses offhand?
16:25
<vagrantc>
grep ntp /etc/services
16:25
<Roasted_>
123
16:25
tcp udp
16:25
<vagrantc>
yup
16:25
i gotta go soon ... but at least you've got an idea of what's wrong
16:25
<Roasted_>
do you believe my setup is correct?
16:26
as far as lts.conf and my server setup?
16:26
I guess the only thing on my server is the fact NTP is installed... I didn't do anything else.
16:26
<vagrantc>
Roasted_: the working server has ntp installed ... is on the same network?
16:27
<Roasted_>
the LTSP server these clients are hitting has NTP installed
16:27
yes
16:28
<vagrantc>
Roasted_: you said there was another LTSP server, where the clients were syncing ... ?
16:28
<Roasted_>
that was with TIMEZONE in lts.conf
16:28
they come up out of whack, but after 2-3 minutes they all get the same time
16:28
<vagrantc>
but no TIMESERVER?
16:28
<Roasted_>
That setup is on a different subnet
16:28
I don't believe so, let me double check
16:29
TIMEZONE=US/Eastern
16:29
no time zone
16:29
er
16:29
server
16:29
<vagrantc>
ntpdate is probably running with the default timeserver i.e. pool.ntp.ubuntu.com or some such
16:30
and on one subnet, they have access to NTP, and on the other NTP is blocked by firewall or some such ... or they have no routing
16:32
<Roasted_>
I just went back to using TIMEZONE and they all booted up with the wrong time, so I'll give them a few minutes and see what they do. I'll revert back to auto then and see what comse along monday.
16:33
I just want to see if they come together after a few mins like the other 2 LTSP servers do
16:36staffencasa (~staffenca@128-193-148-149.oregonstate.edu) left irc: Read error: Connection reset by peer
16:36
<Roasted_>
yeahhhhhh no sync. shoulda happened by now. what a mess.
16:36
oh well...
16:37
<vagrantc>
you'll figure it out eventually
16:37Roasted_ (jason@206.82.22.190) left #ltsp ("Leaving").
16:37Roasted_ (~jason@206.82.22.190) joined #ltsp.
16:38
<vagrantc>
Roasted_: i'd compare the "iptables -L" output on each of your servers.
16:38
Roasted_: and "iptables -L -n"
16:40
<Roasted_>
thanks, I'll write that down
16:41
I'm going to get out of here fo rnow, though
16:41
thanks for the help vagrantc. I'll keep looking for an answer.
16:41
<vagrantc>
good luck
16:42Roasted_ (~jason@206.82.22.190) left irc: Quit: Leaving
17:15vagrantc (~vagrant@c-24-21-191-93.hsd1.or.comcast.net) left irc: Quit: leaving
19:14JamesB192 (debian-tor@gateway/tor-sasl/jamesb192) joined #ltsp.
20:31JamesB192 (debian-tor@gateway/tor-sasl/jamesb192) left #ltsp ("http://quassel-irc.org - Chat comfortably. Anywhere.").
20:43otavio (~otavio@debian/developer/otavio) left irc: Ping timeout: 240 seconds
20:55KBme (~KBme@2001:470:1f13:94::3) left irc: Ping timeout: 260 seconds
20:59KBme (~KBme@2001:470:1f13:94::3) joined #ltsp.
21:22vagrantc (~vagrant@c-24-21-191-93.hsd1.or.comcast.net) joined #ltsp.
21:39viks (ca8a720f@gateway/web/freenode/ip.202.138.114.15) joined #ltsp.
21:41otavio (~otavio@189.114.111.55) joined #ltsp.
21:41otavio (~otavio@189.114.111.55) left irc: Changing host
21:41otavio (~otavio@debian/developer/otavio) joined #ltsp.
21:56RiXtEr (~blah@d22-110.rb.gh.centurytel.net) left irc: Ping timeout: 246 seconds
21:57RiXtEr (~blah@72-161-230-67.dyn.centurytel.net) joined #ltsp.
21:59viks (ca8a720f@gateway/web/freenode/ip.202.138.114.15) left irc: Ping timeout: 252 seconds
22:16viks (ca8a720f@gateway/web/freenode/ip.202.138.114.15) joined #ltsp.
22:27Lns (~Lns@pdpc/supporter/professional/lns) joined #ltsp.
22:42viks (ca8a720f@gateway/web/freenode/ip.202.138.114.15) left irc: Ping timeout: 252 seconds
22:48viks (ca8a720f@gateway/web/freenode/ip.202.138.114.15) joined #ltsp.
23:11
<viks>
how to map local hardisk on ltsp kiosk
23:12
<vagrantc>
viks: is this the same question you've been asking for a week now?
23:12
<viks>
i tried fuse module also but it is not working
23:13
i have done with all configration with lts.conf
23:13
vagrantc : is there any support who can help us to set up this on our production
23:14komunista (~slavko@adsl-195-168-237-003.dynamic.nextra.sk) joined #ltsp.
23:45
<viks>
can any body give me the configration to setup ltsp in kiosk with local hardisk detection
23:51
<vagrantc>
viks: you're probably going to have to be more specific
23:58
<viks>
can u tell me is there any one who can set up this ltsp environment for us
23:58
we want ltsp pxe boot with kiosk mode ...n local hardisk detect on client side automatically ..so that he can use thier own hardisk
23:59
is this possible?
23:59
<vagrantc>
it is technically possible, sure.
23:59
although why would you want to?
00:00--- Sat Apr 9 2011