Tell Me About It!

This is so strange. I have now brought the exact thin client to my remote
subnet to do some logging. Remember that I am connected to the main network
via a VPN tunnel and that both networks have no issues with pinging each
other. The main office network is 10.0.1.x and the remote is 192.168.50.x. I
will include a tcpdump and my dhcpd.conf below for your enjoyment :) It
looks to me like the server is sending the first block and then something
goes wrong on the acknowledgement. There are no unusual log entries in
syslog or messages logfiles either. This seems more and more like a
networking issue rather than a tftp issue. Any help is appreciated as
always.

=== BEGIN TCPDUMP OF ANYTHING TO/FROM HOST 192.168.50.40 ===

07:14:10.590247 IP (tos 0x0, ttl  18, id 2, offset 0, flags [none], proto:
UDP (17), length: 65) 192.168.50.40.2070 > 10.0.1.4.69: [udp sum ok]  37 RRQ
"ltsp/i386/pxelinux.0" octet tsize 0
07:14:10.591507 IP (tos 0x0, ttl  64, id 14319, offset 0, flags [none],
proto: UDP (17), length: 42) 10.0.1.4.32800 > 192.168.50.40.2070: [udp sum
ok] UDP, length 14
07:14:10.696245 IP (tos 0x0, ttl  18, id 3, offset 0, flags [none], proto:
UDP (17), length: 45) 192.168.50.40.2070 > 10.0.1.4.32800: [udp sum ok] UDP,
length 17
07:14:10.704886 IP (tos 0x0, ttl  18, id 4, offset 0, flags [none], proto:
UDP (17), length: 70) 192.168.50.40.2071 > 10.0.1.4.69: [udp sum ok]  42 RRQ
"ltsp/i386/pxelinux.0" octet blksize 1456
07:14:10.705973 IP (tos 0x0, ttl  64, id 14320, offset 0, flags [none],
proto: UDP (17), length: 43) 10.0.1.4.32800 > 192.168.50.40.2071: [udp sum
ok] UDP, length 15
07:14:10.817519 IP (tos 0x0, ttl  18, id 5, offset 0, flags [none], proto:
UDP (17), length: 32) 192.168.50.40.2071 > 10.0.1.4.32800: [udp sum ok] UDP,
length 4
07:14:10.817708 IP (tos 0x0, ttl  64, id 14321, offset 0, flags [none],
proto: UDP (17), length: 1488) 10.0.1.4.32800 > 192.168.50.40.2071: UDP,
length 1460
07:14:11.821026 IP (tos 0x0, ttl  64, id 14322, offset 0, flags [none],
proto: UDP (17), length: 1488) 10.0.1.4.32800 > 192.168.50.40.2071: UDP,
length 1460
07:14:13.820957 IP (tos 0x0, ttl  64, id 14323, offset 0, flags [none],
proto: UDP (17), length: 1488) 10.0.1.4.32800 > 192.168.50.40.2071: UDP,
length 1460
07:14:17.820813 IP (tos 0x0, ttl  64, id 14324, offset 0, flags [none],
proto: UDP (17), length: 1488) 10.0.1.4.32800 > 192.168.50.40.2071: UDP,
length 1460
07:14:25.820555 IP (tos 0x0, ttl  64, id 14325, offset 0, flags [none],
proto: UDP (17), length: 1488) 10.0.1.4.32800 > 192.168.50.40.2071: UDP,
length 1460
07:14:41.820005 IP (tos 0x0, ttl  64, id 14326, offset 0, flags [none],
proto: UDP (17), length: 1488) 10.0.1.4.32800 > 192.168.50.40.2071: UDP,
length 1460
07:14:46.704245 IP (tos 0x0, ttl  18, id 6, offset 0, flags [none], proto:
UDP (17), length: 70) 192.168.50.40.2072 > 10.0.1.4.69: [udp sum ok]  42 ACK
block 0
07:15:58.662417 IP (tos 0x0, ttl  18, id 7, offset 0, flags [none], proto:
UDP (17), length: 70) 192.168.50.40.2073 > 10.0.1.4.69: [udp sum ok]  42 ACK
block 0

The boot never makes it past here

=== END DUMP ===

=== BEGIN dhcpd.conf ===

#
# Sample configuration file for ISC dhcpd for Debian
#
# $Id: dhcpd.conf,v 1.1.1.1 2002/05/21 00:07:44 peloy Exp $
#

# The ddns-updates-style parameter controls whether or not the server will
# attempt to do a DNS update when a lease is confirmed. We default to the
# behavior of the version 2 packages ('none', since DHCP v2 didn't
# have support for DDNS.)
ddns-update-style none;

# option definitions common to all supported networks...
option domain-name "ajwhome";
option domain-name-servers 10.0.1.10;

default-lease-time 600;
max-lease-time 7200;
allow booting;
allow bootp;

subnet 10.0.1.0 netmask 255.255.255.0 {
}

subnet 192.168.50.0 netmask 255.255.255.0 {
authoritative;
use-host-decl-names     on;
option log-servers      10.0.1.4;
option domain-name "ajwhome";
option domain-name-servers 10.0.1.10;
option routers 192.168.50.254;
option broadcast-address 192.168.50.255;
option root-path "/opt/ltsp/i386";

host ajwhmpc1 {
        hardware ethernet       00:07:e9:d0:93:18;
        fixed-address           192.168.50.35;
        next-server             10.0.1.4;
        filename "/ltsp/i386/pxelinux.0";
}

host thin1 {
        hardware ethernet       00:13:90:02:46:a4;
        fixed-address           192.168.50.40;
        next-server             10.0.1.4;
                filename "ltsp/i386/pxelinux.0";
}

host ajwlaptop {
        hardware ethernet       00:08:74:9f:f9:da;
        fixed-address           192.168.50.36;
}
}

=== END dhcpd.conf ===

 


Regards,
Aaron J. Wood
Sun Tire Services, Inc
904-693-0990

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steve
Cayford
Sent: Sunday, June 08, 2008 6:45 PM
To: ltsp-discuss@lists.sourceforge.net
Subject: Re: [Ltsp-discuss] PXE Boot over multiple Subnets using W2003 SBS
asDHCP Server

Okay, that shot down all my theories. I don't know where else to look at the
moment.

-Steve


Aaron J. Wood wrote:
> Steve,
> 
> I am writing this fast as I am running out the door. I booted a 
> windows machine on the remote subnet and was able to retrieve the 
> pxelinux.0 file from the windows machine via tftp. I ran the following
command and received:
> 
>  c:>tftp 10.0.1.4 get /ltsp/i386/linuxpxe.0 Transfer Successful: 13628 
> bytes in 4 seconds
> 
> So this means that tftp is working and not being blocked. This has got 
> to be something else. I will read your email in detail when I return 
> home and post any update.
> 
> Regards,
> Aaron J. Wood
> Sun Tire Services, Inc
> 904-693-0990
> 


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for just about anything Open
Source.
http://sourceforge.net/services/buy/index.php
_____________________________________________________________________
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
No virus found in this incoming message.
Checked by AVG. 
Version: 8.0.100 / Virus Database: 270.0.0/1490 - Release Date: 6/8/2008
5:32 PM


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_____________________________________________________________________
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

Reply via email to