Re: [Ltsp-discuss] Client stops at setting up NIC

[Andreas-Christoph Bernstein]

Zitat von Alkis Georgopoulos :

> On 22/02/2017 10:37 πμ, Andreas-Christoph Bernstein wrote:
>> Interesting. That is new, right? I thought ltsp-pnp doesn't create a
>> chroot. That's why we are still using ltsp-server-standalone on our
>> ubuntu server.
>>
>> So nowadays i would start with ltsp-pnp? Is ltsp-server-standalone
>> obsolete (on ubuntu)?
>
>
> ltsp-pnp has been around for more than 5 years and has been used in
> thousands of installations. If it suits your needs, you can surely use
> it. ltsp-build-client might be deprecated in ltsp6 in favor of other
> methods to build chroots, but for ltsp5 it's of course still supported.
>
> The ltsp-pnp wiki page does say that you need to install the
> ltsp-server-standalone package, so you have some misunderstanding there,
> let's try to clear it up.
>
> ltsp-server: an LTSP server where we don't want DHCPD (and possibly
> TFTPD) because we have those servers elsewhere in our LAN.
> ltsp-server-standalone: an LTSP server which will have DHCPD and TFTPD.
>
> Those are true for both classic ltsp and for ltsp-pnp.
> The difference is that:
> The ltsp-pnp wiki page suggests that you install ltsp-server-standalone
> with dnsmasq as the dhcpd and tftpd server.
> While in the classic ltsp, ltsp-server-standalone installed
> isc-dhcp-server and tftpd-hpa.
>
> The reason that ltsp-pnp prefers dnsmasq instead of those 2 others, is
> because it can also function as "proxyDHCP", while isc-dhcp-server
> cannot do that.
> ProxyDHCP means: "I have a router that does DHCP in my network, so the
> LTSP server should only send the boot filename and root path, and let
> the router manage the IP leases".
>
> Since the "router is DHCPD" scenario is very very common, that's why
> ltsp-pnp preferred dnsmasq and ProxyDHCP.
> And it became the default in recent classic LTSP too, so new LTSP
> installations (2017+) will get dnsmasq by default instead of the other 2
> servers.
> That means that the ltsp-pnp differences from the classic ltsp are now
> really really small; just running `ltsp-update-image -c /` instead of
> running `ltsp-build-client` for the default image.
>
> Btw, `ltsp-config dnsmasq` also sets up a classic DHCPD in the
> 192.168.67.x range, so if you want the old "dual nic" setup, you can
> just set the second nic to 192.168.67.1 and you're ready to go.
>
>
>
> To sum up: ltsp-server-standalone used to prefer to depend on
> isc-dhcp-server and tftpd-hpa, while now it prefers to depends on dnsmasq.
> If someone doesn't want dnsmasq, he can just install the 2 other ones.
>

Thank you Alkis for your detailed response. That clears things up.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
  https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Re: [Ltsp-discuss] Client stops at setting up NIC

[Alkis Georgopoulos]

On 22/02/2017 10:37 πμ, Andreas-Christoph Bernstein wrote:
> Interesting. That is new, right? I thought ltsp-pnp doesn't create a
> chroot. That's why we are still using ltsp-server-standalone on our
> ubuntu server.
>
> So nowadays i would start with ltsp-pnp? Is ltsp-server-standalone
> obsolete (on ubuntu)?


ltsp-pnp has been around for more than 5 years and has been used in 
thousands of installations. If it suits your needs, you can surely use 
it. ltsp-build-client might be deprecated in ltsp6 in favor of other 
methods to build chroots, but for ltsp5 it's of course still supported.

The ltsp-pnp wiki page does say that you need to install the 
ltsp-server-standalone package, so you have some misunderstanding there, 
let's try to clear it up.

ltsp-server: an LTSP server where we don't want DHCPD (and possibly 
TFTPD) because we have those servers elsewhere in our LAN.
ltsp-server-standalone: an LTSP server which will have DHCPD and TFTPD.

Those are true for both classic ltsp and for ltsp-pnp.
The difference is that:
The ltsp-pnp wiki page suggests that you install ltsp-server-standalone 
with dnsmasq as the dhcpd and tftpd server.
While in the classic ltsp, ltsp-server-standalone installed 
isc-dhcp-server and tftpd-hpa.

The reason that ltsp-pnp prefers dnsmasq instead of those 2 others, is 
because it can also function as "proxyDHCP", while isc-dhcp-server 
cannot do that.
ProxyDHCP means: "I have a router that does DHCP in my network, so the 
LTSP server should only send the boot filename and root path, and let 
the router manage the IP leases".

Since the "router is DHCPD" scenario is very very common, that's why 
ltsp-pnp preferred dnsmasq and ProxyDHCP.
And it became the default in recent classic LTSP too, so new LTSP 
installations (2017+) will get dnsmasq by default instead of the other 2 
servers.
That means that the ltsp-pnp differences from the classic ltsp are now 
really really small; just running `ltsp-update-image -c /` instead of 
running `ltsp-build-client` for the default image.

