Do you have a firewall in between the LTSP clients and the server? Opening up TFTP in the firewall (or local IPTables config) doesn't seem to let PXE requests through. Opening up PXE also doesn't seem to. There's some high port requests early on that need to get through.

Drop your firewall and see if it works. Also check your hosts.allow and hosts.deny files to see if the IP range of your clients is allowed to connect to bootp and TFTP.



On Feb 11, 2004, at 7:59 AM, Tom Allison wrote:

Hello,

I'm trying to get ltsp v4.0 set up on my SuSE box.
I've installed tftp and not SuSE's advanced tftp package.
This is a PXE boot configuration.

ltsp server ip: 192.168.1.10
tftp server ip: 192.168.1.10
dhcp server ip: 192.168.1.1

DHCP configuration file entry:

subnet 192.168.1.0 netmask 255.255.255.0
{
        option subnet-mask 255.255.255.0;
        option domain-name "home.tacocat.net";
        option routers 192.168.1.1;
        option domain-name-servers 192.168.1.1;
        range dynamic-bootp 192.168.1.2 192.168.1.200;
        default-lease-time 3600;
        max-lease-time 7200;
        option root-path "192.168.1.10:/opt/ltsp/i386";
}

host loki
{
        hardware ethernet 00:0D:61:37:36:30;
        fixed-address 192.168.1.10;
}

group {
        use-host-decl-names     on;
        next-server             192.168.1.10;
        option log-servers      192.168.1.1;

host ws001 {
hardware ethernet 00:d0:59:39:a8:a1;
fixed-address 192.168.1.201;
filename "/lts/2.4.24-ltsp-1/pxelinux.0";
}
}


From a non-ltsp machine, I can use tftp to get /lts/2.4.24-ltsp-1/pxelinux.o repeatedly.
From this I conclude that the basics of tftp work.
I also see DHCP requests/acks going back and forth to the LTSP client



Here is what I see on the client


DHCP MAC ADDR: 00 D0 59 38 A7 A1
DHCP...
CLIENT IP: 192.168.1.201  MASK:255.255.255.0  DHCP IP: 192.168.1.1
GATEWAY IP: 192.168.1.1
TFTP.......
PXE-E32: TFTP open timeout
TFTP...
PXE-E32: TFTP open timeout
TFTP...
PXE-E32: TFTP open timeout
TFTP...

and then it gives up.

I'm kind of at a loss because I'm at least able to see the DHCP working correctly with regard to the IP assignment. However, I checked the /var/log/xinetd.log entry and cannot find an entry to show attempted access from 192.168.1.201. However, my successfuly download of the pxe kernel from my other linux box does show up on the xinetd.log entries.



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_____________________________________________________________________
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



------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _____________________________________________________________________ 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