Bug#921737: iproute2: `ip route get` problems with 0.0.0.0 and ::

2019-02-14 Thread Clément Hertling (Wxcafé)
Ah, another thing. The behavior that ip route get shows right now is also incorrect in the following way: ``` $ ip route show # [...] 192.168.1.0/24 dev enp0s31f6 proto kernel scope link src 192.168.1.156 metric 100 # [...] $ ip route get 192.168.1.22/28 192.168.1.22 dev enp0s31f6 src

Bug#921737: iproute2: `ip route get` problems with 0.0.0.0 and ::

2019-02-13 Thread Luca Boccassi
On Tue, 2019-02-12 at 17:15 +, Clément Hertling (Wxcafé) wrote: > Hey, > > February 11, 2019 6:27 PM, "Luca Boccassi" wrote: > > > On Fri, 2019-02-08 at 11:55 -0500, Clément 'wxcafé' Hertling wrote: > > > > > Package: iproute2 > > > Version: 4.20.0-2 > > > Severity: normal > > > Tags: ipv6

Bug#921737: iproute2: `ip route get` problems with 0.0.0.0 and ::

2019-02-11 Thread Luca Boccassi
On Fri, 2019-02-08 at 11:55 -0500, Clément 'wxcafé' Hertling wrote: > Package: iproute2 > Version: 4.20.0-2 > Severity: normal > Tags: ipv6 upstream > > > When using `ip route get` with 0.0.0.0 or ::, iproute2 shows multiple > incorrect behaviors: > > - `ip route get 0.0.0.0/0` answers "need at

Bug#921737: iproute2: `ip route get` problems with 0.0.0.0 and ::

2019-02-08 Thread Clément 'wxcafé' Hertling
Package: iproute2 Version: 4.20.0-2 Severity: normal Tags: ipv6 upstream When using `ip route get` with 0.0.0.0 or ::, iproute2 shows multiple incorrect behaviors: - `ip route get 0.0.0.0/0` answers "need at least a destination address", where it should answer with the default route.