booting thin clients and firestarter
 

On 1/31/08, Jonathan Carter (highvoltage) <jonathan@ubuntu.com> wrote:

I've had a similar problem with Firestarter before. How did you remove
it with configs?
I*used*Synaptic*which*has*a*"complete*removal" option.

Did you do a apt-get --purge remove firestarter? IIRC,
Firestarter used to mangle configuration files on installation. Not sure
if it still does that. Have you tried dropping your iptables rules,

I'm*not*sure*there*are*any*to drop (iptables --list reveals only "target prot opt source" - which I assume is the default setting)*.

or
seeing what the result is when doing a port scan with nmap from another machine?
Which*ports*should*I*scan*for?*Is*it*worthwhile*do ing*it*from*the*internet*too?*

Thanks,

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

booting thin clients and firestarter
 

My perfectly working thin-client
network was brought down after I installed Firestarter. Even after a
complete uninstall of Firestarter, I am unable to even ping between
boxes � although syslog on the server clearly sees, recognizes the
MAC addresses and even offers ip addresses to the other boxes:


Examples:


Jan 31 13:02:17 edubuntu dhcpd:
DHCPDISCOVER from 00:50:da:d0:c6:af via eth1


Jan 31 13:02:18 edubuntu dhcpd:
DHCPOFFER on 192.168.0.244 to 00:50:da:d0:c6:af via eth1



and


Jan 31 11:52:00 edubuntu dhcpd:
DHCPDISCOVER from 00:2a:43:ae:30:94 via eth1


Jan 31 11:52:01 edubuntu dhcpd:
DHCPOFFER on 192.168.0.248 to 00:2a:43:ae:30:94 via eth1


As this is the second configuration
with which I seem to have had this problem (this being on an entirely
different install on an entirely different computer). To my
knowledge, nothing of consequence has changed since a few days ago
when everything is working: my ltsp/dhcpd.conf file is identical to
the recommended setup at http://www.edubuntu.org/GettingStarted
(besides an added if/else filter to chose between nbi.img and
pxelinux.0 - I tried replacing that filter with a simple "filename
"/ltsp/pxelinux.0";" line to no avail) and I've removed
the "authoritative" from etc/dhcp3/dhcpd.conf that had been
placed by firestarter).

I'm about ready to give up on this
experiment. Any ideas?

Thanks.

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

booting thin clients and firestarter
 

Hi,

On Sun, 03 Feb 2008, DB Clinton wrote:

> My perfectly working thin-client network was brought down after I installed
> Firestarter. Even after a complete uninstall of Firestarter, I am unable to
> even ping between boxes – although syslog on the server clearly sees,
> recognizes the MAC addresses and even offers ip addresses to the other
> boxes:

> I'm about ready to give up on this experiment. Any ideas?

If the problem coincides with firestarter being installed, it seems likely
that firewall rules are in place stopping some aspects of the thin client
boot process (eg tftp, nbd, etc.).

Could you give us the output of the following command:

sudo iptables --list

Presumably some remnant of the package is still causing issues. Looking at
the contents of the firestarter package, are any of these files still
present on the system?

/etc/network/if-up.d/50firestarter
/etc/network/if-down.d/50firestarter
/usr/sbin/firestarter
/etc/init.d/firestarter
/etc/firestarter/non-routables

Gavin


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

booting thin clients and firestarter
 

On Feb 3, 2008 12:23 PM, Gavin McCullagh <gmccullagh@gmail.com> wrote:

> My perfectly working thin-client network was brought down after I installed
> Firestarter. Even after a complete uninstall of Firestarter, I am unable to
> even ping between boxes – although syslog on the server clearly sees,

> recognizes the MAC addresses and even offers ip addresses to the other
> boxes:
If the problem coincides with firestarter being installed, it seems likely
that firewall rules are in place stopping some aspects of the thin client

boot process (eg tftp, nbd, etc.).

Could you give us the output of the following command:

Â* Â* Â* Â*sudo iptables --listChain INPUT (policy ACCEPT)
targetÂ*Â*Â*Â* prot opt sourceÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* destinationÂ*Â*Â*Â*Â*Â*Â* Â*


Chain FORWARD (policy ACCEPT)
targetÂ*Â*Â*Â* prot opt sourceÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* destinationÂ*Â*Â*Â*Â*Â*Â* Â*

