Gary,
Usually when I run up against a problem like this, I like to examine
the packets.
So, I use tcpdump to grab the packets, and then Ethereal to
take a look inside of the packets.
A command like:
tcpdump -w /tmp/tcpdump.out -s 0 host ws001
that will capture all of the traffice to/from ws001.
The '-s 0' option is important, otherwise, tcpdump will only
capture the first 68 bytes of the packet, and that may not
be enough to tell me the whole story.
Then, I use ethereal to look at the output:
ethereal -r /tmp/tcpdump.out
Of course, knowing what to look for helps alot. Usually, I don't
know exactly what I am looking for going in, but usually, something
will pop-out at me. Such as the source and destination adresses
being on different networks, or lots of arp requests, with no replies,
or some option negotiation taking place between the tftp client
and the tftp server.
You can actually capture the packets directly with ethereal, but I
like to have people use tcpdump for capturing the packets, because
then they can send me the tcpdump.out file (after gzipping it). Then,
I can take a look at it, and see if I spot anything.
The other thing I'd like to suggest is that you get on the #ltsp
IRC channel, and I can work interactively with you to try to
diagnose the problem.
I'm sure we can get it figured out.
Jim McQuillan
[EMAIL PROTECTED]
On Sat, 8 Feb 2003, Gary Jaffe wrote:
> I would appreciate some help with a problem I've been struggling with for some
> time now. I have ltsp_core-3.0.5-0, ltsp_kernel-3.0.5-0,
> ltsp_x_core-3.0.1-1, and ltsp_x_fonts-3.0.0-0 installed on a Redhat 7.3 box.
> I have a single workstation with an NE2000 ISA card obtained from
> disklessworkstations.com in 1999 with an upgraded bootPROM I just received.
>
> When I boot the workstation, everything goes fine until it tries to transfer
> the vmlinuz file with tftp, at which time it sleeps. I get my ip addr OK.
> This is the same spot I failed when I used Jason Pattie's trick of
> downloading a newer Etherboot image with my old bootPROM. So, I suspected
> tftp, especially since my Redhat 7.3 distribution did not come with tftp. I
> had to download tftp-0.28-2.src.rpm and install it. But tftpd seems to be
> running, here's a bit of my ps output after attempting to boot the
> workstation.
>
>---------------------------------------------------------------------------------------------------------------------
> 1612 ? S 0:00 in.tftpd -s /tftpboot
> 1613 ? S 0:00 in.tftpd -s /tftpboot
>
>---------------------------------------------------------------------------------------------------------------------
>
> and this is the message tftp puts in my /var/log/secure file each time I try
> to boot the workstation.
>
>--------------------------------------------------------------------------------------------------------------------
> Jan 28 09:30:02 ws101 xxxxxx[1083]: START: tftp pid=1611 from=192.168.1.2
>
>--------------------------------------------------------------------------------------------------------------------
>
> And here's the output of ls for the vmlinuz file it's trying to download.
>
>--------------------------------------------------------------------------------------------------------------------
> -rw-r--r-- 1 root root 1418240 Sep 4 23:59
> /tftpboot/lts/vmlinuz-2.4.19-ltsp-1
>
>---------------------------------------------------------------------------------------------------------------------
>
> I also upgraded to dhcp-3.0pl1 which was required to use Jason Pattie's trick
> when I had to old bootPROM. Here's what my dhcpd.conf file looks like this.
>
>----------------------------------------------------------------------------------------------------------------------
> ddns-update-style ad-hoc;
>
> default-lease-time 21600;
> max-lease-time 21600;
>
> option subnet-mask 255.255.255.0;
> option broadcast-address 192.168.1.255;
> option routers 192.168.1.1;
> option domain-name-servers 192.168.1.1;
> option domain-name "xxxxxx.net";
> option root-path "192.168.1.1:/opt/ltsp/i386";
> option option-128 code 128 = string;
> option option-129 code 129 = text;
>
> shared-network WORKSTATIONS {
> subnet 192.168.1.0 netmask 255.255.255.0 {
> }
> }
>
> group {
> use-host-decl-names on;
> option log-servers 192.168.1.1;
>
> host ws102 {
> hardware ethernet xx:xx:xx:xx:xx:xx;
> option option-128 e4:45:74:68:00:00;
> option option-129 "NIC=ne IO=0x300";
> fixed-address 192.168.1.2;
> filename "/lts/vmlinuz-2.4.19-ltsp-1";
> }
> }
>
>---------------------------------------------------------------------------------------------------------------
>
> Any thoughts on what might be wrong? I would appreciate any help you could
> give me.
>
> Gary Jaffe
> [EMAIL PROTECTED]
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> _____________________________________________________________________
> Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
> https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help, try #ltsp channel on irc.freenode.net
>
--
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
