----- Original Message ----
From: "edubuntu-users-request@lists.ubuntu.com" <edubuntu-users-request@lists.ubuntu.com>
To: edubuntu-users@lists.ubuntu.com
Sent: Tuesday, September 30, 2008 12:00:02 PM
Subject: edubuntu-users Digest, Vol 28, Issue 51
Send edubuntu-users mailing list submissions to
*** edubuntu-users@lists.ubuntu.com
To subscribe or unsubscribe via the World Wide Web, visit
*** https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
or, via email, send a message with subject or body 'help' to
*** edubuntu-users-request@lists.ubuntu.com
You can reach the person managing the list at
*** edubuntu-users-owner@lists.ubuntu.com
When replying, please edit your Subject line so it is
more specific
than "Re: Contents of edubuntu-users digest..."
I am attempting to setup an Edubuntu 8.04.1 LTSP test environment on our
network that already contains a DNS server run by our parent company
that we have no control over.
The initial test client which is specified by MAC address in the
dhcpd.conf file gets and IP address initially from the LTSP server,
boots pxelinux, and then does another DHCP request this time taking a
response from the corporate DHCP server which causes the client to not
boot Edubuntu (boots to Busy Box).
Based on man dhclient.conf, I can add commands to ignore the corporate
DHCP server, but I'm assuming I'd have to rebuild the client image for
the client to use this file.
Is there a way to include the same
configuration info in lts.conf?
You talked about DNS and DHCP, these are two different network services, and i'm sure DNS has nothing to do with LTSP thin client booting, so, configure your system following the instructions on the edubuntu wiki. There are two types of installations, ltsp-server-standalone and another, depending on whether there's an external DHCP server or if LTSP server is also the DHCP server.
In any case, you may need to issue:
sudo* ltsp-update-sshkeys
sudo ltsp-update-image
on the ltsp server if you are receiving initramfs or busybox on the clients.
Attempted to add network configuration to
dhclient.conf and rebuild
client image. Client still boots to Busy Box. So apparently that's not
the network configuration used by the client during the initial boot.
The client so far loads pxelinux.cfg/default, then loads vmlinuz, then
initrd.img, says ready, then Loading, please wait and does another DHCP
request. What file controls the network settings for this DHCP request
by the client at this point in the boot process?
Thanks,
Tim
-----Original Message-----
From: edubuntu-users-bounces@lists.ubuntu.com
[mailto:edubuntu-users-bounces@lists.ubuntu.com] On Behalf Of Tim Boyden
Sent: Monday, September 29, 2008 11:41 AM
To: edubuntu-users@lists.ubuntu.com
Subject: Client DHCP configuration?
Hi All,
I am attempting to setup an Edubuntu 8.04.1 LTSP test environment on our
network that already contains a DNS server run by our parent company
that we have no control over.
The initial test client which is specified by MAC address in the
dhcpd.conf file gets and IP address initially from the LTSP server,
boots pxelinux, and then does another DHCP request this time taking a
response from the corporate DHCP server which causes the client to not
boot Edubuntu (boots to Busy Box).
Based on man dhclient.conf, I can add commands to ignore the corporate
DHCP server, but I'm assuming I'd have to rebuild the client image for
the client to use this file. Is there a way to include the same
configuration info in lts.conf?
I am attempting to setup an Edubuntu 8.04.1 LTSP test environment on our
network that already contains a DNS server run by our parent company
that we have no control over.
The initial test client which is specified by MAC address in the
dhcpd.conf file gets and IP address initially from the LTSP server,
boots pxelinux, and then does another DHCP request this time taking a
response from the corporate DHCP server which causes the client to not
boot Edubuntu (boots to Busy Box).
Based on man dhclient.conf, I can add commands to ignore the corporate
DHCP server, but I'm assuming I'd have to rebuild the client image for
the client to use this file. Is there a way to include the same
configuration info in lts.conf?
You talked about DNS and DHCP, these are two
different network services, and i'm sure DNS has nothing to do with LTSP thin
client booting, so, configure your system following the instructions on the
edubuntu wiki. There are two types of installations, ltsp-server-standalone and
another, depending on whether there's an external DHCP server or if LTSP server
is also the DHCP server.
In any case, you may need to issue:
sudoÂ* ltsp-update-sshkeys
sudo ltsp-update-image
on the ltsp server if you are receiving initramfs or busybox on the clients.