Hi All,
I COULD FIX this problem with the following solution,
I could distinguish the IP conflict in the network by using following
command in dhclient-script. We need to install “arping” debian package for
this.
*arping -d -I eth0 -c 3 {IP address got from DHCP server} >/dev/null; echo
$?*
*T
sathya sai put forth on 12/22/2009 3:17 AM:
> Hi Stan,
>
> I have already thought about this. But the problem here is, we dont have
> a control over neither over our DHCP server nor the system which
> statically configures the IP address in our subnet. I hope that, this
> true even with the real
Hi Stan,
I have already thought about this. But the problem here is, we dont have a
control over neither over our DHCP server nor the system which statically
configures the IP address in our subnet. I hope that, this true even with
the real time deployment scenario.
So, to overcome I will that it
sathya sai put forth on 12/22/2009 12:26 AM:
> *I could also see that, our debian dhclient presently DOES NOT HAVE AN
> OPTION TO IMPLICITLY SUPPORT THIS.*
>
> But as per RFC 2131, the client should perform a final check to detect
> the IP conflict and send DHCPDECLINE message. Please find the
Hi All,
This is Sathya, a debian etch user who uses dhclient package to configure
the IP address.
Firstly, I would like to give my heartily thanks to you all for your great
dedicated contribution towards this package. As I am newbie to this mailing
list, I am not aware on where to post this quer
Hi All,
This is Sathya, a debian etch user who uses dhclient package to configure
the IP address.
Firstly, I would like to give my heartily thanks to you all for your great
dedicated contribution towards this package. As I am newbie to this mailing
list, I am not aware on where to post this query
6 matches
Mail list logo