Chain OUTPUT (policy ACCEPT)
targetÂ*Â*Â*Â* prot opt sourceÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* destination


Presumably some remnant of the package is still causing issues. Â*Looking at
the contents of the firestarter package, are any of these files still
present on the system?

Â* Â* Â* Â*/etc/network/if-up.d/50firestarter

Â* Â* Â* Â*/etc/network/if-down.d/50firestarter
Â* Â* Â* Â*/usr/sbin/firestarter
Â* Â* Â* Â*/etc/init.d/firestarter
Â* Â* Â* Â*/etc/firestarter/non-routables
None of these is still on the system .
By the way, I realize that I've been working without a real understanding of chroot (which I assume is the directory hierarchy under /opt/ and controls client behavior). I wonder if there could be files in that seemingly vast and complicated hierarchy that have an effect on my problem...Is there a relatively simple tutorial on this subject I should be reading?

With thanks,
David


Gavin


--
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

booting thin clients and firestarter
 

Hi,

On Sun, 03 Feb 2008, DB Clinton wrote:

> > Could you give us the output of the following command:
> >
> > sudo iptables --list
>
> Chain INPUT (policy ACCEPT)
> target prot opt source destination
>
> Chain FORWARD (policy ACCEPT)
> target prot opt source destination
>
> Chain OUTPUT (policy ACCEPT)
> target prot opt source destination

So, there are no firewall rules at all. This suggest firestarter is not a
problem at all. Is it possible you installed firestarter which broke
booting, then you tried various things to fix it, then removed firestarter
which fixed your original problem, but now the "various things" are the
problem?

Can you explain in detail exactly what happens when the boot fails?

You refer to making changes in "etc/dhcp3/dhcpd.conf". That's not the dhcp
config file in LTSP systems. It's /etc/ltsp/dhcpd.conf. Can you check
that that file is present on the system? Could you check that it has lines
something like this:

option root-path "/opt/ltsp/i386";
if substring( option vendor-class-identifier, 0, 9 ) = "PXEClient" {
filename "/ltsp/i386/pxelinux.0";
} else {
filename "/ltsp/i386/nbi.img";
}

and make sure pxelinux.0, nbi.img exist in /opt/ltsp/i386/.

We'll figure it out, it'll just take a little close examination.

Gavin


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

booting thin clients and firestarter
 

On Feb 3, 2008 1:29 PM, Gavin McCullagh <gmccullagh@gmail.com> wrote:


So, there are no firewall rules at all. *This suggest firestarter is not a
problem at all. *Is it possible you installed firestarter which broke
booting, then you tried various things to fix it, then removed firestarter

which fixed your original problem, but now the "various things" are the
problem?
That's certainly a possibility.



Can you explain in detail exactly what happens when the boot fails?
Here's a recap (typed in by hand - there may be errors):
sis900_probe: MAC 00:2A:43:AE:30:94 at vendor 0X0400
sis900_probe: vendor :0X1039 Device 0X0900

sis900_probe: RTL 8201 10/100Mps Phyceiver transceiver found at address 1
sis900_probe: Using RTL 8201 as default
rtl8201_read_mode: Medialink on 100Mbs full duplex
searching for server (DHCP)...no IP adress [repeat until fed up]



You refer to making changes in "etc/dhcp3/dhcpd.conf". *That's not the dhcp

