dhcp server?

[nonnormman]

I'm using a router for dhcp, but I want my dhcp server to assign a specific scope of ip address'. The router assigns 192.168.1.2-192.168.1.50 and I want the dhcp server to assign the range 192.168.1.53-192.168.1.80.

 

[nonnormman]

bump

 

[cleverhandle]

Originally posted by: nonnormman
I'm using a router for dhcp, but I want my dhcp server to assign a specific scope of ip address'. The router assigns 192.168.1.2-192.168.1.50 and I want the dhcp server to assign the range 192.168.1.53-192.168.1.80.

You almost certainly don't want this. You should only be running one DHCP server on a given broadcast segment, otherwise things get complicated. What are you trying to accomplish by splitting the DHCP service across machines? Why can't one machine do the work? There are conceivable situations where you might want more than one DHCP server on a segment, but they're rather unusual and it's not clear why you would want to do this.

Originally posted by: nonnormman
bump

Enough bumping already. Nothinman and I (and probably others) are clearly following this thread and trying to help you. This forum doesn't move that quickly, and we're not at your beck and call, so be patient.

 

[nonnormman]

Originally posted by: cleverhandle

Originally posted by: nonnormman
I'm using a router for dhcp, but I want my dhcp server to assign a specific scope of ip address'. The router assigns 192.168.1.2-192.168.1.50 and I want the dhcp server to assign the range 192.168.1.53-192.168.1.80.

You almost certainly don't want this. You should only be running one DHCP server on a given broadcast segment, otherwise things get complicated. What are you trying to accomplish by splitting the DHCP service across machines? Why can't one machine do the work? There are conceivable situations where you might want more than one DHCP server on a segment, but they're rather unusual and it's not clear why you would want to do this.

Originally posted by: nonnormman
bump

Enough bumping already. Nothinman and I (and probably others) are clearly following this thread and trying to help you. This forum doesn't move that quickly, and we're not at your beck and call, so be patient.

Sorry, I just wanted to make sure the thread would not disapear.

 

[Nothinman]

I'm using a router for dhcp, but I want my dhcp server to assign a specific scope of ip address'. The router assigns 192.168.1.2-192.168.1.50 and I want the dhcp server to assign the range 192.168.1.53-192.168.1.80.

As cleverhandle said, you don't want this. With this setup the best you can hope for is that you'll get lucky and have the right server answer the request first. DHCP is broadcast (mostly) so everyone on the segment sees the requests so every DHCP server will attempt to answer them and you might get lucky and get an address or you might get unlucky and get a DHCPNAK. Why are you attempting to split the range like that?

 

[nonnormman]

I still can't figure out why this thing won't start. When I check the syslog, all I see is local host repeated several times.

 

[cleverhandle]

I'm sure you would be making much more progress if you answer the question both Nothinman and I have already asked: Why do you want two DHCP servers on the same segment? It's highly likely that there's a much simpler method of accomplishing whatever it is you're trying to do, if you would tell us what that is.

If you're set on figuring things out yourself, that's fine. But why create a thread in the first place if you're not going to respond to what people are asking you?

 

[nonnormman]

Originally posted by: cleverhandle
I'm sure you would be making much more progress if you answer the question both Nothinman and I have already asked: Why do you want two DHCP servers on the same segment? It's highly likely that there's a much simpler method of accomplishing whatever it is you're trying to do, if you would tell us what that is.

If you're set on figuring things out yourself, that's fine. But why create a thread in the first place if you're not going to respond to what people are asking you?

All I'm trying to do is to get a linux dhcp server up and running for the experience. It doesn't matter whether it's the only dhcp server on the segment or not, I just want it to work.

 

[imported_Phil]

Originally posted by: nonnormman

Originally posted by: cleverhandle
I'm sure you would be making much more progress if you answer the question both Nothinman and I have already asked: Why do you want two DHCP servers on the same segment? It's highly likely that there's a much simpler method of accomplishing whatever it is you're trying to do, if you would tell us what that is.

If you're set on figuring things out yourself, that's fine. But why create a thread in the first place if you're not going to respond to what people are asking you?

All I'm trying to do is to get a linux dhcp server up and running for the experience. It doesn't matter whether it's the only dhcp server on the segment or not, I just want it to work.

Can you follow instructions? Turn off the other DHCP server.

 

[Nothinman]

I still can't figure out why this thing won't start. When I check the syslog, all I see is local host repeated several times.

Paste the syslog entries here. You could also try starting it with the -d flag (i.e. /usr/sbin/dhcpd3 -d eth1) and see what it says.

It doesn't matter whether it's the only dhcp server on the segment or not, I just want it to work.

Yes it does matter, if you have 2 on the same segment at best you'll have a 50/50 chance of either working properly.

 

[nonnormman]

Originally posted by: Nothinman

I still can't figure out why this thing won't start. When I check the syslog, all I see is local host repeated several times.

Paste the syslog entries here. You could also try starting it with the -d flag (i.e. /usr/sbin/dhcpd3 -d eth1) and see what it says.

It doesn't matter whether it's the only dhcp server on the segment or not, I just want it to work.

Yes it does matter, if you have 2 on the same segment at best you'll have a 50/50 chance of either working properly.

I typed /usr/sbin/dhcpd3 -d eth1 and I got "Not subnet declaration for eth1 (192.168.1.90).
** Ignoring requests on eth1. If this is not what you want, please write a subnet declaration in your dhcpd.conf file for the network segment to which interface eth1 is attached. ** Not configured to listen on any interfaces". Then I typed tail -50 /var/log/messages and got "Localhost Kernel: eth1: Setting full duplex based on M11 #1 link partner capability of 45e1".

 

[Nothinman]

The kernel messages should be irrelevant, it's just the driver coming up and negotiating the speed/duplex.

There's obviously something wrong with your config file, it might be time to just delete it, get the sample and start over.