netdev - Unification of iproute2 "ip route show" v4 and v6 output

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: <20191102103616.GA4307@pi.h5.or.at>
Date:   Sat, 2 Nov 2019 11:36:16 +0100
From:   Ralph Aichinger <ra@...h5.or.at>
To:     netdev@...r.kernel.org
Subject: Unification of iproute2 "ip route show" v4 and v6 output

Hello!

I am basically doing what the Debian maintaner of iproute2 
suggested in Debian bug #535128,

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535128

i want to ask if there is any chance of getting IPv6 routes
(like addresses) from ip by default? 

I understand the dangers of breaking scripts relying on
"traditional" behaviour, on the other hand it seems that
iproute2 always prioritized "doing stuff right" vs. 
"doing it the traditional way". Maybe even some middle
ground (a config option?) would be possible?

TIA
/ralph
-- 
-----------------------------------------------------------------------------
                                                              https://aisg.at
                                                   ausserirdische sind gesund