FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Ubuntu > Edubuntu User

 
 
LinkBack Thread Tools
 
Old 01-12-2009, 08:40 PM
ekul taylor
 
Default Thin Client /etc/hosts entry

I'm not 100% sure but you would either need to write a startup script to add them each boot or (more ideally) add the terminal server as a dns server in the dhcp settings and add any hosts you want to bind on the terminal server


On Mon, Jan 12, 2009 at 4:30 PM, M Rathburn <stretchem@gmail.com> wrote:

Edubuntu 8.10 on amd64



How do I make entries into the /etc/hosts for PXE i386 thin clients? *I

noticed that when I chrooted and tried to edit the file, it shows:



#This is a ltsp chroot and this file will be rewritten in boot process

#of terminal.

127.0.0.1 localhost



So where would I make the entries so they'll propagate to the TC's?



Thanks.







--

edubuntu-users mailing list

edubuntu-users@lists.ubuntu.com

Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users



--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
 
Old 01-13-2009, 06:47 PM
"M Rathburn"
 
Default Thin Client /etc/hosts entry

________________________________

From: ekul taylor [mailto:ekul.taylor@gmail.com]
Sent: Monday, January 12, 2009 4:40 PM
To: stretchem@gmail.com
Cc: Edubuntu Users Group
Subject: Re: Thin Client /etc/hosts entry


I'm not 100% sure but you would either need to write a startup
script to add them each boot or (more ideally) add the terminal server as a
dns server in the dhcp settings and add any hosts you want to bind on the
terminal server


On Mon, Jan 12, 2009 at 4:30 PM, M Rathburn <stretchem@gmail.com>
wrote:


Edubuntu 8.10 on amd64

How do I make entries into the /etc/hosts for PXE i386 thin
clients? I
noticed that when I chrooted and tried to edit the file, it
shows:

#This is a ltsp chroot and this file will be rewritten in
boot process
#of terminal.
127.0.0.1 localhost

So where would I make the entries so they'll propagate to
the TC's?

Thanks.
------------------------------------

On the server, /etc/resolv.conf looks like this:

domain childrenfirstflorida.org
search childrenfirstflorida.org
nameserver 192.168.0.254
nameserver 192.168.1.1


The 0.254 address is the LTSP server, and the 1.1 address is the internet
router. When a thin client boots up, it's /etc/resolv.conf looks like this:

domain childrenfirstflorida.org
search childrenfirstflorida.org
nameserver 192.168.1.1

and it's /etc/hosts looks like this:

127.0.0.1 localhost
127.0.0.2 CFF-1014
192.168.0.254 server


The server's dhcpd.conf portion that matters looks like this:

option domain-name "childrenfirstflorida.org";
option domain-name-servers 192.168.0.254, 192.168.1.1;
option broadcast-address 192.168.0.255;
option routers 192.168.0.254;


The server's /etc/hosts looks like this:

127.0.0.1 localhost
127.0.1.1 ltsp1.childrenfirstflorida.org ltsp1
192.168.1.36 portal.childrenfirstflorida.org

# For thin clients.
192.168.0.14 CFF-1014
192.168.0.12 FPS-1012
192.168.0.16 FPS-1016


It's that 'portal.scholarshipfunding.org' portion that I need to route
locally first, since it's on the same LAN (don't want to go out and back
in). How do I make it so that a thin client's /etc/hosts has that entry for
'192.168.1.36 portal.childrenfirstflorida.org', OR it's default nameserver
is 192.168.0.254 and secondary nameserver is 192.168.1.1?

Thanks.


--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
 
Old 01-13-2009, 07:01 PM
Mickey Moore
 
Default Thin Client /etc/hosts entry

How will you use the DNS names? To ssh into one of the terminals you will first have to ssh into the LTSP which they are connected to. Since you will be creating the session from the LTSP to a client it should be sufficient to have the names in the /etc/host file of the LTSP server. You can assign specific IP addresses to specific devices by assigning it via MAC address in the DHCPD.conf on the LTSP. At least it is not clear to me how you would know a specific thin-client name/address ahead of time any other way.


