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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 24 Sep 2020 10:15:59 -0600
From:   David Ahern <dsahern@...il.com>
To:     "Brian J. Murrell" <brian@...erlinx.bc.ca>, netdev@...r.kernel.org
Subject: Re: RTNETLINK answers: Permission denied

On 9/24/20 5:09 AM, Brian J. Murrell wrote:
> On Tue, 2020-09-22 at 15:04 -0400, Brian J. Murrell wrote:
>> What are the possible causes of:
>>
>> # ip route get 2001:4860:4860::8844
>> RTNETLINK answers: Permission denied
>>
>> when
>>
>> # ip route get fd31:aeb1:48df::99
>> fd31:aeb1:48df::99 from :: dev br-lan proto static src
>> fd31:aeb1:48df::1 metric 1024 pref medium
>>
>> works just fine?
>>
>> Using iproute2 5.0.0.
> 
> No-one with any thoughts on this?  Is there a better place I should be
> asking?
> 

check your routes for a prohibit entry:

$ sudo ip -6 ro add prohibit 2001:4860:4860::8844

$ ip -6 ro ls
::1 dev lo proto kernel metric 256 pref medium
prohibit 2001:4860:4860::8844 dev lo metric 1024 pref medium
...

$ ip -6 ro get 2001:4860:4860::8844
RTNETLINK answers: Permission denied

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