Topic: DHCPD trouble shooting...

[cydonia]

Hi,

upon awaking this morning, am ethernet device on my network would not work.  It was not receiving an ip address from the dhcp server.

It was working last night, the only thing i changed since it was working was installing this contrib:

e-smith-squid-restrict-ip-0.1-1.noarch.rpm


How would i troubleshoot my dhcp server and find out the problem?  For now, i have just configured the device manually, but i want my dhcp back:).

Thanks

[mbachmann]

First remove the contirb and see if that's the reason, obviously.

[cydonia]

Yeh, done that, hasn't fixed anything...

perhaps cause removing the contrib wont modify the changes that the contrib made to iptables or perhaps dhcp for some reason.

Any ideas?

[cydonia]

Well... it seems something to do with my SME's DHCP is stuffed up...

I'm having to configure everything manually...

Will let you know if i work out how to solve this.

[cydonia]

well.  somehow my dhcp has been stuffed up totally, i'm not sure whats wrong.  'service dhcpd status' shows:

/service/dhcpd: up (pid 1698) 63841 seconds, normally down


I am considering just installing SME again... and thus, about a million additional contribs .


Any tips before I go for a reinstall?

[raem]

/sbin/e-smith/signal-event post-upgrade
/sbin/e-smith/signal-event reboot

[cydonia]

Thanks Ray, unfortunately it didn't fix the problem.  Is it possible that my DHCP is somehow ruined?

Looking at my logs, i have found the time when everything stopped working... but i'm not sure how to fix it...


2004-06-30 12:09:55.060606500 DHCPACK on 192.168.1.103 to 00:0b:82:00:ac:4f via eth0
2004-06-30 19:46:06.920710500 DHCPREQUEST for 192.168.1.101 from 00:0d:61:04:4e:7e via eth0
2004-06-30 19:46:07.156435500 DHCPACK on 192.168.1.101 to 00:0d:61:04:4e:7e via eth0
2004-06-30 20:13:08.477999500 DHCPREQUEST for 192.168.1.100 from 00:e0:18:e6:3a:d2 via eth0
2004-06-30 20:13:08.559486500 DHCPACK on 192.168.1.100 to 00:e0:18:e6:3a:d2 via eth0
2004-06-30 22:52:37.194561500 Internet Software Consortium DHCP Server 2.0pl5
2004-06-30 22:52:37.194573500 Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
2004-06-30 22:52:37.194581500 All rights reserved.
2004-06-30 22:52:37.194586500
2004-06-30 22:52:37.194589500 Please contribute if you find this software useful.
2004-06-30 22:52:37.194586500
2004-06-30 22:52:37.194595500 For info, please visit http://www.isc.org/dhcp-contrib.html
2004-06-30 22:52:37.194602500
2004-06-30 22:52:37.486950500 Listening on Socket/eth0/192.168.1.0
2004-06-30 22:52:37.486961500 Sending on   Socket/eth0/192.168.1.0
2004-07-01 00:36:48.446003500 DHCPREQUEST for 192.168.1.103 from 00:0b:82:00:ac:4f via eth0
2004-07-01 00:36:48.446016500 Ignoring unknown client 00:0b:82:00:ac:4f



Thats obviously cause its not in leases, but i thought when a client is first discovered, that DHCP adds it and allows it automatically?


Any ideas?

Thanks.

[cydonia]

Ok, i have a temporary solution, but i'm not sure if its a security risk.

I uncommented the line in DenyUnknownHost so that it will not deny unknowns.  Is this a major security flaw?

Or is this perhaps what got changed somehow?

[mbachmann]

Isn't the "DenyUnknownHost" an option, which a contrib provides? I suggest you uninstalled/reinstalled? Why not ask the builder of the contrib (which is Muzo or Master Sleepy?). Cannot help dhcp-wise, i always use fixed adresses.