--- On Tue, 1/13/09, M Rathburn <stretchem@gmail.com> wrote:

> From: M Rathburn <stretchem@gmail.com>
> Subject: RE: Thin Client /etc/hosts entry
> To: "'Edubuntu Users Group'" <edubuntu-users@lists.ubuntu.com>
> Date: Tuesday, January 13, 2009, 2:47 PM
> ________________________________
>
> From: ekul taylor [mailto:ekul.taylor@gmail.com]
> Sent: Monday, January 12, 2009 4:40 PM
> To: stretchem@gmail.com
> Cc: Edubuntu Users Group
> Subject: Re: Thin Client /etc/hosts entry
>
>
> I'm not 100% sure but you would either need to write a
> startup
> script to add them each boot or (more ideally) add the
> terminal server as a
> dns server in the dhcp settings and add any hosts you want
> to bind on the
> terminal server
>
>
> On Mon, Jan 12, 2009 at 4:30 PM, M Rathburn
> <stretchem@gmail.com>
> wrote:
>
>
> Edubuntu 8.10 on amd64
>
> How do I make entries into the /etc/hosts for PXE i386
> thin
> clients? I
> noticed that when I chrooted and tried to edit the file,
> it
> shows:
>
> #This is a ltsp chroot and this file will be rewritten in
> boot process
> #of terminal.
> 127.0.0.1 localhost
>
> So where would I make the entries so they'll
> propagate to
> the TC's?
>
> Thanks.
> ------------------------------------
>
> On the server, /etc/resolv.conf looks like this:
>
> domain childrenfirstflorida.org
> search childrenfirstflorida.org
> nameserver 192.168.0.254
> nameserver 192.168.1.1
>
>
> The 0.254 address is the LTSP server, and the 1.1 address
> is the internet
> router. When a thin client boots up, it's
> /etc/resolv.conf looks like this:
>
> domain childrenfirstflorida.org
> search childrenfirstflorida.org
> nameserver 192.168.1.1
>
> and it's /etc/hosts looks like this:
>
> 127.0.0.1 localhost
> 127.0.0.2 CFF-1014
> 192.168.0.254 server
>
>
> The server's dhcpd.conf portion that matters looks like
> this:
>
> option domain-name "childrenfirstflorida.org";
> option domain-name-servers 192.168.0.254, 192.168.1.1;
> option broadcast-address 192.168.0.255;
> option routers 192.168.0.254;
>
>
> The server's /etc/hosts looks like this:
>
> 127.0.0.1 localhost
> 127.0.1.1 ltsp1.childrenfirstflorida.org ltsp1
> 192.168.1.36 portal.childrenfirstflorida.org
>
> # For thin clients.
> 192.168.0.14 CFF-1014
> 192.168.0.12 FPS-1012
> 192.168.0.16 FPS-1016
>
>
> It's that 'portal.scholarshipfunding.org'
> portion that I need to route
> locally first, since it's on the same LAN (don't
> want to go out and back
> in). How do I make it so that a thin client's
> /etc/hosts has that entry for
> '192.168.1.36 portal.childrenfirstflorida.org',
> OR it's default nameserver
> is 192.168.0.254 and secondary nameserver is 192.168.1.1?
>
> Thanks.
>
>
> --
> edubuntu-users mailing list
> edubuntu-users@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/edubuntu-users




--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
 
Old 01-14-2009, 03:26 AM
Mickey Moore
 
Default Thin Client /etc/hosts entry

OK - now I get the picture. I had this exact problem. I can give you two other solutions that I have used. My present solution at my main campus for this private/public network address mapping problem is I run BIND9 on my Ubuntu LTSP. I put it in forward only mode to the real DNS server and create entries for the school domain I have public/private conflicts in. I then change the dhcpd.conf file so LTSP is the DNS server for the clients.