Btw, `ltsp-config dnsmasq` also sets up a classic DHCPD in the 
192.168.67.x range, so if you want the old "dual nic" setup, you can 
just set the second nic to 192.168.67.1 and you're ready to go.



To sum up: ltsp-server-standalone used to prefer to depend on 
isc-dhcp-server and tftpd-hpa, while now it prefers to depends on dnsmasq.
If someone doesn't want dnsmasq, he can just install the 2 other ones.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
  https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Re: [Ltsp-discuss] Client stops at setting up NIC

[Andreas-Christoph Bernstein]

Zitat von Alkis Georgopoulos :

> On 22/02/2017 10:10 πμ, Johan Kragsterman wrote:
>>
>> Thanks for the clarification of that, didn't know that.
>  > What I have read about ltsp-pnp is that it can't use other clients
>  > than the architecture of the server. Am I wrong there...?
>  > If so, that makes all the difference.
>
> For example, you can have a 64bit server,
> with the default 64bit ltsp-pnp chroot that can boot 64bit thin and fat
> clients,
> and then you can decide to run ltsp-build-client --arch i386 to support
> older i386 thin clients,
> and then you can decide to follow
> https://help.ubuntu.com/community/UbuntuLTSP/RaspberryPi to build an
> armhf chroot to support booting raspberry pis too,
> etc etc
>
> ltsp-pnp just helps you set up your initial environment,
> and gives you a graphical way to manage your default chroot,
> it doesn't impose any limits to what you can do with your ltsp installation.


Interesting. That is new, right? I thought ltsp-pnp doesn't create a  
chroot. That's why we are still using ltsp-server-standalone on our  
ubuntu server.

So nowadays i would start with ltsp-pnp? Is ltsp-server-standalone  
obsolete (on ubuntu)?

Andreas


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
  https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Re: [Ltsp-discuss] Client stops at setting up NIC

[Alkis Georgopoulos]

On 22/02/2017 10:10 πμ, Johan Kragsterman wrote:
>
> Thanks for the clarification of that, didn't know that.
 > What I have read about ltsp-pnp is that it can't use other clients
 > than the architecture of the server. Am I wrong there...?
 > If so, that makes all the difference.

For example, you can have a 64bit server,
with the default 64bit ltsp-pnp chroot that can boot 64bit thin and fat 
clients,
and then you can decide to run ltsp-build-client --arch i386 to support 
older i386 thin clients,
and then you can decide to follow 
https://help.ubuntu.com/community/UbuntuLTSP/RaspberryPi to build an 
armhf chroot to support booting raspberry pis too,
etc etc

ltsp-pnp just helps you set up your initial environment,
and gives you a graphical way to manage your default chroot,
it doesn't impose any limits to what you can do with your ltsp installation.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
  https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Re: [Ltsp-discuss] Client stops at setting up NIC

[Rolf-Werner Eilert]

Am 21.02.2017 11:25, schrieb Horst Prote:
> Hi Rolf,
>
>> My brand new Intel NUC connects to the server, loads the kernel, but
>> stops/hangs at setting up the network card. When booting in debug mode,
>> it says "try setting the option-129".
> I had this once, many years ago (ltsp-2.x). The solution was a newer
> kernel with better support for the network adapter.
>

I guess it's something like that, unfortunately. And it means setting up 
a newer system for the server, doesn't it?

Regards
Rolf



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
  https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Re: [Ltsp-discuss] Client stops at setting up NIC

[Horst Prote]

Hi Rolf,

> My brand new Intel NUC connects to the server, loads the kernel, but 
> stops/hangs at setting up the network card. When booting in debug mode, 
> it says "try setting the option-129".
I had this once, many years ago (ltsp-2.x). The solution was a newer
kernel with better support for the network adapter.

Regards
Horst

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
  https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Re: [Ltsp-discuss] Client stops at setting up NIC

[Finn Andersen]

Hi Rolf!

I don't think it is related to your problem. But the kernel option
"ipappend 2" vs "ipappend 3" could result in a client not booting properly.

-Finn

On Mon, Feb 20, 2017 at 5:27 PM, Rolf-Werner Eilert 
wrote:

> Hi folks!
>
> My brand new Intel NUC connects to the server, loads the kernel, but
> stops/hangs at setting up the network card. When booting in debug mode,
> it says "try setting the option-129".
>
> As already described, this is an older 64bit server (Suse 12.1) with an
> older LTSP5.
>
> Has anyone here an idea how to get my new NUC running? Later, I will
> have to set up a new server system anyway, but for a first trial I
> thought it would be nice to use the old one.
>
> By the way, LTSP5 normally runs fine on the system. In the past, I tried
> it with different small and larger systems. Sometimes it stops at
> graphics, but I never had this problem with the network adapter.
>
> Regards
> Rolf
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _
> Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
>   https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help,   try #ltsp channel on irc.freenode.net
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot_
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
  https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net