urgent! dhcpd

why the hell is my dhcpd assigning ips from old ip range!!! how do I reset
this thing to assign only new ips as they are written in dhcpd.conf!?

"Damir Galiè" schrieb
> why the hell is my dhcpd assigning ips from old ip
> range!!! how do I reset this thing to assign only
> new ips as they are written in dhcpd.conf!?
>
restart your dhcpd?

# rcdhcpd restart
or
# kill -SIGHUP `pidof dhcpd`
or
something similar according to the instructions of
your distribution?

HTH
Martin

I tried to restart dhcpd, erase lease file, which is empty, tried to reboot.
strange but dhcpd is always giving me the same ip, which is from the old
range. what could be wrong? for example I am getting ip 192.168.0.193. but
that's not in config!!! so strange.

"Martin Blume" <(E-Mail Removed)> wrote in message
news:4310943a$0$1154$(E-Mail Removed)...
> "Damir Galiè" schrieb
>> why the hell is my dhcpd assigning ips from old ip
>> range!!! how do I reset this thing to assign only
>> new ips as they are written in dhcpd.conf!?
>>
> restart your dhcpd?
>
> # rcdhcpd restart
> or
> # kill -SIGHUP `pidof dhcpd`
> or
> something similar according to the instructions of
> your distribution?
>
> HTH
> Martin
>
>
>

ok strange. I removed authoritative; and I got the new ip.

Damir Galic wrote:

> I tried to restart dhcpd, erase lease file, which is empty, tried to
> reboot. strange but dhcpd is always giving me the same ip, which is from
> the old range. what could be wrong? for example I am getting ip
> 192.168.0.193. but that's not in config!!! so strange.
>
The client, as his lease hasn't yet expired, probably re-requests his old
address.

--
Longhorn error#4711: TCPA / NGSCP VIOLATION: Microsoft optical mouse
detected penguin patterns on mousepad. Partition scan in progress
*to*remove*offending*incompatible*products.**Reactivate*MS*software.
Linux woodpecker.homnet.at 2.6.12-mm2[LinuxCounter#295241,ICQ#4918962]

Walter Mautner wrote:
> The client, as his lease hasn't yet expired, probably re-requests his old
> address.

That would have been my guess. I am quite surprised the request got
honoured though. Its not impossible that the client just carried on
using it.

ok this is becomming really annoying. it worked on my pc after removing
authoritative and after disabling nic in windows, but now I am seeing this
for other pc:
Aug 28 10:32:09 skum dhcpd: DHCPREQUEST for 192.168.0.194 from
00:10:a4:e3:ca:28 via eth1: unknown lease 192.168.0.194.
Aug 28 10:32:12 skum dhcpd: DHCPREQUEST for 192.168.0.194 from
00:10:a4:e3:ca:28 via eth1: unknown lease 192.168.0.194.

so is the problem on client's side or the server? why the heck doesn't it
give ip from the ip range?


<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> Walter Mautner wrote:
>> The client, as his lease hasn't yet expired, probably re-requests his old
>> address.
>
> That would have been my guess. I am quite surprised the request got
> honoured though. Its not impossible that the client just carried on
> using it.
>

Damir Galic wrote:
> ok this is becomming really annoying. it worked on my pc after removing
> authoritative and after disabling nic in windows, but now I am seeing this
> for other pc:
> Aug 28 10:32:09 skum dhcpd: DHCPREQUEST for 192.168.0.194 from
> 00:10:a4:e3:ca:28 via eth1: unknown lease 192.168.0.194.
> Aug 28 10:32:12 skum dhcpd: DHCPREQUEST for 192.168.0.194 from
> 00:10:a4:e3:ca:28 via eth1: unknown lease 192.168.0.194.

The dhcpd client on your workstation is asking for a specific address.
You need to tell it to request a fresh one. Try logging onto the
workstation as root and enterting dhclient -r or deleting the contents
of dhclient.leases