From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 30BDBC61CE4 for ; Sat, 19 Jan 2019 20:43:51 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id C444A2086A for ; Sat, 19 Jan 2019 20:43:50 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=4net.rs header.i=@4net.rs header.b="B5NTsq/3" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729741AbfASUnq (ORCPT ); Sat, 19 Jan 2019 15:43:46 -0500 Received: from amazon.4net.rs ([159.69.148.70]:45776 "EHLO amazon.4net.rs" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729695AbfASUnl (ORCPT ); Sat, 19 Jan 2019 15:43:41 -0500 Received: from localhost (amazon.4net.co.rs [127.0.0.1]) by amazon.4net.rs (Postfix) with ESMTP id 7403663BE0E3 for ; Sat, 19 Jan 2019 21:42:36 +0100 (CET) X-Virus-Scanned: amavisd-new at 4net.rs Received: from amazon.4net.rs ([127.0.0.1]) by localhost (amazon.dyn.4net.co.rs [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O3TkUcvSvdtp for ; Sat, 19 Jan 2019 21:42:36 +0100 (CET) Received: from mail.4net.rs (green.4net.rs [10.188.221.8]) by amazon.4net.rs (Postfix) with ESMTP id EDA4663BE0E2 for ; Sat, 19 Jan 2019 21:42:35 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mail.4net.rs (Postfix) with ESMTP id 2B681CB7C7001 for ; Sat, 19 Jan 2019 21:43:39 +0100 (CET) X-Virus-Scanned: amavisd-new at 4net.rs Received: from mail.4net.rs ([127.0.0.1]) by localhost (green.4net.rs [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0d5MNgpWtiQG for ; Sat, 19 Jan 2019 21:43:39 +0100 (CET) Received: from mail.4net.rs (localhost [127.0.0.1]) by mail.4net.rs (Postfix) with ESMTP id C4DC6CB8D2027 for ; Sat, 19 Jan 2019 21:43:38 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=4net.rs; h=mime-version :content-type:content-transfer-encoding:date:from:to:subject :message-id; s=4netrs; bh=gBRuSe4Ao7eq35/qVwUNwH9VnZw=; b=B5NTsq /3D5CyEcBulDNm9OKVZF621307L3Oy3ZE0zhI1bb0ZmGjqnU6XMTjFVmR4NkQ8la 1NO26r/7nkwqzN7/KMz3ze44wz7fEoQBN+wHXl8KFjkMFvO4hBYzYq2Vl0sP9gfR qj4PaoRc3R50qaBWXfJ+A26iqkiEnMwNMY1Nc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=4net.rs; h=mime-version :content-type:content-transfer-encoding:date:from:to:subject :message-id; q=dns; s=4netrs; b=Rfm2DBsVVh67RAPXKgB5+ggr4GKZB4rn 3pUTLzLx+4gfRj2KNQIogUKww3WBClnzddWepMubhS0NV92gXjZve9BijaTv2G9i MVIqDBTNeIzpp9mmgkpMBAocWY4zXRilM1pLGBjFm0pG/95HFOV2KBdlC3mvuwKs tEXotI7R9fg= Received: from 4net.co.rs (localhost [127.0.0.1]) by mail.4net.rs (Postfix) with ESMTPSA id 8AA2ECB7C7001 for ; Sat, 19 Jan 2019 21:43:38 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Sat, 19 Jan 2019 21:43:38 +0100 From: =?UTF-8?Q?Sini=C5=A1a_Bandin?= To: netdev@vger.kernel.org Subject: arp -a equivalent User-Agent: Roundcube Webmail/1.4-beta Message-ID: X-Sender: sinisa@4net.rs Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Hello! There is one thing I am missing from old "arp" command: "arp -a" used to give both symbolic name and numeric address (if resolver is working, of course). Now, with "ip neigh" I can get only one at the time, so I have to issue two commands if I want to check if for eg. a host is alive and I don't know it's IP address (issued by DHCP), but it's name is registered in (dynamic) DNS. First "ip -r neigh" to see what is the hostname (I don't like to remember 100's of hostnames, it's easier to ask Linux for a list), then ping/dig/whatever to resolve that name to IP... Example output: Good # arp -a name.domain.tld (192.168.188.34) at aa:bb:cc:dd:ee:f1 [ether] on wlan0 Not so good # ip neigh 192.168.188.34 dev wlan0 lladdr aa:bb:cc:dd:ee:f1 REACHABLE # ip -r neigh name.domain.tld dev wlan0 lladdr aa:bb:cc:dd:ee:f1 REACHABLE I would expect "ip -a neigh" to behave just like "arp -a", but would be happy with any way to have names and addresses listed together (new option, combination of options, ...) Is there any way this could be implemented? Thank you! -- Srdačan pozdrav/Best regards, Siniša Bandin