From owner-freebsd-net@freebsd.org Tue Aug 28 23:51:05 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 88F51109AD62 for ; Tue, 28 Aug 2018 23:51:05 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0C69C73178; Tue, 28 Aug 2018 23:51:05 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-oi0-x22e.google.com with SMTP id c190-v6so6032270oig.6; Tue, 28 Aug 2018 16:51:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qjGKUp9rIkuJGFbZZSvMtDnwE23OeUpxZBtTZh3zsj8=; b=rrk9mMzUDmWu1PcBAQ8x9xV7rhswKJ/ec+YYM4cQuBCWsNeauAdSPqloZ0hi1pOwXc akHPlLQS57Vfsimn1XHhWN366gphmMAE4FzB3UCwehe8zuIPHAXZK3M5hKxpiQdkoLJy 8Hwuo6dxZwsvd4zaYejb8b34XfZCCR1KegB1ke6l8aE7a2NHFNu3+zSrJioaNpaIrHHi iMCenbechmTNOb+wAGOd6EIvR/A/AcfBFNwXbqtnYxV06BKSRDnmPlfngyUh/4/mODCV Gyb5L8mL+nnn4geWmKRzGZWkVUDsEqQGdgei04P6Wdt5bngmnTUc58xk6ngcopfVDZgg nX7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qjGKUp9rIkuJGFbZZSvMtDnwE23OeUpxZBtTZh3zsj8=; b=tzSbnUgTXLpEQ27SoQrZOQTk9zdObISPDrNEawDp8YgS3gse2V6a+QHQD7vgksK7TR dZD0AI1NK3yAzZO8h8UTxyp/d2NE8WcjTtBK7M+xF7CXmx03SyIXkWHRAPTF3xHZbTGO ORuVfANBWrRiBvdf6JQTc5pJgxwXmdnrLtGMcHjxkjEGQeWhFhG9TMXFYWaYoWdxvj5/ fjLdAGQ4ckUwJEn9QCao4G1wHLdMw7xcFDYzRRaoov2C6NZvxHIPEkFguxnM4YTx8Sag EECxPPjtuKHYZaOzemkm0lZmsc3D5YJymcphfJMTl6JnyKuYu4Llw515y1XA14iKYFjI BWkg== X-Gm-Message-State: APzg51CQk/R1CfZVmV9iYfm8wRUKe4/cRoXZwQ6oNMloQFlp8/uD6cap Q+JW6kA7Z913zBG872y+F9nUhZqNP/zlWgJR+Ok= X-Google-Smtp-Source: ANB0VdbWttI2Tkwy//4GdVaVzyyM+U/mqcm/JmfdK8eMzZ3SFoA4g79Ou7ZR9OFef2/VDLE7T4wj42oqHcZEFc9/jiY= X-Received: by 2002:aca:b789:: with SMTP id h131-v6mr376857oif.298.1535500264155; Tue, 28 Aug 2018 16:51:04 -0700 (PDT) MIME-Version: 1.0 References: <1535379569.2132387.1487489784.45227861@webmail.messagingengine.com> <20180827151302.GA10167@ox> <1535395530.234212.1487804896.64257978@webmail.messagingengine.com> <1535448912.3229649.1488521184.1EE83C33@webmail.messagingengine.com> <3bdfa15a-1b9f-e8cd-00a5-f5fdaaa5d15e@FreeBSD.org> <1535480853.1508751.1489107768.35E0F6F1@webmail.messagingengine.com> <72e8b5b8-631b-35b3-b378-804e69dd3250@FreeBSD.org> <1535484638.1530345.1489178328.3374515B@webmail.messagingengine.com> <32fc6737-87f8-7156-17f0-8e17b65a0812@FreeBSD.org> <1535487192.1547312.1489227960.14DA5D07@webmail.messagingengine.com> In-Reply-To: <1535487192.1547312.1489227960.14DA5D07@webmail.messagingengine.com> From: Kevin Oberman Date: Tue, 28 Aug 2018 16:50:47 -0700 Message-ID: Subject: Re: cxl nic not working after reboot To: marius.h@lden.org Cc: np@freebsd.org, freebsd-net Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Aug 2018 23:51:05 -0000 On Tue, Aug 28, 2018 at 1:14 PM Marius Halden wrote: > On Tue, Aug 28, 2018, at 21:34, Navdeep Parhar wrote: > > On 8/28/18 12:30 PM, Marius Halden wrote: > > > tx_frames does move, rx_frames is stuck at zero. The following > counters are non-zero and does increase when traffic is sent through the > interface, all other are stuck at zero: > > > > > > dev.cxl.0.stats.tx_frames_65_127: 26083 > > > dev.cxl.0.stats.tx_frames_64: 4084 > > > dev.cxl.0.stats.tx_mcast_frames: 26083 > > > dev.cxl.0.stats.tx_bcast_frames: 4084 > > > dev.cxl.0.stats.tx_frames: 30167 > > > dev.cxl.0.stats.tx_octets: 2608846 > > > > > > Anything else I should look at? > > > > > > > What is on the other side of the link? Look at the peer's rx stats and > > see if it received the frames that cxl0 claims it has transmitted or not. > > Our ISPs router is connected to the other side. Unfortunately I don't have > access to any of the counters, but from what I understood when originally > debugging this with our ISP they did not see any traffic. If needed I can > ask them to check the rx counters tomorrow. > > -- > Marius Halden > This looks a lot like either a routing or NDP issue with the adjacent router. Well, an NDP issue devolves to a routing issue. It also possible that RDP is an issue, but, if you can't ping the opposite end, that eliminates RDP. You might check for NDP traffic with tcpdump or wireshark when the connection is restored. If you are not IPv6 conversant, NDP is the IPv6 replacement for ARP and it's pretty obvious how this would impact your connectivity.