The rules for the firewall is to allow all connections for machines on my LAN. I also opened up a web server port and email to everyone.
These rules work for one of my machines. However, the machine which has the Network card that I got from DisklessWS no longer works. The system tries to find the DHCP server but it just goes into <sleep> mode and never moves past this first step. I am not sure how DisklessWS loaded my network card but this is the second card I bought from them which has had some strange behavior. In fact, the machine that now works, I had to pull out a DisklessWS card and put back in my floppy drive and boot off the disk because the card behaved strangely. I am tempted to remove the DisklessWS card and reinstall my floppy in my other machine but I would really rather not do that.
My firewall catches the request from the machine that is not booting - it says
PORT = 67
SENT FROM = 0.0.0.0
SERVICE = bootps
I have tried several things (like explicitly allowing connections from 0.0.0.0 or putting in a specific rule to open up PORT 67 to all machines) however to no avail.
The message file from /var/log directory has the following line:
MAC=ff:ff:ff:ff:ff:ff:00:50:ba:2f:ca:2c:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=576 TOS=0x00 PREC=0x00 TTL=60 ID=0 PROTO=UDP SPT=68 DPT=67 LEN=556
The next two lines are from successful calls from my other client.
Mar 1 13:12:18 prhplinux dhcpd: DHCPDISCOVER from 00:00:c0:58:75:8a via eth0
Mar 1 13:12:18 prhplinux dhcpd: DHCPOFFER on 192.33.61.4 to 00:00:c0:58:75:8a via eth0
From the looks of it the server does not seem to recognize the request fromthe first client as a DHCPDISCOVER.
My dhcpd.conf file is as follows ( the prlinux machine is the one not working):
default-lease-time 21600; max-lease-time 21600;
option subnet-mask 255.255.255.0; option broadcast-address 192.33.61.255; option routers 192.33.61.2; option domain-name-servers 192.33.61.1; option domain-name "res.com"; option root-path "192.33.61.1:/opt/ltsp/i386";
shared-network WORKSTATIONS {
subnet 192.33.61.0 netmask 255.255.255.0 {
range 192.33.61.7 192.33.61.50;
option broadcast-address 192.33.61.255;
}
}group {
use-host-decl-names on;
# option log-servers 192.33.61.254;host prlinux {
hardware ethernet 00:50:BA:2F:CA:2C;
fixed-address 192.33.61.3;
filename "lts/vmlinuz-2.4.19-ltsp-1";
# filename "lts/vmlinuz-2.4.18";
option option-128 e4:45:74:68:00:00; #This is NOT a MAC address
option option-129 "NIC=ne IRQ=5 IO=0x300";
}
host prlinux1 {
# hardware ethernet 00:04:5A:85:37:11;
hardware ethernet 00:00:C0:58:75:8A;
fixed-address 192.33.61.4;
filename "lts/vmlinuz-2.4.19-ltsp-1";
# filename "lts/vmlinuz-2.4.18";
option option-128 e4:45:74:68:00:00; #This is NOT a MAC address
option option-129 "NIC=wd IRQ=10 IO=0x300";
}
Any help on this problem would be greatly appreciated.
Peter
[EMAIL PROTECTED]
_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _____________________________________________________________________ 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
