Dear all,
Sorry I just understand discussions.apple.com and this site are different one.
I am working in Osaka then allow me to link my question to here:
http://discussions.apple.com/thread.jspa?threadID=2675605&tstart=15
If you have any idea on this matter, please kindly append to here.
Thank you very much in advance, comment in Japanese is also very welcome.
Cheers,
MacBook Pro, Mac OS X (10.6.5), This issue also happened on 10.5.6
> (2) DHCP server repeat log like this:
>
> Nov 25 15:15:22 newdhcp2 dhcpd: DHCPDISCOVER from mac:of:the:machine via eth1.CC
> Nov 25 15:15:22 newdhcp2 dhcpd: DHCPOFFER on AAA.BB.CC.205 to from mac:of:the:machine via eth1.CC
このログが繰り返し現れるのは、DHCPアドレス不足のためではないかと思います。要するに、あるマックは、今までのアドレスのリース時間が切れてしまったので、また同じアドレスを要求します。しかし、アドレス不足のためにそのアドレスは既に他のマシンに配布されているため配布できない、、、、元のマックはまた同じアドレスを要求する、、、の繰り返しです。可能なら、DHCPアドレスレンジを増やしてやれば解決するのではないかと思います。（権限がないとかで）、直接DHCPサーバのアドレスレンジを増やすことが出来ないなら、その部屋全体を別のルータ配下におくなどして、とにかく使えるアドレスを増やすことでしか解決できないと思います。
Dear はこさん
Thank you for your reply!
In fact, I also suspected that.
But when this issue happening this Monday, I was using "nmap -sP AAA.BBB.CC.110-255"
and monitoring how many dhcp clients every 10 minutes, the result is there were only less than 50 clients running.
In our DHCP server, range AAA.BBB.CC.1-109 are reserved for static ip. AAA.BBB.CC.110-255 are for dhcp client.
If the issue on Monday shared the same root cause with before,
"DHCPアドレス不足" should not be the reason of this problem.
Cheers,
> I was using "nmap -sP AAA.BBB.CC.110-255"
> and monitoring how many dhcp clients every 10 minutes, the result is there were only less than 50 clients running.
実際に使われているIPがDHCPアドレスレンジより少ないのに、アドレス不足になることはよくあります。（想像ですが）、パソコンやスマートフォンはユーザが気ままにオフにしたり、別の場所に移動したりします。しかし、DHCPサーバの方はユーザがIPを使わなくなったという情報が得られず、そのアドレスはリースタイムが完了するまで使われません。それでアドレス不足になるのかな、、、（他にも理由があるのかもしれません）。リースタイムを短くしてみるとどうですか？
でも、とにかく、私の経験では、このようなログになる時はアドレスを増やしてやれば解決します。でも既に相当アドレスレンジは大きいようですので、IPセグメントを増やす方がいいかもしれません。
同じセグメントにスマートフォンのユーザも相当いるようだと、アドレス不足はすぐ起こります。
I have some new information in this thread:
http://discussions.apple.com/thread.jspa?threadID=2675605&tstart=0
thank you.
I am very interested in this inconvenience.
I am going to prepare a new dhcp server for potentially large number of users, who are believed to use smart phones such as iPhone. I am going to set up short lease time (less than 20 min) for the dhcp server.
If you have correct remedy, please write here.
Thank you.
Dear はこさん、happy new year.
ご返信頂きまして有り難うございます
But looks when the problem happening, there was not so many
DHCP clients connected, also our DHCP server seems not so
busy all the time since we don't have too many DHCP clients.
In addition we don't have iPhone dhcp client which is connect to
this network segment directly although we have some user connecting
to this network segment via wireless router (the router itself connected
to the same network segment with fixed ip, in this network
segment aaa.bbb.ccc.1~110, we use fixed ip, from aaa.bbb.ccc.111~255,
it dhcp client ip range) So, I am a little bit worry about if you can simulate
my problem exactly...
Do you need my tcpdump output which was produced by James's
command when problem happening? (total 4MB, I did not hear from
James up to now and I don't know how to send such data to you if
you want to have a look).
Currently, the problem on the both Macs are no longer there, (problem
always can be recovered automatically within around 2~4 hours),
if you need me to to gather any other information or run any command
when problem happens next time in my environment, please kindly let me know.
One more information, as I wrote in my an another thread in
English apple forum, "update OS and all pathes to the latest can not
resolve this problem", this might be not so accurate. the whole story is:
In Jan.13 afternoon, we had two Mac met this issue at the same time,
one is Mac OS 10.5.x, one is 10.6.x, the 10.5.x one was fixed by
"update OS and all patches to the latest". in the 2nd day morning, when we
checking the 10.6.x Mac, we found it's OS and patches was alread "up to date",
thus we should say "update OS and all patches to the latest":
- might can fix this problem in 10.5.x
- but might not fix this problem in 10.6.x.
Sorry for long descrioption,
and please let me know if you need more information:)
Thanks and best wishes, Shaq.
Self-Assigned IP on Mac OS X
