Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 11 Jul 2013 12:42:32 +0100
From:      krad <kraduk@gmail.com>
To:        s m <sam.gh1986@gmail.com>
Cc:        Eugene <genie@geniechka.ru>, freebsd-questions <freebsd-questions@freebsd.org>
Subject:   Re: prevent ip conflict in dhcp client
Message-ID:  <CALfReydcQFAQFZDVQ7%2B2agsgptxFBS-Rn=2h%2B-94TY2NpMBe=g@mail.gmail.com>
In-Reply-To: <CAA_1SgEam=w6EBaD9ptzfhOtBaL2O93TtVcxHJREFCgynZQNRA@mail.gmail.com>
References:  <CAA_1SgGF%2B%2BHdoe-8Yk0NARO9ifswiXiK7ryOa5AC3GrEXK1VEQ@mail.gmail.com> <6586E17B555D489B83285236A5C95139@geniepc2011> <CAA_1SgEam=w6EBaD9ptzfhOtBaL2O93TtVcxHJREFCgynZQNRA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
alter the pool rand on the network to use say, x.x.x.1-199 on a /24, and
then allocate your statics >200 but <= 254 or add something similar to your
isc-dhcp config

host host.intranet {
  hardware ethernet c8:60:33:1d:f3:57;
  fixed-address 192.168.210.81;
  option host-name "host.intranet";
 }

Alternatively use ipv6 as the automatic ip address configuration tests
exactly like you commented on


On 11 July 2013 12:18, s m <sam.gh1986@gmail.com> wrote:

> thanks Eugene,
> you're right but i forgot to say that my client acts like a router. i mean
> none of interfaces should have ip address in same range (this is conflict
> for me). i can manage each interface to get ip address from DHCP or
> manually. so one interface may get ip address from dhcp server whereas all
> others have ip addresses which are set manually.
> for this situation, do you have any ideas to avoid ip conflict?
> thanks again for your attention
> SAM
>
>
> On Thu, Jul 11, 2013 at 3:06 PM, Eugene <genie@geniechka.ru> wrote:
>
> > Hi Sam,
> >
> > Actually I think this is wrong approach. Correctly configured networks
> > should be consistent and should not need such 'fixes'. Also you should
> > observe the IP provided by upstream DHCP server otherwise it is an
> > invitation for trouble (both technical and possibly legal).
> > Are the 'other' interfaces in your internal networks? Then you should
> > change them to use different address block from that used in your
> > provider's network (there are many address blocks for private networks).
> > And/or you should talk to your admin and discuss the address policy,
> maybe
> > they can give you a fixed address.
> >
> > Best wishes
> > Eugene
> >
> >
> > -----Original Message----- From: s m
> > Sent: Thursday, July 11, 2013 2:19 PM
> > To: freebsd-questions
> > Subject: prevent ip conflict in dhcp client
> >
> >
> > hello all
> >
> > i have a question about dhcp client. i want to know if there is any way
> to
> > understand the ip address which is offered by server before it assigned
> to
> > the interface.
> > i have a freebsd system which one of its interfaces should get ip address
> > from dhcp server whereas other interfaces have ip addresses and their ip
> > address change many times. so i want to prevent ip conflict.  is there
> any
> > way to prevent ip conflict in this situation?
> > i think the best way is to know the ip address which is offered by dhcp
> > server before assigning it to interface  and check if it has conflict
> with
> > others or not. is it possible? if yes, how i can do this?
> >
> > any comments or hints are appreciated.
> > thanks in advance
> > SAM
> > ______________________________**_________________
> > freebsd-questions@freebsd.org mailing list
> > http://lists.freebsd.org/**mailman/listinfo/freebsd-**questions<;
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions>;
> > To unsubscribe, send any mail to "freebsd-questions-**
> > unsubscribe@freebsd.org <freebsd-questions-unsubscribe@freebsd.org>"
> >
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> freebsd-questions-unsubscribe@freebsd.org"
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALfReydcQFAQFZDVQ7%2B2agsgptxFBS-Rn=2h%2B-94TY2NpMBe=g>