Topic: DHCP problem?

[JoshuaR]

Hi guys,
   I've searched around a bit but I can't figure out this problem (not that surprising--newbie).  Anyway, I have SME 7 set up as a private server & gateway.  My network works fine and all the workstations can access the net; the problem is that after a number of hours (I usually notice it overnight), my client machines cannot retrieve an IP via the DHCP.  They work at first though...  If I restart the server, then the client machines can acquire the IPs again and everything works fine.  I don't know what to do.  My first guess is something to do with DHCP lease, but I really don't know...

If anyone could help it'd be really appreciated.

[mmccarn]

Look at /var/log/dhcpd/current to see what is happening.

Look for some other device on the network running DHCP - a home router, a windows system with 'internet connection sharing' turned on, something like that -- most DHCP servers will turn themselves off if they sense another server on the same network segment.

[JoshuaR]

thanks mmccarn, I'll give that a try and see what goes

[TrevorB]

My network works fine and all the workstations can access the net; the problem is that after a number of hours (I usually notice it overnight), my client machines cannot retrieve an IP via the DHCP.  They work at first though...  If I restart the server, then the client machines can acquire the IPs again and everything works fine.

What contribs/other apps. have you loaded?

Also look at what is running (eg. top - and see if anything is taking a lot of cpu).

I have had problems when dhcpd keeps trying to reload and seemed to think that it had 0 allowed addresses - and just kept trying. Removed sme7admin and haven't had a problem since (not necessarily sme7admin's fault, but I haven't been able to track down what might have clashed....).

Good Luck
Trevor B

[JoshuaR]

What contribs/other apps. have you loaded?

None, just what installed default.

I looked up the DHCPD log and it at one point it says "network down" but I don't know what caused that...

Also DHCPCD doesn't start by default, but to be perfectly honest I don't know what it is , I just assumed it was some superfluous DHCP add-on.

I guess I'll have to look that up  

[TrevorB]

I looked up the DHCPD log and it at one point it says "network down" but I don't know what caused that...

Also DHCPCD doesn't start by default, but to be perfectly honest I don't know what it is , I just assumed it was some superfluous DHCP add-on.

dhcpcd is your server getting it's IP (will only be running if you selected 'Use DHCP <whatever>' when configuring your external network).

dhcpd is the dhcp daemon which supplies IP addresses to the workstations on your network. That's the log you need to be looking at...

Trevor B  

[JoshuaR]

dhcpd is the dhcp daemon which supplies IP addresses to the workstations on your network. That's the log you need to be looking at...

hmm, that's where i was looking.  The only thing that looked out of place was

2007-06-21 08:11:30.431303500 receive_packet failed on eth0: Network is down

I don't know how to isolate what caused that, but my network has been running all day no probs, so I'll see in the morning if it continues working...

[Stefano]

dhcpd is the dhcp daemon which supplies IP addresses to the workstations on your network. That's the log you need to be looking at...

hmm, that's where i was looking.  The only thing that looked out of place was

2007-06-21 08:11:30.431303500 receive_packet failed on eth0: Network is down

I don't know how to isolate what caused that, but my network has been running all day no probs, so I'll see in the morning if it continues working...

sounds like eth go to sleep mode..

my 2€c

Ciao

Stefano

[JoshuaR]

sounds like eth go to sleep mode

is that easy/possible to fix?