Second I have come to use a standalone firewall machine in place of the Linksys router I started with based on PFSense. PFSense has a section where you can override the dns with static entries. When you give any machine inside you network the address of the PFsense box as dns server it overrides these static entries and passes the rest on to the real DNS. The PFSense also has a gateway VPN builtin which lets me seemlessly connect my other two campuses together. You can actually login to the pfsense box and run tcpdump to isolate issues both within and outside your network. I discovered a DDOS against my school mail server with this once. It has traffic graphs which show me in and out traffic by time of day. It has firewall logs and state tables which often allow problem resolution without tcpdump. It has proven far more robust and reliable than my Linksys box which I used to have to send someone to the wiring closet to reboot several times a week.

Some samples from my LTSP BIND9 config files follow:

In file /etc/bind/named.conf.options add your ISP DNS server 1 and 2 as below. Note I replaced my ISP's real DNS servers with the xx.xx.xx... entries below

options {
directory "/var/cache/bind";

// If there is a firewall between you and nameservers you want
// to talk to, you might need to uncomment the query-source
// directive below. Previous versions of BIND always asked
// questions using port 53, but BIND 8.1 and later use an unprivileged
// port by default.

// query-source address * port 53;

// If your ISP provided one or more IP addresses for stable
// nameservers, you probably want to use them as forwarders.
// Uncomment the following block, and insert the addresses replacing
// the all-0's placeholder.


// forwarders {
// 0.0.0.0;
// };

forward only;
notify no;
forwarders{
xx.xx.xx.20;
xx.xx.xx.21;
};

In File /etc/bind/named.conf.local again I replaced my real internet name with xxxxxx.org. Note the 10.0.0 is matches my schools private internal address range. You would use your 192.168.... range instead

//
// Do any local configuration here
//

// Consider adding the 1918 zones here, if they are not used in your
// organization
//include "/etc/bind/zones.rfc1918";
zone "xxxxxx.org" {
type master;
file "/etc/bind/xxxxxx.org";
};
zone "0.0.10.in-addr.arpa" in{
type master;tcalex.org
file "/etc/bind/10.0.0";
};

In File /etc/bind/xxxxxx.org where yyyyyyyy and xxxxxx replace my real names

$TTL 43200
@ IN SOA yyyyyyyy.xxxxxx.org. hostmaster.yyyyyyyy.xxxxxx.org. (
2001043001 ; serial
1H ; refresh
15M ; retry
14D ; expire
12H ; default_ttl
)
@ IN MX 5 mail.xxxxxx.org.
@ IN NS yyyyyyyy.xxxxxx.org.
www IN A 10.0.0.211
fierylake IN A 10.0.0.1
adam IN A 10.0.0.4

In File 10.0.0 again yyyyyyyy and xxxxxx replace real names

$TTL 43200
@ IN SOA yyyyyyyy.xxxxxx.org. hostmaster.yyyyyyyy.xxxxxx.org. (
2001043001 ; serial
1H ; refresh
15M ; retry
14D ; expire
12H ; default_ttl
)
@ IN NS yyyyyyyy.xxxxxx.org.
1 IN PTR fierylake.xxxxxx.org.
211 IN PTR www.xxxxxx.org.
4 IN PTR adam.xxxxxx.org.








--- On Tue, 1/13/09, M Rathburn <stretchem@gmail.com> wrote:

> From: M Rathburn <stretchem@gmail.com>
> Subject: RE: Thin Client /etc/hosts entry
> To: tcamdmoore@yahoo.com
> Date: Tuesday, January 13, 2009, 3:33 PM
> > -----Original Message-----
> > From: edubuntu-users-bounces@lists.ubuntu.com
> > [mailto:edubuntu-users-bounces@lists.ubuntu.com] On
> Behalf Of
> > Mickey Moore
> > Sent: Tuesday, January 13, 2009 3:01 PM
> > To: 'Edubuntu Users Group'
> > Subject: RE: Thin Client /etc/hosts entry
> >
> > How will you use the DNS names? To ssh into one of the
>
> > terminals you will first have to ssh into the LTSP
> which they
> > are connected to. Since you will be creating the
> session from
> > the LTSP to a client it should be sufficient to have
> the
> > names in the /etc/host file of the LTSP server. You
> can
> > assign specific IP addresses to specific devices by
> assigning
> > it via MAC address in the DHCPD.conf on the LTSP. At
> least it
> > is not clear to me how you would know a specific
> thin-client
> > name/address ahead of time any other way.
> >
> >
> ----------------------------
>
> Running Firefox as a local app.




--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
 
Old 01-14-2009, 09:46 AM
Gavin McCullagh
 
Default Thin Client /etc/hosts entry

Hi,

On Mon, 12 Jan 2009, M Rathburn wrote:

> How do I make entries into the /etc/hosts for PXE i386 thin clients? I
> noticed that when I chrooted and tried to edit the file, it shows:
>
> #This is a ltsp chroot and this file will be rewritten in boot process
> #of terminal.
> 127.0.0.1 localhost
>
> So where would I make the entries so they'll propagate to the TC's?

A while back I used ltsp to network boot a bunch of servers. I created a
file called

/etc/init.d/customise_client

made it executable and linked it into /etc/rc2.d/ so the script ran on
boot.

The script did a bunch of things like:

echo "w.x.y.z hostname1" >> /etc/hosts
echo "w.x.y.z hostname2" >> /etc/hosts
echo "w.x.y.z hostname3" >> /etc/hosts

It also ran something like:

mac=`ip addr show eth0 | grep 'link/ether' | cut -f 6 -d " "`

to identify the machine by their mac address, then I had a case statement
which compared $mac to a bunch of known macs and made machine-specific
customisations.

This (particularly the machine-specific bit) is not very scalable and not
very pretty, but it suited my purpose.

Gavin


--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
 
Old 01-14-2009, 07:47 PM
"M Rathburn"
 
Default Thin Client /etc/hosts entry

> Hi,
>
> On Mon, 12 Jan 2009, M Rathburn wrote:
>
> > How do I make entries into the /etc/hosts for PXE i386 thin
> clients?
> > I noticed that when I chrooted and tried to edit the file, it shows:
> >
> > #This is a ltsp chroot and this file will be rewritten in
> boot process
> > #of terminal.
> > 127.0.0.1 localhost
> >
> > So where would I make the entries so they'll propagate to the TC's?
>
> A while back I used ltsp to network boot a bunch of servers.
> I created a file called
>
> /etc/init.d/customise_client
>
> made it executable and linked it into /etc/rc2.d/ so the
> script ran on boot.
>
> The script did a bunch of things like:
>
> echo "w.x.y.z hostname1" >> /etc/hosts
> echo "w.x.y.z hostname2" >> /etc/hosts
> echo "w.x.y.z hostname3" >> /etc/hosts
>
> It also ran something like:
>
> mac=`ip addr show eth0 | grep 'link/ether' | cut -f 6 -d " "`
>
> to identify the machine by their mac address, then I had a
> case statement which compared $mac to a bunch of known macs
> and made machine-specific customisations.
>
> This (particularly the machine-specific bit) is not very
> scalable and not very pretty, but it suited my purpose.
>
> Gavin

This works perfectly Gavin! Thanks!

sudo chroot /opt/ltsp/i386
sudo vi /etc/init.d/customize_clients
i
echo "192.168.1.36 portal.childrenfirstflorida.org" >> /etc/hosts
ZZ
sudo chmod 755 /etc/init.d/customize_clients
sudo ln -s ../init.d/customize_clients /etc/rc2.d/S99customize_clients
exit
sudo ltsp-update-image --arch i386


--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
 
Old 01-15-2009, 09:10 AM
Gavin McCullagh
 
Default Thin Client /etc/hosts entry

Hi,

On Wed, 14 Jan 2009, M Rathburn wrote:

> This works perfectly Gavin! Thanks!

Great. As Mickey suggests though, functioning DNS is really the way to do
this.

What I've described is a hack, which can be useful in various instances
where you need to customise the image _post_ boot-up. We had a network
testbed where each machine needed extra network interfaces, a bunch of
static routes, hosts entries, firewall rules, etc. It did that fairly
effectively.

Gavin


--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
 

Thread Tools




All times are GMT. The time now is 02:11 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org