lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <cec19c10a6a9a9817d19a2f4d97c24ac@4net.rs>
Date:   Sat, 19 Jan 2019 21:43:38 +0100
From:   Siniša Bandin <sinisa@...t.rs>
To:     netdev@...r.kernel.org
Subject: arp -a equivalent

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