From owner-freebsd-questions@FreeBSD.ORG Thu Jul 11 13:24:07 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 6773E442 for ; Thu, 11 Jul 2013 13:24:07 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-we0-x230.google.com (mail-we0-x230.google.com [IPv6:2a00:1450:400c:c03::230]) by mx1.freebsd.org (Postfix) with ESMTP id E2AA31CE0 for ; Thu, 11 Jul 2013 13:24:06 +0000 (UTC) Received: by mail-we0-f176.google.com with SMTP id t56so6825935wes.7 for ; Thu, 11 Jul 2013 06:24:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=yx2fMzSWTsUXR2XX80tm8scKJyQemX9UjyiOMt0G4tQ=; b=eWtq+TRq/eIWbn+8nJE+Pe8deETHVa9eFYDk1ZDWv3kfW/UdIoR/gFqHcmpIcPEpes sUFFY4RE/MTa39AH7UORYtyG30mcJq3sTKE+rihIeo14A+OGi2Y9HdqrdEn0pTTzpXAk 3H+O7CeAmMvtxtmCPZ3mruANtFEs0DaPTFCtiQH3kDXKT9z54WapJ6G68/6HLAMQjyxl 5N9nJtsRV57bor4YwwJK956ZsyWwIralJMJXNr1jqSBoHhI9NVpvWweK3G9jPpYf7tbD Ob9u/EUOFSXkLElmIx0iia8X+NyBZb23G5gNJLNfRd/CY9y34hdgfqQfF4TNp7wsOWEv Gerw== MIME-Version: 1.0 X-Received: by 10.180.21.143 with SMTP id v15mr7632305wie.53.1373549046060; Thu, 11 Jul 2013 06:24:06 -0700 (PDT) Received: by 10.216.68.137 with HTTP; Thu, 11 Jul 2013 06:24:05 -0700 (PDT) In-Reply-To: <51DEA945.6090706@fjl.co.uk> References: <6586E17B555D489B83285236A5C95139@geniepc2011> <51DEA945.6090706@fjl.co.uk> Date: Thu, 11 Jul 2013 14:24:05 +0100 Message-ID: Subject: Re: prevent ip conflict in dhcp client From: krad To: Frank Leonhardt Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jul 2013 13:24:07 -0000 what is normal though these days? A lot of the fibre vhdsl lines do use dhcp on the wan link in the uk as they are just presented as ethernet, whilst other providers pppoe. On 11 July 2013 13:47, Frank Leonhardt wrote: > This all sounds like a very strange thing to be doing! But I hate it when > people answer my questions with "Why would you want to do that", so I won't. > > Binding an IPv4 address using a MAC address, which is the answer to a lot > of DHCP problems. But your explanation "my client acts like a router" set > alarm bells ringing. What exactly are you trying to do, and are you aware > that routers aren't (normally) configured using DHCP? If you've got any > kind of normal Internet line it will receive it's IP address using LCP (the > NCP part, and the IPCP to be precise). Or at least, that's how I think it > normally works. > > Regards, Frank. > > > On 11/07/2013 12:43, krad wrote: > >> ops %s/rand/range/ >> >> >> On 11 July 2013 12:42, krad wrote: >> >> 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 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 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@freebsd.org mailing list >>>> http://lists.freebsd.org/**mailman/listinfo/freebsd-**questions >>>> To unsubscribe, send any mail to " >>>> 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 " >> > > ______________________________**_________________ > 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 " >