Re: [dhcwg] DHCP Process Time
Karl Auer <kauer@biplane.com.au> Wed, 28 September 2016 08:30 UTC
Return-Path: <kauer@biplane.com.au>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6287912B463 for <dhcwg@ietfa.amsl.com>; Wed, 28 Sep 2016 01:30:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level:
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BiGbM4ia6uFt for <dhcwg@ietfa.amsl.com>; Wed, 28 Sep 2016 01:30:05 -0700 (PDT)
Received: from ipmail07.adl2.internode.on.net (ipmail07.adl2.internode.on.net [150.101.137.131]) by ietfa.amsl.com (Postfix) with ESMTP id E5A4112B4D2 for <dhcwg@ietf.org>; Wed, 28 Sep 2016 01:30:04 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2ChAQAif+tX/7t/ZZYNTx0BBQELAYM/AQEBAQF1dga2PoQVIIV+AoIqAQIBAQEBAQKFZwEBBCNmCxgCAiYCAlcZiFawb2eNBgEBCAIlgQaFMYRUhC5igjiCWgWZdlOFVIwAjTCIXheDd4N9hW9ghwcBAQE
Received: from eth4284.nsw.adsl.internode.on.net (HELO [192.168.1.142]) ([150.101.127.187]) by ipmail07.adl2.internode.on.net with ESMTP; 28 Sep 2016 18:00:02 +0930
Message-ID: <1475051400.2256.62.camel@biplane.com.au>
From: Karl Auer <kauer@biplane.com.au>
To: dhcwg@ietf.org
Date: Wed, 28 Sep 2016 18:30:00 +1000
In-Reply-To: <CAMpwFvo-J1CMVvDK16L034dPquqBeKq=5LAMgw0ZNCrF8pQMzQ@mail.gmail.com>
References: <CAMpwFvo-J1CMVvDK16L034dPquqBeKq=5LAMgw0ZNCrF8pQMzQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.18.5.2-0ubuntu3
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/rV3SioOosmiAhiOfrWVeDL7UPiM>
Subject: Re: [dhcwg] DHCP Process Time
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Sep 2016 08:30:08 -0000
On Wed, 2016-09-28 at 15:18 +0700, Hans Christian Silaban wrote: > I'm doing a research about DHCP option. I wan't to analyze the DHCP > process time before and after implement the option. Is there any > standard that for the DHCP process time? I mean from the DHCP > DISCOVER until DHCP ACK. Not quite sure what you mean, but there would seem to be four obvious methods to look at the protocol and compare before and after: 1: Turn on verbose logging on whatever server you are using and inspect the logs 2: Run Wireshark on the client and inspect the traffic in real time 3: Capture the traffic on the client or the server using eg tcpdump, then inspect it later in Wireshark 4: Tap a suitable switch port and capture or inspect traffic to/from the server. Wireshark will be able to decode your DHCP options for you. It has an extensive set of decodes for standard and well-known options. If you are using something special, you may need to get comfy with hex or write a decode for your special option. Regards, K. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Karl Auer (kauer@biplane.com.au) http://www.biplane.com.au/kauer http://twitter.com/kauer389 GPG fingerprint: E00D 64ED 9C6A 8605 21E0 0ED0 EE64 2BEE CBCB C38B Old fingerprint: 3C41 82BE A9E7 99A1 B931 5AE7 7638 0147 2C3C 2AC4
- [dhcwg] DHCP Process Time Hans Christian Silaban
- Re: [dhcwg] DHCP Process Time Karl Auer
- Re: [dhcwg] DHCP Process Time Simon Hobson
- Re: [dhcwg] DHCP Process Time Karl Auer
- Re: [dhcwg] DHCP Process Time sthaug