From owner-freebsd-net@FreeBSD.ORG Wed Apr 17 12:46:43 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C5A57F0 for ; Wed, 17 Apr 2013 12:46:43 +0000 (UTC) (envelope-from jmojica@gmail.com) Received: from mail-we0-x233.google.com (mail-we0-x233.google.com [IPv6:2a00:1450:400c:c03::233]) by mx1.freebsd.org (Postfix) with ESMTP id 68E666CF for ; Wed, 17 Apr 2013 12:46:43 +0000 (UTC) Received: by mail-we0-f179.google.com with SMTP id p43so1195434wea.10 for ; Wed, 17 Apr 2013 05:46:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=uOQkWrDQwGAYqvRbXn40uOLUi6BgAHAnwFSGbYpHUhM=; b=iqHA/MC2p2LDoTEhtOMGpV3z5XXjI6voGQLpBanZ0XB7Xc7j6YKauRDM42NqHtZ/8K 68GreaShEyDk1FviRTAJncyWUskbzT2Q462L9T/uhPHdBIBPUTwo8dRCL3Tr1P6cDl/L UqiXAfj8EVupkq5wTOa4F36ZDTOvs1YgTrAMgrqqy6fSTSQ+aHXz50ujNpl8jUTuYxXu ais7gcue7/9wO/ex5ahdnEfl/g2G1ZmgvDXKB9qhKq8WpNHg8I/xOm0Nkk/+0aptEQK0 kOEk4WyVOveRU22ciQ9FlUVe5kw+zkji8zIykoeMq1um8t609iCAln+7Siab8JDia/nB xwGA== MIME-Version: 1.0 X-Received: by 10.194.23.105 with SMTP id l9mr4343729wjf.41.1366202802566; Wed, 17 Apr 2013 05:46:42 -0700 (PDT) Received: by 10.194.122.73 with HTTP; Wed, 17 Apr 2013 05:46:42 -0700 (PDT) Date: Wed, 17 Apr 2013 08:46:42 -0400 Message-ID: Subject: ARP: Error Message in if_ether.c "arprequest: cannot find matching address" From: Juan Mojica To: FreeBSD Net Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Apr 2013 12:46:43 -0000 We manage to hit the following message with some regularity. arprequest: cannot find matching address The code shows a printf: printf("%s: cannot find matching address\n", __func__); Any reason this is a printf and not a log(LOG_ERR, The only things I can come up with are: a) it is a really severe and should be printed out, which if that is the case why isn't there an assert there? b) whoops, that should probably be a log(LOG_ERR, On our end we need to figure out exactly why we're intermittently hitting this patch of code. Thanks, -- Juan Mojica Email: jmojica@gmail.com