I’m stuck in the same place I was stuck before with Edubuntu thin clients.
I could get GDHCPD to work this time. I finally got Webmin to work through the browser. After installing it I typed in the address https://localhost:10000, and it worked! This allows me to configure the DHCP server without having to drop to the command line level or use a text editor to edit configuration files. Yipee! If I get an error, I go to System –> System logs –> File /var/log/syslog. The error message below came from the syslog.I tried adding the package Ubuntu LTSP management GUI. This is the LTSP GUI management tool to set up, modify and manage an
Ubuntu LTSP server Thin Client installation. It guides you through
the Thin Client chroot installation and enables you to adjust dhcp
settings on the server. It also allows you to tweak specific settings
for the Thin Clients. However, I can’t figure out how to get it to run. It looks like it is version 0.0.2. Maybe it’s just not ready.
I found advice for this problem on the Ubuntu forums at
Fail to start DHCP server - no subnet declaration - Ubuntu Forums
WARNING: This post is loaded with Geekspeak, so proceed at your own risk.
I can’t get the DHCP server to start up. I have 2 ethernet cards with eth0 going to the switch for the thin clients and eth1 to the internet gateway. Thank you to those who have offered advice. Below is some more specific information.
Here is what the syslog says.
No subnet declaration for eth0 (172.16.10.1).May 19 16:06:59 tag2513 dhcpd: ** Ignoring requests on eth0. If this is not what
May 19 16:06:59 tag2513 dhcpd: you want, please write a subnet declaration
May 19 16:06:59 tag2513 dhcpd: in your dhcpd.conf file for the network segment
May 19 16:06:59 tag2513 dhcpd: to which interface eth0 is attached.
So, the problem is that the DHCP server won’t start because it says I haven’t declared a subnet.I found a pretty good explanation for setting up thin client network subnet. Using webmin. I think I set it up according to the directions.
The DHCP.config file says
default-lease-time 600;
max-lease-time 7200;
# Ubuntu Server
host TAG2513 {
option subnet-mask 255.255.255.0;
option host-name “tag2513″;
fixed-address 172.16.10.1;
}
# Ubuntu DNS zone
zone Ubuntu.edu. {
primary 172.16.10.10;
key ;
}
# LTSP subnet
subnet 172.16.10.0 netmask 255.255.255.0 {
range 172.16.10.2 172.16.10.20;
pool {
range 172.16.10.2 172.16.10.20;
}
}
The ipaddr command gives the following output
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:48:54:65:bf:ca brd ff:ff:ff:ff:ff:ff
inet 172.16.10.1/24 brd 172.16.10.255 scope global eth0
/etc/default/dhcp3-server says
INTERFACES=eth0
It looks to me like it should work. Why doesn’t it?
Super easy movie maker »« Edubuntu Thin Client Classroom Experiment
I’m not sure. If I get a chance when I go to school tomorrow, I’ll check it out and see what I can find out from my installation.
Full Disclosure: I used K12LTSP for my lab. It is based on Fedora (or now, CentrOS). If you don’t mind using Fedora instead of Ubuntu, it might be an option as well. It did, in my case, install multiple Desktop Environments, which was nice to play with and find what the kids liked best. http://www.k12ltsp.org
I’ll try to remember to check my lab tomorrow if I get a chance and see what my files look like. I didn’t have this many issues getting mine going-so I’m not certain.
Full Disclosure: I used K12LTSP instead of Edubuntu. That might be an option to consider, in my experience, it had more programs to offer than Edubuntu. That might have changed with the latest Edubuntu release. If you’re not against using Fedora (which is what K12LTSP is based on), its an option. I’ll either be upgrading mine this summer, or switching over to Edubuntu–haven’t quite decided yet.
Ok-I’m sitting in front of my LTSP server right now. Here’s what I have…
First of all, my /etc/dhcpd.conf file is basically empty. Here’s what it says:
#
# DHCP Server Configuration file.
# see /usr/share/doc/dhcp*/dhcpd.conf.sample
#
I actually couldn’t believe that is what it was–until I was able to boot up my other machines (making sure they still worked).
In my experience (it took going through this to remember) - I used this file to tell my clients about specific hardware.
Now…there is this sample file in there as well.
# Sample configuration file for ISCD dhcpd
#
# Don't forget to set run_dhcpd=1 in /etc/init.d/dhcpd
# once you adjusted this file and copied it to /etc/dhcpd.conf.
#
default-lease-time 21600;
max-lease-time 21600;
ddns-update-style none;
allow booting;
allow bootp;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.0.255;
option routers 192.168.0.254;
option domain-name-servers 192.168.0.254;
next-server 192.168.0.254;
option domain-name "ltsp";
option root-path "192.168.0.254:/opt/ltsp/i386";
option option-128 code 128 = string;
option option-129 code 129 = text;
option option-221 code 221 = text;
shared-network WORKSTATIONS {
subnet 192.168.0.0 netmask 255.255.255.0 {
range dynamic-bootp 192.168.0.100 192.168.0.253;
use-host-decl-names on;
option log-servers 192.168.0.254;
# trick from Peter Rundle
# newer Macs
if substring (option vendor-class-identifier, 0, 9) = "AAPLBSDPC"
{
filename "yaboot";
option vendor-class-identifier "AAPLBSDPC";
}
# really old iMacs
elsif substring (option option-221, 0, 5) = "Apple"
{
filename "yaboot";
option vendor-class-identifier "AAPLBSDPC";
}
# Intel PXE
elsif substring (option vendor-class-identifier, 0, 9) = "PXEClient"
{
# NOTE: kernels are specified in /tftpboot/lts/pxe/pxelinux.cfg/
filename "/lts/pxe/pxelinux.0";
}
# default to an i386 BOOTP image
else
{
filename "/lts/vmlinuz.ltsp";
}
if substring (option vendor-class-identifier, 20, 3) = "ppc" {
option root-path "192.168.0.254:/opt/ltsp/ppc";
} else {
option root-path "192.168.0.254:/opt/ltsp/i386";
}
}
}
# example configurations for specifying specific kernels to specific clients
group {
use-host-decl-names on;
option log-servers 192.168.0.254;
host ws001 {
hardware ethernet 00:E0:06:E8:00:84;
fixed-address 192.168.0.1;
filename "/lts/vmlinuz.ltsp";
option option-128 e4:45:74:68:00:00;
option option-129 "NIC=3c509";
}
host ws002 {
hardware ethernet 00:D0:09:30:6A:1C;
fixed-address 192.168.0.2;
filename "/lts/vmlinuz.ltsp";
option option-128 e4:45:74:68:00:00;
option option-129 "NIC=ne";
}
host ws003 {
hardware ethernet 00:D0:09:30:28:B2;
fixed-address 192.168.0.3;
# kernels are specified in /tftpboot/lts/boot/pxe/pxelinux.cfg/
filename "/lts/boot/pxe/pxelinux.0";
}
# Apple Specific Settings
# host ws007 {
# hardware ethernet 00:30:65:69:23:60;
# fixed-address 192.168.0.4;
# option root-path "192.168.0.254:/opt/ltsp/ppc";
# filename "yaboot";
# option vendor-class-identifier "AAPLBSDPC";
# }
}
There are also some startup scripts further in to /etc/init.d. You may have to change a setting on one of those to get dhcpd to start.
The 172.***.**.* looks weird to me. LTSP (from my experience) always has used 192.168.0.*** with the server being 192.168.0.254. That could be an issue. I’m not sure if it is different for Edubuntu or not–so that could be an Ubuntu thing.
One other thought, have you been to the official Ubuntu forums and given them your problem? (I’m sure you have–but I figured I’d check) You can also pop on their IRC channel. They’re usually very helpful.
Thanks odometer for the feedback. It helps to see what the DHCPD.config file looks like on a working system.
The 172.16.10.0 is the static address for the server on the network. Our network admin set when he was trying to figure out why id wasn’t working. Although he said the 192.168.x.x is available to use since the school network doesn’t use that IP range. I’m not sure whether or not the rest of the subnet has to be in the same IP range as the server.
I think you’re making the same assumption that I did initially. The IP address of my server at school to the outside world is 10.***.**.***. (I don’t remember exactly). However, the IP address of my server inside my network is 192.168.x.x. On my setup, Eth1 gets its IP via DHCP from the server. Eth0 is a static IP 192.168.0.254.
I’m just speaking from my personal experience. I’m definitely no expert. Basically–I can boot my entire network without plugging my server into the internet. There are times where this is handy–b/c I’m able to keep my kids off the net (when needed). All I do is unplug it from the wall.
However, I’m not sure the IP address is the only issue. It should work either way.
Maybe this link will explain further.
https://help.ubuntu.com/community/EdubuntuDocumentation/EdubuntuCookbook/ServerConfiguration
As you can tell, I truly believe in this solution–so I’ll do what I can to help.