Re: 5.1 `ip route get addr/cidr` regression

2019-05-17 Thread Jason A. Donenfeld
On Fri, May 17, 2019 at 10:19 PM Jason A. Donenfeld wrote: > > On Fri, May 17, 2019 at 7:39 PM David Ahern wrote: > > Not sure why Jason is not seeing that. Really odd that he hits the error > > AND does not get a message back since it requires an updated ip command > > to set the strict checking

Re: 5.1 `ip route get addr/cidr` regression

2019-05-17 Thread Jason A. Donenfeld
On Fri, May 17, 2019 at 7:39 PM David Ahern wrote: > Not sure why Jason is not seeing that. Really odd that he hits the error > AND does not get a message back since it requires an updated ip command > to set the strict checking flag and that command understands extack. > Perhaps no libmnl? Right

Re: 5.1 `ip route get addr/cidr` regression

2019-05-17 Thread David Ahern
On 5/17/19 11:35 AM, Stephen Hemminger wrote: > On Fri, 17 May 2019 09:17:51 -0600 > David Ahern wrote: > >> On 5/17/19 4:22 AM, Jason A. Donenfeld wrote: >>> Hi, >>> >>> I'm back now and catching up with a lot of things. A few people have >>> mentioned to me that wg-quick(8), a bash script that

Re: 5.1 `ip route get addr/cidr` regression

2019-05-17 Thread David Ahern
On 5/17/19 11:35 AM, Stephen Hemminger wrote: > On Fri, 17 May 2019 09:17:51 -0600 > David Ahern wrote: > >> On 5/17/19 4:22 AM, Jason A. Donenfeld wrote: >>> Hi, >>> >>> I'm back now and catching up with a lot of things. A few people have >>> mentioned to me that wg-quick(8), a bash script that

Re: 5.1 `ip route get addr/cidr` regression

2019-05-17 Thread Stephen Hemminger
On Fri, 17 May 2019 09:17:51 -0600 David Ahern wrote: > On 5/17/19 4:22 AM, Jason A. Donenfeld wrote: > > Hi, > > > > I'm back now and catching up with a lot of things. A few people have > > mentioned to me that wg-quick(8), a bash script that makes a bunch of > > iproute2 invocations, appears t

Re: 5.1 `ip route get addr/cidr` regression

2019-05-17 Thread Jason A. Donenfeld
On Fri, May 17, 2019 at 5:21 PM David Ahern wrote: > > On 5/17/19 8:17 AM, Michal Kubecek wrote: > > AFAIK the purpose of 'ip route get' always was to let the user check > > the result of a route lookup, i.e. "what route would be used if I sent > > a packet to an address". To be honest I would hav

Re: 5.1 `ip route get addr/cidr` regression

2019-05-17 Thread David Ahern
On 5/17/19 8:17 AM, Michal Kubecek wrote: > AFAIK the purpose of 'ip route get' always was to let the user check > the result of a route lookup, i.e. "what route would be used if I sent > a packet to an address". To be honest I would have to check how exactly > was "ip route get /" implemented befo

Re: 5.1 `ip route get addr/cidr` regression

2019-05-17 Thread David Ahern
On 5/17/19 4:22 AM, Jason A. Donenfeld wrote: > Hi, > > I'm back now and catching up with a lot of things. A few people have > mentioned to me that wg-quick(8), a bash script that makes a bunch of > iproute2 invocations, appears to be broken on 5.1. I've distilled the > behavior change down to the

Re: 5.1 `ip route get addr/cidr` regression

2019-05-17 Thread Michal Kubecek
On Fri, May 17, 2019 at 12:22:41PM +0200, Jason A. Donenfeld wrote: > Hi, > > I'm back now and catching up with a lot of things. A few people have > mentioned to me that wg-quick(8), a bash script that makes a bunch of > iproute2 invocations, appears to be broken on 5.1. I've distilled the > behav