config file in LTSP systems.
I know. I remarked out (#) "authoritative" (along with every other line, for that matter) which I assumed would force the system to read the ltsp version. Curiously, webmin, under servers, only shows me the dhcp3 version - remarks and all.


*It's /etc/ltsp/dhcpd.conf. *Can you check
that that file is present on the system? *Could you check that it has lines

something like this:It's on the system. Here's the whole thing:
==============================
*

# Default LTSP dhcpd.conf config file.

#



authoritative;



subnet 192.168.0.0 netmask 255.255.255.0 {

*** range 192.168.0.20 192.168.0.250;

*** option domain-name "example.com";

*** option domain-name-servers 192.168.0.1;

*** option broadcast-address 192.168.0.255;

*** option routers 192.168.0.1;

#*** next-server 192.168.0.254;

#*** get-lease-hostnames true;



*** option subnet-mask 255.255.255.0;



#*** filename "/ltsp/pxelinux.0";* [alternative to if/else option below?]



*** option root-path "/opt/ltsp/i386";



*** if substring( option vendor-class-identifier, 0, 9 ) = "PXEClient" {

******* filename "/ltsp/i386/pxelinux.0";

*** } else {

******* filename "/ltsp/i386/nbi.img";

*** }

}
==========================*


and make sure pxelinux.0, nbi.img exist in /opt/ltsp/i386/.
*
They were both in /opt/ltsp/i386/boot/. I copied them to /opt/ltsp/i386/ and ran dhcp3-server restart but no change on the client boot.



We'll figure it out, it'll just take a little close examination.
Thanks. I really do appreciate this!
David



Gavin


--
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

booting thin clients and firestarter
 

Hi,

On Sun, 03 Feb 2008, DB Clinton wrote:

> > Can you explain in detail exactly what happens when the boot fails?
>
> Here's a recap (typed in by hand - there may be errors):
> sis900_probe: MAC 00:2A:43:AE:30:94 at vendor 0X0400
> sis900_probe: vendor :0X1039 Device 0X0900
> sis900_probe: RTL 8201 10/100Mps Phyceiver transceiver found at address 1
> sis900_probe: Using RTL 8201 as default
> rtl8201_read_mode: Medialink on 100Mbs full duplex searching for server (DHCP)...no IP adress [repeat until fed up]

It seems that the DHCP is the problem then.

Are you certain there's a good network link between the thin client server
(and its dhcp server) and the thin client? Can you start this running:

tail -f /var/log/syslog | grep DHCP

and then boot a client. If the DHCP request makes it you should get a line
like
Feb 3 13:12:35 robin dhcpd: DHCPDISCOVER from 00:1d:d9:3e:da:eb via eth0

where the mac address shown is that of your thin client. If you don't get
that, there's some loss of connectivity between server and client.

> > You refer to making changes in "etc/dhcp3/dhcpd.conf". That's not the
> > dhcp config file in LTSP systems.
>
> I know. I remarked out (#) "authoritative" (along with every other line, for
> that matter) which I assumed would force the system to read the ltsp
> version. Curiously, webmin, under servers, only shows me the dhcp3 version -
> remarks and all.

Webmin is not supported in Edubuntu. Some people use it for managing
users, but it's not supported. It sounds like it modifies
/etc/dhcp3/dhcpd.conf which is ignored if /etc/ltsp/dhcpd.conf is present.

> It's on the system. Here's the whole thing:

It looks fine.

> > and make sure pxelinux.0, nbi.img exist in /opt/ltsp/i386/.
>
> They were both in /opt/ltsp/i386/boot/. I copied them to /opt/ltsp/i386/ and
> ran dhcp3-server restart but no change on the client boot.

My mistake, those files don't need to be in the chroot, they need to be in
the tftp server directory, that is /var/lib/tftpboot/, so you should have

/var/lib/tftpboot/ltsp/i386/nbi.img
/var/lib/tftpboot/ltsp/i386/pxelinux.0

You might as well remove the copies you made above.

Gavin


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

booting thin clients and firestarter
 

On Feb 3, 2008 3:32 PM, Gavin McCullagh <gmccullagh@gmail.com> wrote:

> rtl8201_read_mode: Medialink on 100Mbs full duplex searching for server (DHCP)...no IP adress [repeat until fed up]

It seems that the DHCP is the problem then.

Are you certain there's a good network link between the thin client server

(and its dhcp server) and the thin client? *Can you start this running:

* * * * tail -f /var/log/syslog | grep DHCP

and then boot a client. *If the DHCP request makes it you should get a line
like
* * * *Feb *3 13:12:35 robin dhcpd: DHCPDISCOVER from 00:1d:d9:3e:da:eb via eth0


where the mac address shown is that of your thin client. *If you don't get
that, there's some loss of connectivity between server and client.
Here's the output:
Feb* 3 15:54:15 edubuntu dhcpd: DHCPDISCOVER from 00:2a:43:ae:30:94 via eth1

Feb* 3 15:54:15 edubuntu dhcpd: DHCPOFFER on 192.168.0.245 to 00:2a:43:ae:30:94 via eth1
I got a bit confused because one of the kids must have tried to boot my upstairs computer too at the same time so I was getting discoveries and offers to and from both...but in any case, there is definitely connectivity and the MAC addresses are correct.

*
> > and make sure pxelinux.0, nbi.img exist in /opt/ltsp/i386/.

>
> They were both in /opt/ltsp/i386/boot/. I copied them to /opt/ltsp/i386/ and
> ran dhcp3-server restart but no change on the client boot.

My mistake, those files don't need to be in the chroot, they need to be in

the tftp server directory, that is /var/lib/tftpboot/, so you should have

* * * */var/lib/tftpboot/ltsp/i386/nbi.img
* * * */var/lib/tftpboot/ltsp/i386/pxelinux.0
pxelinux.0 and nbi.img were actually not in that directory either. I copied them there but still no results.



You might as well remove the copies you made above.
Thanks.



Gavin


--
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

booting thin clients and firestarter
 

Hi,

On Sun, 03 Feb 2008, DB Clinton wrote:

> On Feb 3, 2008 3:32 PM, Gavin McCullagh <gmccullagh@gmail.com> wrote:
>
> > > rtl8201_read_mode: Medialink on 100Mbs full duplex searching for server
> > (DHCP)...no IP adress [repeat until fed up]

> > tail -f /var/log/syslog | grep DHCP

> Here's the output:
> Feb 3 15:54:15 edubuntu dhcpd: DHCPDISCOVER from 00:2a:43:ae:30:94 via eth1
> Feb 3 15:54:15 edubuntu dhcpd: DHCPOFFER on 192.168.0.245 to 00:2a:43:ae:30:94 via eth1

A dhcp boot normally looks like this for us:

Feb 1 08:18:57 brooks dhcpd[6450]: DHCPDISCOVER from 00:02:a5:77:46:6a via eth0
Feb 1 08:18:58 brooks dhcpd[6450]: DHCPOFFER on 87.42.170.159 to 00:02:a5:77:46:6a via eth0
Feb 1 08:18:58 brooks dhcpd[6450]: DHCPREQUEST for 87.42.170.159 (87.42.170.254) from 00:02:a5:77:46:6a via eth0
Feb 1 08:18:58 brooks dhcpd[6450]: DHCPACK on 87.42.170.159 to 00:02:a5:77:46:6a via eth0
Feb 1 08:18:58 brooks in.tftpd[21065]: tftp: client does not accept options

do you see all five of those lines in /var/log/syslog?

> > you should have
> >
> > /var/lib/tftpboot/ltsp/i386/nbi.img
> > /var/lib/tftpboot/ltsp/i386/pxelinux.0
>
> pxelinux.0 and nbi.img were actually not in that directory either. I copied
> them there but still no results.

Any thoughts on how that happened? I would have thought you can't have had
booting working ever without at least one of those being in place.

Gavin


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

booting thin clients and firestarter
 

> Here's the output:

> Feb *3 15:54:15 edubuntu dhcpd: DHCPDISCOVER from 00:2a:43:ae:30:94 via eth1
> Feb *3 15:54:15 edubuntu dhcpd: DHCPOFFER on 192.168.0.245 to 00:2a:43:ae:30:94 via eth1


A dhcp boot normally looks like this for us:

Feb *1 08:18:57 brooks dhcpd[6450]: DHCPDISCOVER from 00:02:a5:77:46:6a via eth0
Feb *1 08:18:58 brooks dhcpd[6450]: DHCPOFFER on 87.42.170.159 to 00:02:a5:77:46:6a via eth0

Feb *1 08:18:58 brooks dhcpd[6450]: DHCPREQUEST for 87.42.170.159 (87.42.170.254) from 00:02:a5:77:46:6a via eth0
Feb *1 08:18:58 brooks dhcpd[6450]: DHCPACK on 87.42.170.159 to 00:02:a5:77:46:6a via eth0

Feb *1 08:18:58 brooks in.tftpd[21065]: tftp: client does not accept options


do you see all five of those lines in /var/log/syslog?
Nope. The DHCPREQUEST, DHCPACK AND tftp: client does not... lines don't appear at all.

*
> pxelinux.0 and nbi.img were actually not in that directory either. I copied

> them there but still no results.

Any thoughts on how that happened? *I would have thought you can't have had
booting working ever without at least one of those being in place.

I have no idea. It certainly wasn't anything I did manually as I wasn't even aware there was such a directory until today. Sometime before the "crash", I did install a few packages (in my effort to set up some controls over the internet access of my clients). I installed (and subsequently, post-crash, uninstalled) Firehol, Dansguardian and Squid. I think that was all.

Thanks again


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