Public bug reported:
While installing from the Jaunty alternate CD, the server "internal" NIC is
assigned a static IP of 192.168.0.254 in /etc/network/interfaces.
But /etc/ltsp/dhcpd.conf assumes an IP of 192.168.0.1.
This difference is also present in some of the ltsp scripts.
This makes it impossible to do NATting on the server for the clients to
directly access the Internet (e.g. for the TIMESERVER lts.conf directive to
work, of for localapps-firefox to work), unless one of those two files are
manually modified.
Here are the results of a search for "192.168.0." in the source code:
client/initscripts/Gentoo/ltsp-client-setup.initd:
SERVER="${SERVER:-192.168.0.254}"
client/screen.d/telnet:# the default of '192.168.0.254'
client/ltsp_config: SERVER="${server:-192.168.0.254}"
debian/dhcpd.conf:subnet 192.168.0.0 netmask 255.255.255.0 {
debian/dhcpd.conf: range 192.168.0.20 192.168.0.250;
debian/dhcpd.conf: option domain-name-servers 192.168.0.1;
debian/dhcpd.conf: option broadcast-address 192.168.0.255;
debian/dhcpd.conf: option routers 192.168.0.1;
debian/dhcpd.conf:# next-server 192.168.0.1;
server/doc/QuickInstall:IP 192.168.0.1, then run command below:
server/doc/examples/get_host_random:HOSTS="192.168.0.254 192.168.0.253
192.168.0.252 192.168.0.251"
server/doc/examples/dhcpd-dnsmasq:dhcp-range=192.168.0.20,192.168.0.250,1h
server/configs/dhcpd.conf:subnet 192.168.0.0 netmask 255.255.255.0 {
server/configs/dhcpd.conf: range 192.168.0.20 192.168.0.250;
server/configs/dhcpd.conf: option domain-name-servers 192.168.0.1;
server/configs/dhcpd.conf: option broadcast-address 192.168.0.255;
server/configs/dhcpd.conf: option routers 192.168.0.1;
server/configs/dhcpd.conf: next-server 192.168.0.1;
server/configs/ALTLinux/dhcpd.conf.in:next-server 192.168.0.1;
server/configs/ALTLinux/dhcpd.conf.in:subnet 192.168.0.0 netmask 255.255.255.0 {
server/configs/ALTLinux/dhcpd.conf.in: range 192.168.0.20 192.168.0.250;
server/configs/ALTLinux/dhcpd.conf.in: option domain-name-servers
192.168.0.1;
server/configs/ALTLinux/dhcpd.conf.in: option broadcast-address
192.168.0.255;
server/configs/ALTLinux/dhcpd.conf.in: option routers 192.168.0.1;
server/configs/ALTLinux/dhcpd.conf.in: option root-path
"192.168.0.1:/var/lib/ltsp/@ARCH@";
server/configs/k12linux/mkinitrd/sysconfig-mkinitrd:rootdev="192.168.0.254:/opt/ltsp/i386"
server/scripts/k12linux/dhcpd-update:$origserver="192.168.0.254";
server/scripts/k12linux/dhcpd-update:$orignetwork="192.168.0.0";
server/scripts/k12linux/dhcpd-update: $server="192.168.0.254";
server/scripts/k12linux/dhcpd-update: $network="192.168.0.0";
server/scripts/k12linux/ltsp-server-initialize: DEFAULTIP="192.168.0.254"
server/plugins/ltsp-build-client/Debian/035-create-fs-image:
NBD_ROOT_SERVER=${NBD_ROOT_SERVER:-"192.168.0.1"}
** Affects: ltsp (Ubuntu)
Importance: Undecided
Status: New
--
Inconsistent server IP: 192.168.0.[1-or-254]
https://bugs.launchpad.net/bugs/390155
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
